Re: [twsocket] abnormal winsock behaviour by firewall
Hello! 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. There were other cases of abnormal behavior - AFAIR one of Outpost versions were breaking connection (without informing client about this) when one of data lines in POP3 connection exceeded 1024 bytes. Mail apps without any internal timeouts and manual connection breaking capabilities were mostly affected by this. -- Piotr Hellrayzer Dalek [EMAIL PROTECTED] -- O kobietach, dla kobiet... http://link.interia.pl/f18b4 -- 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
Re: [twsocket] abnormal winsock behaviour by firewall
Norton let's you connect without error which is very abnormal, so I hereby clasify the product as 'not good' :) I share your opinion. I frequently have ICS user contacting me because they heve problems with their application. It happend frequently that Norton security product is the culprit. Maybe only because it is misconfiguraed by the user, I don't know. -- Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html -- [EMAIL PROTECTED] http://www.overbyte.be - Original Message - From: Wilfried Mestdagh [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Friday, September 16, 2005 11:58 PM Subject: Re: [twsocket] abnormal winsock behaviour by firewall Hello Francois, 10053 is connection aborted. I guess Norton is listening on all ports and abort the connections he is configured to deny. Yes I think so too. I think this is totally wrong, most other firewalls give a 10060 (timeout) whitch is also wrong, but at least is gives a TCP connection a more or less normal behaviour. Norton let's you connect without error which is very abnormal, so I hereby clasify the product as 'not good' :) --- 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
Re: [twsocket] abnormal winsock behaviour by firewall
We have a program that contacts our web site for information (standard http request). Sometimes, one of our users will not be paying attention and will allow Norton Internet Security to block our application. In the past, Norton would return a 10061 (connection refused) error which made sense in that situation. Lately, Norton has been returning a 11004 (no data) error which makes no sense. Steve Endicott At 12:16 AM 9/17/2005, you wrote: Norton let's you connect without error which is very abnormal, so I hereby clasify the product as 'not good' :) I share your opinion. I frequently have ICS user contacting me because they heve problems with their application. It happend frequently that Norton security product is the culprit. Maybe only because it is misconfiguraed by the user, I don't know. -- Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html -- [EMAIL PROTECTED] http://www.overbyte.be - Original Message - From: Wilfried Mestdagh [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Friday, September 16, 2005 11:58 PM Subject: Re: [twsocket] abnormal winsock behaviour by firewall Hello Francois, 10053 is connection aborted. I guess Norton is listening on all ports and abort the connections he is configured to deny. Yes I think so too. I think this is totally wrong, most other firewalls give a 10060 (timeout) whitch is also wrong, but at least is gives a TCP connection a more or less normal behaviour. Norton let's you connect without error which is very abnormal, so I hereby clasify the product as 'not good' :) --- 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 -- 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
Re: [twsocket] abnormal winsock behaviour by firewall
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
Re: [twsocket] abnormal winsock behaviour by firewall
Hello Francois, 10053 is connection aborted. I guess Norton is listening on all ports and abort the connections he is configured to deny. Yes I think so too. I think this is totally wrong, most other firewalls give a 10060 (timeout) whitch is also wrong, but at least is gives a TCP connection a more or less normal behaviour. Norton let's you connect without error which is very abnormal, so I hereby clasify the product as 'not good' :) --- 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
