MBP IPSec VPN Address Collision

Discussion in 'OT Technology' started by Zak8022, Apr 29, 2010.

  1. Zak8022

    Zak8022 New Member

    Joined:
    Apr 16, 2004
    Messages:
    4,012
    Likes Received:
    0
    Location:
    Maryland
    Just got a new 15" MBP, set up a vpn client (IPSecuritas). I swear it worked last week on my MBP, but now it does not. It says there's an "address collision". I understand the basics of what that means, but i can connect using the same exact set up on my Wife's MB (still on 10.5 tho, not sure if that matters).

    I can also still connect via bootcamp/my old thinkpad, both use the same basic settings/config even tho its thru a different client.

    Can anyone help out? Give me some tips on what to look for? I'm really stumped since this exact config/app works fine on my Wife's MB.
     
  2. Zak8022

    Zak8022 New Member

    Joined:
    Apr 16, 2004
    Messages:
    4,012
    Likes Received:
    0
    Location:
    Maryland
    I seem to have gotten this fixed. Apparently VMware Fusion had set up a vmnet that just so happened to be the same ip address/range of my vpn destination network. Uninstalled VMware, works fine. Haven't had time to reinstall yet, but think it just picks a random addy for its vmnet, so i'm hoping i'll luck out next time.
     

Share This Page