| View previous topic :: View next topic |
| Author |
Message |
Biker
Apprentice
Joined: 11 Jun 2003
Posts: 170
Location: A very dark, cold and moisty place...
|
 Posted: Wed Dec 24, 2003 2:42 pm Post subject: telnet from Linux and from Windows behaves differently |
 |
|
Must change ADSL provider and ISP.
As a result, I have (unfortunately) become stuck with an ADSL modem of the brand and type BeWan Ethernet ADSL cx, where the "cx" seems to be some special version provided by BeWan to Tele2 in France. (Can't find this ADSL modem on the BeWan web site.)
One of the actions I need to perform to set this up, is to connect to their modem through telnet in my local network. I learnt a lot while setting up an alias address on the Ehternet card I will use for this purpose and I can now successfully contact the telnet server in the modem from any computer in my network. (It's hooked up to the 'external' card on the default gateway PC.)
But the result is everything but satisfactory. Characters are missing, control codes seem to be wrong and the telnet 'site' behaves most erratically. Accessing any Internet servers through this gateway PC works perfectly well, going through the existing modem that will be phased out.
By chance (???) I happen to temporarily have access to a Win2k based PC. I hooked up the ADSL modem to this computer over a crossed Ethernet cable and tried to telnet to it. Lo and behold if this didn't work perfectly well! All data comes through, control characters and all. The telnet 'site' works perfect.
Question:
What's the difference in a Windows 2k telnet client and a Linux client, or what are the significant differences in the configuration of these clients?
Biker
_________________
The Internet never forgets.
Where 'never' points in the direction of a moment in the very, very far future. |
|
| Back to top |
|
 |
scout
Veteran
Joined: 08 Mar 2003
Posts: 1991
Location: France, Paris en Semaine / Metz le W-E
|
| Posted: Wed Dec 24, 2003 4:12 pm Post subject: |
|
|
| Quote: | | What's the difference in a Windows 2k telnet client and a Linux client |
I honestly don't know, but you might try to install a different telnet client for linux.
There are at least two different packages:
| Code: | * net-misc/netkit-telnetd
Latest version available: 0.17-r3
Latest version installed: [ Not Installed ]
Size of downloaded files: 130 kB
Homepage: ftp://ftp.uk.linux.org/pub/linux/Networking/netkit/
Description: Standard Linux telnet client and server
* net-misc/telnet-bsd
Latest version available: 1.0
Latest version installed: [ Not Installed ]
Size of downloaded files: 169 kB
Homepage: ftp://ftp.suse.com/pub/people/kukuk/ipv6/
Description: Telnet and telnetd ported from OpenBSD with IPv6 support |
_________________
http://petition.eurolinux.org/ - Petition against ePatents
L'essence de la finesse |
|
| Back to top |
|
|
Biker
Apprentice
Joined: 11 Jun 2003
Posts: 170
Location: A very dark, cold and moisty place...
|
| Posted: Thu Jan 08, 2004 8:06 pm Post subject: |
|
|
| scout wrote: |
I honestly don't know, but you might try to install a different telnet client for linux.
There are at least two different packages:
|
OK, it took some time.  But I have now tried both the telnet-bsd version of telnet plus putty but they behave in the same way as the standard Linux telnet client.
So the question remains:
What does the Windows telnet client do so differently from the Linux telnet client?
The difference in behaviour are typically that the Linux client(s) ignores most control characters sent down from the telnet server in the modem. (BTW, I've found out that the modem runs a VxWorks based telnet server and software from Conexant Systems)
Also, when I enter characters in the Windows telnet client, they are immediately interpreted by the server, while the Linux telnet client requires me to hit enter for the server to read the character.
Biker
_________________
The Internet never forgets.
Where 'never' points in the direction of a moment in the very, very far future. |
|
| Back to top |
|
|
Arno
Tux's lil' helper
Joined: 19 Oct 2002
Posts: 126
Location: France
|
| Posted: Fri Jan 09, 2004 12:52 am Post subject: |
|
|
| Biker wrote: | | Also, when I enter characters in the Windows telnet client, they are immediately interpreted by the server, while the Linux telnet client requires me to hit enter for the server to read the character. |
I think that most Un*x Telnet clients default to line mode (IIRC, as recommended in one of the Telnet RFCs), Windows Telnet clients are character mode only. |
|
| Back to top |
|
|
Biker
Apprentice
Joined: 11 Jun 2003
Posts: 170
Location: A very dark, cold and moisty place...
|
| Posted: Fri Jan 09, 2004 4:48 pm Post subject: |
|
|
| Arno wrote: | | I think that most Un*x Telnet clients default to line mode (IIRC, as recommended in one of the Telnet RFCs), Windows Telnet clients are character mode only. |
You got it. By using putty with the option 'Local line editing: Force off' it works.
Great. Thanks for the tip!
Biker
_________________
The Internet never forgets.
Where 'never' points in the direction of a moment in the very, very far future. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Networking & Security
