Failure to start Telnet sessions using NTLM authentication by members of the TelnetClients group (326638)
The information in this article applies to:
- Microsoft Windows XP 64-Bit Edition Version 2003
- Microsoft Windows Server 2003, Datacenter Edition
- Microsoft Windows Server 2003, Enterprise Edition
- Microsoft Windows Server 2003, Standard Edition
- Microsoft Windows Server 2003, Web Edition
- Microsoft Windows Small Business Server 2003, Premium Edition
- Microsoft Windows Small Business Server 2003, Standard Edition
This article was previously published under Q326638 SYMPTOMSNon-administrator users listed in the TelnetClients group
are unable to start Telnet sessions using NTLM authentication after doing one
or more of the following tasks:
- Converting the file system of a hard disk from the FAT file
system to the NTFS file system
- Applying default security templates
- Executing the DCPromo process
This problem occurs only with non-admin users who try to start
Telnet sessions using NTLM authentication. RESOLUTIONThe administrator must explicitly give read permissions on
Cmd.exe to the TelnetClients group. This is because during
setup of the operating system, Telnet Server gives read permissions on Cmd.exe
to the TelnetClients group. The read permission on Cmd.exe is
required because Telnet Server launches Cmd.exe as the user who is trying to
start the Telnet session.
When performing any of the three tasks
mentioned in the "Symptoms" section, the read permission on Cmd.exe that is
given to users who are listed in the TelnetClients group is
lost. This loss prevents these users from starting Telnet sessions using NTLM
authentication.
Note You cannot use the Telnet
sessions to execute the DCPromo process because of the security precaution in
Microsoft Windows Server 2003. If you assign read permissions to the
TelnetClients group, there may be a potential security risk to
the domain controller.
Modification Type: | Minor | Last Reviewed: | 11/22/2004 |
---|
Keywords: | kbDSWSFU2003Swept kbprb KB326638 |
---|
|