Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Windows XP SP3 - No network connectivity


  • Please log in to reply
5 replies to this topic

#1 Tuxh

Tuxh

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:09:48 AM

Posted 27 July 2010 - 04:40 PM

I'm one of you... I do this for a living, and can't for the life of me get to the bottom of this problem. I figured I'd suck it up and post a request for help before reloading Windows to a secondary partition.

I have researched the event viewer messages and nothing that turns up seems applicable.
With that being said:

I have a windows xp sp 3 laptop, that all of a sudden has lost all of it's networking ability.

In Device Manager I see yellow exclamation marks on the following:
1394 Net Adapter #2
Broadcom NetXtreme 57xxGigabit Controller
Broadcom NetXtreme 57xxGigabit Controller - Packet Scheduler Miniport
Direct Parallel
Intel® PRO/Wireless 3945ABGG Network Connection
Intel® PRO/Wireless 3945ABGG Network Connection - Packet Scheduler Miniport
WAN Miniport (IP)
WAN Miniport (IP) - Packet Scheduler Miniport
WAN Miniport (L2TP)
WAN Miniport (PPOE)
WAN Miniport (PPTP)

In Event Viewer I see the following system events in this order

The Background Intelligent Transfer service terminated with service-specific error 2147952450 (0x80072742)

The IPSEC driver service failed to start due to the following error:
The system cannot find the file specified

The TCP/IP Protocol Driver service depends on the IPSEC driver service which failed to start because of the following error:
The system cannot find the file specified

The AFD service failed to start due to the following error:
The system cannot find the file specified

The Network Location Awareness (NLA) service depends on the AFD service which failed to start due the following error:
The system cannot find the file specified



I have run Malware Bytes without updating the system files yet. It found nothing.

BC AdBot (Login to Remove)

 


#2 Tuxh

Tuxh
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:09:48 AM

Posted 28 July 2010 - 09:46 PM

So it's been over 24 hrs and 50+ views - I don't frequent these forums, so I'm not sure if I'm being impatient or not.

#3 Budapest

Budapest

    Bleepin' Cynic


  • Moderator
  • 23,579 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:11:48 PM

Posted 03 August 2010 - 01:34 AM

Log on as an administrator, go Start > Run and type: "cmd". In the window that appears type: "netsh winsock reset". When the program is finished, you will receive the message: "Successfully reset the Winsock Catalog. You must restart the machine in order to complete the reset." Close the command box and reboot your computer.

Go Start > Run > type: "cmd" In the window that appears type: "ipconfig /flushdns". Close the command box.

Go Start > Control Panel > Network Connections. Right click on your default connection, usually Local Area Connection or Dial-up Connection if you are using Dial-up, and and choose Properties. Double-click on the Internet Protocol (TCP/IP) item. Select the radio button that says "Obtain DNS servers automatically". Reboot.

Warning: Some Internet Service Providers need specific DNS settings. You need to make sure that you know if such DNS settings are required before you make this change.
The power of accurate observation is commonly called cynicism by those who haven't got it.

—George Bernard Shaw

#4 Crenor

Crenor

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:09:48 AM

Posted 23 August 2010 - 09:10 AM

I am having the exact same issue. The fix above does nothing.
I am thinking it is format time.

EDIT
I found out what the issue was, but the solution is still format :/
Ndis.sys was missing from C:\Windows\System32\Drivers
When I placed it back in, I tried starting up a few of the services, a few started to work, I was hopfull. Then it BSOD on me starting up one.
I fixed that and then another did the same thing.

Sure it could be fixed, but not faster than a format.

Edited by Crenor, 23 August 2010 - 10:34 AM.


#5 Tuxh

Tuxh
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:09:48 AM

Posted 23 August 2010 - 01:42 PM

The above fix has not worked for me either. I'm still researching.

#6 Budapest

Budapest

    Bleepin' Cynic


  • Moderator
  • 23,579 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:11:48 PM

Posted 23 August 2010 - 04:01 PM

Try these:

http://www.cexx.org/lspfix.htm
http://www.spychecker.com/program/winsockxpfix.html
The power of accurate observation is commonly called cynicism by those who haven't got it.

—George Bernard Shaw




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users