Bridged Netowrking issue

Discussions related to using VirtualBox on Windows hosts.
TDog
Posts: 11
Joined: 16. Sep 2009, 04:54
Primary OS: MS Windows 7
VBox Version: OSE other
Guest OSses: XP

Bridged Netowrking issue

Post by TDog »

Hello!
I am using 3.0.6
Host OS - Windows 7 Enterprise 32 bit
Guest OS - Windows XP Pro
While using the bridge connection I am getting a right ip assigned by my DHCP server but I am not able to ping anything, therefore no internet and network access.

If I am using the host networking, I have the internet connection but the ip is not from the DHCP scope, ie 10.0.0 as apposite to 10.238.xxx.xxx

I can't think of anything else as I've tried any network setting that Virtualbox has to offer.
Please, help!
TDog
Posts: 11
Joined: 16. Sep 2009, 04:54
Primary OS: MS Windows 7
VBox Version: OSE other
Guest OSses: XP

Re: Bridged Netowrking issue

Post by TDog »

Update:

The exact same thing is happening with the latest Ubuntu installed as a guest.
brochs
Posts: 13
Joined: 8. Jul 2009, 10:18
Primary OS: MS Windows 7
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Win XP, Windows 7 (32), Ubuntu 9.04

Re: Bridged Netowrking issue

Post by brochs »

TDog wrote:Hello!
I am using 3.0.6
Host OS - Windows 7 Enterprise 32 bit
Guest OS - Windows XP Pro
While using the bridge connection I am getting a right ip assigned by my DHCP server but I am not able to ping anything, therefore no internet and network access.

If I am using the host networking, I have the internet connection but the ip is not from the DHCP scope, ie 10.0.0 as apposite to 10.238.xxx.xxx

I can't think of anything else as I've tried any network setting that Virtualbox has to offer.
Please, help!
When in bridge mode, are you trying to Ping by using hostname like www.microsoft.com or by IP like 193.34.xx.xx? If you only have tried using hostname, can you try it again with pinging IP? It sounds like the problem I am experiencing, but I can Ping IP but not hostname.
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: Bridged Netowrking issue

Post by Perryg »

Moving to Windows 7 host
TDog
Posts: 11
Joined: 16. Sep 2009, 04:54
Primary OS: MS Windows 7
VBox Version: OSE other
Guest OSses: XP

Re: Bridged Netowrking issue

Post by TDog »

That is correct, I can ping by ip address but not by its hostname.
If i browse to a web-site by ip, it will start load until it encounters a hostname in the page's code. Then it gets stuck.
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: Bridged Netowrking issue

Post by Perryg »

Look at the DNS. Try using a known good DNS like OpenDSN and see if it works. 208.67.222.222 and 208.67.220.220.
TDog
Posts: 11
Joined: 16. Sep 2009, 04:54
Primary OS: MS Windows 7
VBox Version: OSE other
Guest OSses: XP

Re: Bridged Netowrking issue

Post by TDog »

it uses my corporate dns server. I checked it out, its DHCP even sees my VM and its mac address.

The whole point is I need it to be on my domain.
If it is NAT, I have no internet problems except I can't join the domain.
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: Bridged Netowrking issue

Post by Perryg »

If this is in a Corp domain then you need to check and see if it is using a proxy server or some other reason why DNS is not working for you.
(1) While in bridged mode do an IPconfig /all and look at the information to see if it indicates a reason.
(2) Or you can use nslookup to see if the DNS server is being seen by the guest. Try resolving a named URL using nslookup and see if it returns an ip address.
(3) You may need to contact your network group to see if they have placed restrictions that would keep you from using this type of networking.
TDog
Posts: 11
Joined: 16. Sep 2009, 04:54
Primary OS: MS Windows 7
VBox Version: OSE other
Guest OSses: XP

Re: Bridged Netowrking issue

Post by TDog »

Oh, well, I am in the network group :-)

Here is the result of the nslookup.

C:\Documents and Settings\Administrator>nslookup 10.238.7.254
DNS request timed out.
timeout was 2 seconds.
*** Can't find server name for address 10.238.7.254: Timed out
DNS request timed out.
timeout was 2 seconds.
*** Can't find server name for address 10.238.7.253: Timed out
*** Default servers are not available
Server: UnKnown
Address: 10.238.7.254

DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out

C:\Documents and Settings\Administrator>ping 10.238.7.254

Pinging 10.238.7.254 with 32 bytes of data:

Reply from 10.238.7.254: bytes=32 time<1ms TTL=127
Reply from 10.238.7.254: bytes=32 time<1ms TTL=127
Reply from 10.238.7.254: bytes=32 time<1ms TTL=127
Reply from 10.238.7.254: bytes=32 time<1ms TTL=127

Ping statistics for 10.238.7.254:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

10.238.7.254 is my DNS server.


IPCONFIG results


Windows IP Configuration

