On Thu, 13 Jul 2000 14:49:04 -0500, Glenn McCorkle wrote:
> On Wed, 12 Jul 2000 20:45:10 +0200 (MET DST), Bernie <[EMAIL PROTECTED]>
> wrote:
>> Michael wrote:
>>> This should be definitely FAQ No.1 :-(
>> IMHO we should as answer (I don't have the time to make the FAQ) point out
>> that the user should try PAP/CHAP first and *then* try a scripted login.
>> Just as Michael are getting tired of that question I must say I'm getting
>> tired of the answer to how a connection should be made ;-)
>> PAP/CHAP is the only way AFAIK that Windows 9x, and this was the standard
>> login in Trumpet for 3.x, can connect so I really doubt any user won't be
>> able to connect if there would be no more suggestions that a manual login
>> should be attempted first. Instead of assuming that something is weird at
>> the ISP (except the support personel <g>) we should IMHO assume that they
>> do support PAP/CHAP and try that first. Now if that doesn't work a manual
>> login is in order.
> Very good suggestion. Thank you Bernie.
> Q: What's the easiest way to "login" to my ISP with Arachne?
> A: Use PAP/CHAP as the first line of action.
> During your first setup of Arachne, choose
> not to show the terminal screen.
> Choose not to use an "auto login".
> And be sure to enter your username and password
> on the PAP/CHAP setup screen.
> Glenn McCorkle [EMAIL PROTECTED] North Jackson, Ohio, USA
The terminal screen was a great help when I had login troubles getting
Arachne going for the first time.
After dialing my ISP responds with "** UDS Terminal Server NLUDSOHRV50"
and this showed that dialing, modem and telephone connection were OK.
Then the server gave "Login:" and then things went wrong due to the
Login & Password script containing "-".
Removing those "-"s cleared the script and Arachne went OK.
Indeed questions about connecting and login are the most asked and
tiring ones... and almost any newby starts with them.
Bastiaan
.
-- Arachne V1.61, NON-COMMERCIAL copy, http://arachne.cz/
