VirtualBox builtin DHCP server using NAT not reachable

[lostsheeptweb]

Hello

I have a Windows 7 Pro host and a WinME guest. In the guest both winipcfg and ipconfig /all show 0.0.0.0 as the IP address and the release and renew buttons in winipcfg are greyed out. I have configured the networking using the OS installation procedure and have enabled DHCP, made WINS configuration information obtained by DHCP, and turned off DNS acquisition in the TCP/IP configuration dialog box.

I have the VB NIC adapter "attached to" setting set to NAT and am using the PCNET AMD II NIC adapter. Does anybody have any information or insight into why my WinME VM can't contact the builtin NAT DHCP server?

Thanks in advance

[lostsheeptweb]

Oops. I stupidly forgot to post my vital information.

Host: Windows 7 Pro 64 bit
Guest Windows ME (32 bit)
VB: 4.3.4r91027
NIC adapter attached to: NAT
NIC adapter: PCNET-PCI II
Virtualization hardware: VT-x/AMD-V, Nested paging both enabled
Guest memory: 128 MB RAM
Guest HDD size: 4.0 GB (dynamically allocated), 810 MB currently used

[mpack]

Did you install network adapter drivers in the guest? I don't know about ME, but Win98SE didn't install them by default. Also, the NIC in my (working) Win98SE VM is a "PCnet FAST III (Am79C973)".

Also, network configuration is rather trickier in WinDOS than it became in XP and later.

[lostsheeptweb]

I got busy doing other things and when I decided to get back to this project I was tired of wracking my brains for a solution. So I reinstalled. And in the process of reproducing my previous setup I found out that my VM has internet connectivity just fine *AS LONG* as I don't install the video driver for SciTech Display Doctor 7 Beta.

Simply installing that video driver causes my DHCP setup to break.

So anyway it's not a VirtualBox problem.