missing files for network connectivity

mccoene · 06-05-2009, 08:24 PM

Been working on my son's computer for the last several days after it was infected with many virus, trojans, rootkits. Believed I've killed everything, with use of many tools. Now can't load network drivers. Know I'm missing ndis.sys from C:\windows\system32\drivers folder. Not sure if anything else. Believe that was one of the files that was infected. Registry scan comes out clean now. OS is WinXP Home Edition, with SP2. Reapplied SP2 today. no luck. I can get ndis.sys back in folder, but as soon as I boot, get BSOD before I get Welcome Screen. If I remove ndis.sys from drivers folder, boots fine and I can access everything but NO network. In fact, my adapters are all in Device Manager, but marked with Exclamation marks. When I go to Network Connections, all that is there is Dial-Up & Virtual Private Network. No Local Area Network, and I cannot install one. Event ID: 7026 The following boot-start or system start drivers failed to load:
AFD
IPSEC
MRxSMB
NetBIOS
NetBT
SYMTDI
TCP/IP
Tcpip6

NEED HELP.... WHERE DO I GO FROM HERE?

shehzadarshad · 06-06-2009, 07:37 AM

this is totaly lan card driver problem you should find out right driver for it . when you see the yellow mark is gone in devise manager then it will work and will appear in your computers my network places thanks

**johnwill** · 06-06-2009, 08:24 AM

Start with an SFC run to replace any missing/damaged files: SFC Tutorial

mccoene · 06-06-2009, 01:55 PM

ran sfc /scannow one event 64021 referring to C:\windows\system32\rasmans.dll having a bad signature. was replaced with version 5.1.2600.2180

**johnwill** · 06-07-2009, 02:05 PM

Did it help with the issue?

Next, I'd try the stack reset after the SFC repair.

TCP/IP stack repair options for use with Windows XP with SP2/SP3.

Start, Run, CMD to open a command prompt:

In the command prompt window that opens, type type the following commands:

Note: Type only the text in bold for the following commands.

Reset TCP/IP stack to installation defaults, type: netsh int ip reset reset.log

Reset WINSOCK entries to installation defaults, type: netsh winsock reset catalog

Reboot the machine.

mccoene · 06-10-2009, 06:47 PM

None of those suggestions has helped. When I rename the Ndis.sys file I can reboot the computer fine. When it's named ndis.sys (C:\windows\system32\drivers), then I get a BSOD on boot. Starts to load Windows XP and then goes to a BSOD ending in STOP: 0x0000007E (0xC0000005, 0x80599A59, 0xF8B2B390)

Nothing follows that (as a Normal BSOD would have a file or something that it 'caught')

The only way to recover is to boot into SAFE MODE (safe mode with networking gives same error); rename the NDIS.SYS file to something else, then Windows loads fine, except that there is no networking. MISSING THE LOCAL AREA CONNECTIONS completely, and the network adapters all have the yellow exclamations in Device Manager.

I'm about ready to throw the thing out the window!!!!

bwire · 06-10-2009, 09:54 PM

MICROSOFT Help and Support

How to enable NDIS

http://support.microsoft.com/search/...%3D1033&mode=r

networkthinking · 06-18-2009, 02:21 PM

Hello,
I'm in the same boat. The article linked with for Windows 2000 and running XP Sp3 here.

Summary, whenever we put NDIS.SYS back, the machine blue screens. This PC had a rootkit, vundu, etc but think it's cleaned except for the NDIS.SYS error.

Any suggestions?

Wally

06-05-2009, 08:24 PM	#1 (permalink)
mccoene Registered User Join Date: Oct 2004 Location: Florida Posts: 3 OS: WIN XP SP3	missing files for network connectivity Been working on my son's computer for the last several days after it was infected with many virus, trojans, rootkits. Believed I've killed everything, with use of many tools. Now can't load network drivers. Know I'm missing ndis.sys from C:\windows\system32\drivers folder. Not sure if anything else. Believe that was one of the files that was infected. Registry scan comes out clean now. OS is WinXP Home Edition, with SP2. Reapplied SP2 today. no luck. I can get ndis.sys back in folder, but as soon as I boot, get BSOD before I get Welcome Screen. If I remove ndis.sys from drivers folder, boots fine and I can access everything but NO network. In fact, my adapters are all in Device Manager, but marked with Exclamation marks. When I go to Network Connections, all that is there is Dial-Up & Virtual Private Network. No Local Area Network, and I cannot install one. Event ID: 7026 The following boot-start or system start drivers failed to load: AFD IPSEC MRxSMB NetBIOS NetBT SYMTDI TCP/IP Tcpip6 NEED HELP.... WHERE DO I GO FROM HERE?

