Problem whith Standard MS Telnet Client and sam

[baudoin]

hello,
when I am connect whith standard Microsoft (NT 4.0) telnet client, and run sam, a lot of strange characters displays, like :
?SASources Area ?
?------------------------------------------------------------------------------?
? Custom 1 : Outils SDP -> ?
?+-SAM------Accounts-for-Users-and-Groups-->---------------------------------+ ?
?? SAM Auditing and Security -> ^ ?
?? SAM Backup and Recovery -> ?
Navigation is not usable, also menus, so sam cannot by used.
I am using vt100 term.
With other client (Netterm), all is ok.

Is there a solution to correctly configure the MS telnet, because i don't want to deploy an other telnet client ?

Thank's for all response, and sorry for my very bad language.

O. Decorse.
o.decorse@saprr.fr

[Dan Hetzel]

Hello Baudoin,

Make sure that your TERM environment variable
is set to vt100 before starting SAM.

If you're running csh:
setenv TERM vt100

for other shells (bourne, posix, korn):
export TERM=vt100

It should be OK now...

Dan

[Paula J Frazer-Campbell]

Hi
What service pask are you running on your NT 4.0 machine?

paula

[Dan Hetzel]

Hello again,

I forgot to mention that you should select
the font 'terminal'

select terminal > Preference > Font

This should give you the graphics for all
lines

That's it

Dan

[baudoin]

Thanks for all responses.
The NT SP is Service Pack 3 and an other is Service Pack 5 : the problem is the same with the 2 boxes.
I already chose vt100, with command "ttytype" first to check, and then "export TERM=vt100". The verification "echo $TERM" effectivly displays vt100.
The most interresant information is the "select terminal > Preference > Font" : IT WORKS BETTER : windows, line and menu displays like a commercial telnet software, but after few minutes and manipulations, cursor is placed a the beginning of the line, lines not correctly displays. A 'CTRL-L' produce the same bad result !! May be an /etc/termcap unix problem ?!
So i think i need an other little help ...

[Dan Hetzel]

Hi Baudoin,

I sincerely don't believe that this is a termcap/terminfo issue.
MS telnet doens't seem to deal properly with EOL wrap.

As I had to use sam, and to check this out, I've used it through a commercial product (Hummingbird Exceed) without a single pb.
My TERM was set to vt100.

Sorry but I lacking some free time to help Microsoft in rewriting their telnet utility ;-)

Cheers,

Dan

[Paula J Frazer-Campbell]

Hi

A very good telnet client for NT is Hoastaccess, a trial vervion is available at:-
www.pixel-group.com

I use it on all windows platforms although at present there are a couple of problems with win 2000.
It is fully configurable.
Please be aware that if you enable the command stack your password when you login is held in clear text.

Paula

[Kevin Ernst]

>> The most interresant information is the "select terminal > Preference > Font" : IT WORKS BETTER : windows, line and menu displays like a commercial telnet software, but after few minutes and manipulations, cursor is placed a the beginning of the line, lines not correctly displays. A 'CTRL-L' produce the same bad result !! May be an /etc/termcap unix problem ?!

With some full-screen console applications (notably 'vi'), it helps to set the 'Buffer Size' to 24 rather than the default setting of 25. I'm not sure, but I think VT100's must've been 24 line terminals. (Notice how an xterm always starts with a geometry of 80x24--not 25.) This, unfortunately, doesn't seem to help SAM very much. Control-L's in SAM always work for me, though; sure, it's annoying to have to redraw the screen every so often, but it doesn't stop me from doing anything with SAM.

[baudoin]

Thank's Kevin, but i've got always the same probleme.
Are you using the MS telnet standard client without problem ?
Baudoin.

[Kevin Ernst]

Well, for me MS Telnet isn't perfect, but it's marginally usable. That is, it's usable enough to make a few quick changes, but you still have to press a lot of ^L's to redraw the screen periodically. Using a buffer size of 25 and, as other posters mentioned, a term type of 'vt100' (rather than 'ansi') seems to be slightly better for SAM, but nothing is just right.

After a certain point, I stopped trying to get by with MS Telnet and started to use a PC X server to run SAM with the graphical interface (or in an hpterm) over the network. At my work, we happened to have a site copy of the Hummingbird Exceed PC X server, so I figured out how to set it up and never went back.

You may not want to spend that kind of money just to run SAM, though, so your other options would be to seek out other free/inexpensive shareware terminal emulators or PC X servers.

For a while, I used MicroImages MI/X server, which was at one point completely free. They no longer make this version available on their site ( http://www.microimages.com ), and rather charge for the current 2.x version. You might still be able to find MI/X 1.x on an ftp server somewhere: try http://ftpsearch.lycos.com and search for 'mixnt.zip' (for NT) or 'mix95.zip' for (Win 9x).

Reflections/X includes a high-quality terminal emulator I've seen recommended many times with regard to HP-UX systems in general (and SAM specifically), but it is a rather expensive commercial product. Unfortunately, I'm not having any luck finding the vendor's Web site using a search engine, so hopefully someone else can pipe in with the right info.

--Kevin

[Patrick Wallek]

The web site for WRQ, who produces Reflection X is: www.wrq.com

The also have a plain terminal emulation products called 'Reflection 2' (No, 2 is NOT the version #).

I have used WRQ products for several years and I think they are absolutely great. They are expensive though.

[Kevin Ernst]

Thanks, Patrick. I'll make a mental note of that: WRQ.

[Bill McNAMARA_1]

install linux and you can have it graphical.

[Richard Darling]

The least expensive and easiest to set text terminal emulator I have found is Powerterm from Ericom. We paid about $80 each. They also have good support.

[Kevin Ernst]

Bill:

That's what a PC X server does for you. Like for me, it's important that I'm able to check e-mail using our 'company standard' email client (blah) and log calls using our helpdesk system, which is also Windows-based. I can use Windows software *and* X applications concurrently on the same display by running X server software (we use Exceed) on my workstation.

[Kevin Ernst]

Bill:

That's what a (Windows-based) PC X server does for you. Like for me, it's important that I'm able to check e-mail using our 'company standard' email client (blah) and log calls using our helpdesk system, both of which only run on Windows. I can use Windows software *and* X applications concurrently on the same display by running X server software (we use Exceed) on my workstation.

[Kevin Ernst]

On my *Windows NT* workstation. Sorry, that didn't end up being as clear as I intended. The X server software runs on the Windows system, and serves the display for X applications which you invoke from the HP-UX (or other Unix) system(s).