VPN PPTP Connects but doesn't work

I used to use the built in PPTP VPN connection in the regular Leopard to connect to my employer just fine. It allowed access to the exchange server, intranet web pages, and file servers. Now with the same connection settings I can connect and authenticate just fine but it's as if none of the network requests are going through the VPN. None of the addresses resolve, for file servers, web servers or exchange. I even tried IP addresses and they weren't found either. Watching the VPN traffic meters in the control panel revealed no activity even though various network request were being made.

I tried manually adding DNS info into the VPN settings to no avail. I deleted all DNS info and let it populate itself and no luck. I have an old G5 sitting here with regular Leopard and the VPN connection works just fine.

I've tried deleting the VPN and re-adding and that didn't work either.

This is making me really nervous... I NEED my VPN. Please help 😟

MacBook Pro 17", Mac OS X (10.6), VPN PPTP

Posted on Aug 29, 2009 12:53 AM

Reply
79 replies

Sep 3, 2009 2:21 AM in response to jleomurphy

We too. i think entourage is using the internet connection, not the vpn; in our case we can establish the vpn connection (pptp) but it's not possible to connect to our network drives. Ping server ip -> request timeout; entourage with exchange works because it uses the external ip and connects over the internet, not vpn; we tried also the suggested fixes -> no result.

Sep 3, 2009 9:06 AM in response to Paul Bush

Having the same issue. Editing or deleting .plist file is a no go.
Here are some lines from my /var/log/ppp.log file:

Notice the last line where there is mention of no reply from the remote DHCP server. All my VPNs regardless of remote hardware, exhibit this problem.

Thu Sep 3 11:48:35 2009 : sent \[IP data <src addr xxx.xxx.xxx.xxx> <dst addr 255.255.255.255> <BOOTP Request> <type INFORM> <client id 0x08000000010000> <parameters = 0x6 0x2c 0x2b 0x1 0xf9 0xf>]
Thu Sep 3 11:48:38 2009 : sent \[IP data <src addr xxx.xxx.xxx.xxx> <dst addr 255.255.255.255> <BOOTP Request> <type INFORM> <client id 0x08000000010000> <parameters = 0x6 0x2c 0x2b 0x1 0xf9 0xf>]
Thu Sep 3 11:48:41 2009 : sent \[IP data <src addr xxx.xxx.xxx.xxx> <dst addr 255.255.255.255> <BOOTP Request> <type INFORM> <client id 0x08000000010000> <parameters = 0x6 0x2c 0x2b 0x1 0xf9 0xf>]
Thu Sep 3 11:48:44 2009 : sent \[IP data <src addr xxx.xxx.xxx.xxx> <dst addr 255.255.255.255> <BOOTP Request> <type INFORM> <client id 0x08000000010000> <parameters = 0x6 0x2c 0x2b 0x1 0xf9 0xf>]
Thu Sep 3 11:48:47 2009 : No DHCP server replied

Message was edited by: patrick.boucher

Sep 3, 2009 9:09 AM in response to patrick.boucher

This is the error that was being reported by one of the facilities where I connect.

The administrator added a rule to allow through these "invalid IP packets" and all is well. Maybe this can get some more knowledgeable troubleshooters out there on the right track.

2009-09-03 11:50:33 Deny xxx.xxx.xxx.xxx 255.255.255.255 dhcp/bootp-server/udp 68 67 PPTP unknown invalid IP packet detected by device, firewall drop (internal policy) rc="104" Traffic

Sep 4, 2009 3:03 AM in response to Tim Harris

Deleting the VPN and the normal network setting (Airport, in my case) didn't work. This is the response to the command:

localhost:~ jmurphy$ netstat -nr
Routing tables

Internet:
Destination Gateway Flags Refs Use Netif Expire
default 192.168.0.1 UGSc 74 0 en1
default 172.16.13.93 UGScI 0 0 ppp0
127 127.0.0.1 UCS 0 0 lo0
127.0.0.1 127.0.0.1 UH 1 2 lo0
169.254 link#6 UCS 0 0 en1
172.16.13/24 ppp0 USc 5 0 ppp0
172.16.13.93 172.16.13.139 UH 1 0 ppp0
172.16.143/24 link#7 UC 0 0 vmnet8
172.16.249/24 link#8 UC 0 0 vmnet1
192.168.0 link#6 UCS 1 0 en1
192.168.0.1 0:22:b0:c7:b3:79 UHLWI 75 179 en1 1196
192.168.0.196 127.0.0.1 UHS 0 0 lo0
216.75.138.188 192.168.0.1 UGHS 0 0 en1

Internet6:
Destination Gateway Flags Netif Expire
::1 ::1 UH lo0
fe80::%lo0/64 fe80::1%lo0 Uc lo0
fe80::1%lo0 link#1 UHL lo0
fe80::%en1/64 link#6 UC en1
fe80::223:12ff:fe57:8bd4%en1 0:23:12:57:8b:d4 UHL lo0
ff01::/32 ::1 Um lo0
ff02::/32 ::1 UmC lo0
ff02::/32 link#6 UmC en1
localhost:~ jmurphy$

Sep 4, 2009 6:56 AM in response to Tim Harris

Thanks for the help Tim.

Here's my version of netstat -nr:

<pre>titanium:~ pboucher$ netstat -nr
Routing tables

