Unable to PXE Boot with WinPE

[Michael Withrow]

Hello,
I have just installed RDP 3.1. I am trying to grab an image of a server. I run the job the server PXE boots, grabs a DHCP address, loads WinPe then.

PXE Boot
Initializing Windows PE ...
Starting Network ...
Establishing Network Connection ...
Validating IP Adress ...
Restarting DHCP Client Service Retry 1 ...
Restarting DHCP Client Service Retry 2 ...
Restarting DHCP Client Service Retry 3 ...
Authenticating Connection ... (sits here for 3 min)
Then the AClient comes up and errors out and closes session.

Can someone assist me. I called HP support and they told me rebuild the RDP server (which I did) and obviously that wasn't it.

[Gordon Leonard]

Let me *guess* you have multiple NICs and some can't get to the RDP server. Restarting DHCP Client Service Retry X, simple means it's restarting the NICs in hopes of getting an IP address. Since you didn't say you go to the count of 20 I would assume one of your NICs did get an IP address, however; this NIC can't talk to the DS - thus you fail to map a drive.

Try this as a *test* - connect ALL your NICs to the same network as the RDP server and see if you get the same error.

As a side note you should have the "help" desk explain there logic if your ever asked to rebuild. Please post the case number.

[Michael Withrow]

Hey Gordon,
How is it going? Ok, I initially had a team setup. I dissolved the team, disabled all but the primary nic, and tried again. This time it only restarted the DHCP Client Service 2 and then the same results.

[Gordon Leonard]

I really need to look at the name before I respond. :)

I just sent an email to Danielle to see how things were progressing. Expect a follow-up email.

[SPa]

I have the same issue here...While initalizing Windows PE...it sits up at restarting DHCP Client Service: retry 1 and goes on...


Any ideas.I'm using RDP 3.1

[Jan van der Valk]

I do have the seem problem.

It fails on authenticating to de RDP Server.

Who has a solution for this??

[rob west_1]

What server s/w are you using for dhcp.

I use 2000 as I don't have to get it authorised in ad. In fact I run rdp 3.10 in a workgroup.

Try disabling additional nic in bios.

Also link them directly via a cable and not thru a switch to rule out that element.

I also used option 43 in dhcp which I only think you need in routed networks.

[SPa]

Well...i didn't had the authentication issue...just that it used to sit at Restarting DHCP Client Service Retry and then unable to Map.

The client was able to load the altiris client once.

I tried disabling all the NIC's(even the second port of onboard NIC) but did not help.The Client server in my case is Proliant Dl380 G4.

I then resolved it by moving the PXE NIC above the addon NIC in the Boot Priority and left the other options as it is that is floppy,CDROM and Hard Drive above the NIC.

Cleared NVRAM,rebooted and everything went smoothly.

Disabling should also have helped as it seems the other NIC were trying to connect when the server rebooted after loading the client.Anyways...All is well that ends well.

I have tried again and everything works fine.

[Tony Glynn]

Same issue here only it eventually connects after 5-10 retries. The DHCP server I'm using is w2003 R2 - the RDP 3.10 server is co-located.

The server being built DHCP's the PXE boot and downloads the PE image fine everytime - PE loads and then the "Restarting DHCP client service: retry X" begins. Typically it 10+ times before I get a connection (if at all).

In the meantime the RDP job times out with "Unable to boot to Windows automation"

The servers are C-Class BL460's. They boot DOS (it DHCP's as well) with NO issues.

I'm swiftly losing faith with this....

[Tom Hanifan]

I'm having the exact same problem, but only with newly opened BL25P

