Re: SCW with Terminal Services Custom Port

From: Roger Abell (mvpNOSpam_at_asu.edu)
Date: 05/18/05 

Date: Tue, 17 May 2005 19:43:00 -0700

You could try using the SCW and instead of directly applying the
result, have it saved. Then, go into the XML file and modify the
rule in the IPsec portion so that it is using your port instead of
tcp 3389. You could likely just open the file in notepad and do
a find on 3389 to get you nose pointed at it.
I am not sure that it is (only) the IPsec rules that are getting in your
way, however, and am not in position here and now to test this.
It may only be using a predefined firewall exception for RDP.
If that is the case, you could consider having a custom firewall
exception defined. 

-- 
Roger Abell
Microsoft MVP (Windows  Security)
MCSE (W2k3,W2k,Nt4)  MCDBA
"Parhez Sattar" <pxs01@grh.org> wrote in message
news:eSYV%233zWFHA.3712@TK2MSFTNGP09.phx.gbl...
> 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?
>
>

Relevant Pages

  • SCW with Terminal Services Custom Port
    ... In my attempts to apply SP1 and then configure the security of our Terminal ... SCW is not compatible with customizing the RDP port on the server. ... SCW, it seems like the server only accepts RDP connections using 3389. ...
    (microsoft.public.windows.terminal_services)
  • SCW with Terminal Services Custom Port
    ... In my attempts to apply SP1 and then configure the security of our Terminal ... SCW is not compatible with customizing the RDP port on the server. ... SCW, it seems like the server only accepts RDP connections using 3389. ...
    (microsoft.public.windows.server.security)
  • Re: W2000 security
    ... claimed SCW did not deliver but then made reference to IE, ... BUT they forgot the WHOLE of their o/s was badly designed and the WHOLE of ... IE is badly designed in the context of security, ... "Windows Media Player" that can't be uninstalled on a PRODUCTION SERVER ...
    (microsoft.public.security)
  • Re: Security Configuration Editor versus Wizard for 2003 policy
    ... I have not used it much myself but SCW so far seems impressive in that it is ... tailored to server role and can implement ipsec filtering policy to also ... The general .inf security templates are ... not tailored to a server role. ...
    (microsoft.public.windows.server.security)
  • Re: Security Template vs SCW
    ... you should notice that use of SCW is intended ... I have used mostly security templates provided by MS to harden my member ... Also, we have FS, DHCP and other services in a cluster server. ...
    (microsoft.public.windows.server.security)