On Thu, 21 Oct 1999, Ulrik Buchholtz wrote:
|I'm trying to connect to an NT server that provides callback via the cbcp.
|It used to work just fine, until they changed the phone number and god knows
|what else. Now it seems as if they reject my password even though I'm using
|it right now under Windows(R). I have really no idea what could be wrong.
If you are sure of the password then it could be one of two things. As I
understand CBCP the authentication is performed before the call back so I'd
guess that the problem here is that the NT has a broken ACCM, assuming that
the server has either been replaced or "upgraded". Try replacing the pppd
option "asyncmap 0" with "asyncmap a0000" .
Be aware that at least some NT RAS call back servers may present a problem
after call back. I *think* they assume that the LCP options negotiated on
the first call are still valid on the call back. If pppd is restarted to
accept the call back then pppd doesn't know this and the same ACCM problem
exists. A solution for this, as of ppp-2.3.7, is to execute pppd on the
call back with the option "receive-all". "man pppd" for what this does.
|Thanks you in advance,
I'd like conformation as to whether these suggestions work or not.
Thank *you* in advance.
---
Clifford Kite Not a guru. (tm)
-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to [EMAIL PROTECTED]
