[...] > These are the last lines of my /var/log/syslog: > Oct 3 04:12:35 colorado pppd[664]: pppd 2.3.11 started by root, uid 0 > Oct 3 04:12:36 colorado chat[665]: abort on (BUSY) > Oct 3 04:12:36 colorado chat[665]: abort on (NO CARRIER) > Oct 3 04:12:36 colorado chat[665]: abort on (VOICE) > Oct 3 04:12:36 colorado chat[665]: abort on (NO DIALTONE) > Oct 3 04:12:36 colorado chat[665]: abort on (NO DIAL TONE) > Oct 3 04:12:36 colorado chat[665]: abort on (NO ANSWER) > Oct 3 04:12:36 colorado chat[665]: send (AT &F0 E0 &C1 &D2 V1 S0=0\V1W0^M) > Oct 3 04:12:37 colorado chat[665]: expect (OK) > Oct 3 04:13:05 colorado chat[665]: ^M > Oct 3 04:13:05 colorado chat[665]: OK > Oct 3 04:13:05 colorado chat[665]: -- got it > Oct 3 04:13:05 colorado chat[665]: send (ATDT6129220^M) > Oct 3 04:13:05 colorado chat[665]: expect (CONNECT) > Oct 3 04:13:05 colorado chat[665]: ^M > Oct 3 04:13:50 colorado pppd[664]: Connect script failed > Oct 3 04:13:50 colorado chat[665]: alarm > Oct 3 04:13:50 colorado chat[665]: Failed > Oct 3 04:13:51 colorado pppd[664]: Exit.
Well, not a solution, but try to add "kdebug 1" to your ppp options file. I'm experiencing a similar situation, but had no time to continue work on it. In my case, it seems that my configuration is rejecting pap authentication, but I couldn't see why. Maybe such a log might help somebody else on this list to find the solution. Christoph Simon [EMAIL PROTECTED] -- ^X^C q quit :q ^C end x exit ZZ ^D ? help shit .
