Upgrade to version 3.1.2 breaks stuff

[slimedog1]

I have a couple of problems with Win7-64bit guest.

I am running Virtualbox 3.1.2r56127

First, It sees the network card, but name resolution is NOT working. I can ping xxx.xxx.xxx.xxx addresses, but I cannot ping http://www.google.com, for example. This started just after I upgraded to 3.1.2

Also, I cannot get sound to work under win7-ultimate-64bit guest. Sound works fine for winxp, just not win7 (either device). What's up with that?

Do I need to revert back to 3.0.1?

[Perryg]

Version 3.1.0 - 3.1.2 was a major upgrade.
Were these working in version 3.0.1?
If so it is recommended that you need to un-install and then reinstall the new version.
Also even if it does not ask you should reboot the host since it is Windows.

[slimedog1]

I have rebooted the guest several times. I guess I can try a reinstall. I originally did an upgrade. It didn't complain. I also rebooted the main PC after the upgrade.

Oh, yeah. It worked fine in 3.0.1....

[slimedog1]

I attempted to back it out to 3.0.12. It backed out and the DNS worked. I have now reinstalled to 3.1.2 and now DNS no longer works??? Whats up? What have I done?

The DNS is broken for 32bit winxp as well as 64bit win7.

[slimedog1]

One more bit of information. NAT networking works ok for this client. It is the bridged networking that seems to be broken...

[Perryg]

Interesting, I don't have this problem. Does it work if you put an external DNS address in the guest?

[slimedog1]

No, I can force the DNS address of 192.168.1.1 and it functions the same. I can ping that address and I can route out if I use ip addresses. I have no name server outside of 192.168.1.1 to try.

This is consistent with WinXP and Win7. Both clients I can break by setting networking to bridged. Could it be some funky setting in the router? Where would I look?

[Perryg]

So I assume the host does work. Can you post the output of ipconfig /all from the host and one guest that is not working?

Also OpenDNS has this address you can use to test the guest 208.67.222.222. Just put that in the guest DNS field.
Also you might want to turn off the firewall in the host & guest to determine if it is blocking anything.
All of these are tests to try to figure out why you are having problems, not necessarily solutions.

[slimedog1]

Both of the following are exactly the same guests.

This works:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : worker
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . :

Ethernet adapter Local Area Connection 5:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Desktop Adapter
#2
Physical Address. . . . . . . . . : 08-00-27-38-C6-23
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 10.0.2.15
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.0.2.2
DHCP Server . . . . . . . . . . . : 10.0.2.2
DNS Servers . . . . . . . . . . . : 192.168.1.1
Lease Obtained. . . . . . . . . . : Friday, December 18, 2009 9:24:06 AM

Lease Expires . . . . . . . . . . : Saturday, December 19, 2009 9:24:06
AM

This doesnt:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : worker
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 5:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Desktop Adapter
#2
Physical Address. . . . . . . . . : 08-00-27-38-C6-23
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.21.120
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.1.1

C:\Documents and Settings>

[Perryg]

This is the configuration of the second one and shows that you are either getting an address from another DHCP server (host) or it is not working and Windows is using its built in address. First thing to try it to re-install VBox by right clicking the install and then left click on run as admin. When prompted select repair. When complete reboot the host.

Autoconfiguration IP Address. . . : 169.254.21.120
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.1.1

[slimedog1]

It looks like virtualbox is acting as the dhcp server. I guess I need to better understand bridged networking and get it configured properly. It looks like something may have changed in that setup.

[Perryg]

Try disabling host-only DHCP server and see if it works. VBox - preferences - network (click the screw driver image) DHCP server - take the check mark out of enable server.

[slimedog1]

Ok, i am back to this again.

I have tried enabling 208.67.222.222 as the name server (DNS) in the guest with no success. I have not only disabled any host only eth adapters I have also removed all of them with no change.

The guest will ping the name server (either 192.168.1.1 or 208.67.222.222) but will no resolve names from them. I have tried this with OpenSolaris, Fedora, Win7 and WinXP. All fail when using the bridged ethernet connection. I have tried updating the ethernet drivers on the guests, but they are already current.

I would really rather not use the NAT connection, I prefer bridged. Have there been any bugs reported on this? Is there any way to check?

Gary

[Xenomorph]

Ok, this is the third thread I've seen on this (check the Windows Host forum).

Host:
Windows 7 Professional x86

Guest:
Windows XP SP3

With Bridged networking, DNS fails. I can ping IP addresses, but DNS never resolves.

[Perryg]

These kinds of problems that are reproducible should be reported to bugtracker. You will need to setup an account there as it is on a different system.
It would also help if you can post the ticket number here so other can see the progress, add information, or see the final results.