Host Name . . . . . . . . . . . . : myhostname
Primary Dns Suffix . . . . . . . : MYCORPORATEDOMAIN
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : MYCORPORATEDOMAIN
MYCORPORATEDOMAIN.

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . : mycorporatedomain.
Description . . . . . . . . . . . : Intel(R) PRO/1000 T Server Adapter
Physical Address. . . . . . . . . : 08-00-27-3D-8A-AC
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 10.238.12.204
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.238.12.1
DHCP Server . . . . . . . . . . . : 10.238.7.253
DNS Servers . . . . . . . . . . . : 10.238.7.254
10.238.7.253
Primary WINS Server . . . . . . . : 10.238.7.253
Secondary WINS Server . . . . . . : 10.238.89.30
10.238.7.254
Lease Obtained. . . . . . . . . . : Friday, September 18, 2009 11:42:13 AM
Lease Expires . . . . . . . . . . : Saturday, September 26, 2009 11:42:13 AM


Edited some infor for privacy but you can see that it obtains the ip from my DNS server. More over, this ip (12.204) is reserved on DHCP, so here is another proof that the VM joins the network but is not able to resolve any hostname.

The same config works just fine for my co-worker sitting next to me.

I thought it could have been something with the network port.
However, we are both in the same IP range, and there is no security enabled on the Cisco port I am connected to. I checked.

Moreover, the Cisco switch sees the mac address of my VM as being connected.

From Cisco:

nyc1swd10d> (enable) sh cam dyn | inc 8a-ac

Port Name Status Vlan Level Duplex Speed Type
----- ------------------ ---------- ---------- ------ ------ ----- ------------
3/15 connected 12 normal a-full a-100 10/100BaseTX

Furthermore:

Port AuxiliaryVlan AuxVlan-Status
----- ------------- --------------
3/15 none none


Port Security Violation Shutdown-Time Age-Time Max-Addr Trap IfIndex
----- -------- --------- ------------- -------- -------- -------- -------
3/15 disabled shutdown 0 0 1 disabled 103

Additionally, checked the firewall, nothing in there detects blocks on connection from 12.204
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: Bridged Netowrking issue

Post by Perryg »

Out of curiosity what happens if you disable the Windows 7 firewall completely?
Also some VPN clients have been known to filter guest requests. Are you using any on the host or guest?
TDog
Posts: 11
Joined: 16. Sep 2009, 04:54
Primary OS: MS Windows 7
VBox Version: OSE other
Guest OSses: XP

Re: Bridged Netowrking issue

Post by TDog »

Windows firewall is disabled on both, the host and the guest by the domain policy. The guest picks up the policies from the domain!

From the guest: attempted RDP to a machine outside the network. By IP - success, by the hostname - no go.
VPN software is not running. - edit: That was a good catch, by the way, I forgot about Shrew!
Last edited by TDog on 25. Sep 2009, 21:47, edited 1 time in total.
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: Bridged Netowrking issue

Post by Perryg »

I don't know what to tell you since I am not there it is really hard to diagnose this remotely, but I definitely believe it is a DNS issue.
You say that your co-worker does not have this problem. Try to compare the two and see what the difference is.
I see where you are running VLAN, have you entered your guests MAC/ipaddress in the config.? The reason I ask is the MAC that you are showing does not appear to be one that would be generated by VBox. It might be but I have not seen one that looks like this before.
brochs
Posts: 13
Joined: 8. Jul 2009, 10:18
Primary OS: MS Windows 7
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Win XP, Windows 7 (32), Ubuntu 9.04

Re: Bridged Netowrking issue

Post by brochs »

Perryg wrote:I don't know what to tell you since I am not there it is really hard to diagnose this remotely, but I definitely believe it is a DNS issue.
You say that your co-worker does not have this problem. Try to compare the two and see what the difference is.
I see where you are running VLAN, have you entered your guests MAC/ipaddress in the config.? The reason I ask is the MAC that you are showing does not appear to be one that would be generated by VBox. It might be but I have not seen one that looks like this before.
This is a DNS problem yes, but the problem probably lays within Windows 7 or even the NIC driver for the Intel adapter. I have exactly the same problem when bridging over the Intel Pro 100/1000 NIC, but when I remove the cable and use WLan as connector for the bridge everything works fine (or at least better).

It's only the DNS requests that are blocked, using only IP addresses everything is working. It's not a Domain or not Domain problem, it just a general problem on Windows 7 host, and I suspect it's Windows 7 with some Intel NIC's.

I can also add that the problem also exixts when using VMWare Desktop!
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: Bridged Netowrking issue

Post by Perryg »

I have been tracking this and it does appear to be a Windows 7 problem and a lot of people (not just virtual users) are beating the heads against a wall trying to get this to work.
I have gleaned the follow from several Windows forums that say this should get you back on the net but since I don't use Windows 7 as host I can only tell you that the original posters state that it worked for them.

Open a command prompt as administrator in Win 7 and type each of these commands:

Code: Select all

ipconfig /flushdns
netsh interface tcp set global autotuninglevel=highlyrestricted
netsh int ip reset
As stated if this does not work for you then it is not going to work until Microsoft fixes the problem, which seems to be random. Also all of the people that I have contacted about this says to disable the IPv6, not sure why but that is their suggestion.
TDog
Posts: 11
Joined: 16. Sep 2009, 04:54
Primary OS: MS Windows 7
VBox Version: OSE other
Guest OSses: XP

Re: Bridged Netowrking issue

Post by TDog »

I did as you suggested, and it did not work. The only difference is that strangely enough I can now ping my DHCP server by name but no internet.
And you are right, no go with the VMWare as well.


I wonder if Virtual PC 2007 (put it to try the XP mode) has screwed something up.
Post Reply