• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 243
  • Last Modified:

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.
0
jusery7
Asked:
jusery7
1 Solution
 
Chris MillardCommented:
It could be a faulty NIC in the laptop. Could you possibly get a USB->Ethernet adapter to try?
0
 
jonahzonaCommented:
Just for trouble shooting purposes, have you tried assigning a static address? Just to see if you could establish a connection?
0
 
askurat1Commented:
0
Automating Your MSP Business

The road to profitability.
Delivering superior services is key to ensuring customer satisfaction and the consequent long-term relationships that enable MSPs to lock in predictable, recurring revenue. What's the best way to deliver superior service? One word: automation.

 
jusery7Author Commented:
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.
0
 
jonahzonaCommented:
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.
0
 
jusery7Author Commented:
It looks like it may have been a CA issue.  We navigated to the certsrv site for our domain, and installed a certificate chain, then reinstalled the certificate for the computer, and it has been working for about 30 minutes now and through several reboots.
0
 
jonahzonaCommented:
Wow. Didn't see that one coming.

Good to hear. I am saving this one in the archives.
0
 
jonahzonaCommented:
You should close this thread so it gets put in the Solutions center.
0
 
jusery7Author Commented:
All of the solutions were helpful and ultimately led to my finding the CA fix.
0

Featured Post

The IT Degree for Career Advancement

Earn your B.S. in Network Operations and Security and become a network and IT security expert. This WGU degree program curriculum was designed with tech-savvy, self-motivated students in mind – allowing you to use your technical expertise, to address real-world business problems.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now