This might be due to winsock2 corruption.you can try the following Solution
#How to determine whether the Winsock2 key is corrupted
To determine if the symptoms are caused by a problem with the Winsock2 key, use one of the following methods.
Method 1: Use the Netdiag tool
To use the Netdiag tool, you must install the Microsoft Windows XP Support Tools. To do so, follow these steps:
Note
If you already have Support Tools installed, go to the second procedure in this section.
If you do not have Support Tools installed and you do not have the Windows XP Setup CD, go to Method 2.
Insert your Windows XP Setup CD
Locate the Support\Tools folder
Double-click the Setup.exe file
Follow the steps on the screen until you reach the Select An Installation Type screen
On the Select An Installation Type screen
Click Complete
Click Next
When the installation is complete, follow these steps:
Click Start
Click Run
Type the following in the Run box
Command
Click OK
Type
netdiag /test:winsock
Press Enter
The Netdiag tool will return the test results for several network components, including the Winsock.
For more details about the test, use /v at the end of the netdiag command: netdiag /test:winsock /v
Method 2: Use the Msinfo32 program
Note Use this method only if you do not have a Windows XP Setup CD and you do not have Support Tools installed.
Click Start
Click Run
Type in the Run box
Msinfo32
Click OK
Expand Components
Expand Network
Click Protocol
You will have ten sections under Protocol
The section headings will include the following names if the Winsock2 key is undamaged:
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, the Winsock2 key is corrupted, or you have a third-party add-on, such as proxy software, installed.
If you have a third-party add-on installed, the name of the add-on will replace the letters "MSAFD" in the list.
If there are more than ten sections in the list, you have third-party additions installed.
If there are fewer than ten sections, there is information missing.
Note These entries represent an installation with only the TCP/IP protocol installed. You can have a working Winsock and see additional entries if another protocol is installed. For example, if you install NWLink IPX/SPX, you will see 7 additional sections, for a total of 17. Below is an example heading of one of the new sections:
MSAFD nwlnkipx [IPX]
Also, each of the new sections that are created by installing NWLink IPX/SPX start with "MSAFD." Therefore, there are still only two sections that do not start with those letters.
If the Netdiag test fails, or if you determined that there is Winsock corruption by looking at Msinfo32, you must repair the Winsock2 key by using the steps in the next section.
How to Recover from Winsock2 Corruption
To resolve this issue, delete the corrupted registry keys, and then reinstall the TCP/IP protocol.
Step 1: Delete the corrupted registry keys
Click Start
Click Run
In the Open box type
regedit
Click OK
In Registry Editor, locate the following keys, right-click each key, and then click Delete:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services
\Winsock
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services
\Winsock2
When you are prompted to confirm the deletion, click Yes
Note Restart the computer after you delete the Winsock keys. Doing so causes the Windows XP operating system to create new shell entries for those two keys. If you do not restart the computer after you delete the Winsock keys, the next step does not work correctly.
Step 2: Install TCP/IP
Right-click the network connection
Click Properties
Click Install
Click Protocol
Click Add
Click Have Disk
Type
C:\Windows\inf
Click OK
On the list of available protocols, click Internet Protocol (TCP/IP)
Click OK
Restart the computer
if you need any help please post your email id
Regards,
Amrith
Former Senior Escalation Engineer
(Linksys , Microsoft)