c:\> netstat -an | find ":23"
[download]

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

Cheers - L~R

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.

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

Is there a telnet server running on the XP machine?

And if so, please explain :)

----
I wanted to explore how Perl's closures can be manipulated, and ended up creating an object system by accident.
-- Schemer

:(){ :|:&};:

Note: All code is untested, unless otherwise stated

Other monks have pointed to problems with MS telnet server's implementation. My guess is that you've not reached these problems yet as the Telnet server that comes with win2k & up uses funky Microsoft only authentification by default

For win2K (and probably XP) you need to look in the local microsoft help for "telnet admin" and follow the bouncing wizard to change authentication from "NTLM" to "plain."

If MS telnet server doesn't work w/ Net::Telnet and you hae to install another server anyway, consider a ssh server as you won't be passing passwords over the net in the clear. Every cracked box I've seen or heard of has had a password sniffer installed

Actually, I am not sure. I will check shortly (I think I made a bad assumption it was running). I'm a bit new to running Perl in a Windows env. Would you have any recommendations besides using a telnet server ?

To explain my situation, from a master server I want to be able to run scripts on a remote windows system. Initially I thought rsh was the way to go, so then I thought about writing a client/server app, but if I can help it, I don't want a remote system to have the dependancy of running a script and "listening" for commands to execute.

I've also been told ssh and SOAP::Lite might be worth considering.