Networking in Windows guest fails after upgrade from 2.0.2 to 2.0.4 => Check local DNS server

[Todd A. Jacobs]

All Windows guests now report local connectivity *only* after upgrading. This is true for both Windows Vista and Windows XP guests running on 64-bit Debian:

Linux deltani 2.6.26-1-amd64 #1 SMP Thu Oct 9 14:16:53 UTC 2008 x86_64 GNU/Linux

No configuration changes were made to the guests before this failure. The only thing that seems to have changed is the 2.0.4 upgrade a few days ago.

Releasing and renewing the IP address inside the guest makes no different, nor does running "sudo /etc/init.d/vboxnet restart" or restarting the VirtualBox GUI. In short, all guests are currently unusable because they lack connectivity.

I'm attaching some logs, bot from 2.0.2 and 2.0.4 for comparison.

[Todd A. Jacobs]

Two sets of log files each for WinXP and Vista, showing 2.0.2 and 2.0.4

[splark]

I confirm this behavior. On a Server 2008 x64 host all guest network connectivity is broken after upgrading to 2.0.4

Additionally on the Machine settings page when trying to change the "Adapter -> Attached to:" setting to "Host Interface" an error is shown: "No host network interface is selected on the Network:Adapter 1 page." but there is no option to choose an interface. (Screen shot attached)

[splark]

screenshot showing broken network settings in 2.0.4

[Stepan Lendak]

same trouble. FC9 x64

[Frank Mehnert]

splark: Did you recreate the host interface devices as advised in the installer?

[Frank Mehnert]

tjacobs, it seems you have a local DNS server/cache or something like this running which is different between your 2.0.2 and your 2.0.4 configuration. Please disable this local DNS server and you will get your internet back.

[Frank Mehnert]

Actually this should be finally fixed in 2.1.0.