Telnet issue

[Charles Lavin]

Hi --

I'm not sure where the problem is here.

I am attempting to telnet to a Unix host from a WinXP SP2 box using the MS
telnet client.

telnet 192.168.101.10 connects me to the host, but the host identifies the
session as a VT100 terminal.

So, using the command-line switch supplied by a telnet /? command, I enter

telnet -t ansi 192.168.101.10

and the host still identifies the session as a VT100 terminal.

So I try this:

$ telnet

Welcome to Microsoft Telnet Client

Escape Character is 'CTRL+]'

Microsoft Telnet> set term ansi
Will term type
Preferred term type is ansi
Microsoft Telnet> open 192.168.101.10


and the host STILL identifies the terminal as a VT100.


Note that if I use any other terminal program (puTTY, TinyTERM), upon login
the host identifies the terminal as the terminal type set by the terminal
emulator.

I've been reading the docs at
http://www.microsoft.com/resources/.../proddocs/en-us/telnet_commands.mspx?mfr=true,
but they aren't being any help. Because, as pointed out above, no matter
what I do, the telnet client identifies itself to the host as a VT100.

What do I need to do with the MS telnet client so that, upon login, the host
identifies the terminal as an ANSI terminal?

Thanks,
CL

 

[Michael W. Ryder]

Hi --

I'm not sure where the problem is here.

I am attempting to telnet to a Unix host from a WinXP SP2 box using the MS
telnet client.

telnet 192.168.101.10 connects me to the host, but the host identifies the
session as a VT100 terminal.

This command on my RS/6000 returns ansi.

So, using the command-line switch supplied by a telnet /? command, I enter

telnet -t ansi 192.168.101.10

and the host still identifies the session as a VT100 terminal.

So I try this:

$ telnet

Welcome to Microsoft Telnet Client

Escape Character is 'CTRL+]'

Microsoft Telnet> set term ansi
Will term type
Preferred term type is ansi
Microsoft Telnet> open 192.168.101.10


and the host STILL identifies the terminal as a VT100.

Again, this returns ansi under AIX.
Are you connecting directly to the Unix computer or through a router? I
am connecting through a switch only and it works fine for me. Another
possibility is if the computer you are connecting to won't accept ansi
connections.

 

[Charles Lavin]

I'm connecting to an RS/6000. In this particular case, I'm hitting it
through a VPN tunnel.

I'd _love_ for the RS/6000 to return a TERM value of ansi. But it will not
with the MS telnet client. It will with puTTY. And TinyTERM, which is
configured to emulate an ibm3151, causes the RS/6000 to set TERM to ibm3151.
All from the same PC, through the same tunnel.

???

Tnx
CL

Hi --

I'm not sure where the problem is here.

I am attempting to telnet to a Unix host from a WinXP SP2 box using the
MS
telnet client.

telnet 192.168.101.10 connects me to the host, but the host identifies
the
session as a VT100 terminal.

This command on my RS/6000 returns ansi.

So, using the command-line switch supplied by a telnet /? command, I
enter

telnet -t ansi 192.168.101.10

and the host still identifies the session as a VT100 terminal.

So I try this:

$ telnet

Welcome to Microsoft Telnet Client

Escape Character is 'CTRL+]'

Microsoft Telnet> set term ansi
Will term type
Preferred term type is ansi
Microsoft Telnet> open 192.168.101.10


and the host STILL identifies the terminal as a VT100.

Again, this returns ansi under AIX.
Are you connecting directly to the Unix computer or through a router? I
am connecting through a switch only and it works fine for me. Another
possibility is if the computer you are connecting to won't accept ansi
connections.

Note that if I use any other terminal program (puTTY, TinyTERM), upon
login
the host identifies the terminal as the terminal type set by the terminal
emulator.

I've been reading the docs at
http://www.microsoft.com/resources/.../proddocs/en-us/telnet_commands.mspx?mfr=true,
but they aren't being any help. Because, as pointed out above, no matter
what I do, the telnet client identifies itself to the host as a VT100.

What do I need to do with the MS telnet client so that, upon login, the
host
identifies the terminal as an ANSI terminal?

Thanks,
CL

 

[Charles Lavin]

Hi again --

I've verified that this behavior is consistent across multiple RS/6000s.
Different clients, different VPN connections, same results. The RS/6000
always identifies the MS telnet session as a VT100.

???

CL

Hi --

I'm not sure where the problem is here.

I am attempting to telnet to a Unix host from a WinXP SP2 box using the
MS
telnet client.

telnet 192.168.101.10 connects me to the host, but the host identifies
the
session as a VT100 terminal.

This command on my RS/6000 returns ansi.

So, using the command-line switch supplied by a telnet /? command, I
enter

telnet -t ansi 192.168.101.10

and the host still identifies the session as a VT100 terminal.

So I try this:

$ telnet

Welcome to Microsoft Telnet Client

Escape Character is 'CTRL+]'

Microsoft Telnet> set term ansi
Will term type
Preferred term type is ansi
Microsoft Telnet> open 192.168.101.10


and the host STILL identifies the terminal as a VT100.

Again, this returns ansi under AIX.
Are you connecting directly to the Unix computer or through a router? I
am connecting through a switch only and it works fine for me. Another
possibility is if the computer you are connecting to won't accept ansi
connections.

Note that if I use any other terminal program (puTTY, TinyTERM), upon
login
the host identifies the terminal as the terminal type set by the terminal
emulator.

I've been reading the docs at
http://www.microsoft.com/resources/.../proddocs/en-us/telnet_commands.mspx?mfr=true,
but they aren't being any help. Because, as pointed out above, no matter
what I do, the telnet client identifies itself to the host as a VT100.

What do I need to do with the MS telnet client so that, upon login, the
host
identifies the terminal as an ANSI terminal?

Thanks,
CL

 

[Michael W. Ryder]

Hi again --

I've verified that this behavior is consistent across multiple RS/6000s.
Different clients, different VPN connections, same results. The RS/6000
always identifies the MS telnet session as a VT100.

???

Are you able to set the TERM variable on the other computers? Maybe in
the .profile for your login you can set TERM and export it.

CL

Hi --

I'm not sure where the problem is here.

I am attempting to telnet to a Unix host from a WinXP SP2 box using the
MS
telnet client.

telnet 192.168.101.10 connects me to the host, but the host identifies
the
session as a VT100 terminal.

This command on my RS/6000 returns ansi.

So, using the command-line switch supplied by a telnet /? command, I
enter

telnet -t ansi 192.168.101.10

and the host still identifies the session as a VT100 terminal.

So I try this:

$ telnet

Welcome to Microsoft Telnet Client

Escape Character is 'CTRL+]'

Microsoft Telnet> set term ansi
Will term type
Preferred term type is ansi
Microsoft Telnet> open 192.168.101.10


and the host STILL identifies the terminal as a VT100.

Again, this returns ansi under AIX.
Are you connecting directly to the Unix computer or through a router? I
am connecting through a switch only and it works fine for me. Another
possibility is if the computer you are connecting to won't accept ansi
connections.

Note that if I use any other terminal program (puTTY, TinyTERM), upon
login
the host identifies the terminal as the terminal type set by the terminal
emulator.

I've been reading the docs at
http://www.microsoft.com/resources/.../proddocs/en-us/telnet_commands.mspx?mfr=true,
but they aren't being any help. Because, as pointed out above, no matter
what I do, the telnet client identifies itself to the host as a VT100.

What do I need to do with the MS telnet client so that, upon login, the
host
identifies the terminal as an ANSI terminal?

Thanks,
CL