WDS DHCP Issue

Hello,

I am trying to use WDS to roll out an image to a large number of identical machines.  I have followed the step by step guide found here to setup WDS:
http://technet.microsoft.com/en-us/library/cc766320(WS.10).aspx

I have booted up a client vista 64 machine and configured the network boot priority in the bios.  The client gets an IP / establishes TFTP connection and then I pressed F12 to trigger the boot from WDS.  The computer has a white loading bar and the WDS server IP at the bottom of the screen which completes to 100%.  The Windows Vista rotating green bar on black background is then shown followed by the vista background with a message saying Please Wait.  I then get the following error message:

WDS Client: an error occurred while obtaining an IP address from the DHCP Server.  Please check to ensure there is an operational DHCP server on this network segment.

I press shift + F10 to load a command prompt and type IP config /ALL which shows no network adapters.  

I edited the boot.wim file by mounting the file and using peimg to import the LAN card RIS64\Vista\LAN\driver.inf file for the PC's (Asus P6T-SE Motherboards/Realtek Network Cards).  I then unmounted as per these instructions:

http://support.microsoft.com/kb/923834

When i boot the PC up now it does exactly the same as before.  Once in command prompt on the PC again I go to ipconfig and still nothing is shown.  I check the folder: x:windows\system32\drivestore\filerepository\drivername\  and i can see all the drivers in there fine.  I try to run drvload driver.inf and it fails to load.  I try WPEutil initializenetwork which responds succesful but again nothing happens, no IP, no NIC showing up in IPConfig etc.

Does anyone have any ideas where I am going wrong as ive spent ages on this now.

Thanks

LVL 1
cloughsAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

marcustechCommented:
Check to make sure there is not an additional DHCP server running on the router there as it may conflict with the server.

The boot rom should be sufficient to obtain an IP address from the server, therefore I think there may be some sort of a conflict here.
0
cloughsAuthor Commented:
Hello,
Thanks for your response.  There is only one DHCP running on a completely separate server on the network.  This gives addresses to all the clients on the network and also when the Bootp process takes place the client PC's get given an IP address correctly.  It then establishes TFTP communication and then starts to download the boot image.  It seems to be the inital step of this process that cant contact DHCP for some reason.  If I go to shift + F10 and do an IPconfig /renew the machine gets no addresses.  I believe this is because it cannot find its own loopback or ethernet adapter for some reason but I could be wrong as this is new to me.

Thanks
0
marcustechCommented:
I would expect it's looking for DHCP on the WDS server, although I haven't played with WDS thoroughly. Is there any chance you would be able to isolate the WDS server from the network, enable DHCP, and try the WDS service again?
0
Newly released Acronis True Image 2019

In announcing the release of the 15th Anniversary Edition of Acronis True Image 2019, the company revealed that its artificial intelligence-based anti-ransomware technology – stopped more than 200,000 ransomware attacks on 150,000 customers last year.

cloughsAuthor Commented:
Hello,

Yes I see what you are saying now, the DHCP service is not installed on the WDS server at the moment.  This was not part of the step by step guide so I assumed this wasnt necessary.  There is a Network Settings tab where you set an IP address range for multicast to use.  I assume it is like RRAS where by WDS gives out the IP as required from its own separate pool and ignores the LAN DHCP server.

Unfortunately I cant isolate the server very easily as WDS is running on one of our DC's.

Thanks
0
cloughsAuthor Commented:
A further update to this query, I had to modify the UDP port ranges from the defaults to 62000 - 63000 in order to fix the DNS conflict bug which I found earlier on in the WDS deployment scenario.  This shouldnt affect DHCP though as far as I am aware.
0
cloughsAuthor Commented:
A further update to this issue, I have installed the DHCP on the WDS server itself and disabled the original DHCP server.  It finds the new DHCP server at PXEBoot as it did before but gives the same error about not being able to get an IP address from DHCP as it loads the windows background.  Anyone any ideas?

Thanks
0
cloughsAuthor Commented:
found the answer to this - the imagex command was importing the drivers to the wrong version of vista... i had to use a different instance other than 1.

0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
dcadlerCommented:
Cloughs,

I am having the exact same problem that you described in your initial post. However, in this same network, I have successfully ran WinPE boot.wim from WDS on other computers types, Including Asus M2N-MS SE Plus, HP 2140 Netbook and Lenovo G530. This issue seems specific to one particular computer type, 2GoPC netbook that has a Realtek 8136 chip for the onboard NIC. I tried running drvload driver.inf with the driver.inf actually the Netrtle.inf that is the driver used by the 2GoPC. When I did this, I got an error...

Unable to load e:\driver.netrtle.inf <error 0x80070103>

Any suggestions?

Dave
0
cloughsAuthor Commented:
Have you tried these commands before?

imagex.exe /mountrw C:\Temp\PE\boot.wim 1 C:\Temp\PE\mount
(mount the image)

peimg.exe /inf=C:\Temp\PE\VMWNIC\vmxnet.inf C:\Temp\PE\mount\Windows
(add a driver)

peimg.exe /inf=C:\Temp\PE\VMWNIC\vmware-nic.inf C:\Temp\PE\mount\Windows
(add another driver)

imagex.exe /unmount C:\Temp\PE\mount /commit
(unmount/apply changes to the image)

Please note the "1" in the first command stands for the instance of windows i.e. the version.  I had to try 1 and 2 to eventually get mine working.  The number dictates vista busniess/ultimate and so on..

Thanks

0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.