virtualbox.org

Hello,

i've got a problem with the NAT networking in Virtualbox 2.2.2 on a windows host.

The network interface in the virtual machine get's an ip adress assigned by the "dhcp server", and i am able to resolve dns names, but there is no possibility to generate any ip traffic. It seems like i can reach the next hop (virtualbox itself) and after that i only get stars in traceroute.

Since i am in a company network i won't try out the briged networking for security reasons and do not know if this works.

has anyone of you ever noticed anything like that or knows how to solve it?


Greeting from germany
nofoo

Check out these chapters in the VBox Users Guide.

• 6.4. Network Address Translation (NAT)
• 6.4.1. Configuring port forwarding with NAT
• 6.4.3. NAT limitations

Well i read the manual.
Ok, while traceroute is icmp based i can understand that it doesn't show any other hop than the vbox-router.
BUT: the manual says ping should work now. (Even if it's ICMP too) It doesn't in my case.
Also i should be able to do an apt-get update or installing packages inside a linux vm without doing some port forwarding voodoo. In older VirtualBox versions this worked like a charm

Try reinstalling as admin (right click the install icon, left click run as...) the select repair. Reboot after that and see if it will work.