Telnet read isuue

Hi all
First of all thanks for taking time to help me with my problem. Let me explain
I have developed a telnet connection program that connects to a switch and interacts with it. But unfortunately when i try to login to the switch after sending the password the switch does not reply.
If i try and connect directly (without the use of my program) with the switch using telnet i can login without any problems.
below is the flow
1. readUntil the prompt "USERNAME>"
2. send the username
3. readUntil the propmt "PASSWORD>"
4. send the password
5. readUntil the prompt "WELCOME>"
i can get to step 5 using the telnet utility. But im not getting the "WELCOME>" prompt when i use my program.
the readUntil() method reads the input and returns what ever that is sent. It reads character by character
While the send(String value) method writes the String value as a byte stream along with a Carriage Return.
When using my program step 5 does not return anything. (The switch doesnt reply) But it provides the correct output when i use a telnet connection.
I have checked Both the read and send methods and cannot find a flaw.
what could be the reasons for this ?
  private StringBuffer readUntil(String pattern) {
    try {
      System.out.println(
      char lastChar = pattern.charAt(pattern.length() - 1);
      StringBuffer sb = new StringBuffer();
      //for timinging out purposes
      long startTime = System.currentTimeMillis();
      long currentTime = 0;
      char ch = ' ';
      while (true) {
        currentTime = System.currentTimeMillis();
        if ( (currentTime - startTime) > TIME_OUT) {
          return sb.append(TIME_OUT_STRING);
        if (ch == lastChar) {
          if (sb.toString().endsWith(pattern)) {
            System.out.println("");
            System.out.println(
            return sb;
        if (in.available() > 0) {
          ch = (char) in.read();
          sb.append(ch);
          System.out.print(ch);
          startTime = System.currentTimeMillis();
        else {
          Thread.sleep(1);
    catch (Exception e) {
      Debug.getInstance().printUsingDebug(e);
      logger.log(Level.SEVERE, "Problem in Reading from stream", e);
    return null;
  private int writeln(String value) {
    try {
      out.write(value.getBytes());
      out.write(13);
    catch (IOException ex) {
      Debug.getInstance().printUsingDebug(ex);
    return ConnectorError.SUCCESS;
}Please note that this program works fine with the same type of switch on several other machines.

currentTime = System.currentTimeMillis();
if ( (currentTime - startTime) > TIME_OUT) Delete that and use Socket.setSoTimeout, and catch SocketTimeoutException below.
if (in.available() > 0) {Delete this test.
else {
Thread.sleep(1);
}Delete this 'else' block. Just let the read() block until data arrives or the timeout occurs.
catch (Exception e) {Here you must distinguish between SocketTimeoutException and IOException. There's not much point in catching anything else.
out.write(value.getBytes());
out.write(13);
  out.write(value+"\r\n".getBytes();
  out.flush();

Similar Messages

  • Query works in Tera Term but not in Telnet Read.vi

    I am using Telnet Write.vi to execute a command such as GET_VERSION
    Then using Telnet Read.vi, I am expecting several lines to be returned.
    This works if I manually do this with Tera Term.
    But with LabVIEW, the Telnet Read.vi simply returns the command from the Telnet Write.vi
    What do I have to configure to change this behavior?

    Edit:
    Needed to add carriage return +  newline 
    DUH.

  • Endless Telnet Read Loop

    Hi
    My goal is to constantly archive data to a local machine thru a Telnet connection.  I receive a small amount of streaming data (25 bytes/second) thru a static IP address.  The code that is attached is my attempt to
    1) initiate a Telnet connection to a static IP address
    2) read the streaming data, write to binary file on local machine
    3) send some pertinent info to the screen for the user
    since I always want to have the VI reconnect if the Telnet connection is dropped (or times out), I attempt an "endless" loop that will
    4) close the Telnet connection
    5) reopen the Telnet connection
    6) recommence writing data to binary file on local machine
    My questions are:
    Q1) Did I write this correctly?  Behavior is erratic.  Sometimes works perfectly, sometimes doesn't work.  I am unclear if I need to use a sequence of events within the outer loop to properly reconnect whenever a telnet connection is lost (sequence1: open Telnet, 2: write data. 3: close session, loop back to 1).
    Q2) Often, when there appears to be no successful Telnet connection (by this, I mean no data streams to the screen which indicates the data feed will not be written to a binary file on the local machine), the numbers in the "File Size (bytes)"  continue to increase.  When I open the binary file to see what is being written I find the same character repeated instead of the data I wish to collect.  I think perhaps that the Telnet Read is reading something, but I don't know what it is, or how to control it.  Any ideas?
    Thanks!
    Attachments:
    MBB06RawTelemetry.vi ‏27 KB

    I said stop the inner loop either when the
    button is pressed (as you still have) OR there is an error.  So look at
    the status of the error wire and OR it with the stop button before
    wiring into the inner loops stop terminal.
    Ok. Clear now.
    I'm not sure
    why you'd be getting a stop/continue dialog for error 56 because I
    can't see anywhere in the code that would cause the dialog to pop up. 
    Drop some more indicators on your error wires, or probes.  Run with
    highlight execution turned on.  Do any or all of these things until you
    can figure out where the error is occurring.
    Ok.  I can do this.  More later if necessary.  
    I don't know
    where ^@ would be getting generated from unless somehow the telnet
    protocol is doing it.  What you could do is put a case structue or
    select statement in the middle of the string so that if there is no
    error, the string value goes from the read to the file.  If there is an
    error, an empty string goes to the file.
    What do you mean by "in the middle"?
    Q3: Is it possible that having multiple Telnet sessions open at one time would create issues like this?  The final goal is to archive the telemetered data from 6 stations at once through the telnet port of one machine.
    Go Beavers.

  • Error 56 in Telnet Read

    Hi!
    Does anybody know why I get error 56 with Telnet Read function even
    connection is workin fine and I can receive messages trough Telnet? I
    have tryed to use Line read and normal mode. With normal mode i have
    use bytes to read values, which are same as send data or even smaller
    than sended data, but always I get error 56. After error 56 apperars,
    sended message from Telnet Read buffer is read to my VI and everything
    works correctly. Problem in this is that I would like to error handler
    to tell user when connection realy doesn't work, but now error 56 comes
    even everything works fine.
    Thanks for all help I can get.

    Using Labview 8.5, XP, Telnet Line Client, I get the following error 56, TCP Read in Telnet Buffered Read.vi->Telnet Read.vi:3->Telnet Line Client.vi.
    I looked up this error which looks to be a Networking error:  56 The network operation exceeded the user-specified or system time limit. 
    The data does seem to return properly but this has been an ongoing issue with previous Telnet clients we are using.

  • Telnet read problem -- Telnet read back

    I am trying to use telnet to send TL1 command to my UUT and expect to read back measurement data.  I was able to read proper data once in a while but most of the time I read back the TL1 command that I sent.  I tried different read mode and timeout period but nothing seem to matter.  My vi was written in Labview 8.2.1 with Internet toolkit.  I read in the forum about some limitation of the telnet read problem of the vi from the internet toolkit,  Is there any better read driver around?
    Thanks,
    Patrick 

    Hey!  I have a few questions for you that should help us solve this problem.  First, have you tried out the telnet shipping example "Telnet Line Client.vi".  This will help us minimize programming errors, etc.  Also, what type of device are you trying to communicate with?  Are there other forms of communication available?  For example, does the device also have a serial port, GPIB Port, etc.?  Also, is it possible to write to the device using TCP/IP (This is what telnet is based on)?  Let me know the answers to these questions and I will be better equipped to help you out!!
    Thanks!
    Dan
    Daniel Eaton
    National Instruments
    Systems Engineering
    Embedded and Industrial Control

  • Telnet Read VI and variable length response

    I am trying out Internet Toolkit's Telnet VIs.
    It seems that the Telnet Read VI defaults to 60 bytes.
    I am not sure what is the best way to deal with the situation of a variable length response.
    Some responses are 3 lines; others can be 50 lines.

    the line seperator is explicitedly <CR><LF> or carriage return and line feed. No other line seperator is automatically supported.
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • Telnet read problem

    While doing telnet read, if the operation times out, I don't get an error.
    I am using telnet read in line mode. My line separator is my prompt char
    "cli>". Timeout is set to 10seconds. If I turn of power to my device after I
    logged in successfully, my telnet read operation should fail, but telnet
    read return OK.
    vishi

    I just checked the version of the Internet Toolkit that I have just to check, and that is apparently the intended behaviour. For some reason, NI tends to not see timeouts as an error.
    The thing to do is open up the read icon and follow the error clusters through. In the version I have, there are several places where there is a small icon labled "NO TO" on the error cluster that (you guessed it) filters out any timeout errors that occur.
    The simple fix is to rename the read VI and then go through it and remove all the timeout filters--which really shouldn't be there in the first place.
    Mike...
    Certified Professional Instructor
    Certified LabVIEW Architect
    LabVIEW Champion
    "... after all, He's not a tame lion..."
    Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

  • Two Telnet read VI's running at the same time interfere with each other

    I have a situation where multiple tests must test multiple UUT’s on the same computer. To send commands to and get responses from the UUT's I use a telnet session. The telnet read VI uses a semaphore. Therefore when two separate top level VI's are running, each calling the Telnet read VI, if one Top Level VI is using the Telnet Read VI the other Top Level VI waits for the first one to complete before it can use the Telnet Read VI. This VI is setup for reentrant execution but because of the semaphore it cannot truly be used as a reentrant function. This causes severe problems when trying to communicate with two different telnet sessions simultaneously.
    In the past I have avoided this problem by compiling everything into an executable. Then each Top Level program runs completely independently with no interdependences. However, now I am implementing Teststand and I need to call the same Top Level VI's. I need to be able to get information into them and back out of them from Teststand. This means that I can no longer compile them into stand alone executables. I did compile each top level VI into its own Share DLL thinking that then each top level program would have its own library to call upon. This did not work. Even though both top level programs are compiled into their own DLL there is still interdependency when calling the telnet read VI. One program waits for the other to finish reading from its telnet connection before it can read from its own telnet connection. Since I have to continuously read from the telnet connection, sometimes for up to half and hour, the tests do not function simultaneously. How can I get around this? Is there a solution?
    Josh
    PS The Telnet Read VI I am refering to came with the Internet Toolset package. Attached is a copy of the VI I use to communicat with the UUT's.
    Attachments:
    GUI_Telnet_W-R_Auto.vi ‏64 KB

    Sorry about the confusion.
    The file I attached is in the hierarchy of two separate top-level VI's. The telnet connect is opened once and closed once in each top-level program. The ref number is then passed into and out of the VI that I attached. I use this VI to repeatedly send commands via telnet and wait for the appropriate responses. The telnet read VI is given a read line separator and reads from the telnet connection until it matches the read line separator with a text string read back from the telnet connection. If not match is found it times out and creates an error.
    I am not sure how to provide an example of the overall scheme since the problem occurs when both top level VI's are compiled each into their own shared DLLs. Those DLLs are then call from Teststand and at some points they are both running at the same time on the same computer connected to two different UUT's.
    The question I have is why does one DLL share functions with the other? When one DLL is using the telnet read VI the other DLL waits for the first one to finish with it before it can it use the telnet read VI. If they were both compiled separately each into their own DLL shouldn't they each have their own set of functions to call upon instead of having to share? I know that if the two top-level VI's are not compiled they cannot both execute the same sub-VI at the same time. The only way to get around this is to set the execution property on the sub-VI to reentrant.
    I actually fixed the problem by setting the VI I attached and the Telnet Buffered Read.VI (called by Telnet Read.vi) execution properties to reentrant. However, I am still concerned about two separate DLLs sharing sub-VIs. Why does it do this?
    Joshua

  • Telnet library: asynchronous read and write

    I need control a device using the telnet protocol. It sends its logging messages asynchronous and I need to send commands to to setup it for measurements. There is no prompt, where it is waiting for commands. Therefore I can't use "Telnet Read Until".
    My idea is now to start a thread with a loop calling   "Telnet Read" and sending the commands from the main thread. Is multithreading in that way supported by CVIs telnet library ?

    Hi mkossmann,
    you can use multithreading in CVI as in native C.
    When your target does not send any starting comment, I guess your idea could be a good way to implement the communication in CVI.
    Regards,
    Melanie

  • How do I connect multiple telnet clients to a telnet server in LabVIEW?

    Good afternoon,
    I'm writing a telnet server in LabView 6.1 that needs to handle multiple clients. To do this, I modified the "viserver\runvi.llb" example to use the telnet VI's from the Internet Toolkit instead of the TCP VI's. Then I changed the Open VI Reference to point to my telnet handler. Right now my handler just echoes the characters received from the client.
    My software works ok for the first connection. After the server accepts two or more connections, characters typed in one client get echoed to all clients. In addition, only one client will accept characters at a time. The client accepting input changes randomly every few seconds as characters are entered.
    Has anyon
    e gotten the telnet VI's to run in parallel? Not sure if they are thread-safe or not. If you have some experience with this, I have attached my llb if you think you can help.
    Thanks!
    Chris Norris
    Carrier Access Corp.
    [email protected]
    (303) 218-5826
    Attachments:
    CAC_Telnet_Server.llb ‏92 KB

    I don't think there's a problem with the TCP/connection portion of things. My feeling is that the problem is lurking somewhere in the timing of the application, or in the way LabVIEW task scheduling/multitasking is working compared to the way you expect it to work.
    For instance, I'm wondering why you stuck with 25 seconds (25000 ms) as the timeout value for the Telnet Read in Telnet Handler.vi. I assume you're expecting LabVIEW to quickly "sleep" that while loop and move on to check on the while loops of any other Telnet Handler.vi instances that might have been spawned as a result of connection requests from other remote clients.
    Instead, it seems to me (on my system, anyway, with three simultaneous connections active) that LabVIEW is not cyc
    ling through the other Telnet Handler.vi instances as you expect, but is only getting to them to read a byte at a time each time the main loop iterates in response to a byte appearing from the first of the three remote clients.
    If you change the Telnet Read timeout to 50 ms instead, the behavior is closer to what you might expect, but still not perfect.
    Because timing/threading/scheduling is a complicated subject in LabVIEW, I'm going to give LabVIEW the benefit of the doubt and assume it's operating as designed. Maybe someone else can provide more insight into what's happening in this particular case, and whether reentrancy or something else is affecting things.
    One option I would consider if I were in your shoes: program a simpler version of things that mimics Date Server.vi and cycles through a queue of connections to service them without relying on spawning new reentrant instances of a handler VI.
    I realize that your version of things (along with the reentrancy example
    that ships with LabVIEW) is expressly intended to handle this daemon-style situation, but simpler may be better for the purposes of debugging and development ease.
    My two cents,
    John Lum
    National Instruments

  • Telnet data out

    Hello,
    I am having a problem with the telnet read data out, i am getting with the wanted output also many other characters, is there any way to filter those?
    example:
        [1;1HMicrosoft Windows XP [Version 5.1.2600] [2;1H(C) Copyright 1985-2001 Microsoft Corp. [4;1HC:\Documents and Settings\bmulab\Desktop> [4;42H [4;44H [4;1HC:\Documents and Settings\bmulab\Desktop>cd C:\Documents and Settings\bmulab\Des [5;1Hktop\nic [6;1H [4;45H [7;1H [4;46H [7;1H [7;1HC:\Documents and Settings\bmulab\Desktop\nic> [4;47H [7;46H [4;48H [7;46H [4;49H [7;46H [4;50H [7;46H [4;51H [7;46H [4;52H [7;46H [4;53H [7;46H [4;54H [7;46H [4;55H [7;46H [4;56H [7;46H [4;57H [7;46H [4;58H [7;46H [4;59H [7;46H [4;60H [7;46H [4;61H [7;46H [4;62H [7;46H [4;63H [7;46H [4;64H [7;46H [4;65H [7;46H [4;66H [7;46H [4;67H [7;46H [4;68H [7;46H [4;69H [7;46H [4;70H [7;46H [4;71H [7;46H [4;72H [7;46H [4;73H [7;46H [4;74H [7;46H [4;75H [7;46H [4;76H [7;46H [4;77H [7;46H [4;78H [7;46H [4;79H [7;46H [4;80H [7;46H [5;1H [7;46H [5;2H [7;46H [5;3H [7;46H [5;4H [7;46H [5;5H [7;46H [5;6H [7;46H [5;7H [7;46H [5;8H [7;46H [5;9H [5;1H [6;1H [7;46H [7;48H [7;1HC:\Documents and Settings\bmulab\Desktop\nic>Disable_NIC.exe [8;1H [7;49H [8;1H [7;50H [8;1H [7;51H [8;1H [7;52H [8;1H [9;1HC:\Documents and Settings\bmulab\Desktop\nic> [7;53H [9;46H [7;54H [9;46H [7;55H [9;46H [7;56H [9;46H [7;57H [9;46H [7;58H [9;46H [7;59H [9;46H [7;60H [9;46H [7;61H [7;1H [8;1H [9;46H [9;48H [9;1HC:\Documents and Settings\bmulab\Desktop\nic>cd C:\Documents and Settings\bmulab [10;1H\Desktop\nic [11;1H [9;49H [12;1H [9;50H [12;46H [12;1HC:\Documents and Settings\bmulab\Desktop\nic> [9;51H [12;46H [9;52H [12;46H [9;53H [12;46H [9;54H [12;46H [9;55H [12;46H [9;56H [12;46H [9;57H [12;46H [9;58H [12;46H [9;59H [12;46H [9;60H [12;46H [9;61H [12;46H [9;62H [12;46H [9;63H [12;46H [9;64H [12;46H [9;65H [12;46H [9;66H [12;46H [9;67H [12;46H [9;68H [12;46H [9;69H [12;46H [9;70H [12;46H [9;71H [12;46H [9;72H [12;46H [9;73H [12;46H [9;74H [12;46H [9;75H [12;46H [9;76H [12;46H [9;77H [12;46H [9;78H [12;46H [9;79H [12;46H [9;80H [12;46H [10;1H [12;46H [10;2H [12;46H [10;3H [12;46H [10;4H [12;46H [10;5H [12;46H [10;6H [12;46H [10;7H [12;46H [10;8H [12;46H [10;9H [12;46H [10;10H [12;46H [10;11H [12;46H [10;12H [12;46H [10;13H [10;1H [11;1H [12;46H [12;48H [12;1HC:\Documents and Settings\bmulab\Desktop\nic>Enable_NIC.exe [13;1H [12;49H [13;1H [12;50H [14;46H [14;1HC:\Documents and Settings\bmulab\Desktop\nic> [12;51H [14;46H [12;52H [14;46H [12;53H [14;46H [12;54H [14;46H [12;55H [14;46H [12;56H [14;46H [12;57H [14;46H [12;58H [14;46H [12;59H [14;46H [12;60H [12;1H [13;1H [14;46H"
    Thanks.

    Hi Alvarion_Israel,
    which charachters do you want to filter out?
    Mike

  • How to use the telnet command line in Labview

    Hi, someone can help me, I need to use a Telnet session in Labview but without using the http protocol, in this application I can only access the Telnet session using command line, here is an example of how I can access:
    From my computer, click on Start, then Run and then type in CMD.
    In the command line enter “telnet 192.168.0.1 5454” (without the quote marks) to bring up a blank DOS screen with a blinking cursor.
    Type “AT” and press the ENTER key, you should receive an “OK” response.
    Type in capital letters “AT+CMAR=1234” (without the quote marks)

    I had a similar situation and here is what I did...
    In MAX (Measurement and Automation eXplorer)
    Select Devices and Interfaces
    Select VISA TCP/IP Resources
    Create a new resource
    Select Manual Entry of Raw Socket
    Enter the IP address and port (23 is the standard telnet port)
    Give it a name. (VISA Ailas)
    Now this "Device" will show up in the VISA drop down just like any other VISA device.
    Use the VISA read and write just like you were communicating through a com port.
    Since Telnet does not have a stop bit like serial, make sure you enable the termination character.
    On your VISA reads set the number of characters to a big number, then VISA will read until it gets the termination character.
    See my attached snippet of my Telnet read vi
    Message Edited by RTSLVU on 06-16-2010 01:49 PM
    Message Edited by RTSLVU on 06-16-2010 01:50 PM
    Attachments:
    telnet.png ‏40 KB
    max1.png ‏33 KB
    max2.png ‏31 KB

  • Telnet Buffer Questions

    Hi,
    Modems are configured to telemeter data to a LabView VI.  The LabView VI works as designed when hardwired to the instruments.  Now a modem and internet connection replace the hardwire, so a reconfiguration of the VI was required using Telnet Read/Writes instead of VISA Read/Writes.  Initially there were some kinks associated with the modem configurations, but those have been worked out.  Reason for backstory: I believe I have isolated my issue to how I use/configure Telnet Read.
    My issue: data dropouts and incomplete data packets.  I receive 25 bytes of binary data per second, easiestly viewed as Hex when it streams in.  A valid packet looks like this:
    0119 81CC 4C47 884B 5722 7ECA 000A FA37 7E52 FC66 7CF7 25D0 04
    where 01 begins the sequence, and 04 ends the sequence.  All the mess inbetween is useful to me, but completely uninteresting to most sane people.  Attached are two examples of code.  The first, TelnetEx.vi, is a simple version of how I use the Telnet Read.  When I use this configuration I think I am buffering 25 bytes of data then ending the line whenever a hex04 is observed.  All too frequently I receive packets that are not 25 bytes long, but end in hex04.  By the way, I haven't been successful using 'normal' or'immediate' mode with the Telnet Read - I get no data packets delivered at all.  (??)
    So I thought if I could hardwire a way to spot-check the 25-byte buffered data packet then I would outsmart the incomplete packets (an incomplete packet results in false spikes in my data as the VI is wired to look for data in a particular byte location in the data packet). An example of this shoddy attempt is shown in TelnetEx.vi.  When I apply this filter, I receive no data.  The filter is supposed to look for hex01, then look for hex04, then count to see if they are 25 bytes apart, and if they are, send that data to the rest of the VI because it is a valid packet.
    One last note: I have been tinkering with the VI and found that if I use the time-delay at a faster sampling rate (10Hz) than my instrument (instrument = 1Hz) then I have fewer incomplete packets delivered, and sometimes there is a pause that looks like a data dropout and then I receive multiple packets at once.  This is probably a connection/packet delivery issue, but perhaps someone has seen this before and knows a good way to handle it?
    Is the Telnet Read buffer a FIFO?  Is there a more sophisticated method of checking the validitiy of a data packet than my mangled attempt?
    Thanks,
    ~Tristan
    Solved!
    Go to Solution.
    Attachments:
    TelnetEx.vi ‏17 KB
    TelnetEx2.vi ‏24 KB

    Take a look at the revised example. Also, are you guaranteed that the 0x04 will never be part of the data itself and it will only appear as the termination character? My example assumes that it will only appear as a termination character and never be part of the valid data. Have you sniffed the data using a LAN analyzer (think Wireshark) to verify what is actually being sent by the device?
    Under the hood at the socket layer data does get buffered. In fact, depending on the implementation of the stackon the device sending the data you could receive multiple packets of your data in a single TCP packet. It is legal and valid for the stack to buffer data before sending it. This generally occurs more often when you are sending lots of small packets very quickly. In your case I doubt this is happening.
    Message Edited by Mark Yedinak on 10-22-2009 05:24 PM
    Mark Yedinak
    "Does anyone know where the love of God goes when the waves turn the minutes to hours?"
    Wreck of the Edmund Fitzgerald - Gordon Lightfoot
    Attachments:
    TelnetEx-1.vi ‏21 KB

  • Telnet Error code 56 with Telnet Line Client Example?

    Using Labview 8.5, XP, Telnet Line Client, I get the following error 56, TCP Read in Telnet Buffered Read.vi->Telnet Read.vi:3->Telnet Line Client.vi.
    I looked up this error which looks to be a Networking error:  56 The network operation exceeded the user-specified or system time limit. 
    The data does seem to return properly but this has been an ongoing issue with previous Telnet clients we are using.

    Hi ShotSimon,
    You may want to refer to this KB. The Telnet Listen.vi uses the TCP Listen.vi. I hope that helps!
    Mike Lyons
    National Instruments
    http://www.ni.com/devzone

  • Telnet error (Code: 62)

    I'm running VIs (LV8.6) under TestStand 4.1.
    The
    following message is from a Telnet Read/Write vi.  I usually open the
    Telnet connection at the beginning of the test and close it at the
    end.  Sometimes there is a gap of long time without any telnet
    activity.  I set the timout of the Telnet connection to 1 hour.
    Any idea what this error mean?
    ------------------------------- Run Time Error ----------------------------------------------------
    A Run-time error has occurred in step: Remove All clocks Priorities
    Sequence: Select_TMU_input
    SequenceFile: D:\views\quad3_HLXC1536\NPI\TESTER\Work\HLXC1536\Seq\HLXC1536.seq
    Error
    Message: TCP Read in NI_InternetTK_Core_VIs.lvlib:Telnet Buffered
    Read.vi->NI_InternetTK_Core_VIs.lvlib:Telnet
    Read.vi:1->TelnetReadWrite.vi->TelnetReadWrite.vi.ProxyCaller
    Error Code: 62
    Thanks
    Rafi

    The error code means:
    The system caused the network connection to be aborted.
    It's possible that the device you are telnetting into is timing out and closing the connection. In general I find it much more relaible to open a connection, use it, and then close it before long periods of inactivity.
    Mike...
    Certified Professional Instructor
    Certified LabVIEW Architect
    LabVIEW Champion
    "... after all, He's not a tame lion..."
    Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Maybe you are looking for

  • Concurrent report ending in warning with status 127 (post upgrade to R12.1.

    Hi, We ran a concurrent report with Print options set for a custom report. The report is ending in warning with the below error: ------------- 1) PRINT   ------------- Printing output file. Request ID : 356879180       Number of copies : 1       Prin

  • TS4268 I updated the 7.0 IOS Now I can not use my face time

    I updated to the 7.0 IOS but now when I try to use FaceTime it says Could not sign in. Please check your network connection and try again. I have tryed multiple wifi locations as well as not using wifi at all. Help

  • G5, Airport Extreme, and NO MORE SIGNAL!

    ok...I hope someone out there can help me with my issue here. I have a first generation 1.8ghz single processor G5 (900mhz bus) and had it built custom with an Airport Extreme card. I've been running the recent software of everything. Well up until a

  • Retrieve account members with time balance of "last"

    Hi everyone, I am trying to write a report scripts that will retrieve from the Accounts dimensions all members that have Time Balance of Account information of "Last". I haven't been able to get the correct syntax to do this retrieval. Is there an ex

  • OC4J and BC4J Runtime installation for Solaris (Unix)!

    We have successfully installed, configured and deployed JSP/BC4J apps using OC4J and BC4J on Windows NT/2000. However, our production environment is Solaris. We have installed OC4J on Solaris, with some difficulties. How/where is the installation pro