in reply to Trying to use Net::Telnet from Linux to a XP machine [connection refused]

TASdvlper,
First of all, there is a known problem with using Net::Telnet to a windows box. With that said, you probably do not have the service running. 
c:\> netstat -an | find ":23"

[download]
If you do not see the machine listening on port 23, you will need to enable it as a service. Be sure to read the notes at the bottom, since there are some differences between WinXP and 2003.

If it is running, something is blocking the connection such as IPSec.

Cheers - L~R

  • Comment on Re: Trying to use Net::Telnet from Linux to a XP machine [connection refused]
  • Download Code

Replies are listed 'Best First'.
Re: Re: Trying to use Net::Telnet from Linux to a XP machine [connection refused]
by TASdvlper (Monk) on Oct 27, 2003 at 20:54 UTC
    I got the telnet service running and I can telnet from a command line, but in the script I'm getting the following message:

    timed-out waiting for command prompt at Telnet.pl line 13 (line 13 is the $t->login(...) command.

[reply]
      As offered up in Limbic~Region's link.

      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.

      You mention you are running the MS Telnet Service....I think that everyone here is right...that is the culprit and you might consider replacing it with an RFC compliant Telnet Server

[reply]

In Section Seekers of Perl Wisdom