[pptp-server] (no subject)

[Richard]

check if your internal interface and the variable "localip" in
/etc/pptpd.conf are the same. Also "localip" MUST be one IP, and NOT
something like 192.168.0.1-[some other number]


Regards,
Richard


> On Sun, 14 Apr 2002 sfesta at spidermite.net wrote:
> 
> [...]
> > Apr 14 15:01:51 argon pptpd[2504]: CTRL: Client 192.168.0.252 control
> > connection
> > started
> > Apr 14 15:01:51 argon pptpd[2504]: CTRL: Starting call (launching pppd,
> > opening GRE)Apr 14 15:01:51 argon pppd[2505]: pppd 2.4.1 started by root,
> > uid 0
> > Apr 14 15:01:51 argon pppd[2505]: Using interface ppp0
> > Apr 14 15:01:51 argon pppd[2505]: Connect: ppp0 <--> /dev/pts/2
> > Apr 14 15:01:51 argon /etc/hotplug/net.agent: assuming ppp0 is already up
> > Apr 14 15:01:54 argon pppd[2505]: MSCHAP-v2 peer authentication succeeded
> > for
> > sfestaApr 14 15:01:54 argon pppd[2505]: Could not determine local IP
> > address
> > Apr 14 15:01:54 argon pppd[2505]: Connection terminated.
> > Apr 14 15:01:54 argon pppd[2505]: Connect time 0.1 minutes.
> > Apr 14 15:01:54 argon pppd[2505]: Sent 140 bytes, received 100 bytes.
> > Apr 14 15:01:54 argon pppd[2505]: Exit.
> > 
> > 
> > Can Anyone Help?
> 
> Probably someone here can help, but we are going to need to see the
> "debug" output of ppp to have a chance.
> 
> Make sure that: (1) you are pasing the option "debug" to ppp and (2) ppp's
> debug messages are geting logged somewhere (/var/log/debug and/or
> /var/log/ppp are likely suspects; but you might wish to tweak your syslog
> config).
> 
> In those messages, we ought to be able to see what's provoking the
> "Connection terminated.".
> 
> HTH,
> Neale.
> 
> _______________________________________________
> pptp-server maillist  -  pptp-server at lists.schulte.org
> http://lists.schulte.org/mailman/listinfo/pptp-server
> --- To unsubscribe, go to the url just above this line. --