RE: SCW with Terminal Services Custom Port
- From: "Patrick Rouse" <PatrickRouse@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 17 May 2005 20:13:01 -0700
I've said this before, and I'll say it again. Changing your listening port
from 3389 to something else does not make your servers more secure, as anyone
with tools (or skills) good enough to crack your system, has the ability to
find the listening port.
The most exploited TCP Ports are 25 (SMTP) & 80 (HTTP), not RDP, which to
recollection has not had an exploited secuity flaw in several years.
Require strong passwords and you'll be fine.
--
Patrick Rouse
Microsoft MVP - Terminal Server
http://www.workthin.com
"Parhez Sattar" wrote:
> In my attempts to apply SP1 and then configure the security of our Terminal
> Services server using the Security Configuration Wizard, it appears that the
> SCW is not compatible with customizing the RDP port on the server. We had
> changed that port number from 3389 to something else and after running the
> SCW, it seems like the server only accepts RDP connections using 3389.
> During the SCW, we did notice that the Network Security section mentioned
> that the RDP port was set to 3389 and I couldn't change that. I had just
> hoped that the registry key change would still take precedence.
> Unfortunately, that doesn't seem to be case.
>
>
> Does anybody know how to use SCW yet keep that custom RDP port on the
> Terminal Server?
>
>
>
.
- Follow-Ups:
- Re: SCW with Terminal Services Custom Port
- From: Parhez Sattar
- Re: SCW with Terminal Services Custom Port
- References:
- SCW with Terminal Services Custom Port
- From: Parhez Sattar
- SCW with Terminal Services Custom Port
- Prev by Date: Re: Printing to a USB Dell AIO-922
- Next by Date: No Domain Option on Login Window
- Previous by thread: SCW with Terminal Services Custom Port
- Next by thread: Re: SCW with Terminal Services Custom Port
- Index(es):
Relevant Pages
|