Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[JDick]

I have a WYSE-60 telnet connection to a serial device server.

After logging on, every prompt in the software has a Euro symbol at the start.  Even Yes/No options that default to Y or N have the Euro symbol in their place. 

Another terminal emulator package we are testing works normally.  Would like to continue using ICE.TCP, as already have 10 of the 30 or so licenses I need.
 

[Bob]

What's changed from when it was working?

[JDick]

What we are doing is replacing our dumb serial terminals with the serial device servers.  We then use a terminal emulator to create a telnet session with the device server.  Cabling is simpler, and it's very stable.

IceTCP has never worked in this configuration.  Smartterm does, but I would prefer to use IceTCP for a variety of reasons, not the least of which is our existing licensing.

IceTCP does work if we directly telnet to the server vs. using the intermediate serial device server.  The direct telnet connections corrupt files if they unexpectedly terminate or do not terminate correctly, which IceTCP manages to do once a week or so on each workstation.

We can interchange the serial device server with the following three options and they all work.
1) replace device server with dumb terminal.
2) replace device server with PC running really old serial version of DejaWin
3) use device server, PC has telnet session (using Smartterm) to device server, device server has serial connection to Unix server.

Thanks,
James

[Bob]

You shouldn't have a problem with a session closing unexpectedly (with a direct telnet).

Try turning on keepalives (configuration->general->Keep alive interval)
Try 6 (once a minute).

As for the euro thing, are you using 24 or 25 line wyse? If 25, try 24. The application will switch it to 25 if need be and it could be the terminal server can't figure out what a wyse60-25 "query terminal type response" refers to.

[JDick]

We've tried both the 24 and 25 line WYSE emulation - same response.

In a perfect network world - no the telnet would keep alive.  We may also be at the mercy of our software in that it may just not handle the telnet session dropping cleanly whereas another package might.

1st - Ice.TCP doesn't always close the session cleanly.
2nd - We run terminals over wifi in the warehouse, in the back of 18 wheelers, etc - direct telnet sessions crash every time the signal fades, the telnet to serial device connections can cut out and resume with no problems.
3rd - Users turn off their power strips, turn off there computers, and generally be...well you know - users....
4th - We run remote terminals over VPN's, the DSL networks used at a couple places go down a couple times a month, plus the folks using wireless broadband modems have the attendant cellular coverage issues. 

[deanna]

What version/build of PLUS are you running?