garbled response when TCP connect is used with telnet



Hi Folks,
 
I am creating a VI that connects to the local machine via telnet and runs a small executable.
I execute the TCP connect VI and and then do a TCP read and get some characters yy%yyu ETC...
I suspect this is the login banner. I have tried the TCP communication example VI's and get the same characters.
 
I can start a DOS window and telnet into the system and run the executable with not problem.
 
I also have  another application that starts telnet allows me to connect and send and recieve commands and responses using Labview with no problems.
 
The machine is a xP machine and I have started the telnet service manually.
 
Any Ideas what I am doing wrong?
 I am not a Telnet expert so I may not be doing things in the right sequence to get a readable response.
It's  just confusing that one method works and the other does not not.
 
 
J.R.
.



Relevant Pages

  • RE: Timeout strategy: terminal vs Telnet drivers
    ... >>> layer may or may not send them as individual packets. ... > The context was Telnet which IS an application wrt TCP ...
    (comp.os.vms)
  • Re: Start telnet on Windows XP Home from Fedora Core 1
    ... normal telnet port (TCP 23)... ... Also, in general, you DO NOT want the ports you list ... Jeffrey Randow (Windows Networking & Smart Display MVP) ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: Setting up network access for a CUPS printer
    ... I have opened the ipp port on that ... > TCP and UDP? ... (192.168.1.2 is the address of the client on the LAN) ... > Can you telnet to the port on the host? ...
    (comp.os.linux.misc)
  • Re: Cant "telnet mail-host 25"
    ... "telnet server-host port" for a lot of ports, even though the server to serve the port is running in server-host. ... So it seems the [TCP ZeroWindow] resets the TCP connection. ...
    (linux.redhat.misc)
  • Re: Suggestions for custom application-layer protocol?
    ... then why not just use the telnet protocol and telnet ... I also want the protocol to be ... > be sent over a TCP socket? ... Who can initiate a message and who can initiate a connection ...
    (comp.os.linux.embedded)