Client getting wrong DHCP address

[Jobos]

I've been given a Windows 7 laptop that will not connect to the network and keeps getting 169.254.x.x address (we use 10.2.x.x). At first I thought it was a wifi problem so removed and added the wifi profile but it still wouldn't connect but even using an ethernet cable it still gets the 169.254.x.x address. What I don't understand is the laptop is getting the correct DNS addresses and domain suffix so it must the connecting to DHCP right? There is nothing listed in DHCP or DNS for this machine name.

 

The laptop is listed in Ruckus and showing the 169.254.x.x address.

Edited February 4, 2019 by Jobos

[Jawloms]

169.254.x.x means it couldn't be assigned an IP address. Do you have availability in your scope still? You've not run out of addresses?

 

Stuart

[Jobos]

No still got 187 addresses free

[Shadow_Walker]

Disable and renable the adapter? Reinstall the adapter sometimes fixes odd ones for me.

[Jawloms]

"netsh winsock reset" at an elevated command prompt, then reboot. I've still no idea what it does, but it seems to fix a multitude of problems! Might work.....

[Jobos]

Disable and renable the adapter? Reinstall the adapter sometimes fixes odd ones for me.

Did that

 

"netsh winsock reset" at an elevated command prompt, then reboot. I've still no idea what it does, but it seems to fix a multitude of problems! Might work.....

And that

 

I thought giving a static address might work and it did until I removed the address and set it back to dynamic now I'm back with a 169.254 address.

[fredbayker]

The MAC address isn’t blacklisted (can’t remember the proper term) on the DHCP scope is it?

You could install wireshark in the client and sniff the packets to see if it’s sending/receiving the DHCP discover/ack/request packets

[ass17]

You need to rebuild the TCP stack as well as other things.

 

Open a CMD as administrator and run these following commands:

 

 

netsh winsock reset

 

netsh int ip reset

 

netsh interface ipv4 reset

 

netsh interface ipv6 reset

 

netsh interface tcp reset

 

netsh int reset all

 

ipconfig /flushdns

 

nbtstat -R

 

nbtstat -RR

 

netsh interface tcp set global autotuninglevel=disabled

 

netsh advfirewall reset

Edited February 4, 2019 by ass17

[MatthewL]

Can you tether it to a phone in hot spot mode, does it get an IP address then?

[Sonic007]

Can you delete the adapter and re-install it.

[leegcvcc]

Is the VLAN available on AP and switch?

[Jobos]

The MAC address isn’t blacklisted (can’t remember the proper term) on the DHCP scope is it?

You could install wireshark in the client and sniff the packets to see if it’s sending/receiving the DHCP discover/ack/request packets

 

No the laptop was working ok but I'm told it crashed and the student couldn't logon again

 

Can you delete the adapter and re-install it.

 

Tried that.

 

Is the VLAN available on AP and switch?

 

Yes.

 

@ass17 Thanks I'm back there tomorrow so will try that.

[Sonic007]

Have you checked IPV4 properties are set to Automatic?

 

Is there any anti-virus/firewall software like Mcafee or similar on there?

 

 

Check in services.msc that DHCP client is started.

Edited February 5, 2019 by Sonic007

[Jobos]

I've tried all of the above but no joy.

 

@Sonic007 the DHCP client won't start and reports error 5: access is denied.

 

I've googled the error and tried resetting permissions on HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dhcp and HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TcpIp as well as adding system and networkservice to C:\Windows\System32\dnsapi.dll so might be best to just reimage the machine.

[Sonic007]

I'd really be tempted to backup your files and re-image the machine. Sounds like dhcp is broken somewhere.

It isnt worth spending any more time on it.

[ricki]

I would try a usb WiFi dongle before reimagine and disable the onboard WiFi. If this does not work reimagine Richard

[Jobos]

I would try a usb WiFi dongle before reimagine and disable the onboard WiFi. If this does not work reimagine Richard

 

It has now been reimaged but before that a direct cable connection didn't work either.