Search Again:

Re: Telnet to BSDI still not working

From: Shawn Hogan
Date: Tuesday, July 21, 1998
Time: 1:12:14 pm

Bill Warner wrote:

>For one thing, they probably set the terminal type during negotiation, that
>way tset won't prompt for it later.

Yep... That's exactly what it's doing (and what I tried to do with the
new telscrpt.exe file). But it didn't like it... so that's why I want to
see what else they are doing. :-)


>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.

Maybe so... but I would rather have it just "work" then explain to people
how to change their shell account config. :-)


>Heh, I know that feeling, but we can't all be experts at everything...

I know, I know... I'm just used to being the best at what I do.
hehehehe... (that was a little joke). hehe


>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...

Well I still want to make it "just work" without any shell configuration.
:-)

- Shawn

-------------------------------
Shawn D. Hogan
President, Data Point Solutions
http://www.data-point.com
(619) 452-3696
ICQ: 8319647



Messages In This Thread:



Return to Digital Point Solutions' Home Page