Telnet paste from Windows 2000 to Unix problem

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Recently my company has switched to new dell workstations (gx620's), and now
the Microsoft Telnet Client, that comes with Windows 2000, is no longer
reliable when we paste text into a telnet session with a unix server. The
problem is that random characters end up replaced by other characters. If we
are telnetting another windows server we do not have this issue with paste.
In doing some research I saw that there are telnet clients that have some
sort of delay/slow paste features which lead me to believe that maybe the new
workstations are pasting the text too fast? Thanks.
 
Try using Hyperterminal as the Telnet Client instead of the commandline
version.


--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/techinfo/Guidance/2004.asp
http://www.microsoft.com/isaserver/techinfo/Guidance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp

Deployment Guidelines for ISA Server 2004 Enterprise Edition
http://www.microsoft.com/technet/prodtechnol/isa/2004/deploy/dgisaserver.mspx
 
Thank you for the suggestion. I actually wanted to know if this is a known
issue, and if there is a fix or workaround for this. I know there are
probably better solutions (hyperterminal) and third party telnet clients we
could use, so this request is more for the conveinience of being able to
access telnet right from a command window. Thanks again for the reply.

Phillip Windell said:
Try using Hyperterminal as the Telnet Client instead of the commandline
version.


--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/techinfo/Guidance/2004.asp
http://www.microsoft.com/isaserver/techinfo/Guidance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp

Deployment Guidelines for ISA Server 2004 Enterprise Edition
http://www.microsoft.com/technet/prodtechnol/isa/2004/deploy/dgisaserver.mspx
-----------------------------------------------------



FIC_WILL said:
Recently my company has switched to new dell workstations (gx620's), and now
the Microsoft Telnet Client, that comes with Windows 2000, is no longer
reliable when we paste text into a telnet session with a unix server. The
problem is that random characters end up replaced by other characters. If we
are telnetting another windows server we do not have this issue with paste.
In doing some research I saw that there are telnet clients that have some
sort of delay/slow paste features which lead me to believe that maybe the new
workstations are pasting the text too fast? Thanks.
Click to expand...
Click to expand...
 
Recently my company has switched to new dell workstations

You have my sympathies :-)
sort of delay/slow paste features which lead me to believe that maybe the
new
workstations are pasting the text too fast?
Click to expand...

I've had this happen where a remote could not accept input as quickly as I
could paste it into a window. My solution was, as previously suggested, to
use Hyperterm as the telnet client. In hyperterm properties, under Ascii
Setup, you can place character and line delays in miliseconds. For me,
placing a 20 ms delay between characters solved the problem. As a note, I
didn't get incorrect characters, but I did have characters missing.

As far as being a known problem with a fix, I would think the receiving end
is where the problem exists. Since a telnet session can transmit at whatever
rate your network runs, the receiving telnet client would have to be able to
process the stream at full rate. You may be able to set up Xon/Xoff
handshaking, but that is controlled at the application layer, so it might
not be quick enough to prevent errors.

....kurt
 
Does anyone think this is something that is worth opening a case with
Microsoft over? Do you think they would acknowledge this as a bug maybe?
Thanks.
 
Back
Top