[pptp-server] LCP: time out

Örjan Johansson orjan at whyevenbother.com
Tue Mar 19 19:35:37 CST 2002


Thanx for your help guys! 
I'm one step closer now. I  applied the require mppe patch, so skipping
the '+chapms-v2' got me through without warnings about unrecognized
options.
 
Now when I try and connect the client semms to connect. It stops and
waits at the 'verifying username and password'. When I look at the log
it says :
Mar 20 01:44:37 howdy pptpd[8063]: CTRL: Starting call (launching pppd,
opening GRE)
Mar 20 01:44:37 howdy pppd[8064]: pppd 2.4.1 started by root, uid 0
Mar 20 01:44:37 howdy pppd[8064]: Using interface ppp0
Mar 20 01:44:37 howdy pppd[8064]: Connect: ppp0 <--> /dev/pts/2
Mar 20 01:45:08 howdy pppd[8064]: LCP: timeout sending Config-Requests 
Mar 20 01:45:08 howdy pppd[8064]: Connection terminated.
Mar 20 01:45:08 howdy pppd[8064]: Exit.

The negotiation/lcp should go over tcp/1723 right? And the data over
protocol 47? I've made sure my shorewall lets all this through.
Any chance I could see some sample options files? I'm running RH7.2,
patched 2.4.9-31 kernel, pppd 2.4.1 with the three patches, and poptop
1.0.1. My options file looks like this (at the moment, it changes every
five seconds testing...:-):
debug
lock
mtu 1490
mru 1490
auth
idle 300
maxfail 3
proxyarp
#refuse-pap
#refuse-chap
#refuse-chapms
ipcp-accept-local
ipcp-accept-remote
lcp-echo-failure 3
lcp-echo-interval 5
deflate 0
#chapms
#chapms-v2
mppe-40
mppe-128
mppe-stateless
 
My clients (2k pro and xp pro) are configured to require encryption, set
to pptp, and set to use mschapv2.


Any ideas extremely appreciated! I gotta be at work in a few hours, but
can't give up just yet. How come frustrating things like these are also
so much fun...? :-)

Cheers,

Örjan




More information about the pptp-server mailing list