I have also seen this issue when winsock in xp is "broken". Repaing 
winsock as stated here and rebooting fixes the issue. 
http://support.microsoft.com/kb/817571

Tom Stachowiak
D'Youville College

Reply via email to