Comment 80 for bug 259168

I have to admit that 0.7 has many bugs that should have been addressed before release. I do use 0.7 since hardy because I depend on my sprint card to connect and 0.7 handles it very well. As nm 0.7 pptp is kind of broken, I can see how people are upset. I myself, am surprised that pptp still has bugs. Maybe the developers are underestimating the amount of people that use pptp. I don't know.

There are two ways to make pptp work today:

A. Install kvpnc, configure and you are good to go. I used this myself when I was testing 0.7 in Hardy and pptp was non-existant. It works very solidly.

or

B. Force pptp to work in nm 0.7 via hacks & teaks via the gconfig editor.

here are workarounds for these problems.

1. You need to add a refuse-eap key in gconfig and set it to yes. If you don't do this, the pptp client will send the host-name instead of your user name to the server. This will cause your connection to be rejected.

2. If you are using a domain name to log in, don't put it in the domain box. Instead, put your domain name and your user-name together in the name field. domain\login

3. This is my gconf setup:

gateway xxx.xxx.xxx.xxx -- put in the ip of your server here
lcp-echo-failure 5
lcp-echo-interval 30
mppe-stateful yes
no-vj-comp yes
refuse-chap yes
refuse-eap yes -- new key you must put in.
refuse-mschap yes
refuse-pap yes
require-mppe yes
require-mppe-128 yes
service-type org.freedesktop.NetowrkManager.pptp
user domain\userlogin -- you have to do it like this otherwise it won't work. on the gui, leave the domain name blank.

And finally, the keys must be added in system\networking\connections\yourvpnpptpconnectio n\vpn.

The refuse-eap key trick was found by somebody else so I don't take credit for it.

Hope this helps....