Broken NAT networking after upgrade to 3.0.0

[elfarto]

Hi, this is my first post, i've been using VirtualBox for one year mainly to have a separate connection to my company's VPN (Cisco VPN based). I'm running in a Vista 64 Host and my guest OS is WinXP SP3 32bit w/ Intel Pro/1000 network driver.
I upgraded from 2.4.4 to 3.0.0 and after the upgrade i have several problems, the worst being broken nat connectivity: ping or connections to the internet will either fail or drop packets. (in one case pinging my VPN gateway showed an intermittent response from 10.0.2.2, works fine on VB 2.2.4), the rest of the test pings would fail, connectivity to VPN would not work at all (fails to contact the VPN gateway), Internet browsing would hang halfway from loading webpages.
The Windows GUI is also broken, after shutting down the guest you cannot change the Networking Mode (it will display no dropdown menu , or crash the GUI), you need to close and re-open the interface.
I've also had several Virtual Machine crashes .
I had to downgrade back to 2.2.4 in order to get a working VPN (and internet) connection.

I really liked the features on 3.0.0 but it seem like it still has some issues.
I'm willing to give 3.0.0 another try provided anyone can point me in the right direction to overcome these problems.

[Perryg]

There is always a chance that the install was bad. You can try it again and this time right click on the install icon and left click on run as admin. Watch for any errors and remember to reboot the host after the install.

[elfarto]

Did that, no luck, no errors during the install. NAT is still semi-broken.
Any idea why a ping to an internet host is being replied (or at least it seems to come ) from the VBox gateway?

[Perryg]

No idea at this time. I am still trying to shake out a few bugs myself. I know that this was a major release and has some nasty bugs in it for some people but not for others. This makes it hard to track down. Why will it work for me but not you, and why does it work sometimes and not the next time. The best that we can hope for at the moment is to report these things here and if no solution is found then the next step is to file a ticket with bugtracker. You already have what I would have suggested. You say that you use the IntrlPRO/1000 adapter. This has been an outstanding problem with network issues in version 3.0.0. Maybe you should try one of the others and see if it improves. Please let us know if this does help and also if it does not.

[elfarto]

Just in case, i've uninstalled, reinstalled 3.0.0, and reinstalled Additions 3.0.0 on the guest
For the record there are no Firewall Software installed on the Host, I'm connecting to internet using the Wireless link on my laptop.


This is the result of a ping to http://www.yahoo.com

Code: Select all

C:\Documents and Settings\hz9d76>ping www.yahoo.com

Pinging www-real.wa1.b.yahoo.com [209.191.93.52] with 32 bytes of data:

Reply from 10.0.2.2: bytes=32 time=179ms TTL=45
Reply from 10.0.2.2: bytes=32 time=181ms TTL=45
Request timed out.
Reply from 209.191.93.52: bytes=32 time=179ms TTL=45

Ping statistics for 209.191.93.52:
    Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
    Minimum = 179ms, Maximum = 181ms, Average = 179ms

VPN Connection is still a NO-GO as it is browsing any "heavy" webpage like digg.com

[elfarto]

Forgot to mention that i was using the PCNet Driver before upgrading to 3.0.0, after detecting the problem and based upon some googling i decided to switch to Intel Pro/1000 which by the way works perfectly under 2.2.4 (as did PCNET)

[wayne_zhang]

I have the same problem. My host system is Vista Ultimate x64 SP2, my guest system is Windows XP SP3, and I am using Cisco VPN to access my corporate email and intranet. After upgrading to 3.0.0, VPN became extremely slow and very unstable, whatever I use PCnet or Intel Pro/1000 MT Desktop. I also encountered a number of VirtualBox GUI crashes after upgrading my VirtualBox to 3.0.0.

Is there any workaround to solve the problem?

[Alainke2]

Same problem here with the Cisco VPN connection. It is horribly slow or does not work at all. I can connect to the vpn gateway but that's about it. RDP connections time-out not to mention Outlook.
Everything worked fine under 2.2.4.

I've also tested with the Intel adapter but the results remain the same. Upgrading the Vbox Additions to V3 did not improve things either.

I think I'm gonna switch back to the V2 version for now.

Alain.

[yesitspeter]

I have the same issue, including the VPN problems described above. I attempted to add another network adapter, and the next time I started my VM, it found both network adapters to have "Limited or No Connectivity." After disabling one of them, the entire VM crashed (not the guest OS, the VM). I found multiple overflow errors in the VirtualBox log.

[brott]

Same issue. I am using Ubuntu 9.04 (32 bit) as the host, and Windows XP as the guest. I am using a wireless connection via my laptop. In 2.2.4, networking is flawless. Upon upgrading to 3.0.0, I cannot establish an IP - cannot VPN, hit websites, etc.

Thanks

[elfarto]

Looks like we have an well defined issue, i'm willing to re-install 3.0.0 and provide whatever logs are necessary to track down the issue.

[rasta]

Looks like this may have been fixed in SVN. See bug #4343.

[washirv]

Still a problem in 3.0.2; Cisco VPN is all but unusable.

(Many thanks to Vbox hosts for maintaining v2 clients for download yet. :)

[rasta]

I concur that the NAT problem has NOT been fixed in 3.0.2 (WinXP 32-bit host, Solaris 10 u7 32-bit guest with VT-x).

[avok00]

I also have this exact same issue, NAT dropping packets like crazy around 66% loss, this begun since 3.0 and now continues in 3.0.2 Anyone posted a bug on this? Any workaround?