WdsClient: An error occurred while obtaining an IP address from the DHCP server.

Question

_{Tuesday, March 8, 2016 10:21 AM}

Hi!

I'm trying to deploy a WDS server for a while, but I get the next error (but then in dutch): **WdsClient: 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.*The server I work with is Server 2012R2.
*

What I have tried:

• Downloaded and implemented all 16 ethernet drivers for the client (HP Probook 430 G2) by the WDS "add drivers" feature.
• Implemented all drivers from an official W7 "Applications and Driver Recovery DVD" in WDS. (this solved an missing driver error earlier)
• tried a different boot.wim and install.wim from another Windows 7 pro .iso.
• Tried 4 different HP computers (3 laptops and 1 desktop). one of these laptops is my own computer, which worked fine by another WDS server from my last traineeship.
• Installed the server on a different computer.
• Reinstalled the Server like 4 times totally.
• Rebuilded everything in VMware Workstation, everything works fine in here untill I connect a physical computer by peer-to-peer cable, than I get the error again (drivers from HP site and CD as told above are added).
• The different networks I tried: a cisco switch with 4 clients and 1 server attached, nothing more. I read about the portforwarding problem in cisco switches, so I tried peer-to-peer between a physical Server and client and like I said between a virtual switch in vmware.
• First installed the server with the DHCP role, tested the connections, IP addresses are leased and I can ping while clients are in Windows 7.
• I get the error while running the setup from the boot.wim, so I have a connection with the server, however if I start a command prompt by SHIFT+F10 and put "ipconfig" in, the results are pretty empty: "Windows IP-configuration". Even after a few minutes I have no IP configuration. Results of the command "ipconfig /renew" is: "An error occured while releasing interface Loopback Pseudo-Interface 1: The system cannot find the file specified."
• DHCP configuration on active scope: 60 "PXEClient" and 66 for the ip address of my WDS server.
• DHCP properties in WDS: "Do not listen on DHCP ports" and "Configure DHCp options to indicate that this is also a PXE server" are enabled because my Windows DHCP role is active beside the WDS role on the same phisical server.
• Configured the \windows\system32\startnet.cmd succesfully in a mounted image 3 times from different suggestions, doesn't help me either.

I read aslwell that it could be something with HP. I only have 1 DHCP server active to be clear. I'm not using DNS. My teachers at school can't help me, I hope someone here can! I would be amazing happy if the problem wille be solved.

Thanks!

All replies (3)

_{Wednesday, March 9, 2016 9:06 AM ✅Answered}

Hi Alex,

>> I get the error while running the setup from the boot.wim, so I have a connection with the server, however if I start a command prompt by SHIFT+F10 and put "ipconfig" in, the results are pretty empty: "Windows IP-configuration". Even after a few minutes I have no IP configuration. Results of the command "ipconfig /renew" is: "An error occured while releasing interface Loopback Pseudo-Interface 1: The system cannot find the file specified."

According your description,it seems to be a driver issue. As far as I know,you should  extract and only add the  corresponding Drivers into the boot image,if you added them all, you will getting hardware errors on the PC.

  Best Regards,

Cartman

Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected].

_{Tuesday, March 8, 2016 11:09 AM}

Update:

While in the command prompt when the error occurs I can ping 127.0.0.1 with a successful reply.

_{Thursday, March 10, 2016 9:37 AM}

Hi Cartman,

Thank you very much! It worked. I had to delete all drivers and added a new one with a new boot image. Now with only 1 NICDRV from another HP Probook it worked. You made my day perfect.

I still think the IP error I get is a bit strange for a wrong (or too many) drivers.

Best Regards,

Alex