this RDP server has worked for a year now, been upgraded with every major release and 3.1 has worked with other BL25P, BL45P, BL20P, blades have all worked fine, BL25P servers that I racked 2 weeks ago worked fine, nothing has changed on the server (I'm the only person who has access to it)

I'm starting to think it's a firmware difference, they're even the same generation and I'm running out of ideas

[Charles Riggs]

Sounds wierd but I was able to get around it by selecting WINPE managed which launched Altirus X 64 preboot. After first reboot I let it get the default winpe which uses Altirus x86 and it worked fine from there. Crazy but works everytime.

[Alastair Harrison]

I am seeing the same problem.

Installed RDP 3.1.0 as a Simple RDP Installation with DHCP & PXE installed on the same server.

I have tried to run jobs on both a DC7100 desktop PC, DL380G3 & DL380G4. I see exactly the same issue on each target client:-

PXE Boot
Initializing Windows PE ...
Starting Network ...
Establishing Network Connection ...
Validating IP Adress ...
Restarting DHCP Client Service Retry 1 ...
Restarting DHCP Client Service Retry 2 ...
Restarting DHCP Client Service Retry 3 ...
This continues to Retry 19...

Both target clients and RDP Server are on the same LAN.

I'm running RDP 3.1.0 on a 2003 Standard Edition Server. I built the OS with SP1 and all security fixes and rebuilt after seeing these problems with an OS without SP1 & the security fixes but still see the same issue. At least this proves it's not an OS related SP1 or Msoft hotfix issue.

[Gordon Leonard · Accepted solution]

Restarting DHCP Client Service Retry 1 ...
Restarting DHCP Client Service Retry 2 ...
Restarting DHCP Client Service Retry

Means it's trying to get a valid IP address.

There are some issues with RDP 3.1 in the way PXE passes back the MAC address to the console. You should use RDP 3.5.

[Reto Stauffacher]

I also got this Problem and i use the version 3.5.
no suggestions?

[Michael Withrow]

Loaded 3.5 and got past the problem. I miss the 98 boot files though. WinPE is SO SLOW.

[jsu]

Gordon,
Does RDP3.5 address the multiple NIC problem? (some NICs aren't on the RDP LAN) And if so, how? Are NICs disabled? Or is the mapping/authentication algorithm 'improved' (retries?)?
Thx,
Jay

[Gordon Leonard]

I'm assuming WINDOWS.

***Does RDP3.5 address the multiple NIC problem?
(some NICs aren't on the RDP LAN) And if so, how? ***

The AClient just looks for *any* network connection. Thus if NIC1 is connect to the RDP network and NIC2 is on the "other" network and NIC2 get's an IP first game over...maybe.

The older version of RDP would just do a self assign IP if it didn't get one from a DHCP server. What good is an IP of 169.x.x.x? Not with RDP 3.1 or greater which rejects self assigned IP's.

You need to ensure that NIC2 can *not* get an IP via DHCP or hack the startnet.cmd to exclude the NIC2 network IP's [by hack I mean you will not receive any support from HP]

attached UNSUPPORTED hacking PDF

[jsu]

The "unsupported hack" that Gordon attaches was a valiant effort, but alas, does not address the problem (for me).

I/we have done a little more investigation and obtained a promising solution from a consultant...

For those of us who are running multiple LANs between the Deployment Server and Clients, each in their own subnet space, you can identify the WinPE and Linux preboot Deployment Server in the LMHOSTS and host files respectively.

Access them via the PXE Configuration, then edit the desired boot image. In the dialog, "Network Drive Mappings" select the checkbox to "create an entry in the LMHOSTS file for the Deployment server file store..."

[Gordon Leonard]

Hmmm...you problem seems to change from a client which has one NIC on the RDP network to having none.

If your client is on a different network you need only setup a helper address on your router.

Having multiple PXE servers is good when you don't want a lot of traffic crossing a slow link. Also multiple PXE servers mean more hands on management.

[Doug Hafley]

I'm having this same kind of problem with every single one of my DL320 G5 servers. It appears to me that the hardware is PXE boot capable but the version of Windows PE doesn't have a good driver so it fails. I'm looking into updating the windows pe with a custom one that has the nic and sata drivers that I need for this server. I noticed today that there is a new version of RDP and I think I'll end up trying that one out and seeing if that updates my boot image to something that may work.

[Gordon Leonard]

DL320 G5 was placed on the support matrix in RDP 3.1. The current version of RDP is 3.5 - please please check the MD5 checksum after you D/L it.

Make sure you use an ISO burner that suppors ISO:1999 standards.

Michael Withrow - please kill this thread. :)

[Marcus Hock]

Hi,
We are using RDP 3.5 and have the following issue:
- DHCP is on a seperate Server in the LAN
- I created a custom WinPE for x86 only. Made this image Default Boot and "Deployment Image" (in PXE-tab "DS")
- Client: Dl360G5, only NIC 1 is connected


- It boots fine once, then waits for job
- I assign a Job (default DL/ML/BL W2K Deployment Job), it reboots
- WinPE boots again (no selection possible this time, but it says its x86 above the progress bar)
- When "Validating IP Address", it keeps restarting DHCP Client Service
- The DHCP log says it didn't receive a request

I initially had the problem, that the "default" managed PE (x86 and x64) has shown this issue after the first boot (before it was assigned a job). Thought it might be the X64 NIC drivers. x86 seemed to work, but only once...?!?
Sounds like SPa had the same Problem?

Will try to delete all other images tomorrow - just to make sure it uses myX86image for 2nd boot too...

Bye

[Marcus Hock]

Hi!

I found out the following two problems:

- The boot image which is "preconfigured" (called "WinPE Managed") is the one with the Problem. It does not not execute the hardware detection (though my custom WinPE boot image does!). I think that's the reason why it does not send the DHCP request.

- When I initially boot myX86 and it detects hardware, I can assign a job (as mentioned above, the preconfigured "Deploy ML/BL/DL..."). But after the first reboot it ALWAYS boots WinPE managed (with the mentioned Problem). In PXE Configuration, I have set both Standard Boot Option and Initial Deployment-Boot Option to myX86 (in the DS-tab). But it keeps booting WinPE managed in the second boot.

Question:
1. Why does the WinPE Managed not detect hardware?
2. Why does PXE boot to WinPE managed (in second step)?

Thank You
Marcus

[Larry Lipkovitch]

I've got a similar issue.
I'm running RDP 3.5 on a DL380G3
I'm trying to install images on brand new BL465C blades
DHCP is running on RDP server
RDP server (DHCP) and BL465C's are on the same network segment.
I tried disabling NIC2 in the bios and also creating a custom boot with the latest drivers for the NICs (NC370i).
I'm still getting:
Restarting DHCP Client Service: retry 1 ... 20 then reboots the server.
Any suggestions?

[Gordon Leonard]

Larry

Post a screen shot of this (include the background image/desktop of the target server).