On 6/20/07, Adam Sills <[EMAIL PROTECTED]> wrote:
If I try to connect to a server which is not listening on a port, my connection fails immediately with "the target machine actively refused the connection" (because its remote IP stack received the request but refused the connection because the port is not open).
That part makes sense. That's the behavior I've been describing and that's what my experience has shown me. The behavior of a firewall is to make it look exactly like a server is not
listening on a port. So with a firewall you receive "the target machine actively refused the connection" and it looks no different than a server without that open port.
This makes sense, theoretically, but I don't recall this behavior by the firewalls with which I've worked. It's entirely possible, however, that some (most?) firewalls work this way. I would never claim to be a firewall expert :). -- Steve Johnson =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
