Internet browsing not working well mayb caused by Virtualbox

codecks · Post by **codecks** » 15. Dec 2008, 22:13

First of all: I did investigate the net and this forum to find some similar problems but with no luck, if someone finds something be glad and drop a link.

So, this is my situation:

My computer has a Vista x64 Ultimate edition installed. I also have the latest version of virtualbox installed (2.0.6). There's 1 VM1 adapter bridged with my physical network card that I use for my virtual machines (one at a time)
With the last upgrade I had to recreate the VM1 adapter (wich is normal when upgrading virtualbox) so my guests (ubuntu, win xp) could use my internal network and access the internet.
I think the problem started after doing that upgrade to the newest version of virtualbox, but I'm not sure, since I have the problem for a while now and didn't investigate it immediately.

So as the title of this topic mention, I can't always browse the internet. When I type an url like for example www.google.com I see in the status bar of the browser that it is connected to the site, or waiting for a response from the site and then most of the time it hangs: page timeout. I did test with several browsers each one had the same behaviour.
Sometimes, when the pc is up for a while it will work correctly, then when I leave the pc for a while and come back the problem happens again. It's working well very 'randomly'.

I also noticed there's a problem creating the bridge: simply selecting the two adapters (the virtual VM1 and the physical adapter) 'right click --> bridge' doesn't work (windows error creating bridge). I had to select the properties of the bridge and manually add the two adapters wich worked fine.

Another thing, browsing through a virtualbox works perfectly (I'm actually posting this through my ubuntu virtual box)

Things I did test:

Browsing my local network works well
Pinging site url's work
Tried another router: changed nothing
Disabled firewall & antivirus: changed nothing
Tried another physical network adapter (mobo has 3 cards, 2 cabled and 1 wireless): changed nothing
netsh winsock reset: changed nothing
netsh int ip reset: changed nothing
fix, dynamic ip configurations: changed nothing

I think something must have gone wrong with that bridging, but maybe I'm wrong, anyways if someone has some refreshing ideas, just shoot

Greets

Dimitri

Post by **vbox4me2** » 15. Dec 2008, 22:21

Did you try rebuilding the bridge?

codecks · Post by **codecks** » 15. Dec 2008, 22:35

vbox4me2 wrote:Did you try rebuilding the bridge?

by simply removing the adapters from the bridge ? or with some special command ? I did remove them from the bridge by unselecting them in the properties

Post by **vbox4me2** » 15. Dec 2008, 22:38

Sri, I meant the HIF, remove them all and rebuild them from scratch.

codecks · Post by **codecks** » 15. Dec 2008, 22:56

the thing is, I removed the bridge and the 'vm1 external' interfaces now. My computer working directly with the physical network adapter, and it's still the same problem.

Post by **vbox4me2** » 15. Dec 2008, 23:32

What about the host itself, is that working ok?
Does the host have non standard DNS addresses?

Ie. mostly it should be on the Host:

Code: Select all

Dhcp Enabled. . . . . . . . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.20
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1

The gateway = the router = dns handling

But some have this:

Code: Select all

Dhcp Enabled. . . . . . . . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.20
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 64.65.66.67 (ISP dns)

The gateway = the router = passthrough dns handling

This later setting can cause problems.
Make sure your router handles it all, whatever traffic is then going out via host or guest will follow the same path.

codecks · Post by **codecks** » 16. Dec 2008, 09:37

IP configuration:

Code: Select all

DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::2d74:1120:e345:2f83%12(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.16(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Route Print:

Code: Select all

Interface List
 12 ...00 1d 60 ee 22 d8 ...... Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Con
troller
  1 ........................... Software Loopback Interface 1
 13 ...00 00 00 00 00 00 00 e0  isatap.home
  9 ...02 00 54 55 4e 01 ...... Teredo Tunneling Pseudo-Interface

IPv4 Route Table

Code: Select all

Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.1.1     192.168.1.16     20
        127.0.0.0        255.0.0.0         On-link         127.0.0.1    306
        127.0.0.1  255.255.255.255         On-link         127.0.0.1    306
  127.255.255.255  255.255.255.255         On-link         127.0.0.1    306
      192.168.1.0    255.255.255.0         On-link      192.168.1.16    276
     192.168.1.16  255.255.255.255         On-link      192.168.1.16    276
    192.168.1.255  255.255.255.255         On-link      192.168.1.16    276
        224.0.0.0        240.0.0.0         On-link         127.0.0.1    306
        224.0.0.0        240.0.0.0         On-link      192.168.1.16    276
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    306
  255.255.255.255  255.255.255.255         On-link      192.168.1.16    276

Persistent Routes:
  None

IPv6 Route Table

Code: Select all

Active Routes:
 If Metric Network Destination      Gateway
  9     18 ::/0                     On-link
  1    306 ::1/128                  On-link
  9     18 2001::/32                On-link
  9    266 2001:0:d5c7:a2ca:2017:143d:a44b:26e6/128
                                    On-link
 12    276 fe80::/64                On-link
  9    266 fe80::/64                On-link
  9    266 fe80::2017:143d:a44b:26e6/128
                                    On-link
 12    276 fe80::2d74:1120:e345:2f83/128
                                    On-link
  1    306 ff00::/8                 On-link
  9    266 ff00::/8                 On-link
 12    276 ff00::/8                 On-link

Persistent Routes:
  None

These settings seems to be normal to me. I'm not very aware about IPv6 tho

Post by **vbox4me2** » 16. Dec 2008, 11:04

Does the host work ok?
What happens if you disable ipv6 host and guest(s)?

codecks · Post by **codecks** » 16. Dec 2008, 18:17

vbox4me2 wrote:Does the host work ok?
What happens if you disable ipv6 host and guest(s)?

Well, it's all about the vista host here.
I allready tried to disable ipv6 (on the host) by unchecking them in the adapter properties but with no luck. I really don't know what I could do further, except reinstall the whole thing (but I'd like to avoid this)

Post by **Sasquatch** » 16. Dec 2008, 22:07

I've added a few code blocks here and there for some. Please do that yourself next time.

As you have a valid IPv6 address, I would suspect that that is a possible problem. If you disable IPv6, you probably need to restart the network (do a repair, or reboot).
Another thing, did you bridge you wired interface, or your wireless one? Wireless doesn't always work with a bridge.

codecks · Post by **codecks** » 16. Dec 2008, 22:27

Sasquatch wrote:I've added a few code blocks here and there for some. Please do that yourself next time.

As you have a valid IPv6 address, I would suspect that that is a possible problem. If you disable IPv6, you probably need to restart the network (do a repair, or reboot).
Another thing, did you bridge you wired interface, or your wireless one? Wireless doesn't always work with a bridge.

will do, thanks for pointing me out.

Going to try that, disable IPV6 by unchecking the boxes in the network card properties. It's all over a wired interface. Also I'd like to mention the bridge has been deleted now. The problem is about my host box not working well when it comes to browsing. Everything else seems to work ok (msn, torrents,...) My virtual machines now use nat to go on the net and they seem to have the same problem as the host. Which wasn't like that with a bridge. Indeed with a bridge only the host had browsing problems, virtual machines did work perfectly for browsing internet pages.