Topic: PPTP connect problems

[ben]

Hi all,

I can't get a windows XP client to connect to my SME 7.1 box. When I connect from the XP box, it gets past the "connecting" and "verifying username and password" steps, then disconnects at the "registering your computer on the network" step. It disconnects with the message "Error 734: The PPP link control protocol was terminated".

/var/log/messages shows this:

Feb 22 14:47:44 neon pptpd[8679]: CTRL: Client 192.168.0.3 control connection started
Feb 22 14:47:44 neon pptpd[8679]: CTRL: Starting call (launching pppd, opening GRE)
Feb 22 14:47:44 neon pppd[8680]: Plugin radius.so loaded.
Feb 22 14:47:44 neon pppd[8680]: RADIUS plugin initialized.
Feb 22 14:47:44 neon pppd[8680]: pppd 2.4.4 started by root, uid 0
Feb 22 14:47:44 neon kernel: divert: not allocating divert_blk for non-ethernet device ppp0
Feb 22 14:47:44 neon pppd[8680]: Using interface ppp0
Feb 22 14:47:44 neon pppd[8680]: Connect: ppp0 <--> /dev/pts/1
Feb 22 14:47:47 neon pptpd[8679]: CTRL: Ignored a SET LINK INFO packet with real ACCMs!
Feb 22 14:47:47 neon pppd[8680]: MPPE required, but kernel has no support.
Feb 22 14:47:47 neon pppd[8680]: Connection terminated.
Feb 22 14:47:47 neon pppd[8680]: Connect time 0.1 minutes.
Feb 22 14:47:47 neon pppd[8680]: Sent 0 bytes, received 0 bytes.
Feb 22 14:47:47 neon pptpd[8679]: CTRL: Reaping child PPP[8680]
Feb 22 14:47:47 neon kernel: divert: no divert_blk to free, ppp0 not ethernet
Feb 22 14:47:47 neon pppd[8680]: Exit.
Feb 22 14:47:47 neon pptpd[8679]: CTRL: Client 192.168.0.3 control connection finished

Can anyone help me get the PPTP connections working?

Thanks,

 - Ben

[ldkeen]

Ben,

MPPE required, but kernel has no support.

This problem has been discussed before. It basically means that the kernel was upgraded but without the required pptp modules. If you search the forums for the above you should find instructions on the steps required to fix it.
Lloyd

[harkete]

[concerning: in log files: MPPE required, but kernel has no support. ]

I've read through the post concerning this issue and I can't really figure out how to fix it. I'm running:

uname -r
2.6.9-42.0.8.ELsmp

rpm -qa |grep ppp
rp-pppoe-3.5-22
ppp-2.4.4-1.3.el4.sme
kmod-ppp-smp-1.0.2-1.2.6.9_42.0.3.EL
kmod-ppp-1.0.2-1.2.6.9_42.0.3.EL

If I check the grub file I have the following options:


title SME Server (2.6.9-42.0.8.ELsmp)
        root (hd0,0)
        kernel /vmlinuz-2.6.9-42.0.8.ELsmp ro root=/dev/main/root
        initrd /initrd-2.6.9-42.0.8.ELsmp.img
title SME Server (2.6.9-42.0.8.EL)
        root (hd0,0)
        kernel /vmlinuz-2.6.9-42.0.8.EL ro root=/dev/main/root
        initrd /initrd-2.6.9-42.0.8.EL.img
title SME Server (2.6.9-42.0.3.ELsmp)
        root (hd0,0)
        kernel /vmlinuz-2.6.9-42.0.3.ELsmp ro root=/dev/main/root
        initrd /initrd-2.6.9-42.0.3.ELsmp.img
title SME Server-up (2.6.9-42.0.3.EL)
        root (hd0,0)
        kernel /vmlinuz-2.6.9-42.0.3.EL ro root=/dev/main/root
        initrd /initrd-2.6.9-42.0.3.EL.img

Could someone kind please explain what to do to get VPN up and running (and please I'm 600 km away from the server ... so if I can do it from the shell it would be fantastic ...) ? Do I have to boot into another version of the server? And if I have to - why? This was a completely clean install just two weeks ago. I then yum:ed it until it was up-to-date, from the server-manager. Once I did it (yum:ed) from the shell, but I ran the "signal-event whatever commands" afterwards. (They were not written on the same line thou ... is that a problem?).

I'm quite a Linux novice ...

Some help would be greatly appreciated!

Thanks
/Erik

[william_syd]

Your kernel version and your kernel modules (kmod) version do not match.

You will have to choose an earlier kernel at boot time (SME Server-up (2.6.9-42.0.3.EL) ).

The newer kmods are not in the regular repositories as yet.

[william_syd]

Could someone kind please explain what to do to get VPN up and running (and please I'm 600 km away from the server ... so if I can do it from the shell it would be fantastic ...)

Just saw the above.

In your grub.conf file you will have a default line saying 0

0 is the first kernel in the list below it.

Count down, starting a 0 till you get to the kernel you want (looks like 2 for you) and change the default line.

Then just reboot.

[harkete]

Just as a follow up:

If I yum the server, why does the kernel and kmods go out of sync? Is there a way of yumming that prevents this from happening?

Is it safe to swith to another version of the server? Some user reported the machine not booting properly after changing the os version ...

Just curious to know ...

/Erik

[william_syd]

If I yum the server, why does the kernel and kmods go out of sync?

CentOS updated the kernel before SME developers updated the kmods.

Is there a way of yumming that prevents this from happening?

Be selective with what you update. I believe the developers are looking for  a way to avoid this issue. Check the bug tracker.

Is it safe to swith to another version of the server?

It was working before. Should not be an issue.

Some user reported the machine not booting properly after changing the os version ...

Please provide the links to support this.

Just curious to know ...

Never hurts.

[harkete]

Thanks a lot for your help!!!

Here's the user that had problems with reverting to an earlier version:

http://forums.contribs.org/index.php?topic=34173.0

/Erik

[william_syd]

Thanks a lot for your help!!!

Here's the user that had problems with reverting to an earlier version:

http://forums.contribs.org/index.php?topic=34173.0

/Erik

That thread never came to a conclusion.

Also look at his running kernel and module versions. They are around the other way to yours. People with later kernels who revert back to previous one appear to have no problem.

Bug 2454