Yah, yahread all that.
Question is, how do you stop the Win2K telnet server from defaulting to an ANSI
terminal?
This is particularly worrisome as the option_send method has not yet been written for
the Net::Telnet module so it is impossible to ask the Win2K server to change from
inside the perl app.
I have tired the following unsuccessfully:
1. Reordered the terminal parameters setting on the Win2K telnet server box in the
c:\winnt\system32\termcap file (this was an attempted hack as I know nothing about
termcap files),
2. Renamed the termcap file to that tlntsvr couldn't find it which causes tlntsvr to
exit after login,
3. Used the /y switch in the console execution entry in the registry.
At this stage of the game, I am going to give up since the option_send method is not
up yet. Since my app simply requires me to identify whether a remote perl script
executed successfully on the target Win2K machine, I can search through the gibberish
with regex and check. Unfortunately, this does not solve the more general issue
regarding the tlntsvr on a Win2K box.
Mickeysoft has ZERO information on the termcap file anywhere on their website but it
appears to follow the Unix syntax. They also have ZERO information on how to change
the default terminal setting for the tlntsvr.
Anyhow, That's it for me on this issue.
Cheers and thanx to everybody for the help,
jOhn
> -Original Message-
> From: Kevin Pendleton [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, November 28, 2002 12:56 PM
> To: John Serink; [EMAIL PROTECTED];
> [EMAIL PROTECTED]
> Subject: Re: Net::Telnet on Win2K
>
>
> John,
>
> The problem is outlined in the Net:Telnet documentation. The
> "loads of
> gibberish" is ANSI terminal escape characters. I haven't
> worked with that
> exact telnet application, but some allow you to turn ANSI off
> and on
>
> http://search.cpan.org/author/JROGERS/Net-Telnet-3.03/lib/Net/
> Telnet.pm
>
> Connecting to a Remote MS-Windows Machine
>
> By default MS-Windows doesn't come with a TELNET server.
> However third party
> TELNET servers are available. Unfortunately many of these
> servers falsely
> claim to be a TELNET server. This is especially true of the so-called
> "Microsoft Telnet Server" that comes installed with some
> newer versions
> MS-Windows.
>
> When a TELNET server first accepts a connection, it must use
> the ASCII
> control characters carriage-return and line-feed to start a
> new line (see
> RFC854). A server like the "Microsoft Telnet Server" that
> doesn't do this,
> isn't a TELNET server. These servers send ANSI terminal
> escape sequences to
> position to a column on a subsequent line and to even
> position while writing
> characters that are adjacent to each other. Worse, when
> sending output these
> servers resend previously sent command output in a misguided
> attempt to
> display an entire terminal screen.
>
> Connecting Net::Telnet to one of these false TELNET servers
> makes your job
> of parsing command output very difficult. It's better to
> replace a false
> TELNET server with a real TELNET server. The better TELNET
> servers for
> MS-Windows allow you to avoid the ANSI escapes by turning off
> something some
> of them call console mode.
>
> Kevin
>
> _
> STOP MORE SPAM with the new MSN 8 and get 2 months FREE*
> http://join.msn.com/?page=features/junkmail
>
>
___
Perl-Win32-Users mailing list
[EMAIL PROTECTED]
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs