Not sure if both items are fixed by the same thing but I was driving my IS department nuts, generating hundreds (literally) of Land Attack alerts that looked like this: (I changed the IP address to be cautious 
<162>Sep 10 2012 05:16:10: %ASA-2-106017: Deny IP due to Land Attack from 148.300.66.135 to 148.300.66.135
Here's the fix...
1. Start up Windows in Parallels before connecting to VPN
2. Launch Activity Monitor on Mac and quit any instance of naptd that isn't running as "root" user (I had two instances for naptd running).
3. Connect to VPN and all is well.
4. Disconnect form VPN, then suspend/shutdown Windows (log off first because that second instance of naptd is going to fire up again).
Let me know if you know how to kill off the second instance of naptd permenently!
I also did some other things (like changed the clock sync setting in Parallels under the configuration for my guest machine to "sync from either os" because my Windows logs kept noting my system was being tampered with and several other things regarding dhcp, parallels, static ip for Windows, shared internet setting on the mac) but for sure, quitting that second instance of naptd that wasn't running under "root" fixed the land attack alerts. Something else I did my have stopped the lockout but I have a feeling that second instance of naptd might have been causing both problems.
Last edited: Sep 11, 2012