I am consistently seeing PPTP disconnect on one client when accessing mapped network drives, network places, and send/receive to an exchange server.. I have not had any luck finding these error messages on google and don't see any reason this link should be shutting down - not only that, but it's inconsistent. Sometimes you can browse network shares (It worked for a long time) but not lately.
Here's what I was able to pull from the logs:
2003-Nov 4 09:12:07 (none) pptpd[24215]: GRE: read(fd=6,buffer=8055600,len=8260) from network failed: status = -1 error = Message too long
2003-Nov 4 09:12:07 (none) pptpd[24215]: CTRL: GRE-tunnel has collapsed (GRE read or PTY write failed (gre,pty)=(6,5))
2003-Nov 4 09:12:07 (none) pptpd[24215]: CTRL: Closing child BCrelay with pid 0
2003-Nov 4 09:12:07 (none) pptpd[24215]: CTRL: Closing child ppp with pid 24223
2003-Nov 4 09:12:07 (none) pptpd[24215]: CTRL: Client 66.173.100.58 control connection finished
2003-Nov 4 09:12:07 (none) pptpd[24215]: CTRL: Exiting now
2003-Nov 4 09:12:07 (none) pptpd[22808]: MGR: Reaped child 24215
2003-Nov 4 09:12:07 (none) pppd[24223]: Terminating on signal 2.
The link comes up fine, you can browse the network and sometimes send/receive mail - but this is the only error I've seen out of pptp.
IPSec has problems on this link also and I have yet to establish a connection from that particular client location to the ASL box.
If anyone has any ideas I'm open to them.. Here's what I've done so far.
Changed MTU/MRU server side to 1200
turned off deflate and bsdcomp
128bit mppe is on
40bit is off
Verified PMTU is enabled client side.
Again I see no reason for this to occur and can't find the above error on google.. This is driving me batty, and really making my client unhappy. [:(]
*Update* This was caused by having the SSH Sentinel Firewall rules setup with accept any protocol in any port-range between the client and remote server, and internal network. For whatever reason (even though the traffic was allowed) something was happening at the firewall that was causing problems.
This thread was automatically locked due to age.
