- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- ProLiant Deployment and Provisioning
- >
- Re: Unable to PXE Boot with WinPE
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-09-2006 05:00 AM
тАО11-09-2006 05:00 AM
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.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-12-2006 12:47 AM
тАО11-12-2006 12:47 AM
Re: Unable to PXE Boot with WinPE
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-13-2006 12:38 AM
тАО11-13-2006 12:38 AM
Re: Unable to PXE Boot with WinPE
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-13-2006 12:54 AM
тАО11-13-2006 12:54 AM
Re: Unable to PXE Boot with WinPE
I just sent an email to Danielle to see how things were progressing. Expect a follow-up email.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-22-2006 04:04 PM
тАО11-22-2006 04:04 PM
Re: Unable to PXE Boot with WinPE
Any ideas.I'm using RDP 3.1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-23-2006 12:27 AM
тАО11-23-2006 12:27 AM
Re: Unable to PXE Boot with WinPE
I do have the seem problem.
It fails on authenticating to de RDP Server.
Who has a solution for this??
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-23-2006 03:02 AM
тАО11-23-2006 03:02 AM
Re: Unable to PXE Boot with WinPE
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-23-2006 04:42 PM
тАО11-23-2006 04:42 PM
Re: Unable to PXE Boot with WinPE
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-28-2006 02:47 PM
тАО11-28-2006 02:47 PM
Re: Unable to PXE Boot with WinPE
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....
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-04-2006 04:29 AM
тАО12-04-2006 04:29 AM
Re: Unable to PXE Boot with WinPE
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-09-2007 09:01 AM
тАО02-09-2007 09:01 AM
Re: Unable to PXE Boot with WinPE
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-07-2007 12:56 AM
тАО03-07-2007 12:56 AM
Re: Unable to PXE Boot with WinPE
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-08-2007 04:49 AM
тАО03-08-2007 04:49 AM
SolutionRestarting 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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-11-2007 10:40 PM
тАО03-11-2007 10:40 PM
Re: Unable to PXE Boot with WinPE
no suggestions?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-11-2007 11:55 PM
тАО03-11-2007 11:55 PM
Re: Unable to PXE Boot with WinPE
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-12-2007 11:00 AM
тАО03-12-2007 11:00 AM
Re: Unable to PXE Boot with WinPE
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-13-2007 03:29 AM
тАО03-13-2007 03:29 AM
Re: Unable to PXE Boot with WinPE
***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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-11-2007 05:07 AM
тАО04-11-2007 05:07 AM
Re: Unable to PXE Boot with WinPE
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..."
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-11-2007 08:53 AM
тАО04-11-2007 08:53 AM
Re: Unable to PXE Boot with WinPE
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-13-2007 08:24 AM
тАО04-13-2007 08:24 AM
Re: Unable to PXE Boot with WinPE
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-13-2007 08:41 AM
тАО04-13-2007 08:41 AM
Re: Unable to PXE Boot with WinPE
Make sure you use an ISO burner that suppors ISO:1999 standards.
Michael Withrow - please kill this thread. :)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-10-2007 08:43 AM
тАО05-10-2007 08:43 AM
Re: Unable to PXE Boot with WinPE
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-10-2007 08:58 PM
тАО05-10-2007 08:58 PM
Re: Unable to PXE Boot with WinPE
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-11-2007 02:14 AM
тАО06-11-2007 02:14 AM
Re: Unable to PXE Boot with WinPE
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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-11-2007 05:48 AM
тАО06-11-2007 05:48 AM
Re: Unable to PXE Boot with WinPE
Post a screen shot of this (include the background image/desktop of the target server).