There had bee on relevant answer already to the question from Pierre
Blais - Quebec City on the non-loading packet driver,
> I tried many products (Arachne, Bobcat, Nettamer, and so on). The
> connection alw ays establish, but just before to receive my IP adress,
> this error message appea rs "No packet driver found", and the call is
> canceled.
- i.e., Nettamer has its own packet driver and there should not be
another one (tried to) be loaded. This said, there *is* a recurrent
problem with the (non-)loading of DOSPPP/EPPPD (thus, for its use with
*other* programs than Nettamer).
I think of three possible reasons for non-succes:
1. the dialler script;
2. wrong or tweaked starter-sequences from the dial-in server which do
not follow standards, so that the authentification procedure doesn't
work.
Perhaps the first has to do with the second too: I found that *some*
dial-in servers, after that the physical modem-to-modem connection was
established, either needed, or just would badly react to, a CR or a
whitespace-CR(-LF) sequence sent when the dialler finishes. Depending
on this condition, the server dialled-in to woul - or woul *not* -
send the opening sequence for PPP negotiation which the packet driver
then needs.
This is pure trial and error; but one can find out with a normal telco
program like Telix with dialling in to the net access point and
inputting all sorts of things manually. If one "garbage" line, which
ends on a "~" (tilde), is coming in repeatedly and in regular short
intervals, then the connection is Ok and the ppp negotiation of the
packet driver would be able to start.
And not that with *some* dial-in points, it's the *dialler* which has
to do a login-dialogue first, before the change is done to the
standardised ppp negotiation.
*Then* it's still a question, depending on the server-side tweaks, if
this negotiation succedes. And quite a lot can go wrong here. It seems
that DOSPPP/EPPPD is not flexible enough vis-a-vis certain
implementation variations done on the server side - and it's not
developped any more since 1997. Nettamer's (integrated) paket driver
can manage with some of these variations/tweakings much better.
Thus for practical reasons I'd try to get Nettamer to login
successfully first, then to try the eventual dial script elements for
the *dialler* used preceding DOSPPP.
Sadly enough, Nettamer's packet driver is not available separately,
and those who followed the Nettamer list came to know that there would
be only dim prospects for that in future. So all hope has to be placed
on David Lindauer and his LSppp to overcome those problems with DOSPPP.
It looks very promising but I have to admit that I could not make it
run yet, apparently for some modem/dialler glitch. Though I hope the
best.
// Heimo Claasen // <hammer at revobild dot net> // Brussels 2001-02-01
The WebPlace of ReRead - and much to read ==> http://www.revobild.net
To unsubscribe from SURVPC send a message to [EMAIL PROTECTED] with
unsubscribe SURVPC in the body of the message.
Also, trim this footer from any quoted replies.
More info can be found at;
http://www.softcon.com/archives/SURVPC.html
