> On Tue, 6 May 1997, Patrick C. Wolf wrote:
>
> > Anyone know why this happens? It appears that the user is specifying the
> > correct username and password, but after 1 minute and 5 seconds the PPP
> > connection never finishes. The user is using Trumpet Winsock. These
> > messages occur in /var/adm/messages for every time the user tries to
> > establish a PPP login.
> >
> > May 6 12:20:00 pm1 dialnet: port S1 Pnmt-ttc succeeded dest 206.101.58.250
> > May 6 12:21:05 pm1 dialnet: port S1 ppp_sync failed dest 206.101.58.250
>
> I've seen this happen with customers who have PAP enabled in Trumpet
> Winsock. For some reason, the PAP implementation in Trumpet is slightly
> broken, and if you use scripting of any kind to get TW connected, the PAP
> support seems to break completely.
This is the correct behavior, if you use script login. As seen above, the user is already
authenticated (user Pnmt-ttc). If PAP is enabled with Trumpet, it sends a LCP PAP request
*after* the PPP handshake starts. The Portmaster sends LCP PAP reject, because the user
already authenticated. Just unmark the PAP button under Trumpet PPP options.
Or change the script, that is just dials out and exits when DCD is detected. You may then
use PAP, because the Portmaster does PPP autodetect on the login prompt.
Frank
-- Frank M. Heinzius MMS Communication GmbH mailto:frimp@mms.de Eiffestrasse 598 http://www.mms.de 20537 Hamburg, Germany Phone: +49 40 211105-0 Fax: +49 40 210 32 210