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