Author Topic: Winsock Errors  (Read 5850 times)

0 Members and 1 Guest are viewing this topic.

gprzybyl

  • Guest
Winsock Errors
« on: November 16, 2004, 05:35:10 PM »
I am seeing the following in some of the clients error logs:

11/15/2004   9:13:29 PM   1100571209   SYSTEM   1308   Cannot connect First server conn attempt (192.168.1.43:31511) failed. socket, WinSock error 0x00002751 has occurred.  
11/15/2004   9:13:29 PM   1100571209   SYSTEM   1308   Cannot connect Second server conn attempt (avastms: 192.168.1.43:31511) failed. socket, WinSock error 0x017275F0 has occurred.  
11/15/2004   9:13:29 PM   1100571209   SYSTEM   1308   Cannot connect Third server conn attempt (last good: 192.168.1.43:31511) failed. socket, WinSock error 0x00002751 has occurred.  
11/15/2004   9:13:34 PM   1100571214   SYSTEM   1308   Cannot connect Server lookup didn't find any AMS'! socket, WinSock error 0x00000000 has occurred.  
11/15/2004   9:13:34 PM   1100571214   SYSTEM   1308   Cannot connect ServerConnection socket, WinSock error 0x00002751 has occurred.  


What do the three winsock errors mean?  Also when I do a netstat -an on .43 (the ams)  I don't see anything listening on port 31511 should I?

Offline Vlk

  • Avast CEO
  • Serious Graphoman
  • *
  • Posts: 11658
  • Please don't send me IM's. Email only. Thx.
    • ALWIL Software
Re:Winsock Errors
« Reply #1 on: November 16, 2004, 06:05:16 PM »
Well...

0x2751 means HOST UNREACHABLE. It might've been a communication problem?

BTW the port number seems to be being logged incorrectly - my bet is that it's in the network order format (i.e. bits are swaped).

We'll try to fix it.


BTW nice try to get some extra points on the forum :P

Cheers
Vlk
If at first you don't succeed, then skydiving's not for you.