This is a discussion on Telnet to Windows; Start Plink to another system fails - SSH ; Hi All, I have a script that telnets to a windows box, then starts plink to open a com port on that server. The issue is that the connection will only work if I type Sloooooowly ... the script fails ...
Hi All,
I have a script that telnets to a windows box, then starts plink to
open a com port on that server.
The issue is that the connection will only work if I type
Sloooooowly ... the script fails miserably with lots of garbage
characters being sent to the com port.
I tried telnet to the Windows box then using plink to telnet with the
same result.
Also, when it does work ... typing slow ... every key typed is echoed
back ...
Example:
# llss
instead of
# ls
Any help is greatly appreciated!
Larry
============== log =======================================
Welcome to Microsoft Telnet Service
login: motocapsqa
password:
*================================================= ==============
Welcome to Microsoft Telnet Server.
*================================================= ==============
D:\Profiles\motocapsqa>
D:\Profiles\motocapsqa>D:\Profiles\qbrt78\Desktop\p4\qa\phate\EXE
\plink.exe -load COM6_115200_8N1
# ls --color=never
ls -color=?ever
ls: invalid option -- o
BusyBox v1.9.1 (2008-06-27 06:45:31 EDT) multi-call binary
Usage: ls [-1AacCdeFilnpLRrSsTtuvwxXhk] [filenames...]
List directory contents
Options:
..
..
..
# route add -net 10.13.223.0 netmask 255.255.255.0 gw 192.168.0.220
ro?ue? ad -net 10.13.22?.0?n?em?ak 2?5.255?.25.0 gw 192.16?.0.?20
-sh: ro?ue?: not found
#