VirtualBox

Ticket #2504 (closed defect: fixed)

Opened 5 years ago

Last modified 5 years ago

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

Reported by: tjacobs Owned by:
Priority: critical Component: network/NAT
Version: VirtualBox 2.0.4 Keywords: NAT connectivity
Cc: Guest type: Windows
Host type: Linux

Description

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.

Attachments

virtualbox_logs.zip Download (44.8 KB) - added by tjacobs 5 years ago.
Two sets of log files each for WinXP and Vista, showing 2.0.2 and 2.0.4
xvm network screen shot.jpg Download (50.6 KB) - added by splark 5 years ago.
screenshot showing broken network settings in 2.0.4

Change History

Changed 5 years ago by tjacobs

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

comment:1 Changed 5 years ago by 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)

Changed 5 years ago by splark

screenshot showing broken network settings in 2.0.4

comment:2 Changed 5 years ago by creon

same trouble. FC9 x64

comment:3 Changed 5 years ago by frank

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

comment:4 Changed 5 years ago by frank

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

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.

comment:5 Changed 5 years ago by frank

  • Status changed from new to closed
  • Resolution set to fixed
  • Component changed from network to network/NAT

Actually this should be finally fixed in 2.1.0.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use