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 - 
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


[twsocket] multiple nics and broadcasts

2005-09-16 Thread Kenny Mah
This is a question about how to deal with multiple
nics and broadcasts.

If I had a computer (A) with multiple nics listening
to broadcasts, with each nic attached to a separate
network.

And then I had another computer (B), on one of those
networks, send a UDP broadcast.

Can computer (A) determine which of its IP
addresses intercepted the broadcast?

Thanks, 
Kenny



__ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com
-- 
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] multiple nics and broadcasts

2005-09-16 Thread Marcello Vezzelli
Kenny Mah wrote:

 This is a question about how to deal with multiple
 nics and broadcasts.
 
 If I had a computer (A) with multiple nics listening
 to broadcasts, with each nic attached to a separate
 network.
 
 And then I had another computer (B), on one of those
 networks, send a UDP broadcast.
 
 Can computer (A) determine which of its IP
 addresses intercepted the broadcast?

If every nic has 1 IP, you can bind an udp socket to each IP, listening on 
the port to which you're sending broadcasts.
So you'll end up with a TWSocket for each nic.

There could be a better solution, tough.


-- 
Marcello Vezzelli
CTO
Software Development Department
E-Works s.r.l.
tel. +39 059 2929081
fax +39 059 2925035
Direzionale 70 - Via Giardini 456/c
41100 Modena - Italy

-
La presente comunicazione, che potrebbe contenere informazioni riservate e/o 
protette da segreto professionale, è indirizzata esclusivamente ai 
destinatari della medesima qui indicati. Le opinioni, le conclusioni e le 
altre informazioni qui contenute, che non siano relative alla nostra 
attività caratteristica, devono essere considerate come non inviate né 
avvalorate da noi. Tutti i pareri e le informazioni qui contenuti sono 
soggetti ai termini ed alle condizioni previsti dagli accordi che regolano 
il nostro rapporto con il cliente. Nel caso in cui abbiate ricevuto per 
errore la presente comunicazione, vogliate cortesemente darcene immediata 
notizia, rispondendo a questo stesso indirizzo di e-mail, e poi procedere 
alla cancellazione di questo messaggio dal Vostro sistema. E' strettamente 
proibito e potrebbe essere fonte di violazione di legge qualsiasi uso, 
comunicazione, copia o diffusione dei contenuti di questa comunicazione da 
parte di chi la abbia ricevuta per errore o in violazione degli scopi della 
presente.
-
This communication, that may contain confidential and/or legally privileged 
information, is intended solely for the use of the intended addressees. 
Opinions, conclusions and other information contained in this message, that 
do not relate to the official business of this firm, shall be considered as 
not given or endorsed by it. Every opinion or advice contained in this 
communication is subject to the terms and conditions provided by the 
agreement governing the engagement with such a client. If you have received 
this communication in error, please notify us immediately by responding to 
this email and then delete it from your system. Any use, disclosure, copying 
or distribution of the contents of this communication by a not-intended 
recipient or in violation of the purposes of this communication is strictly 
prohibited and may be unlawful.
-- 
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


[twsocket] SocksServer. Host name resolving.

2005-09-16 Thread asvetov
Hello all!

Using TWSocket, when the connection is established via SocksServer, is this
possible to specify whether the address of destination host is resolved on
the client system or passed to SocksServer for resolving? Currently, if I
understood correct, the host name is always resolved on the client system,
but sometimes the local policies can forbid local DNS operations.

Thanks  Best regards, A.Svetov
-- 
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

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 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