Windows networking (host and client)

[pharoe]

My physical network setup is pretty standard: router with some PCs behind in subnet 192.168.2.0/24, both linux and windows, router runs embedded Linux.

I got a problem when trying NAT networking under XP SP2 as host and client:
client simply tries to get a DHCP address for ages without ever acquiring one

If I use host interface but don't bridge it on the host I can only ping the virtual host interface. Tried enabling IP forwarding on the host, same result.

I only ever got it working with host interface and bridging on the host but I don't want to do that (any bridging)

Do I have to enable/do anything special on host or client to make NAT work? E..g. run any services like in VMware or such? Maybe some Windows services belonging to the OS and not VBox?

[Sasquatch]

With NAT, VB provides the Guest with an IP address in the range of 10.0.2.0. This should work without any problems. If you do have problems (and you have them ), try to reinstall VB.

[pharoe]

This is my 3rd VBox install. A friend who is another VBox user couldn't get it to work any other way (than host interface with bridging). Neither could #virtualbox on freenode help.

[Sasquatch]

Have you tried another LAN interface or a new Guest install? If it works on a new fresh install, then it's a problem in the Guest.
What happens if you add a vdi from a system that has NAT working?

[pharoe]

I haven't tried another guest OS yet. Tho with host interface and static IP it works without a hitch.

Guess I will try to install debian as a guest and check again

[over_clox]

I'll second that - I've _never_ had a problem with VBox's NAT support, other than the expected problem where PING doesn't work. I've had more problems from host adapter mode, and that usually works fine too. I agree, its probably a fault with the guest system.