On 6/20/07, Adam Sills <[EMAIL PROTECTED]> wrote:
A time out would indicate that *someone* was listening on that port but refused to establish the connection and response, which would expose data to the bad guys (they'd know something was back there). Actively refused means nobody is listening on that port.
No, that's backwards. When a connection is "actively" refused, it means that a machine received the request, but no one was listening. In my experience with sockets (extensive, actually), this is the way it works. Try closing the RDP(3389?) port using the firewall on a machine and then try connecting to it via Remote Desktop. You'll see that the request will time out. The error message being returned by remoting (with which I have very little experience) in this case is simply MS's (poor, IMO) choice of words for the socket error. -- Steve Johnson =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