06-06-2009, 07:37 AM	#2 (permalink)
shehzadarshad Registered User Join Date: Jun 2009 Posts: 4 OS: Server 2008	Re: missing files for network connectivity this is totaly lan card driver problem you should find out right driver for it . when you see the yellow mark is gone in devise manager then it will work and will appear in your computers my network places thanks

06-06-2009, 08:24 AM	#3 (permalink)
johnwill Manager, Networking Forums Join Date: Sep 2002 Location: S.E. Pennsylvania, US Posts: 41,607 OS: Windows 7, XP-Pro, Vista, Linux Blog Entries: 1	Re: missing files for network connectivity Start with an SFC run to replace any missing/damaged files: SFC Tutorial __________________ If TSF has helped you, Tell us about it! or Donate to help keep the site up! Microsoft MVP - Windows Desktop Experience

06-06-2009, 01:55 PM	#4 (permalink)
mccoene Registered User Join Date: Oct 2004 Location: Florida Posts: 3 OS: WIN XP SP3	Re: missing files for network connectivity ran sfc /scannow one event 64021 referring to C:\windows\system32\rasmans.dll having a bad signature. was replaced with version 5.1.2600.2180

06-07-2009, 02:05 PM	#5 (permalink)
johnwill Manager, Networking Forums Join Date: Sep 2002 Location: S.E. Pennsylvania, US Posts: 41,607 OS: Windows 7, XP-Pro, Vista, Linux Blog Entries: 1	Re: missing files for network connectivity Did it help with the issue? Next, I'd try the stack reset after the SFC repair. TCP/IP stack repair options for use with Windows XP with SP2/SP3. Start, Run, CMD to open a command prompt: In the command prompt window that opens, type type the following commands: Note: Type only the text in bold for the following commands. Reset TCP/IP stack to installation defaults, type: netsh int ip reset reset.log Reset WINSOCK entries to installation defaults, type: netsh winsock reset catalog Reboot the machine. __________________ If TSF has helped you, Tell us about it! or Donate to help keep the site up! Microsoft MVP - Windows Desktop Experience

06-10-2009, 06:47 PM	#6 (permalink)
mccoene Registered User Join Date: Oct 2004 Location: Florida Posts: 3 OS: WIN XP SP3	Re: missing files for network connectivity None of those suggestions has helped. When I rename the Ndis.sys file I can reboot the computer fine. When it's named ndis.sys (C:\windows\system32\drivers), then I get a BSOD on boot. Starts to load Windows XP and then goes to a BSOD ending in STOP: 0x0000007E (0xC0000005, 0x80599A59, 0xF8B2B390) Nothing follows that (as a Normal BSOD would have a file or something that it 'caught') The only way to recover is to boot into SAFE MODE (safe mode with networking gives same error); rename the NDIS.SYS file to something else, then Windows loads fine, except that there is no networking. MISSING THE LOCAL AREA CONNECTIONS completely, and the network adapters all have the yellow exclamations in Device Manager. I'm about ready to throw the thing out the window!!!!

06-10-2009, 09:54 PM	#7 (permalink)
bwire Registered User Join Date: Nov 2007 Posts: 34 OS: XP / VISTA	Re: missing files for network connectivity MICROSOFT Help and Support How to enable NDIS http://support.microsoft.com/search/...%3D1033&mode=r Last edited by bwire; 06-10-2009 at 09:59 PM.

06-18-2009, 02:21 PM	#8 (permalink)
networkthinking Registered User Join Date: Jun 2009 Posts: 1 OS: XP SP3	Re: missing files for network connectivity Hello, I'm in the same boat. The article linked with for Windows 2000 and running XP Sp3 here. Summary, whenever we put NDIS.SYS back, the machine blue screens. This PC had a rootkit, vundu, etc but think it's cleaned except for the NDIS.SYS error. Any suggestions? Wally