Re: MS telnet w/ alternate terminal type?

Hi --

I cannot change the TERM value on users' profiles because that would screw
up their logons at the office or when using other telnet clients. The system
as set up now has no trouble adjusting the TERM value depending on the
emulation in use by the telnet client -- except when that telnet client is
Microsoft's.

As it is, logging in as an ANSI device represents a loss of functionality,
but one that is acceptable for the purposes for which I want to be able to
use the MS telnet client. Using the ANSI emulation on a MS telnet client
costs us wide screen displays, function key control, slave printing and
other features of the IBM 3151 upon which the software is built.

And if I do manually change the TERM value from inside AIX, then I get the
basic functionality I need from the telnet program.

But the users are not at liberty to make that change. Their profiles take
them straight to the application menu, which looks like crap when rendered
for a vt100.

I can replicate this problem from several Windows XP and Windows Vista PCs
here, to half a dozen AIX and SCO boxes of various OS levels.

Additionally, I had a colleague at another firm replicate this problem using
Windows XP and Windows 2000 clients onto several other AIX boxes. He also
informed me that this problem has bitten him in the past as well.

If this telnet client does indeed support the four emulations it claims to,
then the only thing I can think of is that it is identifying itself to AIX
as something AIX doesn't understand. But I still need to figure out what
that could be ...

A Microsoft support rep skirted the question of why the four emulations all
wind up looking like a vt100 to a Unix host by telling me to change the TERM
value on the host.

Thanks,
CL


"Michael W. Ryder" <_mwryder@xxxxxxxxxxxxxxxx> wrote in message
news:xkycj.80825$MJ6.32356@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Charles Lavin wrote:
Hi --

I posted this to a managed Microsoft ng, but I'm getting nowhere.

Has anyone had any success using the MS telnet client as shipped in
Windows XP to connect to an AIX box as anything other than a vt100
terminal?

According to telnet's own help, as well as several pages of docs I've
found on the MS site, the MS telnet program supports four emulations:
VT100, VT52, ANSI and VTNT.

The command "telnet -t ansi hostname" supposedly connects to the host
using the ANSI emulation (which is what I need).

An alternate way to do this is with the telnet command "set term ansi".

However, four different AIX hosts (one AIX 3.2.5, one AIX 4.1, two AIX
5.2) set their TERM values to vt100 when I log in from the MS telnet
client, no matter which terminal emulation I select on the telnet command
line.

Other programs, such as TinyTERM and puTTY, don't have this problem
setting up telnet sessions with these hosts.

Does anyone know how to get the MS telnet program to properly identify
itself so that AIX sets it up as an ansi device?

Thanks,
CL



As I mentioned in the MS newsgroup I have no problems getting this to work
as you want. You mentioned different servers giving you the same results,
is this also true with different PCs? Maybe trying a laptop that has not
been changed from the default configuration.
I asked before if you could changed the .profile file for your login to
set and export the TERM variable. Were you able to do this?


.

Relevant Pages

  • Re: MS telnet w/ alternate terminal type?
    ... up their logons at the office or when using other telnet clients. ... emulation in use by the telnet client -- except when that telnet client is ... Using the ANSI emulation on a MS telnet client ... And if I do manually change the TERM value from inside AIX, ...
    (comp.unix.aix)
  • Re: Headless fun
    ... I am not clear as to what does not have an ansi option, your terminal, ... I am working with a headless server ... "telnet" kernel boot parameter solves lots of my problems. ... telnet client to configure the install/rescue - depending on what you ...
    (comp.os.linux.setup)
  • Re: MS telnet w/ alternate terminal type?
    ... The system as set up now has no trouble adjusting the TERM value depending on the emulation in use by the telnet client -- except when that telnet client is Microsoft's. ... Using the ANSI emulation on a MS telnet client costs us wide screen displays, function key control, slave printing and other features of the IBM 3151 upon which the software is built. ... I can replicate this problem from several Windows XP and Windows Vista PCs here, to half a dozen AIX and SCO boxes of various OS levels. ...
    (comp.unix.aix)
  • Re: MS telnet w/ alternate terminal type?
    ... be -- to log in and use the local telnet client to get limited functionality ... If the MS telnet program does indeed support these alternate terminal ... Using the ANSI emulation on ... And if I do manually change the TERM value from inside AIX, ...
    (comp.unix.aix)
  • Re: MS telnet w/ alternate terminal type?
    ... be -- to log in and use the local telnet client to get limited functionality ... It allows telnet connections and you can specify the emulation. ... And if I do manually change the TERM value from inside AIX, ...
    (comp.unix.aix)