Network Access After Norton Anti-Virus Install Added 12/9/03 Sometimes you can't access a WinXP computer after

installing Norton Anti-Virus. There might be a variety of errors at the other computer depending on the operating system. On the XP computer, in the Event Viewer / System log, there will be the following error: The server's configuration parameter "irpstacksize" is too small for the server to use a local device. 1. Start Regedit 2. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\pa rameters 3. Edit the IRPStackSize 4. Give it a value of 15 5. Reboot the computer Fixing Cryptographic Services Error Added 12/8/03 If you get an error about the Cryptographic services when trying to apply the Security Updates or Service Pack 1, run the following from Start / Run - note, you might want to just cut and paste the text. net stop cryptsvc ren %systemroot%\system32\catroot2 oldcatroot2 net start cryptsvc regsvr32 softpub.dll regsvr32 wintrust.dll regsvr32 initpki.dll regsvr32 dssenh.dll regsvr32 rsaenh.dll regsvr32 gpkcsp.dll regsvr32 sccbase.dll regsvr32 slbcsp.dll regsvr32 cryptdlg.dll

NTOSKRNL Missing or Corrupt Added 2/9/03

If you get an error that NTOSKRNL not found: 1. Insert and boot from your WindowsXP CD. 2. At the first R=Repair option, press the R key 3. Press the number that corresponds to the correct location for the installation of Windows you want to repair. Typically this will be #1 4. Change to the drive that has the CD ROM. 5. CD i386 6. expand ntkrnlmp.ex_ C:\Windows\System32\ntoskrnl.exe 7. If WindowsXP is installed in a different location, just make the necessary change to C:\Windows 8. Take out the CD ROM and type exit HAL.DLL Missing or Corrupt Added 2/9/03 If you get an error regarding a missing or corrupt hal.dll file, it might simply be the BOOT.INI file on the root of the C: drive that is misconfigured 1. Insert and boot from your WindowsXP CD. 2. At the first R=Repair option, press the R key 3. Press the number that corresponds to the correct location for the installation of Windows you want to repair. Typically this will be #1 4. Type bootcfg /list to show the current entries in the BOOT.INI file 5. Type bootcfg /rebuild to repair it 6. Take out the CD ROM and type exit Corrupted or Missing \WINDOWS\SYSTEM32\CONFIG Added 2/9/03 If you get the error: Windows could not start because the following files is missing or corrupt \WINDOWS\SYSTEM32\CONFIG\SYSTEM or \WINDOWS\SYSTEM32\CONFIG\SOFTWARE 1. Insert and boot from your WindowsXP CD. 2. At the first R=Repair option, press the R key 3. Press the number that corresponds to the correct location for the installation of Windows you want to repair. Typically this will be #1 4. Enter in the administrator password when requested 5. cd \windows\system32\config 6. Depending on which section was corrupted: ren software software.bad or ren system system.bad 7. Depending on which section was corrupted copy \windows\repair\system copy \windows\repair\software 8. Take out the CD ROM and type exit NTLDR or NTDETECT.COM Not Found

Added 2/9/03 If you get an error that NTLDR is not found during bootup, If you have FAT32 partitions, it is much simpler than with NTFS. Just boot with a Win98 floppy and copy the NTLDR or NTDETECT.COM files from the i386 directory to the root of the C:\ drive. For NTFS: 1. Insert and boot from your WindowsXP CD. 2. At the first R=Repair option, press the R key 3. Press the number that corresponds to the correct location for the installation of Windows you want to repair. Typically this will be #1 4. Enter in the administrator password when requested 5. Enter in the following commands (X: is replaced by the actual drive letter that is assigned to the CD ROM drive. COPY X:\i386\NTLDR C\: COPY X:\i386\NTDETECT.COM C:\ 6. Take out the CD ROM and type exit

�Repairing Damaged Winsock2 Updated 6/26/04 The symptoms when Winsock2 is damaged show when you try to release and renew the IP address using IPCONFIG. And you get the following error message: An error occurred while renewing interface 'Internet': An operation was attempted on something that is not a socket. Also Internet Explorer may give the following error message: The page cannot be displayed Additionally, you may have no IP address or no Automatic Private IP Addressing (APIPA) address, and you may be receiving IP packets but not sending them. There are two easy ways to determine if Winsock2 is damaged: From the XP source files, go to the Support / Tools directory

Winsock Test Method 1 Run netdiag /test:winsock The end should say Winsock test ..... passed Winsock Test Method 2 1. Run Msinfo32 2. Click on the + by Components 3. Click on the by Network 4. Click on Protocol 5. There should be 10 sections if the Winsock2 key is ok MSAFD Tcpip [TCP/IP] MSAFD Tcpip [UDP/IP] RSVP UDP Service Provider RSVP TCP Service Provider MSAFD NetBIOS [\Device\NetBT_Tcpip... MSAFD NetBIOS [\Device\NetBT_Tcpip... MSAFD NetBIOS [\Device\NetBT_Tcpip... MSAFD NetBIOS [\Device\NetBT_Tcpip... MSAFD NetBIOS [\Device\NetBT_Tcpip... MSAFD NetBIOS [\Device\NetBT_Tcpip... If the names are anything different from those in this list, then likely Winsock2 is corrupted and needs to be repaired. If you have any 3rd party software installed, the name MSAFD may be changed. There should be no fewer than 10 sections. To repair Winsock2 1. Run Regedit 2. Delete the following two registry keys: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock2 Download Reg file to delete these entries 3. Restart the computer 4. Go to Network Connections 5. Right click and select Properties 6. Click on the Install button 7. Select Protocol 8. Click on the Add �button 9. Click on the Have Disk button 10. Browse to the \Windows\inf directory 11. Click on the Open button 12. Click on the OK button 13. Highlight Internet Protocol (TCP/IP) 14. Click on the OK button 15. Reboot

������� Or Download Reg file to add the correct registries back in