169.xxx.xxx.xxx IP Address
I manage a network for a small Catholic School. In one computer lab there are two switches for the 30+ computers. I have two computers sitting right next to each other. One is getting a valid IP address and the other is getting one in the 169,xxx range. They are connected to the same switch. Here is what I have done and none of it hassolved the problem:
1) unplugged the power from the modem, router and switch and then reconnected each in order;
2) Plugged the 169 computer into the same port in the switch that the 192 computer had been using;
3) Plugged the cable from the 192 computer into the 169 PC;
4) Tried to release and renew the IP address;
5) Uninstalled and reinstalled the NIC.
Any suggestions what I need to do to solve this problem. The PC is Windows 7 Pro.
Thank you!
Robert
1) unplugged the power from the modem, router and switch and then reconnected each in order;
2) Plugged the 169 computer into the same port in the switch that the 192 computer had been using;
3) Plugged the cable from the 192 computer into the 169 PC;
4) Tried to release and renew the IP address;
5) Uninstalled and reinstalled the NIC.
Any suggestions what I need to do to solve this problem. The PC is Windows 7 Pro.
Thank you!
Robert
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Scott Thomson
Lastly go into the properties of the network device (change adapter settings) in the network sharing window and make sure that the machine is set to automatically obtain ip address. It sounds like it may be set to manual or something.
Since the machine is not being issued an IP, is it possible that your DHCP addresses are exhausted? If you assign it a static IP (outside the DHCP scope), are you able to communicate to the other machines?
Just rearranging the order for your troubleshooting mentioned above and adding one more command
- Check your DHCP server for available addresses.
Default lease period is usually 8 days. There may be devices no longer on the network with IP address lease still active.
- If possible, connect the computer to a router running DHCP to see if the NIC is the problem.
- Reset your NIC
Disable and re-enable the NIC
From elevated dos prompt, run netsh winsock reset and netsh interface ip reset
The 169.... is a class B APIPA address that a device auto generates by itself if it's not able to obtain ans address from a DHCP server from 169.254.0.1 to 169.254.255.254 with a 255.255.0.0 subnet mask
- Check your DHCP server for available addresses.
Default lease period is usually 8 days. There may be devices no longer on the network with IP address lease still active.
- If possible, connect the computer to a router running DHCP to see if the NIC is the problem.
- Reset your NIC
Disable and re-enable the NIC
From elevated dos prompt, run netsh winsock reset and netsh interface ip reset
The 169.... is a class B APIPA address that a device auto generates by itself if it's not able to obtain ans address from a DHCP server from 169.254.0.1 to 169.254.255.254 with a 255.255.0.0 subnet mask
check "client for microsoft networks" isn't missing from the "this connection uses the following items:" on the properties page of the adapter.
also does the nic work if its manually assigned an IP ? are you getting the connection and activity lights on the nic when you plug in the eth cable ?
also does the nic work if its manually assigned an IP ? are you getting the connection and activity lights on the nic when you plug in the eth cable ?
If you try to configure static IP - outside of DHCP scope, does the client communicate with others on the net, can you do ping?
As a follow up to my previous post above. What steps have you done so far and what has been the outcome?
-Rafael
-Rafael
@RobertEhinger - Thanks, and I was happy to help.