Off-Topic: (Probable) Leopard fix to connect to Windows VPN
Posted on January 15, 2009
This has been frustrating me for the longest time. Mac OS X has both L2TP and PPTP support for VPNs but for some reason it has a very difficult time dealing with Windows based PPTP VPNs. Speculation goes on along the lines that OS X uses a newer implementation of PPTP, and Windows doesn’t (or most probable, it has a buggy implementation that only works on Windows, same problem as SMB, LDAP3, etc).
Whatever the reason, the behavior that I’ve been seeing is that Leopard is able to connect to a Windows VPN, it is able to authenticate, it is able to route correctly but then it won’t drop the connection but simply stops routing packages into the VPN tunnel after around 5 min of usage. So, I decided to Google around and I tried a few tricks.
Up until now I am connected to my company’s Windows VPN for 1 hr – which might be a world record! Let me explain a few things I tried and that might have helped in this.
First, I tried a trick I read in a forum:
- Open System Preferences → Network
- Click the “Location” drop down menu and choose “Edit Locations …”
- Create a brand new Location
- Configure your Wifi or Ethernet connection so you’re online
- On the lower left corner, click on the “+” button, then on “Interface” choose “VPN” and on “VPN Type”, choose “PPTP”.
- Configure your VPN using your company’s setting (IP address, “DOMAIN\username”, type your password clicking on the “Authentication Settings …” button.
- Again on the lower left corner, click on the 3rd icon, next to the “-” icon and choose “Set Service Order …”
- Drag and drop your VPN service to the top of the list
If you have VMWare Fusion installed, I read that the virtual network adapters could be one of the reasons so you need to stop them typing this in the Terminal:
After that, again in the Network Preferences Pane, I connected into my VPN and surprisingly the connection stayed on for more than 1 hr whereas I couldn’t stay connected for more than 5 min before that. None of the steps above make much
sense, but it seems to have worked for me.
I also left a Terminal open constantly pinging some server inside the company network to make sure I am keeping the connection alive. I have no idea if those steps actually solve the problem or I just got lucky all of a sudden. Please drop a line in the comments if it solved it for you or if you have other insights around this issue.
Bottom line: if you can, don’t build a Windows-based network.
blog comments powered by Disqus
Archives
- February 12(2)
- December 11(1)
- November 11(4)
- October 11(6)
- September 11(5)
- August 11(1)
- July 11(5)
- May 11(4)
- April 11(11)
- March 11(4)
- February 11(3)
- January 11(4)
- December 10(9)
- November 10(2)
- October 10(10)
- September 10(4)
- August 10(6)
- July 10(14)
- June 10(16)
- May 10(8)
- April 10(14)
- March 10(9)
- February 10(6)
- January 10(14)
- December 09(10)
- November 09(10)
- October 09(7)
- September 09(19)
- August 09(4)
- July 09(12)
- June 09(7)
- May 09(12)
- April 09(11)
- March 09(9)
- February 09(9)
- January 09(12)
- December 08(14)
- November 08(20)
- October 08(15)
- September 08(18)
- August 08(25)
- July 08(13)
- June 08(21)
- May 08(29)
- April 08(27)
- March 08(12)
- February 08(32)
- January 08(31)
- December 07(27)
- November 07(30)
- October 07(25)
- September 07(28)
- August 07(16)
- July 07(15)
- June 07(16)
- May 07(7)
- April 07(13)
- March 07(8)
- February 07(9)
- January 07(24)
- December 06(17)
- November 06(17)
- October 06(15)
- September 06(38)




