Avatar of JScho10
JScho10
Flag for United States of America asked on

Win7 Pro computer Network Adapter Not Responding

Working on a Powerpoint file and the computer network connection stopped. Lost connection to the network drive.

Restarted computer, and seems like network adapter is not responding.  Have lights connecting to Ethernet and blinking.  Changed Ethernet connections. No joy.  Ping and get unable to contact IP driver-general failure.

Go to Control Panel Settings / Network Sharing Center / and Get "View your network information" Unknown.  

Where would you suggest I start with troubleshooting.  Thanks!
DesktopsPCWindows 7

Avatar of undefined
Last Comment
JScho10

8/22/2022 - Mon
SOLUTION
John

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
Rob Hutchinson

What model computer is it?

Does it have both a wireless adapter and a LAN adapter?
JScho10

ASKER
Answers for John:
1.  Followed your instructions and got the following responses in cmd.exe:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Windows\system32>netsh int ip reset c:\resetlog.txt
Reseting Global, OK!
Reseting Interface, OK!
Restart the computer to complete this action.

C:\Windows\system32>ipconfig /flushdns

Windows IP Configuration

Could not flush the DNS Resolver Cache: Function failed during execution.

C:\Windows\system32>net stop dnscache
The DNS Client service is not started.

More help is available by typing NET HELPMSG 3521.


C:\Windows\system32>net start dnscache
System error 1068 has occurred.

The dependency service or group failed to start.


C:\Windows\system32>

2. Restarted computer with no improvement.

3. Ran Malwarebytes and found no virus's or malware.

4. Tried installing a USB Network Card with same problem.

Answer for Rob:

The computer is an HP Pro 3500 (Mfg #D3K31UT#ABA) no wireless.
ASKER CERTIFIED SOLUTION
JScho10

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
SOLUTION
Log in to continue reading
Log In
Sign up - Free for 7 days
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
John

C:\Windows\system32>net stop dnscache
 The DNS Client service is not started


This says DNS is not working or cannot start.

Open an admin command prompt and run:

SFC /SCANNOW twice. Allow to complete.

Now shut down the computer (not restart). Now start it.  Run TCP/IP Reset again and now check if you can restart DNS. DNS not starting or resolving will cause internet issues.

Look in c:\windows\system32\drivers\etc\hosts and make sure all entries in here are comments only.
Experts Exchange has (a) saved my job multiple times, (b) saved me hours, days, and even weeks of work, and often (c) makes me look like a superhero! This place is MAGIC!
Walt Forbes
JScho10

ASKER
John: DNS Client is now working since I changed to normal startup in config and all the startup files loaded. (see my previous post)

Rob: There is no wireless card.

Thank you all for your input!
JScho10

ASKER
Wasn't able get a direct solution from the advice but got me on the right track by following the troubleshooting procedure.   Changing the msconfig fixed the problem.  Don't know how it occurred though.