WDS Client : Unable to Obtain IP

[Darylrese]

I just tried a Windows 8.1 boot image and that has the same error.

 

I'm going to also create a x32 boot image for Windows 7 just to test.

 

I cant get into Windows to check the driver ID at the moment as i wiped the SSD when installing Windows 7 through the Windows 10 boot image.

[dapaulio]

maybe it is a conflicting driver?

 

if you create a new windows 7 boot.wim and only inject the 400 G3 nic driver, does that work?

[Darylrese]

Nope, i have already tried a new boot image with only the drivers for this PC and no luck.

 

Just trying a 32 bit boot image as we speak to see if it likes the 32 bit driver

[dapaulio]

just to eliminate a faulty NIC have you tried deploying on another G3? you would be extremely unluck if you picked the only one wit a NIC fault

 

Another suggestion is the NIC firmware upto date?

 

It does sound like nothing more than a network driver issue so i would suggest installing windows manually from a cd. confirm the vendor and device id and go from there. thinking back i did actually have to do this for my G2's took me ages to find the correct driver, turned out that HP had the wrong driver for the hardware

[Darylrese]

OK so the Windows 7 x86 boot image didnt work either.

 

I'm going to install Windows 7 on the SSD in another computer and install it back into the ProDesk 400 to see if the driver is missing once complete. I'll then try and install the driver once i am in Windows 7 to verify its the correct one.

 

I only have 1 of the new ProDesk 400's at this point as i was trying them out before i bulk order. At this rate ill be buying some older chipset PC's just to avoid all the hassle!

Edited May 26, 2016 by Darylrese

[Darylrese]

OK strange.

 

So i built the SSD in another machine, put it into the ProDesk 400 and the KB and mouse dont work because no USB 3.0 driver. Installed that using a PS2 keyboard and the network driver is already installed and working without installing one from my USB.

 

So here is a screenshot of device manager after installing all the drivers i have.

 

 

The only thing i can see is missing is PCI drivers. In the driver info for the network adaptor, it lists PCI\VEN_10EC&DEV_8168&SUBSYS_8062103&REV_15 but in the .inf for the driver that is not present;

 

; 8168

%RTL8168.DeviceDesc% = RTL8168.ndi, PCI\VEN_10EC&DEV_8168&REV_01

%RTL8168.DeviceDesc% = RTL8168.ndi, PCI\VEN_10EC&DEV_8168&SUBSYS_816810EC&REV_01

%RTL8168.DeviceDesc% = RTL8168.ndi, PCI\VEN_10EC&DEV_8168&SUBSYS_30B6103C&REV_01 ;HP Notebook

%RTL8168.DeviceDesc% = RTL8168.ndi, PCI\VEN_10EC&DEV_8168&SUBSYS_30CC103C&REV_01 ;HP Notebook

[Burconix_Greg]

http://ftp.hp.com/pub/softpaq/sp74501-75000/sp74584.exe

 

C:\SWSetup\SP74584\WIN7\64

 

Its a special "HP Enzo" driver

 

hp64win7.inf

%RTL8168.DeviceDesc% = RTL8168HS5WOLHideType2.ndi, PCI\VEN_10EC&DEV_8168&SUBSYS_8062103C&REV_15 ;HP_Enzo

[Darylrese]

Already got that one injected mate, not working.

 

I tried manually dismounting the image and adding it and that didn't work either.

[Burconix_Greg]

If you extract it in windows on the PC in question, Device Manager, Right click Update Driver

 

Browse Manually to: C:\SWSetup\SP74584\WIN7\64

(assuming OS is x64)

 

Will it install that specific driver?

[Darylrese]

Yep working fine if i run the installer.

Edited May 26, 2016 by Darylrese

[Darylrese]

OK think im getting somewhere.

 

I just made another clean x64 boot image with no drivers atall, then it said no network driver found. I installed only the newest network driver and its started!!!!

 

I'm going to add the drivers 1 by 1 until i find the culprit. Looks like a conflicting driver somewhere.

[dapaulio]

looks like we are getting somewhere

[Darylrese]

WOOHOO it's building! Just need to check if there are any drivers missing once complete.

[dapaulio]

WOOHOO it's building! Just need to check if there are any drivers missing once complete.

 

what was the issue then conflicting driver in the boot.wim?

 

Glad you got it sorted

[gtg93]

FYI / if anyone is interested - I had a similar issue at one of my sites... Rather than a driver not working / network connection, it was just taking a little longer to get an IP than the timeout limit. There's a sneaky way round it in which you get the machine to ping the server and wait for a reply before continuing the WDS sequence. Info here:

 

WdsClient - An error occurred while obtaining an IP address from the DHCP server. | The Rambling Techie

[newpersn]

When I get this problem I open up command prompt and do ipconfig renew. Seems to help it along a little for me.