Telnet Server best practices

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

Best practices

• Provide user-level security

  To control the access that Telnet users have to files on the server, use only the NTFS file system on the system partition. Create a TelnetClients group, add all Telnet users to that group, and then assign file and directory permissions to control the access that members have to the files and directories.

• Allow users to disconnect before stopping the service

  Before you stop Telnet Server or uninstall it, send a message to Telnet client sessions that you are about to stop the service. You can then stop the service after the users have had the opportunity to close their sessions.

• Make sure that the client code page matches the code page of the UNIX terminal

  If users will be connecting to Telnet Server from computers running an internationalized version of UNIX (such as a version capable of supporting European languages), you should ensure that the code page used by the command shell can display extended characters properly. To set the code page for all users when they log on, edit systemroot\system\login.cmd to add the chcp command to set the appropriate code page. For example, to support English and Western European UNIX, add the command chcp 1252.