SCW with Terminal Services Custom Port
From: Parhez Sattar (pxs01_at_grh.org)
Date: 05/18/05
- Next message: Roger Abell: "Re: SCW with Terminal Services Custom Port"
- Previous message: Steven L Umbach: "Re: Kerberos Question"
- Next in thread: Roger Abell: "Re: SCW with Terminal Services Custom Port"
- Reply: Roger Abell: "Re: SCW with Terminal Services Custom Port"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Tue, 17 May 2005 17:10:24 -0700
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?
- Next message: Roger Abell: "Re: SCW with Terminal Services Custom Port"
- Previous message: Steven L Umbach: "Re: Kerberos Question"
- Next in thread: Roger Abell: "Re: SCW with Terminal Services Custom Port"
- Reply: Roger Abell: "Re: SCW with Terminal Services Custom Port"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|