jusery7
asked on
Limited or no connectivity
I have a laptop in a Windows Domain that is connecting via wireless but will not connect to our wired LAN. This is a new issue as it has always worked before. I have uninstalled the NIC, updated the drivers, ran the repair, verified that Automatically Detect DHCP and DNS are selected, run an IPCONFIG /flushdns, and IPCONFIG /registerdns, disjoining it from the domain, rejoining it to the domain, re-imaging the computer completely, and running enough MS Fixit tools to choke a donkey. The ethernet connection will work sporadically for 2-20 minutes, but will always lose its IP and go back to the APIPA address in the 169.x.x.x. range.
It could be a faulty NIC in the laptop. Could you possibly get a USB->Ethernet adapter to try?
Just for trouble shooting purposes, have you tried assigning a static address? Just to see if you could establish a connection?
Try these fixes: http://www.click2web.com/169.php
ASKER
Yes, I did add a static address, but had the same limited results. I am testing a USB NIC on it now and it seems to be working. I'm going to be very disappointed if it is a faulty NIC.
If a static address did not give you a connection, I would be close to saying its dead.
However, the link that was posted above does detail how to repair the Winsock registry entries. Maybe try that?
Also, just wanted to make sure you have tried this connection with multiple Cat5 cables in multiple ports that you know are functioning. Just in case.
However, the link that was posted above does detail how to repair the Winsock registry entries. Maybe try that?
Also, just wanted to make sure you have tried this connection with multiple Cat5 cables in multiple ports that you know are functioning. Just in case.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Wow. Didn't see that one coming.
Good to hear. I am saving this one in the archives.
Good to hear. I am saving this one in the archives.
You should close this thread so it gets put in the Solutions center.
ASKER
All of the solutions were helpful and ultimately led to my finding the CA fix.