PXE stops at Initializing TCP/IP via DHCP

[Chris Hudock]

Greetings,

I recently upgraded my dhcp server to windows 2003. Since then I can not use pxe or a network boot disk to connect to my RDP server.

I upgraded to 1.50, HotfixC and still no luck. Please help!

- Chris

[Robert Hearn]

Since both PXE and floppy are affected, I'd say it's definitely your DHCP server.
Is your DHCP server authorized?
Are you sure it's handing out IP addresses?
Is your scope big enough - are you running out of addresses?


Robert Hearn
http://www.rdpguru.com/

[Chris Hudock]

Hello.

We don't have AD running so it does not need to be authorized. It is currently handing out addresses for my entire office. There are plenty of addresses free because the subnet I build servers in has its own dhcp scope. Currently the only address in use is the blade I am trying to boot.

I saw a post somewhere that the scope option ClientID 060 needs to be added. But I believe that is only if you have PXE and DHCP running on the same server, which I do not.

Any other ideas?

- Chris

[Richard Mouser]

Chris,

This is almost always due to a conflicting IP address on the network. Here is how to check:

1) Check the IP address your PXE client is getting (shown during PXE boot).

2) See if you can PING that address from your deployment server.

3) Turn off the target server and try the PING again. If you get a response, the DHCP server is handing out an IP address that someone else is already using. In this case, just exclude the address from your DHCP range.

There is a KB article on this:

http://h18013.www1.hp.com/products/servers/management/rdp/knowledgebase/00000115.html