Cause: The program displayed a Windows dialog
box or caused and error message to be displayed. Programs started
through Telnet Client run on the Telnet server. As a result, any
Windows user interface that is displayed by the program appears on
the server, not the client computer.
Solution: Ask the administrator of the Telnet
server computer to close any dialog or message boxes on the
server.
Cause: Default font used by Telnet Client does
not support extended characters, such as characters with
accents.
Solution: Change the font used by Telnet
Client to a TrueType font. Right-click the Telnet Client title bar,
click Properties, and then click the Font tab. In the
Font list, click a TrueType font.
Cause: Telnet Client recognizes only drive
letters mapped during the current Telnet session. Consequently,
Telnet Client users cannot access network drives using drive
letters mapped by other Telnet users or by local server users.
Solution: Telnet Client users must use the
net use command to map network drives to drive letters
themselves.
Cause: Because of NTLM limitations, it might
not be possible to access network resources or connect to another
computer without providing your user name and password again during
the session.
Solution: Use the net use command
to connect to a network resource before attempting to use the
network resource. Supply your user name (including the domain) and
password using the /user option, as shown in this syntax for
connecting to a network drive:
net use [drive: | *] \\computer\directory/user:domain\userpassword | *
