Search Again:

Re: Telnet to BSDI still not working

From: Serge Pluess
Date: Tuesday, July 21, 1998
Time: 1:49:10 pm

At 02:39 PM 7/21/98 -0500, you wrote:
>For one thing, they probably set the terminal type during negotiation, that
>way tset won't prompt for it later.
>
>Anyway, let me know if you ever do want to peek at the BSDI source...
>
>Yeah, IMO that's not necessarily a bad option. After all, your original
>telnet client *does* work, and this is as much, if not more, a shell
>account config. issue as a telnet issue.
>
>Heh, I know that feeling, but we can't all be experts at everything...
>
>Ugly and unnecessary. All they have to do is configure the shell account
>not to prompt, or configure Optigold-ISP to answer the "Terminal type?"
>prompt. Trivial. You wouldn't blame your telnet client if someone had
>their shell account configured to use S/Key logins and failed to set
>Opigold-ISP to give the correct responses, would you? As far as I can see,
>this is the same thing. People have their accounts configured to prompt
>for something (terminal type) and they are not supplying the correct
response.
>
>*** Keep in mind that all of this applies to your *old* telnet client. I
>haven't had a chance to DL the new one...
>
>--Bill

The telnet session never even gets to the point of a prompt at all. The
debug window says that the connect is successful and then in the title-bar
of the window the first line of the BSDI 2.1 banner is displayed. It never
gets to a login or a Terminal Type prompt.
None of the account on that machine is set to prompt for a terminal type.

All the different tries including yours with changing the shell account
and/or configuring to prompt, etc have resulted in absolutely no change of
behaviour.

Greetings

Serge



Messages In This Thread:



Return to Digital Point Solutions' Home Page