kaede15 Posted June 2, 2016 Share #1 Posted June 2, 2016 (edited) Hi I tried to installed in my Win10 Ent in Hyper V but got stucked in the synology assistant... apparently it can detect the recent installed DSM. Config: Hyper V, 1vCPU, 2048Mb ram, IDE00 vhdx 128gb, IDE01 vhdx 80gb, IDE10 CD boot and Legacy NIC (external network) Power on and 3rd option. it gave me a valid internal ip but no luck detecting using sylogony assis. ISO: XPEnoboot_DS3615xs_5.2-5644.5 Synology Assistant Version 6.0-7319 PAT file: didnt get here yet.. Edited June 3, 2016 by Guest Link to comment Share on other sites More sharing options...
haydibe Posted June 2, 2016 Share #2 Posted June 2, 2016 Is the "valid internal ip" in the same subnet as your windows host? You could use a browser and open the url http://"valid internal ip":5000 and get to the installer. Are you sure the network adapter of your vm (in hyper v) is set to bridged mode? Link to comment Share on other sites More sharing options...
kaede15 Posted June 3, 2016 Author Share #3 Posted June 3, 2016 Yes to the subnet and yes to the bridge. And I also try the url replacing with this "valid ip"... Anyway I switched to VMware Workstation Pro 12 and got it setup in lest than 10 minutes with all the pat updates. I'm kind of getting tired of these network issues of hyper v. Its is extremely unreliable and buggy. But since it comes with windows it's kind of default program to go to. But I'm reverting to VMware. (BTW it is the same problem I had with Pfsense 231 in hyper v, valid network ip but wan packets CANT flow to lan... so its kind of pointless to run in hyperv) Anyhow thx switching back to VMware and EXSi 5.5 and giving the middle finger to hyperv Link to comment Share on other sites More sharing options...
Recommended Posts