more change port problems....

[Kerry Alt]

Hi,

How does one find out if port 22 is blocked on my server?
I have been able to make connections when Terminal
Service is listening on port 8080, but what I really need
is for it to listen on port 22 (that's the only port open
on the client's firewall). But connections through that
port time out. A netstat -n on the client shows that the
connection is 'ESTABLISHED' but I get no logon. Is 22
blocked by default on the server?

Thanks,

Kerry

 

[Jeffrey Randow (MVP)]

I am assuming that you have reset the registy entry to change the
listening port to 22...

Have you tried to connect to the machine on the local LAN using the
:22 port number.

Also, make sure that there isn't a SSH server on one of the machines
that may be winning out over the Remote Desktop server (in other
words, check the firewall configuration and port forwarding).

Jeffrey Randow (Windows MVP - Networking & Smart Display)
(e-mail address removed)

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Wiki -
http://www.remotenetworktechnology.com
Smart Display Support - http://www.smartdisplays.net
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone