6 replies
by peeweezee97 Accepted solution
by ---tk--- Accepted solution
When you type ipconfig, what do you get?
If you get a 169.x.x.x, windows is giving its self an address. When you plug the cable into the NIC, do you get link lights on the NIC? If not then I would say the cable is bad, the cable is not connected to the switch, or the port on the switch is bad. Or in some cases the NIC is malfunctioning but the OS doesn't realize it (happens every now and then).
In Device Manager, I would uninstall the NIC, the right click my computer, scan for new hardware, and reinstall the nic...
Try those trouble shotting steps and post up your results... or if you have already done them let us know...
by cg it Accepted solution
then the XP machine won't get an address.
There could be lots of reasons why a computer plugging into a network port doesn't get an address. One would be, ss mentioned no DHCP server.
by ---tk--- Accepted solution
by peeweezee97 Accepted solution
Tried to do what you suggested but in vain.
Additional information: The nic is on Dell OptiPlex 330, Windows xp service pack 2.
Tried to put in a separate nic but the pc was behaving the same; blinking yellow light and giving ip address of 192.168.1.2 (on releasing and renewing the ip address). Status; Sent 100 received 93 but other pc on the same network are just working properly
by churdoo Accepted solution
... I've seen a hosed WINSOCK cause a PC to not obtain a DHCP lease, especially if the rig has recently been hit with malware.
If you're at SP2 or higher, can do a
NETSH WINSOCK RESET
at a CMD prompt and reboot to see if that fixes.
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending