Re: [twsocket] abnormal winsock behaviour by firewall

2005-09-19 Thread Piotr Dałek
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

Re: [twsocket] abnormal winsock behaviour by firewall

2005-09-17 Thread Francois PIETTE
@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

Re: [twsocket] abnormal winsock behaviour by firewall

2005-09-17 Thread Steve Endicott
-- [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

Re: [twsocket] abnormal winsock behaviour by firewall

2005-09-16 Thread Francois Piette
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

Re: [twsocket] abnormal winsock behaviour by firewall

2005-09-16 Thread Wilfried Mestdagh
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