How to recover lost LAN adapter access

Have lost all lan access after updating a graphics driver, and deleting an unused TheGreenbow VPN application.  Windows is showing a possible lan adapter driver issue.

I have two adapters on the mother board, same results on either one.

I did a system restore which put back the old graphics driver... no effect.

I rolled back the lan adapter driver and re-installed the current... no effect. (Marvel Yukon 88E8056)

IPv4 is set to a static address.  Status screen shows it not connected.

Device manager shows the adapter as being ok and enabled.

IPconfig /all is not showing the adapter at all.

My conclusion is that the uninstall of TheGreenbow has removed a needed item, but what?

Any ideas?

Paul



PaulWolpertAsked:
Who is Participating?
 
digitapConnect With a Mentor Commented:
perhaps you have a hinky driver.  use this procedure to remove drivers for hardware that is no longer installed.

http://support.microsoft.com/kb/315539

also consider resetting TCP IP.

Reinstall and reset TCP/IP (Internet Protocol) for Windows 7 (32 and 64):

1.Click on Start button. 2.Click on Accessories. 3.Right click on Command Prompt and select Run as Administrator. 4.Type netsh int ip reset c:\resetlog.txt in the Command Prompt shell, and then press the Enter key. Do not restart computer. 5.Type winsock reset in the Command Prompt shell, and then press the Enter key. 6.Restart the computer.

You'll find a log with the changes in c:\resetlog.txt.
0
 
moon_blue69Connect With a Mentor Commented:
can you try uninstalling it from device manager and click on scan for hardware changes and see what it brings up?. Is youd device disabled by any change check that in device manager and please check in network connections as well.
0
 
PaulWolpertAuthor Commented:
Thank you both for your responses.

Uninstalled in device mgr, the scan found it and reinstalled.  (I had tried both the old driver and a newer one made no difference.

Ran the ip and winsock resets, no difference.

Ipconfig /all is still not showing the device.  A ping to it's static address just returns a timeout.

Device Mgr;  Device Working properly, no conflicts.

Network Connection; Enabled, IPv4 no connection, Ipv4 set to static address.

The newest driver for the NIC has been in place and working without problems since sometime in July of this year.

Any other thoughts would be appreciated.

Paul
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
PaulWolpertAuthor Commented:
I did fine the following in the troubleshooting log.

Windows couldn't automatically bind the IP protocol stack to the network adapter
0
 
digitapCommented:
on a long shot, what do you think of this link?

http://bit.ly/gptI35
0
 
PaulWolpertAuthor Commented:
Ended up blowing the client away, and reinstalled the client. Problem resolved.
0
 
digitapCommented:
glad you got it and thanks for the points!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.