PPTPD not working

PPTPD not working

Post by Peter Würt » Sun, 15 Sep 2002 22:47:04



i dont know what to do anymore... i'm trying to get ppptpd running for a
week now, but i cant get my win-workstation connected via vpn...
as described i downloaded the source of the linux kernel and pppd, patched
both... and voila.. i got a ppp_mppe module... that was a incredible success
for me :)
so i tried to connect again... but it doesnt work..

the logs are attached... does somebody know whats the problem? win says "the
remote computer does not support the required data encryption type"...
using the option "optional encryption" does work... but is this a solution?!

Sep 14 15:01:14 hermes pptpd[15513]: CTRL: Client 192.168.0.11 control
connection started
Sep 14 15:01:14 hermes pptpd[15513]: CTRL: Starting call (launching pppd,
opening GRE)
Sep 14 15:01:14 hermes pppd[15514]: pppd 2.4.1 started by root, uid 0
Sep 14 15:01:14 hermes pppd[15514]: Using interface ppp1
Sep 14 15:01:14 hermes pppd[15514]: Connect: ppp1 <--> /dev/pts/3
Sep 14 15:01:17 hermes pptpd[15513]: CTRL: Ignored a SET LINK INFO packet
with real ACCMs!
Sep 14 15:01:17 hermes kernel: mppe_decomp_alloc: options rejected: o[0]=12,
o[1]=06, o[2]=00, o[3]=c5, o[4]=da, o[5]=ed
Sep 14 15:01:17 hermes kernel: mppe_decomp_alloc: options rejected: o[0]=12,
o[1]=06, o[2]=00, o[3]=c5, o[4]=da, o[5]=ed
Sep 14 15:01:17 hermes pppd[15514]: MSCHAP-v2 peer authentication succeeded
for vpn
Sep 14 15:01:17 hermes kernel: mppe_comp_alloc: options rejected: o[0]=12,
o[1]=06, o[2]=01, o[3]=c5, o[4]=da, o[5]=ed
Sep 14 15:01:17 hermes pppd[15514]: Cannot determine ethernet address for
proxy ARP
Sep 14 15:01:17 hermes pppd[15514]: local  IP address 192.168.0.2
Sep 14 15:01:17 hermes pppd[15514]: remote IP address 192.168.1.2
Sep 14 15:01:18 hermes kernel: mppe_comp_alloc: options rejected: o[0]=12,
o[1]=06, o[2]=01, o[3]=c5, o[4]=da, o[5]=ed
Sep 14 15:01:18 hermes pppd[15514]: LCP terminated by peer

Sep 14 15:01:21 hermes pppd[15514]: Connection terminated.
Sep 14 15:01:21 hermes pppd[15514]: Connect time 0.1 minutes.
Sep 14 15:01:21 hermes pppd[15514]: Sent 173 bytes, received 752 bytes.
Sep 14 15:01:21 hermes pptpd[15513]: GRE: read error: Bad file descriptor
Sep 14 15:01:21 hermes pptpd[15513]: CTRL: PTY read or GRE write failed
(pty,gre)=(-1,-1)
Sep 14 15:01:21 hermes pptpd[15513]: CTRL: Client 192.168.0.11 control
connection finished
Sep 14 15:01:37 hermes pppd[15514]: Exit.

 
 
 

1. pptpd only works with a single client

I have set up pptpd under Debian 3.0 and it works fine with a single client.
The problem is, as soon as a second client connects, the 2nd client cannot
ping anyone.

I have updated my firewall script to forward packets from both ppp
interfaces, but it still doesn't work.

Has anyone got more than one simultaneous client to work with pptpd?

cheers

2. cases, power supplies, etc.

3. PPP COMPRESSION NOT LOADING UP IN PPTPD VPN SESSIONS

4. Using the 'make' utility

5. Kernel-nfs working, plain nfs not working.

6. Need automated ftp script

7. USB not working with 2.5.69, worked with .68

8. Modem doesn't connect w/ wvdial or minicom

9. PPP working, /etc/ppp/ip-up not working, HELP Please

10. PPPD w/ PAP not working, works fine w/o PAP

11. RIPQUERY works with routed but it does not work with gated???

12. Some Hardware that works with Linux and some that works not!

13. Samba works, but does not work when i go into X????