Strange DNS problem

[gcstang]

HI,

I am having a very strange problem on Windows 7 x 64 host. When running guests in NIC bridge mode I get a IP from DHCP on guests, I can ping all IP addresses both private and on internet, but pinging e.g. http://www.pcworld.com I get no response. Clearly it’s something with the DNS which is the same as my host use, and I can ping it from guest. Setting guest OS to NAT everything works just fine.
The problem exist in both windows and Linux guests (X86). Someone have any ideas? I have to mention that I have tried VMware Desktop and get the same problem there.

I'm having this exact same issue in 3.0.6, worked fine in 3.0.4 and all previous versions.

I've also tried OpenDNS, DNS settings instead of using my router and still only works with the IP address

[brochs]

I have dicovered something starnge now.

Using bridge NIC on guest over my WLan is now working, WLan is same subnett as my lan and same DHCP. But on my Intel PRO 1000 (Intel 82566MM GB NIC) it is not working. This have to be a driver issue, or some settings that is blocking DNS on guest bridge NIC.

[gcstang]

Guess I'm going back to 3.0.2, would be nice if we could get another version that was working entirely.

3.0.4 had SATA issues with secondary drives and now this with the DNS....

I love the product just wish testing and/or support was a bit better.

[Sasquatch]

Guess I'm going back to 3.0.2, would be nice if we could get another version that was working entirely.

3.0.4 had SATA issues with secondary drives and now this with the DNS....

I love the product just wish testing and/or support was a bit better.

This NIC thing is really hard to find, because for all we know, it can be the driver itself that is causing the problem. Either downgrading the version, or installing a newer version of the driver could solve this issue. Also, it seems to happen with only one NIC type. There used to be some problem with Realtek (wireless) cards too, not accepting bridged method, but that seems to be fixed. Really, it's not easy to tackle every hardware option.

[gcstang]

Guess I'm going back to 3.0.2, would be nice if we could get another version that was working entirely.

3.0.4 had SATA issues with secondary drives and now this with the DNS....

I love the product just wish testing and/or support was a bit better.

This NIC thing is really hard to find, because for all we know, it can be the driver itself that is causing the problem. Either downgrading the version, or installing a newer version of the driver could solve this issue. Also, it seems to happen with only one NIC type. There used to be some problem with Realtek (wireless) cards too, not accepting bridged method, but that seems to be fixed. Really, it's not easy to tackle every hardware option.

Not sure if it will help but I have "Broadcom NetXtreme 57xx Gigabit Controller" in my XPS M1710...3.0.2 doesn't work anymore either, I've even tried another VM that works on someone's computer(with same NIC). I'm pretty much dead in the water, I tried an uninstall and removed all files from VBox then reinstalled and configured again, also tried upgrading my driver, but no luck.

[TDog]

Hi!

I just fixed exactly the same problem.

Do you by any chance have any VPN client installed or any network device (beside the vm, of course) that may have loaded 3rd party drivers? Check your network connection properties and see if there is something "extra".

In my case it was Shrew VPN client messing the things up.

[gcstang]

Hi!

I just fixed exactly the same problem.

Do you by any chance have any VPN client installed or any network device (beside the vm, of course) that may have loaded 3rd party drivers? Check your network connection properties and see if there is something "extra".

In my case it was Shrew VPN client messing the things up.

I do use Shrew but so does the other person that is not having any issues.

[Perryg]

@gcstang,
I think what tdog was getting at is to remove the VPN client, then reinstall VBox then re-install the VPN client.
I have seen this before as well and it does not effect everyone but for some reason it messes up the install of VBox for some and this usually fixes it.

[TDog]

My apologies if i was not clear.
But I do hope it is going to fix your issue. I was banging my head for 2 weeks.
Perryg, I did not even bother reinstalling the VBox.
Step 1: Removed the Shrew Filter from network connection properties.
Step 2: Tested VBox - OK
Step 3: Reboot
Step 4: Checked VBox. Tested OK
Step 5: Reinstalled Shrew VPN
Step 6: Reboot
Step 7: Checked VBox - OK. Checked Shrew VPN - OK
Step 8: Went to the movies (optional )

[gcstang]

My apologies if i was not clear.
But I do hope it is going to fix your issue. I was banging my head for 2 weeks.
Perryg, I did not even bother reinstalling the VBox.
Step 1: Removed the Shrew Filter from network connection properties.
Step 2: Tested VBox - OK
Step 3: Reboot
Step 4: Checked VBox. Tested OK
Step 5: Reinstalled Shrew VPN
Step 6: Reboot
Step 7: Checked VBox - OK. Checked Shrew VPN - OK
Step 8: Went to the movies (optional )

Thank you that worked perfectly....AWESOME!

[TDog]

Glad it worked for you.

And on a personal side, Shrew VPN is total crap.

It now decided to completely block the traffic for what it was intended for - the VPN itself.
IPSec Daemon service is buggy as hell.
Just had totally removed it and reverted back to Cisco.

[gcstang]

Glad it worked for you.

And on a personal side, Shrew VPN is total crap.

It now decided to completely block the traffic for what it was intended for - the VPN itself.
IPSec Daemon service is buggy as hell.
Just had totally removed it and reverted back to Cisco.

Unfortunately Cisco is not an option, I'm using Windows 7 64bit and Cisco declines to support IPSec on any 64 OS....all our clients happen to use Cisco. So I can either start a VM everytime I want to connect over a VPN or just start ShrewSoft.

[carrot]

Thanks for all, although I went with the route of stopping "ShrewSoft DNS Proxy Daemon" from the services. That worked just as well, I don't need DNS over my VPNs. Hopefully that helps some that just want to fix the problem quick without reinstalling VBOX/Shrewsoft.