Can't set a lan adapter to fixed IP address

I have a Win 7 PC with a LAN adapter that needs a static IP address: 192.168.0.210. Previously this PC was set up with the static IP address. After a windows update, the adapter will not function properly with the static address assigned.

I can put in the static address into the adapter properties. However, when I do an ipconfig from the command prompt, it shows the adapter as a 169.x.x.x address.

The adapter will pick up a valid address from DHCP and function properly. Unfortunately, I need this PC to have a static address.

I removed the Windows update. I used system restore to put PC back to a known good working date.
I uninstalled the LAN adapter from the device manager. I did not delete the driver. Scanned and reinstalled the adapter.

I am thinking about replacing the adapter. Any other suggestions for this strange problem?



I have seen this happen on a network where we use all static IPs and no DHCP at all.
In one case the IP address being assigned was a duplicate.
There was no warning about the duplicate that one would normally expect. It just didn't work.



The 169.xxxx address is very odd. That is what you will typically get when you have an adapter set for DHCP and it is unsuccessful at getting an address.

When you set the static address and reboot, does the configuration page (where you set the address) still show the static address?



Is this computer a member of a domain that has policy dictating DHCP?
I would configure the DHCP server to include 192.168.0.210 into its scope or a new scope and reserve the address 192.168.0.210 for the specific NIC MAC.
It will always get the same address that way, but the settings in the NIC properties can be set to DHCP.
If it still doesn't work after that, you probably have a failed NIC that just happened to have failed at the same time as the update, or a damaged driver for the NIC.
At that point download the correct driver for the NIC from the manufacturer of the NIC not Microsoft and ignore any WHQL messages you get about the driver not being windows certified and see if the NIC works correctly.
Still no joy, then buy a new NIC would be my recommendation. They are too cheap to mess with very long.



I have seen this happen on a network where we use all static IPs and no DHCP at all.
In one case the IP address being assigned was a duplicate.
There was no warning about the duplicate that one would normally expect. It just didn't work.



good thought Fred. Try doing an NSlookup for the IP address from the command prompt on another workstation.
Also there could be residual NETBIOS information of another workstation that used to be on .210 depending on the architecture of your network.
Flushing the DNS and ARP cache of the other workstations, restarting the DHCP service, (or Router if that is your DHCP server), and even cycling power on your switch to flush your MAC / IP relationship to the NIC in question might help.



Have you tried:
Click Start > All Programs > Accessories, right-click on Command Prompt and choose Run as administrator. ...
At the command prompt type: netsh winsock reset catalog and press [Enter].
Next type: netsh int ip reset reset.log and press [Enter].

Share this

Related Posts

There was an error in this gadget