wutang200 Posted February 22, 2016 Share #1 Posted February 22, 2016 I'm trying to install Xpenology onto Virtual Box but having some trouble with getting the Synology Assistant to find the box. Tried my best to follow the guide posted on here but still unable to get the Assistant to find it. I've got to the stage where I boot the Xpenology VM, but then can't get any further. I've tried to bridge my LAN connection with my Virtual Box adapter but still no luck. I got as far as it getting given an IP address which I was able to ping from my PC but couldn't get any further. Anyone come across this before? Link to comment Share on other sites More sharing options...
paranoia68 Posted February 27, 2016 Share #2 Posted February 27, 2016 Same problem here: I can login to the nas with browser, but the DSM says there is no internet connection and shows no help of anything else to connect to the net for use. The synology asssistent does also not find the nas and fint.synology.com does the same.... I tried, NAS, with portforward fron host to slave en visa versa, and even bridgemode does not work for the problem. Is there any one that managed to get this working? Please help. Link to comment Share on other sites More sharing options...
sbv3000 Posted February 27, 2016 Share #3 Posted February 27, 2016 Under VB network advanced settings, try the different NIC emulations (default is normally the Intel desktop) Link to comment Share on other sites More sharing options...
berwhale Posted February 27, 2016 Share #4 Posted February 27, 2016 This guys says you need to setup a Bridged Adapter... http://www.wijngaard.org/synology-virtu ... irtualbox/ Link to comment Share on other sites More sharing options...
brantje Posted February 28, 2016 Share #5 Posted February 28, 2016 If you use NAT network you have to forward port 5000 to your virtualbox. If you used bridged adapter, then you can find xpenology by Syno Assistant. Posted via Xpenology.us Link to comment Share on other sites More sharing options...
wutang200 Posted March 2, 2016 Author Share #6 Posted March 2, 2016 I fixed it by creating a bridged adapter but there's a general network settings area in Virtual Box that also needs looking at (separate to the network settings for the VM). Link to comment Share on other sites More sharing options...
Recommended Posts