![]() |
|
|
|
#1
|
|||
|
|||
|
Hi
When I try to connect to a telnet session on a Windows 2003 server (built-in telnet server), I get disconnected right away. Trace output: SecureCRT - Version 6.5.0 (build 380) SENT do SUPPRESS GO AHEAD SENT will TERMINAL TYPE RCVD do AUTHENTICATE SENT will AUTHENTICATE RCVD will ECHO SENT do ECHO RCVD will SUPPRESS GO AHEAD RCVD do NEW ENVIRON SENT wont NEW ENVIRON RCVD do NAWS SENT will NAWS RCVD do BINARY SENT will BINARY RCVD will BINARY SENT do BINARY RCVD do TERMINAL TYPE RCVD Authenticate SEND NTLM [LOCAL] : Stream has closed [CLOSE_TYPE_NONSPECIFIC] : The operation completed successfully. Emulation is set to ANSI - same result with VT100 When emulation is set to xterm, I can connect, but with wrong keyboard emulation. If I use Windows' own telnet client or putty (terminal-type string=ansi), there are no problems. Best regards - Jesper Danielsen |
|
#2
|
||||
|
||||
|
Hello Jesper,
Can you send trace options output to support@vandyke.com (with subject Forum 4789) showing a successful connection using xterm emulation? It's usually best not to post trace options on a public forum. I'd like to establish e-mail contact so that we can also look at PuTTY's equivalent of trace options as well if we need to. Do you have access to the server log file? Do you get different results if you open Session Options / Terminal / Emulation / Advanced and enable "Terminal type" and set it to "ansi", all lower case exactly the way you've typed in PuTTY's terminal type entry box? |
![]() |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | Search this Thread |
| Display Modes | |
|
|