Chris and Bill - thanks for the notes but I'm telling ya I'm not using default ports, not connecting to port 22, and not connecting to an unused socket. I have Unidata SSH set to port 21023 and I can see it running. Telnet to 21023 causes a dialog to display on the server desktop.
Bill, you're right that there should be a connection failed message with sockets rejecting connections from clients that are using the wrong protocol. I suspect UD might be trying to do that but it's failing and throwing an exception. That's the bug. Now, if you actually are running SSH on your port 22 then you're not seeing the same thing I am. Best, T > -----Original Message----- > From:Bill Haskett > Tony: > This is what I get... > C:\Documents and Settings\wphaskett>telnet 192.168.1.12 22 > Connecting To 192.168.1.12... > Could not open connection to the host, on port 22: > Connect failed > > The reason I asked if you had something running on > port 22 is I'd suspect you would get what I did, > unless something was listening (anything really) on > that port. ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
