[pptp-server] NT error 718: timeout?

[Gunnar Hellekson]

I'm working off linux 2.0.36, pppd 2.3.5, pptpd 0.8.6 from the RPM,
and NT 4.0 sp4 as a client.

pppd and the NT RAS client seem to talk to each other perfectly well, but the 
pppd doesn't seem to be responding to the client's password.  It happens 
regardless of the IPs I'm using, and the password auth. on NT is set to allow 
cleartext.  Any pointers?

Here's the pptpd.conf (suggested elsewhere on the list):

debug 1                 # this didn't increase verbosity... should it?
localip 192.168.0.234
remoteip 192.168.0.235
speed 115200


The /etc/ppp/options:

local
lock
debug

and the chap-secret:
user pptp-server        password *

Here's my syslog, with the added benefit of the packet filter's logs.
The rejected UDP packets don't seem to matter, as allowing them through
still yields the same error:

May 28 20:51:46 firewall kernel: IP fw-in acc eth0 TCP <remote-ip>:1046 <server-ip>:1723 L=44 S=0x1C I=21249 F=0x0040 T=117  
May 28 20:51:46 firewall kernel: IP fw-in rej eth0 UDP <remote-ip>:137 <server-ip>:137 L=78 S=0x00 I=22017 F=0x0000 T=117  
May 28 20:51:47 pptpd-server pppd[8036]: pppd 2.3.5 started by root, uid 0
May 28 20:51:47 pptpd-server pppd[8036]: Using interface ppp0
May 28 20:51:47 pptpd-server pppd[8036]: Connect: ppp0 <--> /dev/ttya0
May 28 20:51:48 firewall kernel: IP fw-in rej eth0 UDP <remote-ip>:137 <server-ip>:137 L=78 S=0x00 I=23297 F=0x0000 T=117  
May 28 20:51:49 firewall kernel: IP fw-in rej eth0 UDP <remote-ip>:137 <server-ip>:137 L=78 S=0x00 I=23809 F=0x0000 T=117  

# right about here, NT complains "Error 718: Timed out waiting for a valid response from the remote PPP peer"

May 28 20:52:17 pptpd-server pppd[8036]: LCP: timeout sending Config-Requests
May 28 20:52:17 pptpd-server pppd[8036]: Connection terminated.
May 28 20:52:17 pptpd-server pppd[8036]: Exit.
May 28 20:53:58 pptpd-server kernel: PPP: ppp line discipline successfully unregistered 


-- 
Gunnar Hellekson                     t r i l u x  i n t e r n e t  g r o u p
  RIP is irrelevant. Spoofing is futile. Your routes will be aggregated.