Remote Desktop port change problems...

[Kerry Alt]

Greetings,

My client firewall blocks everything but ports 80 and 22/23, so I read
many threads and changed the listening port on the Terminal Services
server to 80. I've double checked this. IIS is running fine on 80. But
when I try to connect from the client with xxx.xxx.xxx.xx:80, I get a
"connection timed out" response. A netstat -a on the client indicates
the connection was ESTABLISHED (any other port gets a host not found
error) but I never get a login window.

I got the keepers of the firewall to temporarily open up port 3389 and
everything worked fine. But when they closed 3389 and I changed the
listening port on the server to 80, I again get no login window and a
timeout.

This behaviour happens whether the client is on the extranet or
intranet.

Any pointers here would be helpful; I've spent the last several hours
reading postings, but I probably missed the one answer that addressed
this problem.

Thanks,

Kerry

 

[David Jones]

If IIS is running on port 80, Remote Desktop can't also
be running on port 80 - you'd need to uninstall and turn
off IIS.

 

[Kerry Alt]

I had the same behavior on port 22, which can be shared if
ssh server isn't running, and that didn't work either. Is
it the same reason?

Kerry