Hi Trevor,
About "No Carrier with Arachne browser" of Aug. 9:
T4> I can hear the modem dialing/operating and in
T4> the terminal window I see (after authenti-
T4> cation) meaningless symbols... ...then I get
T4> the message - "NO CARRIER".
MS> ...launch and configure the packet-driver from
MS> a separate dialer... ...forget about the
MS> internal one which you can find in LSPPP...
T4> I am using the terminal (miniterm) and I am
T4> viewing data packets after authentication...
The night reaches its end already so i'll try this
old adage until i can write further on your topic:
an image is worth a thousand words they say and my
time grows short so, i hope you won't mind i used
a counterpart of Arachne's dialer to illustrate!
;->
http://public.sogetel.net/bicephale/PPP-Auth.HTMl
The DOS capture would be exactly the same. My 1st
picture shows a case where the ISP is known to be
DOS friendly but i used so much time to enter the
UserName, it finally was ready to give up! Should
i have continued to ignore the prompt long enough,
the ISP would have disconnected me (this given ISP
has some very well behaved terminal servers in its
pool)... My second picture is for when i complete
the TTY LogIn in time (no PAP/CHAP authentication
here), the PPP protocol negociation follows next
but since i haven't closed the window yet it means
the ISP's PPP protocol has no reciprocal peer and
since PAP/CHAP authentication require the PPP part
to complete 1st, euh... in the case of an ISP who
isn't that much DOS friendly, euh, this would just
mean no authentication has taken place at all.
;^)
There's a 3rd picture i could have taken but then
you wouldn't have seen much because when PPP/CHAP
authentication is used one doesn't have to wait a
single bit: as soon as the CARRIER condition is
detected you know the MoDems have negociated their
connection successfully and it's time to start the
PPP protocol (hence, the terminal window would be
closed before most ISPs can even send their prompt
if any). One reason which can make an ISP hang up
on you is because the PPP packet-driver simply is
not found, meaning it won't take over; another is
you couldn't agree on the authentication protocol.
In any case, the "Chicken Tracks" are no proof you
have been validated successfully, even when an ISP
seems to support manual LogIn, i've seen instances
when i still had to enable PAP or CHAP validation!
8-b,
For this reason, i suggest you always try to use a
form of automated authentication even if scripting
is active, euh... Ho, and one very old bug that i
never managed to bring enough focus on is the fact
that the packet-driver may be present but it fails
to take adequate control of one's MoDem because of
the way in which the wizard gets its corresponding
serial-port defined on the driver's command-line!
%-o
T4> ...which packet driver do you recommend?
PS> Two things to try, firstly Arachne version
PS> 1.85 and secondly use the alternative LSPPP
PS> dialer, see: http://83.67.55.228/
I checked the later reference, i found it's valid.
I don't believe using Arachne v1.85 will make much
difference though, if the problem is with the way
it builds its command-line you're still in trouble.
The last verion of LSPPP (2003-Oct-12) is fine with
me but then, again, i just don't trust its internal
dialer!!! Yet, here's a short path to this driver:
http://members.tripod.com/~ladsoft/lsppp/lsppp10.zip
T4> Merci beaucoup pour votre assitance...
It's a pleasure, you're most welcomed! 8-)
Salutations,
Michel Samson
a/s Bicephale