unknown terminal type network

[PinkeyNBrain]

Not 100% if this is more appropriate here or under a perl forum - effectively a cut-n-paste of this has been already done there.....

I have a script which telnetsinto a unix-AIX box from Windows. All is well.

Starting to use the same routine to log into a SuSE10 box and am seeing the following in the input_log()

Last login: (bla bla bla)
tset: unknown terminal type network
Terminal type?

I can type in 'ansi', hit return and I'm good to go. But that seems like I'm ignoring the root cause. If I type in 'telnet xxx' from a dos prompt, I do not receive the request for a terminal type.

On the AIX I found that 'env | grep TERM' while using my (perl) script I get "TERM=dumb". If I telnet directly into the AIX I get "TERM=ansi"

Likewise, dos-telnet into SuSE, TERM=ansi. Using the script I'm getting (apparently) TERM=network which isn't recognized.

Any thoughts out there?

 

[columb]

In your windows script use

telnet -t ansi xxx

The -t flag sets the terminal type. I've tested this against an AIX box and changed $TERM from ansi to vt100

On the internet no one knows you're a dog

Columb Healy

 

[PinkeyNBrain]

I'll have to keep that in mind. The windows script is actually a perl script using a telnet module. I'm not able to find anywhere in the module the ability to stub in the termtype. I'm suspecting that since the AIX box can default to a known terminal type (i.e. dumb in this case) that I can set up the equivalent default in SuSE versus asking. However I'm a bit new to SuSE and will have to keep digging. Until then I'm just stubbing in band-aid fix into my script that effectively examines the host and blindly echos out the string 'ansi' immediately after logging on. It's working for now, but I'm aiming for a better fix. Thanks for the [-t <term>] reminder though.

 

[PHV]

In the SuSE box you may find some info in the man telnetd page.

Hope This Helps, PH.
FAQ219-2884
FAQ181-2886