Path: utzoo!attcan!uunet!cs.utexas.edu!sun-barr!olivea!apple!amdahl!datta From: datta@uts.amdahl.com (Diptish Datta) Newsgroups: comp.protocols.tcp-ip Subject: Telnet echo negotiation question Summary: Server echoes data after negotiating no echo Keywords: Telnet Echo Message-ID: Date: 26 Oct 90 21:29:56 GMT Reply-To: datta@amdahl.uts.amdahl.com (Diptish Datta) Distribution: comp.protocols.tcp-ip Organization: Amdahl Corporation, Sunnyvale CA Lines: 28 Does any one out there know of two machines communicating with the telnet protocol and not using remote echo? If so, then the remote server should not be echoing characters typed in at the client and the local client should echo the keyboard entries to the screen - right? Well, I have a lana analyzer trace of a MVS machine logging in to a Unisys unix machine. The MVS machine seems to negotiate no remote echo but it looks to me like the remote machine echoes data any way. Here is what the echo option negotiation looks like: C <------ will echo S L dont echo ------> E I <------ wont echng the server not to echo E dont echo ------> V N wont echo ------> E T <------ dont echo R The way I read this is that the server offers to echo, the client refuses, and server agrees. Then the client says that he wont echo and server says no problem. Then I see the login prompt from the server and the user id data from the client. The server then echoes the user id right back! Basically the Unisys machine seems to have negotiated no remote echo but echoes anyway. Does any one out there have an explanation? Mail direct to me at datta@amdahl.uts.amdahl.com