This behaviour may occur if the WinSocks library or the TCP/IP stack have
been
corrupted.
RESOLUTION
==========
To resolve this issue, follow these steps.
WARNING: If you use Registry Editor incorrectly, you may cause serious
problems
that may
require you to reinstall your operating system. Microsoft cannot guarantee
that you
can solve
problems that result from using Registry Editor incorrectly. Use Registry
Editor at
your own
risk.
1. Open Registry Editor by going to Start > Run. On the Open line type
"Regedit"
(Without the quotation marks" and click OK
2. Navigate to the following registry keys :
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock2
3. Delete the above listed keys from the registry, and close the Registry
Editor.
4. Uninstall the TCP/IP protocol from the GUI.
Go to Start > Settings > Control Panel. Launch the Network and Dial-Up
connections
applet. Right Click "Local Area Connection" and choose properties. If
TCP/IP is the
only protocol listed install another protocol such as NetBEUI.
Highlight "Internet Protocol (TCP/IP)" and click Uninstall. Follow the
on-screen
instructions to uninstall TCP/IP.
5. Restart the computer, and then reinstall TCP/IP if it is not installed
automatically:
6. Test for Network connectivity.
WARNING: Using Registry Editor incorrectly can cause serious problems that
may require you to reinstall Windows <95, 98>. Microsoft cannot guarantee
that problems resulting from the incorrect use of Registry Editor can be
solved. Use Registry Editor at your own risk.
With that said, let me assist you.
--------------------
unable to initialize windows socket interface, error code 0
for window 2000..how to solve without format the pc
__
Danny Slye
Microsoft Support Professional
MCSE
This posting is provided "AS IS" with no warranties and confers no rights.
Please reply to the newsgroup so that others may benefit. Thanks!
