Broken NAT networking after upgrade to 3.0.0

[mdmadph]

Having this same problem with WinXP hosts and Win7 guests. Trying ping known servers and getting about a 60% loss as well.

[rasta]

See bug #4343.

[zeuchx]

I have the same problem with Virtualbox V3.0.2.

[elfarto]

Any idea when this will be fixed in the mainstream release ?
I particularly like VB 3, but this is definitely a showstopper for me since bridge networking on the office causes my switchport to shutdown (due to the nazi policies of network security dept.).
Thanks!

[Perryg]

Have you tried to switch to the IntelPro/1000 T server virtual Network Adapter yet to see if it will help?
I know there was a problem with this in 3.0.0 and a fix was released in 3.0.2, but some were still having problems and switching helped them out.
I understand from reading bugtracker that another fix is on the way.

[amidsin]

I have also noticed this problem as well. I have experienced that IPSec VPN client (Nortel Connectivity Client) stopped working after upgrading from 2.2.4 to 3.0.2. I have confirmed it by downgrading back and upgrading again a couple of times. Each time I have experienced a problem with version 3.0.2. I was able to work around it by using bridged networking instead of NAT. I hope it helps somebody.

[lshurr]

Thanks for this thread. I had to revert to V2.2.4 from V3.0.2. NAT networking in 3.0.2 is useless until it's fixed and I couldn't bridge to the wireless adapter.

[elfarto]

Doesn't matter which NIC driver i use, the behaviour remains the same.
Any idea if this is going to be fixed by 3.0.3 ?

[avok00]

This is not fixed even in 3.0.4 I checked yesterday. What is going on Sun? I am beginning to think that this project is too amateurish for me to use! How you can not fix a major problem such as NAT in 3 subsequent releases??!!

[lshurr]

Dude, take it easy. I'm frustrated, too, because I'm stuck on 2.2.4 for now, but they're working on it. The Changelog for 3.0.4 shows that 4 NAT-related tickets were closed, but that one of them has been reopened. NAT is a tricky SOB.

[elfarto]

Tricky SOB or not it was working till 3.0 release. Does anyone has the bug# it has been reopened ? i'd love to collaborate to get this solved ?

[Perryg]

You can click the bugtracker link at the bottom of my post or you can simply search the bugtracker by putting
NAT problems site:virtualbox.org in google. I have no problems with NAT and I do have a Vista host and XP guest setup in NAT as one of my test configurations. I suspect while it may be some glitch that some configuration problem can also be in play, since as I say it works for me. Anyway search the bugtracker and if you do not find a post that fits your problem create a ticket. Don't forget to send them your VBox log file.

[washirv]

My Cisco VPN client (v5.0.02.0090) works properly over NAT again with Virtualbox version 3.0.10.

Thanks very much for the fix.