Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I am having trouble with L2TP/IPSec on my OS X 10.7.2 machine and I was wondering what is the best way to figure out which process is taking particular sockets or ports;

My related posts (below), were more particular, but I couldn't figure it out. I am asking more general question, hopefully there would be someone who could help. OS X: how to figure out what prevents L2TP/IPSec from running correctly and OS X 10.7, can't log into any L2TP VPN server

Edit: I tried netstat and lsof but didn't see anything related to my problem. Also it isn't the router (other machines behind it work fine); it is not the firewall (same issue with it off) or LittleSnitch (same issue with it off). There was CiscoANyconnect installed, but the issue persists even after uninstall. My hypothesis is that it changed something that persists even after uninstall.

share|improve this question
    
lsof -i -P doesn't show anything useful either? –  Daniel Beck Jan 20 '12 at 20:57
    
Nothing in lsof or netstat. –  lupincho Jan 20 '12 at 20:59
    
How do you know the socket and/or port begin used is the problem? Does restarting the machine help? –  Daniel Beck Jan 20 '12 at 21:01
    
I don't and restarting doesn't help (even installing 10.7. on top of 10.6 didn't help). I don't want to do clean install, but that may be the only option. When starting the built-in VPN client, it says the following in ppp.log and system.log: timestamp : L2TP: cannot connect racoon control socket: No such file or directory. Because of that I thought that it could be socket or port. But it could be something completely different. Also, LittleSnitch doesn't show any attempt for connection to anything outside (the VPN server). –  lupincho Jan 20 '12 at 21:03
    
Just caught the edit, ignore the answer. I've seen cisco anyconnect mess up quite a few macs lately. even after you uninstall it. –  skub Jan 20 '12 at 21:05
show 3 more comments

1 Answer

up vote 0 down vote accepted

Ok, I figured it out. It wasn't ports and sockets. Turns out that something (possibly CiscoAnyconnect) has unloaded racoon on startup. To fix (with Anyconnect uninstalled) do the following:

launchctl load -w /System/Library/LaunchDaemons/com.apple.racoon.plist

You may also start racoon manually by:

sudo /usr/sbin/racoon

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.