Internet:
Destination Gateway Flags Refs Use Netif Expire
default 192.168.2.1 UGSc 61 0 en1
default link#9 UCSI 1 0 en3
default link#10 UCSI 1 0 en4
10.37.129/24 link#10 UCS 0 0 en4
10.37.129.2 127.0.0.1 UHS 1 1 lo0
10.211.55/24 link#9 UCS 0 0 en3
10.211.55.2 127.0.0.1 UHS 0 1 lo0
127 127.0.0.1 UCS 0 0 lo0
127.0.0.1 127.0.0.1 UH 13 58534 lo0
169.254 link#9 UCS 0 0 en3
172.16.15/24 link#8 UC 1 0 vmnet1
172.16.15.1 0:50:56:c0:0:1 UHLWI 0 1 lo0
172.16.164/24 link#7 UC 1 0 vmnet8
172.16.164.1 0:50:56:c0:0:8 UHLWI 0 1 lo0
192.168.2 link#5 UCS 3 0 en1
192.168.2.1 0:1e:58:36:ed:19 UHLWI 87 524 en1 1158
192.168.2.197 0:23:32:9:c:90 UHLWI 0 0 en1 415
192.168.2.199 127.0.0.1 UHS 0 0 lo0
239.255.255.250 1:0:5e:7f:ff:fa UHmLWI 0 6 en3
239.255.255.250 1:0:5e:7f:ff:fa UHmLWI 0 6 en4

Internet6:
Destination Gateway Flags Netif Expire
::1 ::1 UH lo0
fe80::%lo0/64 fe80::1%lo0 Uc lo0
fe80::1%lo0 link#1 UHL lo0
fe80::%en1/64 link#5 UC en1
fe80::21f:5bff:fece:18be%en1 0:1f:5b:ce:18:be UHL lo0
fe80::%en3/64 link#9 UC en3
fe80::21c:42ff:fe00:8%en3 0:1c:42:0:0:8 UHL lo0
fe80::%en4/64 link#10 UC en4
fe80::21c:42ff:fe00:9%en4 0:1c:42:0:0:9 UHL lo0
ff01::/32 ::1 Um lo0
ff02::/32 ::1 UmC lo0
ff02::/32 link#5 UmC en1
ff02::/32 link#9 UmC en3
ff02::/32 link#10 UmC en4
titanium:~ pboucher$</pre>

Sep 4, 2009 6:58 AM in response to Tim Harris

This is a version with one of my VPNs connected.

<pre>titanium:~ pboucher$ netstat -nr
Routing tables

Internet:
Destination Gateway Flags Refs Use Netif Expire
default 192.168.2.1 UGSc 122 0 en1
default link#9 UCSI 1 0 en3
default link#10 UCSI 1 0 en4
default 10.0.2.22 UGScI 0 0 ppp0
10.0.2/24 ppp0 USc 1 0 ppp0
10.0.2.22 10.0.2.13 UH 1 0 ppp0
10.37.129/24 link#10 UCS 1 0 en4
10.37.129.2 127.0.0.1 UHS 1 1 lo0
10.37.129.255 ff:ff:ff:ff:ff:ff UHLWbI 0 6 en4
10.211.55/24 link#9 UCS 1 0 en3
10.211.55.2 127.0.0.1 UHS 0 1 lo0
10.211.55.255 ff:ff:ff:ff:ff:ff UHLWbI 0 6 en3
127 127.0.0.1 UCS 0 0 lo0
127.0.0.1 127.0.0.1 UH 13 65680 lo0
169.254 link#9 UCS 0 0 en3
172.16.15/24 link#8 UC 2 0 vmnet1
172.16.15.1 0:50:56:c0:0:1 UHLWI 0 1 lo0
172.16.15.255 ff:ff:ff:ff:ff:ff UHLWbI 0 6 vmnet1
172.16.164/24 link#7 UC 2 0 vmnet8
172.16.164.1 0:50:56:c0:0:8 UHLWI 0 1 lo0
172.16.164.255 ff:ff:ff:ff:ff:ff UHLWbI 0 6 vmnet8
192.168.2 link#5 UCS 5 0 en1
192.168.2.1 0:1e:58:36:ed:19 UHLWI 124 764 en1 1199
192.168.2.197 0:23:32:9:c:90 UHLWI 0 0 en1
192.168.2.198 link#5 UHLWI 1 2 en1
192.168.2.199 127.0.0.1 UHS 0 0 lo0
192.168.2.255 ff:ff:ff:ff:ff:ff UHLWbI 0 6 en1
216.94.112.40 192.168.2.1 UGHS 0 0 en1
239.255.255.250 1:0:5e:7f:ff:fa UHmLWI 0 6 en3
239.255.255.250 1:0:5e:7f:ff:fa UHmLWI 0 6 en4

Internet6:
Destination Gateway Flags Netif Expire
::1 ::1 UH lo0
fe80::%lo0/64 fe80::1%lo0 Uc lo0
fe80::1%lo0 link#1 UHL lo0
fe80::%en1/64 link#5 UC en1
fe80::21f:5bff:fece:18be%en1 0:1f:5b:ce:18:be UHL lo0
fe80::%en3/64 link#9 UC en3
fe80::21c:42ff:fe00:8%en3 0:1c:42:0:0:8 UHL lo0
fe80::%en4/64 link#10 UC en4
fe80::21c:42ff:fe00:9%en4 0:1c:42:0:0:9 UHL lo0
ff01::/32 ::1 Um lo0
ff02::/32 ::1 UmC lo0
ff02::/32 link#5 UmC en1
ff02::/32 link#9 UmC en3
ff02::/32 link#10 UmC en4
titanium:~ pboucher$</pre>

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

VPN PPTP Connects but doesn't work

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.