A couple of weeks back, I was testing a DHCP configuration scenario using a number of virtual machines and needed them to obtain their IP addresses from a Windows 2000 DHCP server within my virtual network. That should work, but for some reason, my virtual clients were picking up strange private IP addresses in the range 10.237.0.16-10.237.255.254 (not even the familiar automatic private IP addresses in the range 169.254.0.1-169.254.255.254). After a while, I discovered that Virtual Server has the capability to provide its own DHCP service and that this was enabled. By editing the configuration for the internal network I was using, I could disable Virtual Server’s DHCP server, allowing my clients to locate the correct DHCP server.
I devote a lot of time to this website and I don't charge for access, so please don't use ad-blocking software that removes my only source of income (even if some of the ads that Google serves up are of dubious quality...).
Technology
4 Comments
Thanks, that saved me a heap of time, keep up the good work.
Thans dude. Youre a live saver. I was booting WinPE created with BDD. But it found the wrong DHCP. Now i know. I disabled it and WinPE is working like a charm.
THANKS.
Thanks, saved me a lot of time when I Googled for 10.237.0.16 to find out why on Earth I was getting that instead of an IP from the range I expected from our internal DHCP server :)
I’ve looked for solution of this problem over allmost entire Internet and here I’ve found it here. Thanks