What ports to open for Remote Desktop on Domain. TCP/IP filtering WIN 2000/2003?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I'm building a web server and want to deny all in-bound
ports except those that are absolutely needed. I have it
allowing http, https, SQL, and 3389 (Terminal Services). I
need it to allow me to remotely connect via Remote Desktop
for the time being.

I thought I was set once I opened 3389 and was able to
successfully log in about 4 times before it started telling
me that the domain didn't exist. I'm guessing it let me in
those few times because Windows caches the last few remote
log ins. What other ports (TCP, UDP, IP) do I need to
allow in order to get Remote Desktop properly running?

Thanks.

-Jarold
 
You are correct that Remote Desktop uses TCP port 3389. I don't think this
is the issue. It sounds more like a name resolution issue. Can you post the
exact sequence of events and the exact error message received? Have you
tried connecting just using the IP address rather than the name?

Thanks,
Marc Reynolds
Microsoft Technical Support

This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
 
Port 3389 tcp is the only port that is needed in a default setup. It sounds
like a dns error of some sort. I would run netdiag on the server looking for
any failed tests that may help track down problem. --- Steve
 
Back
Top