No network after standby / host reboot Hi! I have a Debian Linux as guest system on Parallels 8. Parallels tools are installed. If Linux is running and I quit Parallels and start it again, Linux still works, but its network connection is gone. I'm using shared networking. If I run "ifconfig" in Linux, I can't see eth0 anymore. If I reboot the Linux guest, everything works again as expected. What can I do to make Linux network connection work every time I start Parallels without the need to reboot Linux every time when it's resumed from standby? Or how can I shutdown Linux automatically when I quit Parallels or shutdown the host system? Best regards Andreas
I have the same problem with Parallels 9.0. Latest version of Parallels tools is installed. Any suggestion?
Hi Andreas & TomášH , Please change the Network Mode from "Shared" to "Bridged(Default Adapter)": Go to VM Configure(http://kb.parallels.com/117287) -> Hardware -> Network1 -> Type -> Bridge(Default Adapter).
After changing to Bridged mode, please release and renew your IP by following the below steps : Go to Virtual Machine Terminal and type the below mentioned commands without quotes: "sudo ifconfig eth1 down" It will prompt you for the Debain Linux login password, enter the password and hit enter (the password will not be displayed). "sudo ifconfig eth1 up" Now restart your VM and check the internet connection in it.
It works byt it is annoying. I don't want to do it manually anytime it happens. Can you fix it in next version of Parallels? It also happens when I use bridged mode to WiFi adapter and Wifi network is lost for a moment.
This is happening to me with Ubuntu 14.04 and switching the network has no effect; networking is forever busted on the virtual machine once this happens. Further, this is sometimes corrupting networking on mac when it happens; the wifi switches to "no hardware installed" or stops working completely and I need to reboot. In particular it's happening every time I change the networking settings as you suggest above (I just had to reboot again). I upgraded to 9.0.24237 which *claimed* to fix the problem but it is still happening. This is utterly unacceptable.
