Re: Terminal Services

From: Peter Kaufman (no_at_email.com)
Date: 01/01/04


Date: Thu, 01 Jan 2004 17:49:52 +0700

Bob and Steven,

Thanks very much. You guys are great!

Peter

On Wed, 31 Dec 2003 19:02:25 GMT, bobqin@online.microsoft.com (Bob Qin
[MSFT]) wrote:

>Hi Peter,
>
>Thanks for your posting here.
>
>Windows 2000 Terminal Services supports three levels of encryption: Low,
>Medium, and High. The default encryption level is Medium, which is likely
>to be appropriate for most networks. I recommend that you use the High
>encryption level. This level encrypts the data transmission in both
>directions by using a 128-bit key. The High setting prevents the
>possibility of a malicious computer user breaking into the network and
>installing a network packet analyzer to eavesdrop on the Terminal Services
>sessions.
>
>To Secure Communications
>------------------------
>To modify the encryption setting:
>
>1. Click Start, point to Programs, point to Administrative Tools, point to
>Terminal Services Items, and then click Terminal Services
> Configuration.
>
>2. Start the Terminal Services Configuration snap-in in Microsoft
>Management Console (MMC).
>
>3. Click the Connections branch, and then double-click the connection whose
>encryption level you want to change.
>
>4. Click the General tab.
>
>5. In the "Encryption level" box, click the appropriate encryption level.
>
>6. Click OK.
>
>NOTE: The new encryption level takes effect the next time a user logs on.
>If you require multiple levels of encryption on one server, install
>multiple network adapters and configure each adapter separately.
>
>For more information, please refer to the following articles.
>
>HOW TO: Secure Communication Between a Client and Server with Terminal
>Services
>http://support.microsoft.com/?id=306561
>
>Securing Windows 2000 Terminal Services
>http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechn
>ol/win2kts/maintain/optimize/secw2kts.asp
>
>If you have any further questions or concerns, please feel free to let us
>know. It is our pleasure to be of assistance.
>
>Have a nice day!
>
>Regards,
>Bob Qin
>Product Support Services
>Microsoft Corporation
>
>Get Secure! - www.microsoft.com/security
>
>====================================================
>When responding to posts, please "Reply to Group" via your newsreader so
>that others may learn and benefit from your issue.
>====================================================
>This posting is provided "AS IS" with no warranties, and confers no rights.



Relevant Pages

  • RE: Secure / Encrypt Terminal Services
    ... Terminal Services does have decent encryption, ... IPSec is a great solution. ... As for the encryption, I do feel somewhat safe using the built-in ... I would certainly consider additional security. ...
    (Focus-Microsoft)
  • RE: Secure / Encrypt Terminal Services
    ... if you change the ts port - the pocket pc clients ... client connection port. ... doesn't alter the ts encryption level available ... Secure / Encrypt Terminal Services ...
    (Focus-Microsoft)
  • RE: Secure / Encrypt Terminal Services
    ... Terminal Services is a built-in service in Windows 2000 that provides ... admins with a remote desktop for managing a server. ... So, really, the main limitations are the type of encryption or its ...
    (Focus-Microsoft)
  • Re: RDP vs pcAnywhere tradeoffs?
    ... Read some detailed information about RDP. ... or XP Pro and Windows Server 2003 (or, for that matter Windows 2000 Server ... within the OS--they are building on the foundation of Terminal Services, ... > security application and can use passwords and encryption to give moderate ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: PCMCIA wireless help needed
    ... I presume there are several types? ... simplest encryption you could get under Windows. ... > technically not on the network. ...
    (Debian-User)