10053 is "connection aborted". I guess Norton is listening on all ports and abort the connections he is configured to deny.
-- [EMAIL PROTECTED] Author of ICS (Internet Component Suite, freeware) Author of MidWare (Multi-tier framework, freeware) http://www.overbyte.be ----- Original Message ----- From: "Wilfried Mestdagh" <[EMAIL PROTECTED]> To: <twsocket@elists.org> Sent: Friday, September 16, 2005 11:09 AM Subject: [twsocket] abnormal winsock behaviour by firewall > Hello, > > Just information because I think this is interesting to know: > > Normally when I want to know if there is a server on a machine I try to > connect on the port where it should listen and check Error argument in > OnSessionConnected. > > If you do this on a machine where Norton antivirus is running, and you > try to connect on port 'smtp' and there is _no_ server and 'mail > checking' is checked in the antivirus thing then OnSessionConnected will > fire without error and a while later OnsessionClose will fire with a > 10053. > > So dont just rely on the winsock error in OnSessionConnected :( > > -- > Rgds, Wilfried > http://www.mestdagh.biz > > -- > To unsubscribe or change your settings for TWSocket mailing list > please goto http://www.elists.org/mailman/listinfo/twsocket > Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
