Create PPTP VPN Connection

Hello, how could I setup or deploy several PPTP-VPN connections via AppleScript? (System Preferences-Network-Add Interface-VPN-PPTP)
Thanks in advance!

I must confess that I don't know much about network connections. However, using [GUI Scripting|http://www.macosxautomation.com/applescript/uiscripting/index.html], the following script (tested on my MacBook Pro) should add one "VPN (PPTP)" connection to the Network pane of you System Preferences:
tell application "System Preferences"
reveal pane "Network"
activate
tell application "System Events"
tell process "System Preferences"
tell window 1
click button "Add Service"
tell sheet 1
click pop up button 1
click menu item "VPN" of menu 1 of pop up button 1
delay 1
click pop up button 2
click menu item "PPTP" of menu 1 of pop up button 2
click button "Create"
end tell
click button "Apply"
end tell
end tell
delay 1 -- optional (just for visual feedback)
keystroke "w" using {command down}
end tell
end tell
Before using this script, the Accessibility Frameworks must have been enabled by clicking the checkbox labeled "Enable access for assistive devices" in the Universal Access System Preference pane.
Message was edited by: Pierre L.

Similar Messages

  • Internet stops with PPTP VPN connections to ASUS RT-N66U VPN Router

    I have a client with a small office network that has a few people working remotely from Windows 7 and 8 PCs. As an inexpensive solution the client opted to use a VPN router (ASUS RT-N66U) that supports PPTP so remote users could access the shared
    files and SQL DB server. 
    The VPN connectivity for one client was working fine and then stopped working altogether so when the VPN connection is established all Internet and VPN access is stopped. This was especially troubling for me since I work remotely and cannot test or debug after
    the VPN session has been connected. I checked the error logs and found nothing. Also there had been no new programs installed. And finally, I ran a full system antivirus scan with no issues found.
    In case you are facing a similar issue, before trying something remotely that may not work, use the shutdown with reboot command in a COMMAND window and set a timer for something like 3 minutes to reboot in case you get stuck. (e.g. shutdown -r -t 180). 
    Problem: The two symptoms of the VPN connection failure are:
    1) All Internet browsing stops working locally 
    2) No data can pass through the VPN tunnel
    I created a virtual machine on my local network and replicated the client's environment. I experimented with nearly every setting in the VPN dialogue until and came to the final solution. 
    Solution: For the VPN adapter on the remote machines I configured DNS settings and used the remote as the default gateway.
    * VPN adapter Networking IPV4 Properties for:
    - DNS server 1: Main Office VPN Router IP Address
    - DNS server 2: A public DNS server (Google is 8.8.8.8)
    - I also checked the box to "register this connection addresses in DNS"
    Note: Perhaps the local router would also have worked and DNS2 but I didn't test it.
    I have documented this because after reading and searching among many Technical articles and the Microsoft support website, I was unable to find the solution that I came up with so I hope to help someone else. 
    Question1: - Can anyone tell me why the connectivity only works when 'use default gateway on remote network' is checked?
    - I have disabled this option with some business class VPN routers and the connectivity still worked to the remote network but it does not work to the Asus router.
    Question2: From the information provided can I determine where the problem lies?
    Is it the:
    1) Remote client PC
    2) Remote client router
    3) Home office VPN router (Asus RT-N66U)
    If the true culprit cannot be determined yet, what steps do you recommend so I can isolate the true cause of the failure.
    I appreciate any help so that I can be sure my solution is valid and pass along the findings to ASUS if it is their issue.

    Thank you for the suggestion. I have successfully connected through the VPN router when the one client was unable to get VPN throughput working.
    I looked at the routing tables with and without the VPN connection established. The differences are that:
    1) when VPN is NOT active, there is a route from the local NIC IP to the Internet IP address of the local gateway
    destination 68.109.82.xx
    mask 255.255.255.0
    gateway 192.168.0.1
    interface 192.168.0.11
    metric 21
    2) when VPN IS active, the route to the Internet IP address of the local gateway is deleted and a persistent route to the VPN router local network has been added
    Persistent route:
    destination 192.168.21.0
    mask 255.255.255.0
    gateway 192.168.0.1
    interface 192.168.0.11
    metric 1

  • How to Configure an Cisco 5505 for PPTP VPN connectivity

    I currently have a Cisco ASA 5505(ASA Version 8.2(1), and ASDM gui version 6.2) and a Windows 2008 R2 server with one NIC card. Currently the router is connected to the interent sucessfully using the 'outside' interface(devices connected to the 'inside' interface have access to the internet and are assigned IP addresses via DHCP on the Windows 2008 Server which is also connected to the 'inside' interface) When connected with a client on the inside interface I can establish a VPN connection with the W2008 server, however when I try to connect through the internet I cannot. I have tried researching this on the internet, but have not had much luck. I know it has something to do with pptp port and allowing gre, but I am not familiar enough with configuring Cisco devices or the language they use, to configure this router. I feel as though I am missing something small but very critical. Any help or feedback you can provide regarding this issue is most appreicated, thank you.
    *Edit: I have attached a network diagram of what I am trying to accomplish, and I have also attached a dump of the current running-config.

    Hi,
    Below is the link to the admin guide for the RV042.  Chapter 9 covers the configuration of site to site VPN’s and begins on page 123. 
    http://www.cisco.com/en/US/docs/routers/csbr/rv0xx/administration/guide/rv0xx_AG_78-19576.pdf
    If you need further assistance please feel free to contact Cisco Small Business for help in configuring and troubleshooting your VPN.
    Thank you,
    Jason Nickle

  • Cannot Make PPTP VPN Connection in 10.7.4

    As far as I can tell everything is setup correctly but every time I try to connect I get this message:
    You were disconnected by the communication device. Try reconnecting. If the problem continues, verify your settings.
    Console Log:
    6/25/12 5:11:40.382 PM pppd: PPTP connection established.
    6/25/12 5:11:40.443 PM pppd: Connect: ppp0 <--> socket[34:17]
    6/25/12 5:11:40.447 PM pppd: PPTP error when reading socket : EOF
    6/25/12 5:11:40.447 PM pppd: PPTP error when reading header : read -1, expected 12 bytes
    6/25/12 5:11:40.447 PM pppd: PPTP hangup
    6/25/12 5:11:40.448 PM pppd: Connection terminated.
    6/25/12 5:11:40.454 PM pppd: PPTP disconnecting...
    6/25/12 5:11:40.455 PM pppd: PPTP disconnected
    I am trying to connect to a Linux based VPN server.  I have double checked my username and password multiple times, made sure the MTU is set the same on client, server, and router, and tried turning the encryption off and on on the server and the client.  Nothing has made a difference, I get the same error every time.  I am able to FTP and SSH into the Linux box. 
    Any suggestions of other things to try would be much appreciated.  I saw some threads about editing config files on my mac but this is a brand new machine that I have had for a week running an OS that is on it's fourth point release.  I really should not have to muck around with config files but at this point I'm ready to try anything. 

    Looks like it might be a configuration error on the server's end. The VPN makes a connection and tries to read the server's configuration to create a socket for communication, but runs into a formatting error when it is passed an "End of File" character instead of a required component of the socket. Can you try connecting to another VPN server, or perhaps try an L2TP connection instead of PPTP?

  • How do I set up a PPTP VPN connection?

    I've just arrived at uni to find that in my dorm I don't get wifi reception, and the lack of ethernet port in my MacBook Air means I can't just connect via the ethernet port in the wall. Luckily I brought my AirPort Express with me.
    Now the uni internet operates by VPN over a PPTP connection, and given that they do state they're happy for students to connect whatever routers they like, I went right ahead. Trouble is, despite listing the fact that the AirPort Express supports PPTP, I'm not sure how to go about setting it up. A quick google revealed very little. The IT department was happy to provide the logon domain and server address, but I don't know where in the interface to put them, much less where to select PPTP.
    I've been able to get an IP on the thing, but not one indicative of having logged in to the VPN.
    Ideas? Thoughts?

    Hello @mhernandez808,
    Welcome to the HP Support Forums! I see you would like to connect your HP Officejet 4622 to your Wireless network. I would like you to click on the link below to get started:
    Setting Up the Printer for a Wireless network for the HP Officejet 4622
    Please follow all steps listed above to connect to your Home network. Once connected you will be walked through setting up the wireless printer on your Computer.
    I hope this helps, if you have any questions please ask away!!
    Thanks,
    HevnLgh
    I work on behalf of HP
    Please click “Accept as Solution” if you feel my post solved your issue, it will help others find the solution.
    Click the “Kudos Thumbs Up" to the left of the reply button to say “Thanks” for helping!

  • VPN connection created with CMAK fails to update routing table on Windows 8.1 with error 8000ffff

    When my clients connect their CMAK-created VPN, it fails to run the script to set their routing table with the following error:
    Custom script (to update your routing table) failed (8000ffff)
    My objective is to create a VPN connection with split tunneling - does not use the VPN connection as the client's default gateway.
    All my clients are on Windows 8.1 64-bit, and are logged in with Administrative privileges
    My VPN Clients are on 10.242.2.0/24, my internal network is on 10.172.16.0/24
    I want only traffic for 10.172.16.0 to go via the VPN. Everything else should go via the client's internet connection
    My Connection Manager Administration Kit profile, was created on Windows 2012 R2 CMAK with the following settings:
    "Make this connection the client's default gateway" is UNticked on the IPv4 tab.
    Define a routing table update is specified with a text file containing:
    +++ Start of txt file +++
    REMOVE_GATEWAY
    add 10.172.16.0 mask 255.255.255.0 default metric default if default
    +++ End of txt file +++
    The txt file is saved in DOS/Windows format (not Unicode or UTF-8 which I've read causes problems)
    I've tried everything in lower and upper case in the txt file after reading that the file might be case sensitive
    The following appears on the client with logging enabled:
    [cmdial32] 10:42:34
    03 Pre-Init Event       CallingProcess = C:\WINDOWS\system32\rasautou.exe
    [cmdial32] 10:42:40
    04 Pre-Connect Event    ConnectionType = 1
    [cmdial32] 10:42:40
    06 Pre-Tunnel Event     UserName = UserName Domain =  DUNSetting = VPN (L2TP x64 NoGW) Tunnel DeviceName =  TunnelAddress = vpn.mydomain.tld
    [cmdial32] 10:42:43
    07 Connect Event
    [cmdial32] 10:42:43
    09 Custom Action Exe    ActionType = Connect Actions Description = (none) ActionPath = CMDL32.EXE. The program was launched successfully.
    [cmdial32] 10:42:43
    08 Custom Action Dll    ActionType = Connect Actions Description = to update your routing table ActionPath = C:\Users\UserName\AppData\Roaming\Microsoft\Network\Connections\Cm\VPN64\CMROUTE.DLL ReturnValue
    = 0x8000ffff
    [cmdial32] 10:42:43
    21 On-Error Event       ErrorCode = -2147418113 ErrorSource = to update your routing table
    [cmdial32] 10:42:43
    13 Disconnect Event     CallingProcess = C:\WINDOWS\system32\cmdial32.dll
    Where can I find out what error codes 8000ffff or -2147418113 mean?

    That was it. Thanks, Steven
    "By default, the dial-up entry and the VPN entry have Make this connection the default gateway selected.
    Leave this default in place, and remove any gateways by using the REMOVE_GATEWAY command in the routing table update file itself."
    It seems counter-intuitive to leave
    Make this connection the default gateway selected, when I specifically don't want that behaviour, but leaving it selected and using REMOVE_GATEWAY works for me.

  • Automatically create a custom VPN connection and set default wallpaper in a deployment...

    Hey guys,
    I've been hard at work on creating a custom deployment for our company to allow us to start rolling out Windows 7 at the first of next month. I demonstrated it to the brass today and they were blown away. All they asked for was two changes and I admit I'm stumped. Hopefully someone here can help:
    1 - Set Default Wallpaper for *all* users: I've written a script to copy our company wallpaper to "C:\Windows\Web\Wallpaper" during a deployment. Is there any way I can modify that script to set that wallpaper as default for anyone who logs into that computer. Or if there's a non-script way to do this I'm all ears. I just need that wallpaper as default.
    2 - Create a VPN Connection for our company intranet: Right now this is being done manually in the Network and Sharing Center. All they are doing is choosing "Set up a new connection or network" >> "Connect to a workplace" >> "Use my Internet Connection (VPN)" and just entering our VPN server IP Address and giving the connection a name. Surely there has to be a way to automate this with a script or something? Can anyone help?
    3 - BONUS: This is just gravy, but if anyone can tell me how to "silently" or "automatically" disable the "Highlight newly installed programs" checkbox for all users using a script or something, that would be *wonderful*.
    Can anyone help me here?

    1. Go here http://blogs.technet.com/deploymentguys/archive/2008/06/06/useful-script-number-5-adjusting-the-default-user-registry-hive.aspx . There is a script that will set your default wallpaper for you.
    2. Does your company use a VPN client?
    3. This option is set in the Registry. You could create a startup script or add this to your Task Sequence. Create the Dword and set it to 0 to disable highlighting.
    HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Start_NotifyNewApps
    Rich
    http://deploywindows7.wordpress.com/
    Thanks for responding Rich,
    1. I actually came across that script when I was poking around the Deployment guys forums, but I noticed that it did a lot more than just set the Wallpaper. I was trying to "keep it simple" plus the registry editing sort of made me nervous. I guess I can give it a go and see if it can be made to work for me.
    2. Our company dos not use a VPN client. If you look back at my description of the process in bullet point #2 we are just using the Network and Sharing Center that is built into Windows 7 to create a simple VPN connection. That's why I'm so certain there has to be a way to automate this process. ll we are doing is entering an IP Address and giving the connection a name. Surely I can script that, or is there maybe some way to create the connection on one computer and save it as a file that I can then copy to each machine during my deployment?
    3. Thanks for answering my bonus one too. Please forgive my ignorance because I am new to a lot of this. I assume I can create a "file" with the proper registry settings that can be applied during deployment right? I've seen people crate files that do this and use the .reg extension. Do you know how to make one of these or can you link me to a tutorial that steps me through it?
    You could always edit the script to leave the other parts out.  Thanks for the clarification on the VPN Client, just wanted to make absolutely sure. Let me know how if the process you found works for you.
    For the reg key, you would want to create the key I described, add it to your scripts directory, and then add a Client Build Custom Task in StateRestore to set the key in the registry. You can do this by adding a RunLineCommand to the Task Sequence. Then the command would look like this
    cmd /c regedit /s %deployroot%\scripts\NameOfRegKey.reghttp://deploywindows7.wordpress.com/

  • Windows 8.1 Pro Need command to disable "Use default gateway on remote network" option on VPN connection"

    Hello!
    I want to create bat script to create several VPN connection.
    There is powershell command to create vpn connection:
    add-vpnconnection -name "Test VPN" -serveraddress "vpn.example.com" -splittunneling -tunneltype "pptp"
    And I need to create VPN connection without the option "Use default gateway on remote network" option on VPN connection"
    Or modify this option on existent VPN connection with command.
    Please help me to find command option or other command to disable "Use default gateway on remote network" option on VPN connection" feature.

    http://technet.microsoft.com/nl-nl/library/ee431701%28v=ws.10%29.aspx RouteIPv4TrafficOverRAS True – Add a default gateway on the VPN connection False – Do not add default gateway on the VPN connection

  • Remote Desktop/Access shared files over PPTP VPN

    Hello,
    I just bought the RV180W so I can connect to my office computer from anywhere as a VPN client. The two things I need to do while I am connected as a VPN client is to be able to access my files on my office desktop and be able to remote desktop to it as well. I have Win7 on all of my computers. Ideally, I would like to do that over PPTP VPN connection but if that is not possible I can try Cisco QuickVPN software.
    I enabled PPTP on my router and created a user account. I was also able to successfully establish the connection remotely. While I was connected as a PPTP VPN client, I was able to access the Internet and my router setup page which is telling me that the connection is good. However, I was not able to either discover my office PC under my network tab in Win7 nor I was able to remote desktop. I keep my office PC on all the time and it never go to sleep. I did not create any connection policy but maybe this is the problem. Please let me know if you know of a solution.
    Thanks!

    Hi David,
    Thank you for the response.
    I was able to access the router configuration using the local IP address (in my case 192.168.1.1). I don't think I would have been able to access it using the public IP address since I have the router remote management feature disabled.
    Now after reading your email, I was finally able to remote desktop and access shared files through a PPTP VPN connection. Here is what I did:
    1- I separted the PPTP VPN IP address range from my DHCP range (in my case, PPTP VPN range is 192.168.1.200 to 210 and my DHCP range is from 192.168.1.100 to 199)
    2- I assigned my office desktop PC that I am trying to remote desktop to a fixed IP address (192.168.1.20)
    3- For remote desktop, I had to type the IP address (192.168.1.20). Typing the PC name (officepc) or searching for was not working.
    4- For shared files, I had to map a network drive as //192.168.1.20/My Pictures for example. I couldn't find my PC when searched for it under Network.
    After doing all that, I was able to do kinda what I wanted. Ideally, I would have liked to avoid using fixed IP addresses and be able to access computers by their name and see them under the Network tab. Is their a way to do this? I noticed that RV220W offers SSL VPN, would that help me?
    I would appreciate it if you could answer my last two questions.
    Thanks!
    Mustafa

  • Cannot establish VPN connection

    I am using wicd to manage my network connections.
    I am now trying to establish a VPN connection via pptpsetup, but it turned out that it failed to get a sucessful connection. The following is some debuging information:
    PS:
    I can use the VPN on my Android phone and Windows 8 computer with their default settings.
    The router used is TP-LINK WR841N.  I also tried to make the VPN connection throgh a Windows XP guest in my Virtualbox, but I get a 619 ERROR.
    jiang:~/ $ sudo pon kierk debug dump logfd 2 nodetach
    pppd options in effect:
    debug # (from command line)
    nodetach # (from command line)
    logfd 2 # (from command line)
    dump # (from command line)
    noauth # (from /etc/ppp/peers/kirk)
    name jiang # (from /etc/ppp/peers/kirk)
    remotename kirk # (from /etc/ppp/peers/kirk)
    # (from /etc/ppp/peers/kirk)
    pty pptp xxx.xxx.xxx.xxx --nolaunchpppd # (from /etc/ppp/peers/kirk)
    crtscts # (from /etc/ppp/options)
    # (from /etc/ppp/options)
    asyncmap 0 # (from /etc/ppp/options)
    lcp-echo-failure 4 # (from /etc/ppp/options)
    lcp-echo-interval 30 # (from /etc/ppp/options)
    hide-password # (from /etc/ppp/options)
    ipparam kierk # (from /etc/ppp/peers/kirk)
    proxyarp # (from /etc/ppp/options)
    nobsdcomp # (from /etc/ppp/peers/kirk)
    nodeflate # (from /etc/ppp/peers/kirk)
    require-mppe-128 # (from /etc/ppp/peers/kirk)
    noipx # (from /etc/ppp/options)
    using channel 21
    Using interface ppp0
    Connect: ppp0 <--> /dev/pts/1
    sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x71ca3d38> <pcomp> <accomp>]
    sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x71ca3d38> <pcomp> <accomp>]
    rcvd [LCP ConfReq id=0x1 <asyncmap 0x0> <auth chap MS-v2> <magic 0x2c64d2c3> <pcomp> <accomp>]
    sent [LCP ConfAck id=0x1 <asyncmap 0x0> <auth chap MS-v2> <magic 0x2c64d2c3> <pcomp> <accomp>]
    rcvd [CHAP Challenge id=0x2b <a88a56750015778c17b36c340ab95b54>, name = "pptpd"]
    Discarded non-LCP packet when LCP not open
    sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x71ca3d38> <pcomp> <accomp>]
    rcvd [LCP ConfReq id=0x2 <asyncmap 0x0> <auth chap MS-v2> <magic 0x170af2bc> <pcomp> <accomp>]
    sent [LCP ConfAck id=0x2 <asyncmap 0x0> <auth chap MS-v2> <magic 0x170af2bc> <pcomp> <accomp>]
    rcvd [LCP ConfAck id=0x1 <asyncmap 0x0> <magic 0x71ca3d38> <pcomp> <accomp>]
    sent [LCP EchoReq id=0x0 magic=0x71ca3d38]
    rcvd [CHAP Challenge id=0x4f <e7fbc765e5caffc883e1fd5ac7ddd514>, name = "pptpd"]
    Warning - secret file /etc/ppp/chap-secrets has world and/or group access
    added response cache entry 0
    sent [CHAP Response id=0x4f <6d44c943c527b9747f3a45fc527d2fe0000000037d7cd2d3359f8489fd322782173df80a2eb90bf200>, name = "jiang"]
    rcvd [LCP EchoRep id=0x0 magic=0x170af2bc]
    rcvd [CHAP Success id=0x4f "S=08E4FE5840F9196A9EF5377E65C8D20A2C030 M=Access granted"]
    response found in cache (entry 0)
    CHAP authentication succeeded
    Couldn't set pass-filter in kernel: Invalid argument
    sent [CCP ConfReq id=0x1 <mppe +H -M +S -L -D -C>]
    rcvd [CCP ConfReq id=0x1 <mppe +H -M +S -L -D -C>]
    sent [CCP ConfAck id=0x1 <mppe +H -M +S -L -D -C>]
    rcvd [CCP ConfAck id=0x1 <mppe +H -M +S -L -D -C>]
    MPPE 128-bit stateless compression enabled
    sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 192.168.0.103>]
    rcvd [IPCP ConfReq id=0x1 <addr 172.16.36.1>]
    sent [IPCP ConfAck id=0x1 <addr 172.16.36.1>]
    rcvd [IPCP ConfRej id=0x1 <compress VJ 0f 01>]
    sent [IPCP ConfReq id=0x2 <addr 192.168.0.103>]
    rcvd [IPCP ConfNak id=0x2 <addr 172.16.36.5>]
    sent [IPCP ConfReq id=0x3 <addr 172.16.36.5>]
    rcvd [IPCP ConfAck id=0x3 <addr 172.16.36.5>]
    Cannot determine ethernet address for proxy ARP
    local IP address 172.16.36.5
    remote IP address 172.16.36.1
    Script /etc/ppp/ip-up started (pid 13121)
    Script /etc/ppp/ip-up finished (pid 13121), status = 0x0
    Last edited by hellolj (2014-06-24 03:13:14)

    Hi,
    I don't want to sound sarcastic but why didn't you try moving to the NetworkManager utility, I remember well that (yeah it's a Shitian) back in Backtrack 5 and even the fourth connexions were managed by wicd and always caused troubles at some point. NetworkManager handles very well VPN connections without problems and still allows you to make advances configurations. Maybe you should consider trying it in your Virtual Box and post results. Sometimes thiking easy avoids headaches and lets you relax.
    On the other hand, it is true that router's "PPTP & VPN passthrough" option can cause troubles when using VPNs, and catalin's solution might be the best, but unless you absolutely need to use wicd (I can't think of a reason right now), you should consider easing things up with NetworkManager. Again just my belief.
    Are you trying to connect a VPN or create a VPN connection betweed two points ?
    Hope this helps.
    Last edited by sugartest (2014-07-10 13:12:57)

  • Smart card, PPTP VPN

    Hi for ALL,
    I have some trouble. I'm not very skilled in mac.
    I have gemalto smart card reader with smart card for connection to my workplace network via VPN (PPTP).
    In windows OS I just put in USB my token and creating new VPN connection where authentification is smart card (do not need this card use for login to local computer). When starting this VPN connection opening smart card pin window, enter pin, connection esabilisched.
    How do I the same on my macbook?
    P.S. VPN username is email address whith "@"
    THANKS

    any ideas please

  • More then one VPN connection?

    I made ​​a good start using VPN.
    But when I try to create additional VPN connections.
    But the links already established, interrupted.
    So i can online have one VPN established...
    How do i set the server up, so that i can have more?

    Hi There
    I have this exact same problem on L2TP VPN on Lion Server 10.7.3 and earlier (I've yet to try 10.7.4 - what version are you using?) What I've found is you can't have more than on client from the same IP so say if I connect to our VPN via an Internet connection if someone else connects on the same Internet connection they knock me off. But multiple connections are possible from different Internet connections at the same time. So I can have my laptop connected via my home Internet connection (adsl) and connect at the same time from my iPad on 3G but if I use my Laptop and iPad on the same home internet (adsl) whichever connects 1st knocks the other off - hope this makes sense.
    It drives me mad as myself and another employee share the same internet connection (adsl) for a few weeks of the year there is no 3G signal. On our old 10.4 server via PPTP we could have as many VPN connections as we wanted (never went higher than about 5 at a time) from the same internet connection. Not sure if this is a limitation of L2TP or Lion Server have still not managed to get PPPTP to work on Lion server. Going to give 10.7.4 a go 1st when I'm feeling brave...
    Ben

  • Window 8.1 system unable to access network shares via VPN connection

    Is there something inherent to Windows 8.1 that prevents it from accessing shares on a domain?
    I know that it cannot join a domain, but does that also mean that it cannot access shares which are on a domain?
    My problem is that I have several user that are running windows 8.1 that are connecting to our network via a VPN.
    The users have domain accounts but their computers as windows 8.1 cannot joined to the domain.
    So to access network shares they have to use their domain credentials to create a VPN connection.
    Once connected the user can RDP to systems on the domain using their domain accounts, so I know that their user names/passwords and permissions are correct. They can access these systems using the computer name, so I don't feel that I have a DNS issue.
    They can see the shares on our file server, but when they try to access their departments shared file, they receive an access denied message. There are a few shares that are completely wide open, shared to all users and all departments but they cannot access
    those shares either.
    You can ping the file server, from the the client when they are connected to the VPN but you just cannot access any of the shares.
    So...
    I am thinking that it has something to do with windows 8.1 and not being able to join a domain, but I cannot find anything to explicitly support this thought.
    Other users running a variety different OS (windows 7, OSX, Linux) can all access the shares without any problems via the VPN, so I am a little stumped.

    I have done some more testing and oddly enough I can map a drive if I use the IPaddress, but not the computer name, when checking the check box "connect using different credentials"and providing they users domain credentials.
    This seems to point to a DNS issue, one would think, but I can hit the file share server by name \\fileserver.dev.lan
    I can see all the shares, so dns seems to be fine right?
    So I don't understand why I can map a drive using do the IPaddress and not the machine name, but yet I can see and ping the server by name?
    When I try to create a mapped drive by machine name I receive the following message:
    Windows cannot access \\fileserver.dev.lan\all
    You do not have permissions to access \\fileserver.dev.lan. contact your network administrator  to request access.
    But if I use the \\x.x.x.x\all using the very same user and password I get connected with no problem.
    This only seems to happen on windows 8.1, which leads me to think that has something to do with OS. 
    I am thinking about upgrading to windows 8.1 pro, but I don't want to go though the hassle and expanse is the OS is not the problem.

  • How can I create a VPN network between my offices?

    I want to create a conection between my two offices so that they can work better towether.
    I downloaded the OSX Server v2.2 but I haven't been able to create the connection. I have read the help information in the app, but I don't understand what I'm doing wrong.
    here is what I did:
    I created a VPN Connection in Network preferences, then i oppened the server.app and activate the VPN service.
    I fill all the fields, then in the other office i created the VPN Connecion in network preferences and filled out with the information of the other network, but it wasnt able to canect. I might not have all that is needed, here is what I have:
    IMac mid 2010 with OS X server v2.2, this one will be the server host.
    mac mini new, this one will be the client.
    broadband Internet conection in both of my offices.
    I would really apreciate if someone could point me to the right direction.
    Is there a manual that explains how to do thisconnection?

    On the gateway to the remote network, for L2TP over IPSec you need to forward UDP ports 500, 1701, and 4500 to the endpoint.
    You also need either a static external IP address or a domain name for the gateway. Internally, the enpoint needs a static address.

  • Rv220w pptp remote connection use two ip address

                       Hello, I am a long time quick vpn user. I recently purchased a new windows 8.1 pro and the quickvpn fails. After many searches It appears this is a know issue and I should look for another way to connect. I choose to use the PPTP option. I set it up and everything it going well. however I have one slight issues when I try to use an ip specific software on my system that has remotely made the vpn pptp connection. I ran the cmd and check the ipconfig and see now that my computer has two ip address one from the air card I am using to connect to the internet 192.168.0.192 and one that the pptp vpn connection assigns 10.0.0.21 my issue is for my ip specific software to work I am forced to register both ip address for the same computer and each license from the vendor is good for one computer one ip address so this is going to double my operating cost. can anyone help.
    Please let me know if you need more info I will do my best to gather. Thanks in advance.

    I was able to make a quickvpn connection to my rv220w router via a wifi connection. I am unsure of the exact change made and I am now wondering if anyone can review this log and tell me what happened to allow the connection. At first I was very taken back and had to triple check to make sure it was working. Below is today’s router log at 18:00 I was able to make a successful quickvpn connection. Anyone see how? The rest of the morning I was trying repeatedly to make a connection
    is this important? "
    2014-02-01 19:04:31: [rv220w][IKE] INFO:  Ignoring request for negotiation to 166.142.243.242 as Local is configured as Responder.
    2000-01-01 00:00:36: [rv220w][IKE] INFO:  IKE started
    2014-02-01 12:47:49: [rv220w][IKE] INFO:  Adding IPSec configuration with identifier "joey01"
    2014-02-01 12:47:49: [rv220w][IKE] INFO:  Adding IKE configuration with identifier "joey01"
    2014-02-01 12:47:59: [rv220w][IKE] INFO:  Configuration found for 166.155.0.67[500].
    2014-02-01 12:47:59: [rv220w][IKE] INFO:  Received request for new phase 1 negotiation: 192.168.0.10[500]<=>166.155.0.67[500]
    2014-02-01 12:47:59: [rv220w][IKE] INFO:  Beginning Identity Protection mode.
    2014-02-01 12:47:59: [rv220w][IKE] INFO:  Received Vendor ID: MS NT5 ISAKMPOAKLEY
    2014-02-01 12:47:59: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 12:47:59: [rv220w][IKE] INFO:  Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 12:47:59: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 12:48:00: [rv220w][IKE] INFO:  For 166.155.0.67[500], Selected NAT-T version: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 12:48:00: [rv220w][IKE] INFO:  NAT-D payload does not match for 192.168.0.10[500]
    2014-02-01 12:48:00: [rv220w][IKE] INFO:  NAT-D payload matches for 166.155.0.67[500]
    2014-02-01 12:48:00: [rv220w][IKE] INFO:  NAT detected: ME
    2014-02-01 12:48:00: [rv220w][IKE] INFO:  Floating ports for NAT-T with peer 166.155.0.67[4500]
    2014-02-01 12:48:00: [rv220w][IKE] INFO:  ISAKMP-SA established for 192.168.0.10[4500]-166.155.0.67[4500] with spi:3671b391a56b4bee:52b561ece6e2aa09
    2014-02-01 12:48:00: [rv220w][IKE] INFO:  Sending Informational Exchange: notify payload[INITIAL-CONTACT]
    2014-02-01 12:48:00: [rv220w][IKE] INFO:  Responding to new phase 2 negotiation: 192.168.0.10[0]<=>166.155.0.67[0]
    2014-02-01 12:48:00: [rv220w][IKE] INFO:  Using IPsec SA configuration: 10.0.0.0/8<->166.155.0.67/32
    2014-02-01 12:48:00: [rv220w][IKE] INFO:  Adjusting peer's encmode 61443(61443)->Tunnel(1)
    2014-02-01 12:48:01: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 166.155.0.67->192.168.0.10 with spi=266310588(0xfdf93bc)
    2014-02-01 12:48:01: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 192.168.0.10->166.155.0.67 with spi=3530213431(0xd26ac837)
    2014-02-01 12:49:19: [rv220w][IKE] INFO:  Purged ISAKMP-SA with proto_id=ISAKMP and spi=3671b391a56b4bee:52b561ece6e2aa09.
    2014-02-01 12:49:20: [rv220w][IKE] INFO:  ISAKMP-SA deleted for 192.168.0.10[4500]-166.155.0.67[4500] with spi:3671b391a56b4bee:52b561ece6e2aa09
    2014-02-01 13:36:02: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 192.168.0.10->166.155.0.67 with spi=3530213431(0xd26ac837)
    2014-02-01 13:36:02: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 166.155.0.67->192.168.0.10 with spi=266310588(0xfdf93bc)
    2014-02-01 13:46:50: [rv220w][IKE] INFO:  Configuration found for 166.155.0.67[4500].
    2014-02-01 13:46:50: [rv220w][IKE] INFO:  Ports floated, peer initiatedcommunication on 4500
    2014-02-01 13:46:50: [rv220w][IKE] INFO:  Received request for new phase 1 negotiation: 192.168.0.10[4500]<=>166.155.0.67[4500]
    2014-02-01 13:46:50: [rv220w][IKE] INFO:  Beginning Identity Protection mode.
    2014-02-01 13:46:50: [rv220w][IKE] INFO:  Received Vendor ID: MS NT5 ISAKMPOAKLEY
    2014-02-01 13:46:50: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 13:46:50: [rv220w][IKE] INFO:  Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 13:46:50: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 13:46:50: [rv220w][IKE] INFO:  For 166.155.0.67[4500], Selected NAT-T version: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 13:46:50: [rv220w][IKE] INFO:  NAT-D payload does not match for 192.168.0.10[4500]
    2014-02-01 13:46:50: [rv220w][IKE] INFO:  NAT-D payload matches for 166.155.0.67[4500]
    2014-02-01 13:46:50: [rv220w][IKE] INFO:  NAT detected: ME
    2014-02-01 13:46:50: [rv220w][IKE] INFO:  ISAKMP-SA established for 192.168.0.10[4500]-166.155.0.67[4500] with spi:1d7d95d359ea4f66:d71a5efcd843af68
    2014-02-01 13:46:50: [rv220w][IKE] INFO:  Sending Informational Exchange: notify payload[INITIAL-CONTACT]
    2014-02-01 13:46:51: [rv220w][IKE] INFO:  Responding to new phase 2 negotiation: 192.168.0.10[0]<=>166.155.0.67[0]
    2014-02-01 13:46:51: [rv220w][IKE] INFO:  Using IPsec SA configuration: 10.0.0.0/8<->166.155.0.67/32
    2014-02-01 13:46:51: [rv220w][IKE] INFO:  Adjusting peer's encmode 61443(61443)->Tunnel(1)
    2014-02-01 13:46:51: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 166.155.0.67->192.168.0.10 with spi=225127593(0xd6b2ca9)
    2014-02-01 13:46:51: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 192.168.0.10->166.155.0.67 with spi=1534791298(0x5b7b0e82)
    2014-02-01 13:48:34: [rv220w][IKE] INFO:  Purged ISAKMP-SA with proto_id=ISAKMP and spi=1d7d95d359ea4f66:d71a5efcd843af68.
    2014-02-01 13:48:35: [rv220w][IKE] INFO:  ISAKMP-SA deleted for 192.168.0.10[4500]-166.155.0.67[4500] with spi:1d7d95d359ea4f66:d71a5efcd843af68
    2014-02-01 14:34:01: [rv220w][IKE] INFO:  Adding IPSec configuration with identifier "alohavpn"
    2014-02-01 14:34:01: [rv220w][IKE] INFO:  Adding IKE configuration with identifier "alohavpn"
    2014-02-01 14:34:06: [rv220w][IKE] INFO:  Using IPsec SA configuration: 10.0.0.250/8<->166.142.243.242/30
    2014-02-01 14:34:06: [rv220w][IKE] INFO:  Configuration found for 166.142.243.242.
    2014-02-01 14:34:06: [rv220w][IKE] INFO:  Initiating new phase 1 negotiation: 192.168.0.10[500]<=>166.142.243.242[500]
    2014-02-01 14:34:06: [rv220w][IKE] INFO:  Beginning Identity Protection mode.
    2014-02-01 14:34:06: [rv220w][IKE] INFO:   [ident_i1send:180]: XXX: NUMNATTVENDORIDS: 3
    2014-02-01 14:34:06: [rv220w][IKE] INFO:   [ident_i1send:184]: XXX: setting vendorid: 4
    2014-02-01 14:34:06: [rv220w][IKE] INFO:   [ident_i1send:184]: XXX: setting vendorid: 8
    2014-02-01 14:34:06: [rv220w][IKE] INFO:   [ident_i1send:184]: XXX: setting vendorid: 9
    2014-02-01 14:34:27: [rv220w][IKE] INFO:  accept a request to establish IKE-SA: 166.142.243.242
    2014-02-01 14:34:27: [rv220w][IKE] INFO:  Configuration found for 166.142.243.242.
    2014-02-01 14:34:37: [rv220w][IKE] ERROR:  Phase 2 negotiation failed due to time up waiting for phase1. ESP 166.142.243.242->192.168.0.10
    2014-02-01 14:34:52: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 192.168.0.10->166.155.0.67 with spi=1534791298(0x5b7b0e82)
    2014-02-01 14:34:52: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 166.155.0.67->192.168.0.10 with spi=225127593(0xd6b2ca9)
    2014-02-01 14:34:58: [rv220w][IKE] ERROR:  Invalid SA protocol type: 0
    2014-02-01 14:34:58: [rv220w][IKE] ERROR:  Phase 2 negotiation failed due to time up waiting for phase1.
    2014-02-01 14:35:06: [rv220w][IKE] ERROR:  Phase 1 negotiation failed due to time up for 166.142.243.242[500]. a8c862e86c5d65ea:0000000000000000
    2014-02-01 14:35:18: [rv220w][IKE] INFO:  Using IPsec SA configuration: 10.0.0.250/8<->166.142.243.242/30
    2014-02-01 14:35:18: [rv220w][IKE] INFO:  Configuration found for 166.142.243.242.
    2014-02-01 14:35:18: [rv220w][IKE] INFO:  Initiating new phase 1 negotiation: 192.168.0.10[500]<=>166.142.243.242[500]
    2014-02-01 14:35:18: [rv220w][IKE] INFO:  Beginning Identity Protection mode.
    2014-02-01 14:35:18: [rv220w][IKE] INFO:   [ident_i1send:180]: XXX: NUMNATTVENDORIDS: 3
    2014-02-01 14:35:18: [rv220w][IKE] INFO:   [ident_i1send:184]: XXX: setting vendorid: 4
    2014-02-01 14:35:18: [rv220w][IKE] INFO:   [ident_i1send:184]: XXX: setting vendorid: 8
    2014-02-01 14:35:18: [rv220w][IKE] INFO:   [ident_i1send:184]: XXX: setting vendorid: 9
    2014-02-01 14:35:29: [rv220w][IKE] INFO:  an undead schedule has been deleted: 'isakmp_chkph1there'.
    2014-02-01 14:35:29: [rv220w][IKE] INFO:  IPSec configuration with identifier "alohavpn" deleted sucessfully
    2014-02-01 14:35:29: [rv220w][IKE] WARNING:  no phase2 bounded.
    2014-02-01 14:35:29: [rv220w][IKE] INFO:  Purged ISAKMP-SA with spi=44ad4081d881ca39:0000000000000000.
    2014-02-01 14:35:29: [rv220w][IKE] INFO:  an undead schedule has been deleted: 'purge_remote'.
    2014-02-01 14:35:29: [rv220w][IKE] INFO:  an undead schedule has been deleted: 'isakmp_ph1resend'.
    2014-02-01 14:35:29: [rv220w][IKE] INFO:  IKE configuration with identifier "alohavpn" deleted sucessfully
    2014-02-01 14:45:36: [rv220w][IKE] INFO:  Configuration found for 166.155.0.67[4500].
    2014-02-01 14:45:36: [rv220w][IKE] INFO:  Ports floated, peer initiatedcommunication on 4500
    2014-02-01 14:45:36: [rv220w][IKE] INFO:  Received request for new phase 1 negotiation: 192.168.0.10[4500]<=>166.155.0.67[4500]
    2014-02-01 14:45:36: [rv220w][IKE] INFO:  Beginning Identity Protection mode.
    2014-02-01 14:45:36: [rv220w][IKE] INFO:  Received Vendor ID: MS NT5 ISAKMPOAKLEY
    2014-02-01 14:45:36: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 14:45:36: [rv220w][IKE] INFO:  Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 14:45:36: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 14:45:36: [rv220w][IKE] INFO:  For 166.155.0.67[4500], Selected NAT-T version: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 14:45:37: [rv220w][IKE] INFO:  NAT-D payload does not match for 192.168.0.10[4500]
    2014-02-01 14:45:37: [rv220w][IKE] INFO:  NAT-D payload matches for 166.155.0.67[4500]
    2014-02-01 14:45:37: [rv220w][IKE] INFO:  NAT detected: ME
    2014-02-01 14:45:37: [rv220w][IKE] INFO:  ISAKMP-SA established for 192.168.0.10[4500]-166.155.0.67[4500] with spi:e7ff5eebc74fe18e:26a523a055bdd961
    2014-02-01 14:45:37: [rv220w][IKE] INFO:  Sending Informational Exchange: notify payload[INITIAL-CONTACT]
    2014-02-01 14:45:37: [rv220w][IKE] INFO:  Responding to new phase 2 negotiation: 192.168.0.10[0]<=>166.155.0.67[0]
    2014-02-01 14:45:37: [rv220w][IKE] INFO:  Using IPsec SA configuration: 10.0.0.0/8<->166.155.0.67/32
    2014-02-01 14:45:37: [rv220w][IKE] INFO:  Adjusting peer's encmode 61443(61443)->Tunnel(1)
    2014-02-01 14:45:38: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 166.155.0.67->192.168.0.10 with spi=233645680(0xded2670)
    2014-02-01 14:45:38: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 192.168.0.10->166.155.0.67 with spi=3473253380(0xcf05a404)
    2014-02-01 14:47:04: [rv220w][IKE] INFO:  Purged ISAKMP-SA with proto_id=ISAKMP and spi=e7ff5eebc74fe18e:26a523a055bdd961.
    2014-02-01 14:47:05: [rv220w][IKE] INFO:  ISAKMP-SA deleted for 192.168.0.10[4500]-166.155.0.67[4500] with spi:e7ff5eebc74fe18e:26a523a055bdd961
    2014-02-01 14:49:00: [rv220w][IKE] ERROR:  Could not find configuration for 99.120.21.158[500]
    2014-02-01 14:49:01: [rv220w][IKE] ERROR:  Could not find configuration for 99.120.21.158[500]
    2014-02-01 14:49:03: [rv220w][IKE] ERROR:  Could not find configuration for 99.120.21.158[500]
    2014-02-01 14:49:07: [rv220w][IKE] ERROR:  Could not find configuration for 99.120.21.158[500]
    2014-02-01 14:49:42: [rv220w][IKE] INFO:  Adding IPSec configuration with identifier "tim000"
    2014-02-01 14:49:42: [rv220w][IKE] INFO:  Adding IKE configuration with identifier "tim000"
    2014-02-01 14:49:44: [rv220w][IKE] INFO:  Configuration found for 99.120.21.158[500].
    2014-02-01 14:49:44: [rv220w][IKE] INFO:  Received request for new phase 1 negotiation: 192.168.0.10[500]<=>99.120.21.158[500]
    2014-02-01 14:49:44: [rv220w][IKE] INFO:  Beginning Identity Protection mode.
    2014-02-01 14:49:44: [rv220w][IKE] INFO:  Received Vendor ID: MS NT5 ISAKMPOAKLEY
    2014-02-01 14:49:44: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 14:49:44: [rv220w][IKE] INFO:  Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 14:49:44: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 14:49:44: [rv220w][IKE] INFO:  For 99.120.21.158[500], Selected NAT-T version: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 14:49:44: [rv220w][IKE] INFO:  NAT-D payload does not match for 192.168.0.10[500]
    2014-02-01 14:49:44: [rv220w][IKE] INFO:  NAT-D payload does not match for 99.120.21.158[500]
    2014-02-01 14:49:44: [rv220w][IKE] INFO:  NAT detected: ME PEER
    2014-02-01 14:49:44: [rv220w][IKE] INFO:  Floating ports for NAT-T with peer 99.120.21.158[4500]
    2014-02-01 14:49:44: [rv220w][IKE] INFO:  ISAKMP-SA established for 192.168.0.10[4500]-99.120.21.158[4500] with spi:c37856d7496f4bc0:d866a785808f18ff
    2014-02-01 14:49:44: [rv220w][IKE] INFO:  Sending Informational Exchange: notify payload[INITIAL-CONTACT]
    2014-02-01 14:49:45: [rv220w][IKE] INFO:  Responding to new phase 2 negotiation: 192.168.0.10[0]<=>99.120.21.158[0]
    2014-02-01 14:49:45: [rv220w][IKE] INFO:  Using IPsec SA configuration: 10.0.0.0/8<->192.168.1.68/32
    2014-02-01 14:49:45: [rv220w][IKE] INFO:  Adjusting peer's encmode 61443(61443)->Tunnel(1)
    2014-02-01 14:49:45: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 99.120.21.158->192.168.0.10 with spi=201496659(0xc029853)
    2014-02-01 14:49:45: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 192.168.0.10->99.120.21.158 with spi=3623586341(0xd7fb8a25)
    2014-02-01 14:51:02: [rv220w][IKE] INFO:  Purged ISAKMP-SA with proto_id=ISAKMP and spi=c37856d7496f4bc0:d866a785808f18ff.
    2014-02-01 14:51:03: [rv220w][IKE] INFO:  ISAKMP-SA deleted for 192.168.0.10[4500]-99.120.21.158[4500] with spi:c37856d7496f4bc0:d866a785808f18ff
    2014-02-01 15:33:39: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 192.168.0.10->166.155.0.67 with spi=3473253380(0xcf05a404)
    2014-02-01 15:33:39: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 166.155.0.67->192.168.0.10 with spi=233645680(0xded2670)
    2014-02-01 15:37:46: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 192.168.0.10->99.120.21.158 with spi=3623586341(0xd7fb8a25)
    2014-02-01 15:37:46: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 99.120.21.158->192.168.0.10 with spi=201496659(0xc029853)
    2014-02-01 15:38:35: [rv220w][IKE] INFO:  Adding IPSec configuration with identifier "happy00"
    2014-02-01 15:38:35: [rv220w][IKE] INFO:  Adding IKE configuration with identifier "happy00"
    2014-02-01 15:38:55: [rv220w][IKE] INFO:  Using IPsec SA configuration: 10.0.0.0/8<->166.142.243.242/32
    2014-02-01 15:38:55: [rv220w][IKE] INFO:  Configuration found for 166.142.243.242.
    2014-02-01 15:38:55: [rv220w][IKE] INFO:  Ignoring request for negotiation to 166.142.243.242 as Local is configured as Responder.
    2014-02-01 15:40:28: [rv220w][IKE] INFO:  IPSec configuration with identifier "happy00" deleted sucessfully
    2014-02-01 15:40:28: [rv220w][IKE] WARNING:  no phase1 found for "happy00"
    2014-02-01 15:40:28: [rv220w][IKE] INFO:  IKE configuration with identifier "happy00" deleted sucessfully
    2014-02-01 15:40:28: [rv220w][IKE] ERROR:  sainfo identifier not found ("happy00")
    2014-02-01 15:40:28: [rv220w][IKE] ERROR:  Failed to Delete the IPSec configuration with identifier "happy00"
    2014-02-01 15:40:28: [rv220w][IKE] ERROR:  remote identifier not found ("")
    2014-02-01 15:40:28: [rv220w][IKE] ERROR:  Failed to Delete the IKE configuration with identifier ""
    2014-02-01 15:40:47: [rv220w][IKE] INFO:  Adding IPSec configuration with identifier "happy00"
    2014-02-01 15:40:47: [rv220w][IKE] INFO:  Adding IKE configuration with identifier "happy00"
    2014-02-01 15:40:55: [rv220w][IKE] INFO:  Using IPsec SA configuration: 10.0.0.0/8<->166.142.243.242/32
    2014-02-01 15:40:55: [rv220w][IKE] INFO:  Configuration found for 166.142.243.242.
    2014-02-01 15:40:55: [rv220w][IKE] INFO:  Ignoring request for negotiation to 166.142.243.242 as Local is configured as Responder.
    2014-02-01 15:44:52: [rv220w][IKE] WARNING:  no phase2 found for "joey01"
    2014-02-01 15:44:52: [rv220w][IKE] INFO:  IPSec configuration with identifier "joey01" deleted sucessfully
    2014-02-01 15:44:52: [rv220w][IKE] WARNING:  no phase1 found for "joey01"
    2014-02-01 15:44:52: [rv220w][IKE] INFO:  IKE configuration with identifier "joey01" deleted sucessfully
    2014-02-01 15:44:52: [rv220w][IKE] INFO:  Adding IPSec configuration with identifier "joey01"
    2014-02-01 15:44:52: [rv220w][IKE] INFO:  Adding IKE configuration with identifier "joey01"
    2014-02-01 15:45:02: [rv220w][IKE] INFO:  Configuration found for 166.155.0.67[500].
    2014-02-01 15:45:02: [rv220w][IKE] INFO:  Received request for new phase 1 negotiation: 192.168.0.10[500]<=>166.155.0.67[500]
    2014-02-01 15:45:02: [rv220w][IKE] INFO:  Beginning Identity Protection mode.
    2014-02-01 15:45:02: [rv220w][IKE] INFO:  Received Vendor ID: MS NT5 ISAKMPOAKLEY
    2014-02-01 15:45:02: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 15:45:02: [rv220w][IKE] INFO:  Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 15:45:02: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 15:45:02: [rv220w][IKE] INFO:  For 166.155.0.67[500], Selected NAT-T version: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 15:45:03: [rv220w][IKE] INFO:  NAT-D payload does not match for 192.168.0.10[500]
    2014-02-01 15:45:03: [rv220w][IKE] INFO:  NAT-D payload matches for 166.155.0.67[500]
    2014-02-01 15:45:03: [rv220w][IKE] INFO:  NAT detected: ME
    2014-02-01 15:45:03: [rv220w][IKE] INFO:  Floating ports for NAT-T with peer 166.155.0.67[4500]
    2014-02-01 15:45:03: [rv220w][IKE] INFO:  ISAKMP-SA established for 192.168.0.10[4500]-166.155.0.67[4500] with spi:26214a2b8fde97de:0f3107405c30ec29
    2014-02-01 15:45:03: [rv220w][IKE] INFO:  Sending Informational Exchange: notify payload[INITIAL-CONTACT]
    2014-02-01 15:45:03: [rv220w][IKE] INFO:  Responding to new phase 2 negotiation: 192.168.0.10[0]<=>166.155.0.67[0]
    2014-02-01 15:45:03: [rv220w][IKE] INFO:  Using IPsec SA configuration: 10.0.0.0/8<->166.155.0.67/32
    2014-02-01 15:45:03: [rv220w][IKE] INFO:  Adjusting peer's encmode 61443(61443)->Tunnel(1)
    2014-02-01 15:45:04: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 166.155.0.67->192.168.0.10 with spi=171519328(0xa392d60)
    2014-02-01 15:45:04: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 192.168.0.10->166.155.0.67 with spi=995888774(0x3b5c0e86)
    2014-02-01 15:46:19: [rv220w][IKE] INFO:  Purged ISAKMP-SA with proto_id=ISAKMP and spi=26214a2b8fde97de:0f3107405c30ec29.
    2014-02-01 15:46:20: [rv220w][IKE] INFO:  ISAKMP-SA deleted for 192.168.0.10[4500]-166.155.0.67[4500] with spi:26214a2b8fde97de:0f3107405c30ec29
    2014-02-01 15:47:22: [rv220w][IKE] INFO:  IPSec configuration with identifier "happy00" deleted sucessfully
    2014-02-01 15:47:22: [rv220w][IKE] WARNING:  no phase1 found for "happy00"
    2014-02-01 15:47:22: [rv220w][IKE] INFO:  IKE configuration with identifier "happy00" deleted sucessfully
    2014-02-01 15:47:22: [rv220w][IKE] ERROR:  sainfo identifier not found ("happy00")
    2014-02-01 15:47:22: [rv220w][IKE] ERROR:  Failed to Delete the IPSec configuration with identifier "happy00"
    2014-02-01 15:47:22: [rv220w][IKE] ERROR:  remote identifier not found ("")
    2014-02-01 15:47:22: [rv220w][IKE] ERROR:  Failed to Delete the IKE configuration with identifier ""
    2014-02-01 15:48:37: [rv220w][IKE] INFO:  Configuration found for 99.120.21.158[4500].
    2014-02-01 15:48:37: [rv220w][IKE] INFO:  Ports floated, peer initiatedcommunication on 4500
    2014-02-01 15:48:37: [rv220w][IKE] INFO:  Received request for new phase 1 negotiation: 192.168.0.10[4500]<=>99.120.21.158[4500]
    2014-02-01 15:48:37: [rv220w][IKE] INFO:  Beginning Identity Protection mode.
    2014-02-01 15:48:37: [rv220w][IKE] INFO:  Received Vendor ID: MS NT5 ISAKMPOAKLEY
    2014-02-01 15:48:37: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 15:48:37: [rv220w][IKE] INFO:  Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 15:48:37: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 15:48:37: [rv220w][IKE] INFO:  For 99.120.21.158[4500], Selected NAT-T version: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 15:48:37: [rv220w][IKE] INFO:  NAT-D payload does not match for 192.168.0.10[4500]
    2014-02-01 15:48:37: [rv220w][IKE] INFO:  NAT-D payload does not match for 99.120.21.158[4500]
    2014-02-01 15:48:37: [rv220w][IKE] INFO:  NAT detected: ME PEER
    2014-02-01 15:48:37: [rv220w][IKE] INFO:  ISAKMP-SA established for 192.168.0.10[4500]-99.120.21.158[4500] with spi:95b646cb75adbb50:0ed9f31398ea14aa
    2014-02-01 15:48:37: [rv220w][IKE] INFO:  Sending Informational Exchange: notify payload[INITIAL-CONTACT]
    2014-02-01 15:48:37: [rv220w][IKE] INFO:  Responding to new phase 2 negotiation: 192.168.0.10[0]<=>99.120.21.158[0]
    2014-02-01 15:48:37: [rv220w][IKE] INFO:  Using IPsec SA configuration: 10.0.0.0/8<->192.168.1.68/32
    2014-02-01 15:48:37: [rv220w][IKE] INFO:  Adjusting peer's encmode 61443(61443)->Tunnel(1)
    2014-02-01 15:48:38: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 99.120.21.158->192.168.0.10 with spi=254599107(0xf2cdfc3)
    2014-02-01 15:48:38: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 192.168.0.10->99.120.21.158 with spi=2917092721(0xaddf4d71)
    2014-02-01 15:50:17: [rv220w][IKE] INFO:  Purged ISAKMP-SA with proto_id=ISAKMP and spi=95b646cb75adbb50:0ed9f31398ea14aa.
    2014-02-01 15:50:18: [rv220w][IKE] INFO:  ISAKMP-SA deleted for 192.168.0.10[4500]-99.120.21.158[4500] with spi:95b646cb75adbb50:0ed9f31398ea14aa
    2014-02-01 15:50:23: [rv220w][IKE] INFO:  Adding IPSec configuration with identifier "happy00"
    2014-02-01 15:50:23: [rv220w][IKE] INFO:  Adding IKE configuration with identifier "happy00"
    2014-02-01 15:50:39: [rv220w][IKE] INFO:  Using IPsec SA configuration: 10.0.0.0/8<->166.142.243.242/32
    2014-02-01 15:50:39: [rv220w][IKE] INFO:  Configuration found for 166.142.243.242.
    2014-02-01 15:50:39: [rv220w][IKE] INFO:  Ignoring request for negotiation to 166.142.243.242 as Local is configured as Responder.
    2014-02-01 15:51:12: [rv220w][IKE] INFO:  IPSec configuration with identifier "happy00" deleted sucessfully
    2014-02-01 15:51:12: [rv220w][IKE] WARNING:  no phase1 found for "happy00"
    2014-02-01 15:51:12: [rv220w][IKE] INFO:  IKE configuration with identifier "happy00" deleted sucessfully
    2014-02-01 15:51:12: [rv220w][IKE] ERROR:  sainfo identifier not found ("happy00")
    2014-02-01 15:51:12: [rv220w][IKE] ERROR:  Failed to Delete the IPSec configuration with identifier "happy00"
    2014-02-01 15:51:12: [rv220w][IKE] ERROR:  remote identifier not found ("")
    2014-02-01 15:51:12: [rv220w][IKE] ERROR:  Failed to Delete the IKE configuration with identifier ""
    2014-02-01 16:33:05: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 192.168.0.10->166.155.0.67 with spi=995888774(0x3b5c0e86)
    2014-02-01 16:33:05: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 166.155.0.67->192.168.0.10 with spi=171519328(0xa392d60)
    2014-02-01 16:36:39: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 192.168.0.10->99.120.21.158 with spi=2917092721(0xaddf4d71)
    2014-02-01 16:36:39: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 99.120.21.158->192.168.0.10 with spi=254599107(0xf2cdfc3)
    2014-02-01 16:43:50: [rv220w][IKE] INFO:  Configuration found for 166.155.0.67[4500].
    2014-02-01 16:43:50: [rv220w][IKE] INFO:  Ports floated, peer initiatedcommunication on 4500
    2014-02-01 16:43:50: [rv220w][IKE] INFO:  Received request for new phase 1 negotiation: 192.168.0.10[4500]<=>166.155.0.67[4500]
    2014-02-01 16:43:50: [rv220w][IKE] INFO:  Beginning Identity Protection mode.
    2014-02-01 16:43:50: [rv220w][IKE] INFO:  Received Vendor ID: MS NT5 ISAKMPOAKLEY
    2014-02-01 16:43:50: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 16:43:50: [rv220w][IKE] INFO:  Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 16:43:50: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 16:43:50: [rv220w][IKE] INFO:  For 166.155.0.67[4500], Selected NAT-T version: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 16:43:50: [rv220w][IKE] INFO:  NAT-D payload does not match for 192.168.0.10[4500]
    2014-02-01 16:43:50: [rv220w][IKE] INFO:  NAT-D payload matches for 166.155.0.67[4500]
    2014-02-01 16:43:50: [rv220w][IKE] INFO:  NAT detected: ME
    2014-02-01 16:43:50: [rv220w][IKE] INFO:  ISAKMP-SA established for 192.168.0.10[4500]-166.155.0.67[4500] with spi:6a803bd2c559ba70:d005a2ba6e84b619
    2014-02-01 16:43:50: [rv220w][IKE] INFO:  Sending Informational Exchange: notify payload[INITIAL-CONTACT]
    2014-02-01 16:43:50: [rv220w][IKE] INFO:  Responding to new phase 2 negotiation: 192.168.0.10[0]<=>166.155.0.67[0]
    2014-02-01 16:43:50: [rv220w][IKE] INFO:  Using IPsec SA configuration: 10.0.0.0/8<->166.155.0.67/32
    2014-02-01 16:43:50: [rv220w][IKE] INFO:  Adjusting peer's encmode 61443(61443)->Tunnel(1)
    2014-02-01 16:43:51: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 166.155.0.67->192.168.0.10 with spi=98566123(0x5dfffeb)
    2014-02-01 16:43:51: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 192.168.0.10->166.155.0.67 with spi=3231695043(0xc09fc0c3)
    2014-02-01 16:45:28: [rv220w][IKE] INFO:  Purged ISAKMP-SA with proto_id=ISAKMP and spi=6a803bd2c559ba70:d005a2ba6e84b619.
    2014-02-01 16:45:29: [rv220w][IKE] INFO:  ISAKMP-SA deleted for 192.168.0.10[4500]-166.155.0.67[4500] with spi:6a803bd2c559ba70:d005a2ba6e84b619
    2014-02-01 16:47:29: [rv220w][IKE] INFO:  Configuration found for 99.120.21.158[4500].
    2014-02-01 16:47:29: [rv220w][IKE] INFO:  Ports floated, peer initiatedcommunication on 4500
    2014-02-01 16:47:29: [rv220w][IKE] INFO:  Received request for new phase 1 negotiation: 192.168.0.10[4500]<=>99.120.21.158[4500]
    2014-02-01 16:47:29: [rv220w][IKE] INFO:  Beginning Identity Protection mode.
    2014-02-01 16:47:29: [rv220w][IKE] INFO:  Received Vendor ID: MS NT5 ISAKMPOAKLEY
    2014-02-01 16:47:29: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 16:47:29: [rv220w][IKE] INFO:  Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 16:47:29: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 16:47:29: [rv220w][IKE] INFO:  For 99.120.21.158[4500], Selected NAT-T version: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 16:47:29: [rv220w][IKE] INFO:  NAT-D payload does not match for 192.168.0.10[4500]
    2014-02-01 16:47:29: [rv220w][IKE] INFO:  NAT-D payload does not match for 99.120.21.158[4500]
    2014-02-01 16:47:29: [rv220w][IKE] INFO:  NAT detected: ME PEER
    2014-02-01 16:47:29: [rv220w][IKE] INFO:  ISAKMP-SA established for 192.168.0.10[4500]-99.120.21.158[4500] with spi:6852c876e1425084:944da52b84937c9a
    2014-02-01 16:47:29: [rv220w][IKE] INFO:  Sending Informational Exchange: notify payload[INITIAL-CONTACT]
    2014-02-01 16:47:29: [rv220w][IKE] INFO:  Responding to new phase 2 negotiation: 192.168.0.10[0]<=>99.120.21.158[0]
    2014-02-01 16:47:29: [rv220w][IKE] INFO:  Using IPsec SA configuration: 10.0.0.0/8<->192.168.1.68/32
    2014-02-01 16:47:30: [rv220w][IKE] INFO:  Adjusting peer's encmode 61443(61443)->Tunnel(1)
    2014-02-01 16:47:30: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 99.120.21.158->192.168.0.10 with spi=103279842(0x627ece2)
    2014-02-01 16:47:30: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 192.168.0.10->99.120.21.158 with spi=2492252444(0x948cc11c)
    2014-02-01 16:48:47: [rv220w][IKE] INFO:  Purged ISAKMP-SA with proto_id=ISAKMP and spi=6852c876e1425084:944da52b84937c9a.
    2014-02-01 16:48:48: [rv220w][IKE] INFO:  ISAKMP-SA deleted for 192.168.0.10[4500]-99.120.21.158[4500] with spi:6852c876e1425084:944da52b84937c9a
    2014-02-01 17:31:52: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 192.168.0.10->166.155.0.67 with spi=3231695043(0xc09fc0c3)
    2014-02-01 17:31:52: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 166.155.0.67->192.168.0.10 with spi=98566123(0x5dfffeb)
    2014-02-01 17:35:31: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 192.168.0.10->99.120.21.158 with spi=2492252444(0x948cc11c)
    2014-02-01 17:35:31: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 99.120.21.158->192.168.0.10 with spi=103279842(0x627ece2)
    2014-02-01 17:42:40: [rv220w][IKE] INFO:  Configuration found for 166.155.0.67[4500].
    2014-02-01 17:42:40: [rv220w][IKE] INFO:  Ports floated, peer initiatedcommunication on 4500
    2014-02-01 17:42:40: [rv220w][IKE] INFO:  Received request for new phase 1 negotiation: 192.168.0.10[4500]<=>166.155.0.67[4500]
    2014-02-01 17:42:40: [rv220w][IKE] INFO:  Beginning Identity Protection mode.
    2014-02-01 17:42:40: [rv220w][IKE] INFO:  Received Vendor ID: MS NT5 ISAKMPOAKLEY
    2014-02-01 17:42:40: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 17:42:40: [rv220w][IKE] INFO:  Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 17:42:40: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 17:42:40: [rv220w][IKE] INFO:  For 166.155.0.67[4500], Selected NAT-T version: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 17:42:40: [rv220w][IKE] INFO:  NAT-D payload does not match for 192.168.0.10[4500]
    2014-02-01 17:42:40: [rv220w][IKE] INFO:  NAT-D payload matches for 166.155.0.67[4500]
    2014-02-01 17:42:40: [rv220w][IKE] INFO:  NAT detected: ME
    2014-02-01 17:42:41: [rv220w][IKE] INFO:  ISAKMP-SA established for 192.168.0.10[4500]-166.155.0.67[4500] with spi:610f4e8b8a701292:1b5b4fac9129d2cc
    2014-02-01 17:42:41: [rv220w][IKE] INFO:  Sending Informational Exchange: notify payload[INITIAL-CONTACT]
    2014-02-01 17:42:41: [rv220w][IKE] INFO:  Responding to new phase 2 negotiation: 192.168.0.10[0]<=>166.155.0.67[0]
    2014-02-01 17:42:41: [rv220w][IKE] INFO:  Using IPsec SA configuration: 10.0.0.0/8<->166.155.0.67/32
    2014-02-01 17:42:41: [rv220w][IKE] INFO:  Adjusting peer's encmode 61443(61443)->Tunnel(1)
    2014-02-01 17:42:41: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 166.155.0.67->192.168.0.10 with spi=5442197(0x530a95)
    2014-02-01 17:42:41: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 192.168.0.10->166.155.0.67 with spi=281087573(0x10c10e55)
    2014-02-01 17:43:58: [rv220w][IKE] INFO:  Purged ISAKMP-SA with proto_id=ISAKMP and spi=610f4e8b8a701292:1b5b4fac9129d2cc.
    2014-02-01 17:43:59: [rv220w][IKE] INFO:  ISAKMP-SA deleted for 192.168.0.10[4500]-166.155.0.67[4500] with spi:610f4e8b8a701292:1b5b4fac9129d2cc
    2014-02-01 17:46:24: [rv220w][IKE] INFO:  Configuration found for 99.120.21.158[4500].
    2014-02-01 17:46:24: [rv220w][IKE] INFO:  Ports floated, peer initiatedcommunication on 4500
    2014-02-01 17:46:24: [rv220w][IKE] INFO:  Received request for new phase 1 negotiation: 192.168.0.10[4500]<=>99.120.21.158[4500]
    2014-02-01 17:46:24: [rv220w][IKE] INFO:  Beginning Identity Protection mode.
    2014-02-01 17:46:24: [rv220w][IKE] INFO:  Received Vendor ID: MS NT5 ISAKMPOAKLEY
    2014-02-01 17:46:24: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 17:46:24: [rv220w][IKE] INFO:  Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 17:46:24: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 17:46:24: [rv220w][IKE] INFO:  For 99.120.21.158[4500], Selected NAT-T version: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 17:46:24: [rv220w][IKE] INFO:  NAT-D payload does not match for 192.168.0.10[4500]
    2014-02-01 17:46:24: [rv220w][IKE] INFO:  NAT-D payload does not match for 99.120.21.158[4500]
    2014-02-01 17:46:24: [rv220w][IKE] INFO:  NAT detected: ME PEER
    2014-02-01 17:46:25: [rv220w][IKE] INFO:  ISAKMP-SA established for 192.168.0.10[4500]-99.120.21.158[4500] with spi:34fbdc2521b83861:4f04939eefba3853
    2014-02-01 17:46:25: [rv220w][IKE] INFO:  Sending Informational Exchange: notify payload[INITIAL-CONTACT]
    2014-02-01 17:46:25: [rv220w][IKE] INFO:  Responding to new phase 2 negotiation: 192.168.0.10[0]<=>99.120.21.158[0]
    2014-02-01 17:46:25: [rv220w][IKE] INFO:  Using IPsec SA configuration: 10.0.0.0/8<->192.168.1.68/32
    2014-02-01 17:46:25: [rv220w][IKE] INFO:  Adjusting peer's encmode 61443(61443)->Tunnel(1)
    2014-02-01 17:46:25: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 99.120.21.158->192.168.0.10 with spi=232320279(0xdd8ed17)
    2014-02-01 17:46:25: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 192.168.0.10->99.120.21.158 with spi=2789259203(0xa640b7c3)
    2014-02-01 17:48:02: [rv220w][IKE] INFO:  Purged ISAKMP-SA with proto_id=ISAKMP and spi=34fbdc2521b83861:4f04939eefba3853.
    2014-02-01 17:48:03: [rv220w][IKE] INFO:  ISAKMP-SA deleted for 192.168.0.10[4500]-99.120.21.158[4500] with spi:34fbdc2521b83861:4f04939eefba3853
    2014-02-01 18:30:42: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 192.168.0.10->166.155.0.67 with spi=281087573(0x10c10e55)
    2014-02-01 18:30:42: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 166.155.0.67->192.168.0.10 with spi=5442197(0x530a95)
    2014-02-01 18:34:26: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 192.168.0.10->99.120.21.158 with spi=2789259203(0xa640b7c3)
    2014-02-01 18:34:26: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 99.120.21.158->192.168.0.10 with spi=232320279(0xdd8ed17)
    2014-02-01 18:41:21: [rv220w][IKE] INFO:  Configuration found for 166.155.0.67[4500].
    2014-02-01 18:41:21: [rv220w][IKE] INFO:  Ports floated, peer initiatedcommunication on 4500
    2014-02-01 18:41:21: [rv220w][IKE] INFO:  Received request for new phase 1 negotiation: 192.168.0.10[4500]<=>166.155.0.67[4500]
    2014-02-01 18:41:21: [rv220w][IKE] INFO:  Beginning Identity Protection mode.
    2014-02-01 18:41:21: [rv220w][IKE] INFO:  Received Vendor ID: MS NT5 ISAKMPOAKLEY
    2014-02-01 18:41:21: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 18:41:21: [rv220w][IKE] INFO:  Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 18:41:21: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 18:41:21: [rv220w][IKE] INFO:  For 166.155.0.67[4500], Selected NAT-T version: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 18:41:21: [rv220w][IKE] INFO:  NAT-D payload does not match for 192.168.0.10[4500]
    2014-02-01 18:41:21: [rv220w][IKE] INFO:  NAT-D payload matches for 166.155.0.67[4500]
    2014-02-01 18:41:21: [rv220w][IKE] INFO:  NAT detected: ME
    2014-02-01 18:41:22: [rv220w][IKE] INFO:  ISAKMP-SA established for 192.168.0.10[4500]-166.155.0.67[4500] with spi:11605c3a8435559f:38b8c86ef5bc8173
    2014-02-01 18:41:22: [rv220w][IKE] INFO:  Sending Informational Exchange: notify payload[INITIAL-CONTACT]
    2014-02-01 18:41:22: [rv220w][IKE] INFO:  Responding to new phase 2 negotiation: 192.168.0.10[0]<=>166.155.0.67[0]
    2014-02-01 18:41:22: [rv220w][IKE] INFO:  Using IPsec SA configuration: 10.0.0.0/8<->166.155.0.67/32
    2014-02-01 18:41:22: [rv220w][IKE] INFO:  Adjusting peer's encmode 61443(61443)->Tunnel(1)
    2014-02-01 18:41:22: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 166.155.0.67->192.168.0.10 with spi=116125724(0x6ebf01c)
    2014-02-01 18:41:22: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 192.168.0.10->166.155.0.67 with spi=712542982(0x2a788b06)
    2014-02-01 18:43:05: [rv220w][IKE] INFO:  Purged ISAKMP-SA with proto_id=ISAKMP and spi=11605c3a8435559f:38b8c86ef5bc8173.
    2014-02-01 18:43:06: [rv220w][IKE] INFO:  ISAKMP-SA deleted for 192.168.0.10[4500]-166.155.0.67[4500] with spi:11605c3a8435559f:38b8c86ef5bc8173
    2014-02-01 18:45:11: [rv220w][IKE] INFO:  Configuration found for 99.120.21.158[4500].
    2014-02-01 18:45:11: [rv220w][IKE] INFO:  Ports floated, peer initiatedcommunication on 4500
    2014-02-01 18:45:11: [rv220w][IKE] INFO:  Received request for new phase 1 negotiation: 192.168.0.10[4500]<=>99.120.21.158[4500]
    2014-02-01 18:45:11: [rv220w][IKE] INFO:  Beginning Identity Protection mode.
    2014-02-01 18:45:11: [rv220w][IKE] INFO:  Received Vendor ID: MS NT5 ISAKMPOAKLEY
    2014-02-01 18:45:11: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 18:45:11: [rv220w][IKE] INFO:  Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 18:45:11: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 18:45:11: [rv220w][IKE] INFO:  For 99.120.21.158[4500], Selected NAT-T version: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 18:45:11: [rv220w][IKE] INFO:  NAT-D payload does not match for 192.168.0.10[4500]
    2014-02-01 18:45:11: [rv220w][IKE] INFO:  NAT-D payload does not match for 99.120.21.158[4500]
    2014-02-01 18:45:11: [rv220w][IKE] INFO:  NAT detected: ME PEER
    2014-02-01 18:45:11: [rv220w][IKE] INFO:  ISAKMP-SA established for 192.168.0.10[4500]-99.120.21.158[4500] with spi:78a21d9a6ff7a028:d143c9317afa091b
    2014-02-01 18:45:11: [rv220w][IKE] INFO:  Sending Informational Exchange: notify payload[INITIAL-CONTACT]
    2014-02-01 18:45:11: [rv220w][IKE] INFO:  Responding to new phase 2 negotiation: 192.168.0.10[0]<=>99.120.21.158[0]
    2014-02-01 18:45:11: [rv220w][IKE] INFO:  Using IPsec SA configuration: 10.0.0.0/8<->192.168.1.68/32
    2014-02-01 18:45:11: [rv220w][IKE] INFO:  Adjusting peer's encmode 61443(61443)->Tunnel(1)
    2014-02-01 18:45:12: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 99.120.21.158->192.168.0.10 with spi=129883376(0x7bddcf0)
    2014-02-01 18:45:12: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 192.168.0.10->99.120.21.158 with spi=654476335(0x2702842f)
    2014-02-01 18:46:32: [rv220w][IKE] INFO:  Purged ISAKMP-SA with proto_id=ISAKMP and spi=78a21d9a6ff7a028:d143c9317afa091b.
    2014-02-01 18:46:33: [rv220w][IKE] INFO:  ISAKMP-SA deleted for 192.168.0.10[4500]-99.120.21.158[4500] with spi:78a21d9a6ff7a028:d143c9317afa091b
    2014-02-01 19:04:30: [rv220w][IKE] INFO:  Adding IPSec configuration with identifier "happy00"
    2014-02-01 19:04:30: [rv220w][IKE] INFO:  Adding IKE configuration with identifier "happy00"
    2014-02-01 19:04:31: [rv220w][IKE] INFO:  Using IPsec SA configuration: 10.0.0.0/8<->166.142.243.242/32
    2014-02-01 19:04:31: [rv220w][IKE] INFO:  Configuration found for 166.142.243.242.
    2014-02-01 19:04:31: [rv220w][IKE] INFO:  Ignoring request for negotiation to 166.142.243.242 as Local is configured as Responder.
    2014-02-01 19:05:13: [rv220w][IKE] INFO:  IPSec configuration with identifier "happy00" deleted sucessfully
    2014-02-01 19:05:13: [rv220w][IKE] WARNING:  no phase1 found for "happy00"
    2014-02-01 19:05:13: [rv220w][IKE] INFO:  IKE configuration with identifier "happy00" deleted sucessfully
    2014-02-01 19:05:14: [rv220w][IKE] ERROR:  sainfo identifier not found ("happy00")
    2014-02-01 19:05:14: [rv220w][IKE] ERROR:  Failed to Delete the IPSec configuration with identifier "happy00"
    2014-02-01 19:05:14: [rv220w][IKE] ERROR:  remote identifier not found ("")
    2014-02-01 19:05:14: [rv220w][IKE] ERROR:  Failed to Delete the IKE configuration with identifier ""
    2014-02-01 19:05:53: [rv220w][IKE] INFO:  Adding IPSec configuration with identifier "happy00"
    2014-02-01 19:05:53: [rv220w][IKE] INFO:  Adding IKE configuration with identifier "happy00"
    2014-02-01 19:06:07: [rv220w][IKE] INFO:  Using IPsec SA configuration: 10.0.0.0/8<->166.142.243.242/32
    2014-02-01 19:06:07: [rv220w][IKE] INFO:  Configuration found for 166.142.243.242.
    2014-02-01 19:06:07: [rv220w][IKE] INFO:  Ignoring request for negotiation to 166.142.243.242 as Local is configured as Responder.
    2014-02-01 19:06:27: [rv220w][IKE] INFO:  IPSec configuration with identifier "happy00" deleted sucessfully
    2014-02-01 19:06:27: [rv220w][IKE] WARNING:  no phase1 found for "happy00"
    2014-02-01 19:06:27: [rv220w][IKE] INFO:  IKE configuration with identifier "happy00" deleted sucessfully
    2014-02-01 19:06:27: [rv220w][IKE] ERROR:  sainfo identifier not found ("happy00")
    2014-02-01 19:06:27: [rv220w][IKE] ERROR:  Failed to Delete the IPSec configuration with identifier "happy00"
    2014-02-01 19:06:27: [rv220w][IKE] ERROR:  remote identifier not found ("")
    2014-02-01 19:06:27: [rv220w][IKE] ERROR:  Failed to Delete the IKE configuration with identifier ""
    2014-02-01 19:09:21: [rv220w][IKE] INFO:  Adding IPSec configuration with identifier "happy00"
    2014-02-01 19:09:21: [rv220w][IKE] INFO:  Adding IKE configuration with identifier "happy00"
    2014-02-01 19:09:33: [rv220w][IKE] INFO:  Configuration found for 99.101.94.86[500].
    2014-02-01 19:09:33: [rv220w][IKE] INFO:  Received request for new phase 1 negotiation: 192.168.0.10[500]<=>99.101.94.86[500]
    2014-02-01 19:09:33: [rv220w][IKE] INFO:  Beginning Identity Protection mode.
    2014-02-01 19:09:33: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 19:09:33: [rv220w][IKE] INFO:  Received Vendor ID: MS NT5 ISAKMPOAKLEY
    2014-02-01 19:09:33: [rv220w][IKE] INFO:  Received Vendor ID: RFC 3947
    2014-02-01 19:09:33: [rv220w][IKE] INFO:  Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 19:09:33: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 19:09:33: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 19:09:33: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 19:09:33: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 19:09:33: [rv220w][IKE] INFO:  For 99.101.94.86[500], Selected NAT-T version: RFC 3947
    2014-02-01 19:09:33: [rv220w][IKE] INFO:  NAT-D payload does not match for 192.168.0.10[500]
    2014-02-01 19:09:33: [rv220w][IKE] INFO:  NAT-D payload does not match for 99.101.94.86[500]
    2014-02-01 19:09:33: [rv220w][IKE] INFO:  NAT detected: ME PEER
    2014-02-01 19:09:34: [rv220w][IKE] INFO:  Configuration found for 99.101.94.86[500].
    2014-02-01 19:09:34: [rv220w][IKE] INFO:  Received request for new phase 1 negotiation: 192.168.0.10[500]<=>99.101.94.86[500]
    2014-02-01 19:09:34: [rv220w][IKE] INFO:  Beginning Identity Protection mode.
    2014-02-01 19:09:34: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 19:09:34: [rv220w][IKE] INFO:  Received Vendor ID: MS NT5 ISAKMPOAKLEY
    2014-02-01 19:09:34: [rv220w][IKE] INFO:  Received Vendor ID: RFC 3947
    2014-02-01 19:09:34: [rv220w][IKE] INFO:  Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 19:09:34: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 19:09:34: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 19:09:34: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 19:09:34: [rv220w][IKE] INFO:  For 99.101.94.86[500], Selected NAT-T version: RFC 3947
    2014-02-01 19:09:34: [rv220w][IKE] INFO:  NAT-D payload does not match for 192.168.0.10[500]
    2014-02-01 19:09:34: [rv220w][IKE] INFO:  NAT-D payload does not match for 99.101.94.86[500]
    2014-02-01 19:09:34: [rv220w][IKE] INFO:  NAT detected: ME PEER
    2014-02-01 19:09:34: [rv220w][IKE] INFO:  Floating ports for NAT-T with peer 99.101.94.86[4500]
    2014-02-01 19:09:34: [rv220w][IKE] INFO:  ISAKMP-SA established for 192.168.0.10[4500]-99.101.94.86[4500] with spi:c45d81319a7961c2:df7f2a51e8084be5
    2014-02-01 19:09:34: [rv220w][IKE] INFO:  Sending Informational Exchange: notify payload[INITIAL-CONTACT]
    2014-02-01 19:09:34: [rv220w][IKE] NOTIFY:  The packet is retransmitted by 99.101.94.86[500].
    2014-02-01 19:09:35: [rv220w][IKE] INFO:  Responding to new phase 2 negotiation: 192.168.0.10[0]<=>99.101.94.86[0]
    2014-02-01 19:09:35: [rv220w][IKE] INFO:  Using IPsec SA configuration: 10.0.0.0/8<->192.168.0.192/32
    2014-02-01 19:09:35: [rv220w][IKE] INFO:  Adjusting peer's encmode 3(3)->Tunnel(1)
    2014-02-01 19:09:35: [rv220w][IKE] INFO:  Floating ports for NAT-T with peer 99.101.94.86[4500]
    2014-02-01 19:09:35: [rv220w][IKE] INFO:  ISAKMP-SA established for 192.168.0.10[4500]-99.101.94.86[4500] with spi:51bf7e3f5283a021:c319b19d85b0abd0
    2014-02-01 19:09:35: [rv220w][IKE] ERROR:  wrong state 8.
    2014-02-01 19:09:35: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 99.101.94.86->192.168.0.10 with spi=43713598(0x29b043e)
    2014-02-01 19:09:35: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 192.168.0.10->99.101.94.86 with spi=2920045730(0xae0c5ca2)
    2014-02-01 19:10:33: [rv220w][IKE] INFO:  Configuration found for 99.101.94.86[500].
    2014-02-01 19:10:33: [rv220w][IKE] INFO:  Received request for new phase 1 negotiation: 192.168.0.10[500]<=>99.101.94.86[500]
    2014-02-01 19:10:33: [rv220w][IKE] INFO:  Beginning Identity Protection mode.
    2014-02-01 19:10:33: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 19:10:33: [rv220w][IKE] INFO:  Received Vendor ID: MS NT5 ISAKMPOAKLEY
    2014-02-01 19:10:33: [rv220w][IKE] INFO:  Received Vendor ID: RFC 3947
    2014-02-01 19:10:33: [rv220w][IKE] INFO:  Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 19:10:33: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 19:10:33: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 19:10:33: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 19:10:33: [rv220w][IKE] INFO:  For 99.101.94.86[500], Selected NAT-T version: RFC 3947
    2014-02-01 19:10:33: [rv220w][IKE] INFO:  Purged ISAKMP-SA with proto_id=ISAKMP and spi=51bf7e3f5283a021:c319b19d85b0abd0.
    2014-02-01 19:10:33: [rv220w][IKE] INFO:  NAT-D payload does not match for 192.168.0.10[500]
    2014-02-01 19:10:33: [rv220w][IKE] INFO:  NAT-D payload does not match for 99.101.94.86[500]
    2014-02-01 19:10:33: [rv220w][IKE] INFO:  NAT detected: ME PEER
    2014-02-01 19:10:33: [rv220w][IKE] INFO:  Floating ports for NAT-T with peer 99.101.94.86[4500]
    2014-02-01 19:10:33: [rv220w][IKE] INFO:  ISAKMP-SA established for 192.168.0.10[4500]-99.101.94.86[4500] with spi:518570911a48e055:e1b21587fbe64a7d
    2014-02-01 19:10:34: [rv220w][IKE] INFO:  ISAKMP-SA deleted for 192.168.0.10[4500]-99.101.94.86[4500] with spi:51bf7e3f5283a021:c319b19d85b0abd0
    2014-02-01 19:11:31: [rv220w][IKE] INFO:  Purged ISAKMP-SA with proto_id=ISAKMP and spi=518570911a48e055:e1b21587fbe64a7d.
    2014-02-01 19:11:32: [rv220w][IKE] INFO:  ISAKMP-SA deleted for 192.168.0.10[4500]-99.101.94.86[4500] with spi:518570911a48e055:e1b21587fbe64a7d
    2014-02-01 19:29:23: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 192.168.0.10->166.155.0.67 with spi=712542982(0x2a788b06)
    2014-02-01 19:29:23: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 166.155.0.67->192.168.0.10 with spi=116125724(0x6ebf01c)
    2014-02-01 19:33:13: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 192.168.0.10->99.120.21.158 with spi=654476335(0x2702842f)
    2014-02-01 19:33:13: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 99.120.21.158->192.168.0.10 with spi=129883376(0x7bddcf0)
    2014-02-01 19:40:16: [rv220w][IKE] INFO:  Configuration found for 166.155.0.67[4500].
    2014-02-01 19:40:16: [rv220w][IKE] INFO:  Ports floated, peer initiatedcommunication on 4500
    2014-02-01 19:40:16: [rv220w][IKE] INFO:  Received request for new phase 1 negotiation: 192.168.0.10[4500]<=>166.155.0.67[4500]
    2014-02-01 19:40:16: [rv220w][IKE] INFO:  Beginning Identity Protection mode.
    2014-02-01 19:40:16: [rv220w][IKE] INFO:  Received Vendor ID: MS NT5 ISAKMPOAKLEY
    2014-02-01 19:40:16: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 19:40:16: [rv220w][IKE] INFO:  Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 19:40:16: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 19:40:16: [rv220w][IKE] INFO:  For 166.155.0.67[4500], Selected NAT-T version: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 19:40:16: [rv220w][IKE] INFO:  NAT-D payload does not match for 192.168.0.10[4500]
    2014-02-01 19:40:16: [rv220w][IKE] INFO:  NAT-D payload matches for 166.155.0.67[4500]
    2014-02-01 19:40:16: [rv220w][IKE] INFO:  NAT detected: ME
    2014-02-01 19:40:16: [rv220w][IKE] INFO:  ISAKMP-SA established for 192.168.0.10[4500]-166.155.0.67[4500] with spi:86a51befd7ee8b38:1c072d85c8c7ab2e
    2014-02-01 19:40:16: [rv220w][IKE] INFO:  Sending Informational Exchange: notify payload[INITIAL-CONTACT]
    2014-02-01 19:40:16: [rv220w][IKE] INFO:  Responding to new phase 2 negotiation: 192.168.0.10[0]<=>166.155.0.67[0]
    2014-02-01 19:40:16: [rv220w][IKE] INFO:  Using IPsec SA configuration: 10.0.0.0/8<->166.155.0.67/32
    2014-02-01 19:40:16: [rv220w][IKE] INFO:  Adjusting peer's encmode 61443(61443)->Tunnel(1)
    2014-02-01 19:40:17: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 166.155.0.67->192.168.0.10 with spi=131309239(0x7d39eb7)
    2014-02-01 19:40:17: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 192.168.0.10->166.155.0.67 with spi=656105156(0x271b5ec4)
    2014-02-01 19:41:35: [rv220w][IKE] INFO:  Purged ISAKMP-SA with proto_id=ISAKMP and spi=86a51befd7ee8b38:1c072d85c8c7ab2e.
    2014-02-01 19:41:36: [rv220w][IKE] INFO:  ISAKMP-SA deleted for 192.168.0.10[4500]-166.155.0.67[4500] with spi:86a51befd7ee8b38:1c072d85c8c7ab2e
    2014-02-01 19:43:57: [rv220w][IKE] INFO:  Configuration found for 99.120.21.158[4500].
    2014-02-01 19:43:57: [rv220w][IKE] INFO:  Ports floated, peer initiatedcommunication on 4500
    2014-02-01 19:43:57: [rv220w][IKE] INFO:  Received request for new phase 1 negotiation: 192.168.0.10[4500]<=>99.120.21.158[4500]
    2014-02-01 19:43:57: [rv220w][IKE] INFO:  Beginning Identity Protection mode.
    2014-02-01 19:43:57: [rv220w][IKE] INFO:  Received Vendor ID: MS NT5 ISAKMPOAKLEY
    2014-02-01 19:43:57: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 19:43:57: [rv220w][IKE] INFO:  Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 19:43:57: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 19:43:57: [rv220w][IKE] INFO:  For 99.120.21.158[4500], Selected NAT-T version: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 19:43:57: [rv220w][IKE] INFO:  NAT-D payload does not match for 192.168.0.10[4500]
    2014-02-01 19:43:57: [rv220w][IKE] INFO:  NAT-D payload does not match for 99.120.21.158[4500]
    2014-02-01 19:43:57: [rv220w][IKE] INFO:  NAT detected: ME PEER
    2014-02-01 19:43:57: [rv220w][IKE] INFO:  ISAKMP-SA established for 192.168.0.10[4500]-99.120.21.158[4500] with spi:e1442468d0529bbe:f66c9601351bd3a2
    2014-02-01 19:43:57: [rv220w][IKE] INFO:  Sending Informational Exchange: notify payload[INITIAL-CONTACT]
    2014-02-01 19:43:57: [rv220w][IKE] INFO:  Responding to new phase 2 negotiation: 192.168.0.10[0]<=>99.120.21.158[0]
    2014-02-01 19:43:57: [rv220w][IKE] INFO:  Using IPsec SA configuration: 10.0.0.0/8<->192.168.1.68/32
    2014-02-01 19:43:57: [rv220w][IKE] INFO:  Adjusting peer's encmode 61443(61443)->Tunnel(1)
    2014-02-01 19:43:58: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 99.120.21.158->192.168.0.10 with spi=191762664(0xb6e10e8)
    2014-02-01 19:43:58: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 192.168.0.10->99.120.21.158 with spi=3118196926(0xb9dbe8be)
    2014-02-01 19:45:02: [rv220w][IKE] INFO:  Purged ISAKMP-SA with proto_id=ISAKMP and spi=e1442468d0529bbe:f66c9601351bd3a2.
    2014-02-01 19:45:03: [rv220w][IKE] INFO:  ISAKMP-SA deleted for 192.168.0.10[4500]-99.120.21.158[4500] with spi:e1442468d0529bbe:f66c9601351bd3a2
    2014-02-01 19:57:36: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 192.168.0.10->99.101.94.86 with spi=2920045730(0xae0c5ca2)
    2014-02-01 19:57:36: [rv220w][IKE] INFO:  IPsec-SA expired: ESP/Tunnel 99.101.94.86->192.168.0.10 with spi=43713598(0x29b043e)
    2014-02-01 19:59:08: [rv220w][IKE] INFO:  Configuration found for 99.101.94.86[500].
    2014-02-01 19:59:08: [rv220w][IKE] INFO:  Received request for new phase 1 negotiation: 192.168.0.10[500]<=>99.101.94.86[500]
    2014-02-01 19:59:08: [rv220w][IKE] INFO:  Beginning Identity Protection mode.
    2014-02-01 19:59:08: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 19:59:08: [rv220w][IKE] INFO:  Received Vendor ID: MS NT5 ISAKMPOAKLEY
    2014-02-01 19:59:08: [rv220w][IKE] INFO:  Received Vendor ID: RFC 3947
    2014-02-01 19:59:08: [rv220w][IKE] INFO:  Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 19:59:08: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 19:59:08: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 19:59:08: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 19:59:08: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 19:59:08: [rv220w][IKE] INFO:  For 99.101.94.86[500], Selected NAT-T version: RFC 3947
    2014-02-01 19:59:08: [rv220w][IKE] INFO:  NAT-D payload does not match for 192.168.0.10[500]
    2014-02-01 19:59:08: [rv220w][IKE] INFO:  NAT-D payload does not match for 99.101.94.86[500]
    2014-02-01 19:59:08: [rv220w][IKE] INFO:  NAT detected: ME PEER
    2014-02-01 19:59:08: [rv220w][IKE] INFO:  Floating ports for NAT-T with peer 99.101.94.86[4500]
    2014-02-01 19:59:08: [rv220w][IKE] INFO:  ISAKMP-SA established for 192.168.0.10[4500]-99.101.94.86[4500] with spi:5fbfcd9413b4c0f5:76e81b7495bfa7c8
    2014-02-01 19:59:08: [rv220w][IKE] INFO:  Sending Informational Exchange: notify payload[INITIAL-CONTACT]
    2014-02-01 19:59:08: [rv220w][IKE] INFO:  Responding to new phase 2 negotiation: 192.168.0.10[0]<=>99.101.94.86[0]
    2014-02-01 19:59:08: [rv220w][IKE] INFO:  Using IPsec SA configuration: 10.0.0.0/8<->192.168.0.192/32
    2014-02-01 19:59:08: [rv220w][IKE] INFO:  Adjusting peer's encmode 3(3)->Tunnel(1)
    2014-02-01 19:59:09: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 99.101.94.86->192.168.0.10 with spi=267963700(0xff8cd34)
    2014-02-01 19:59:09: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 192.168.0.10->99.101.94.86 with spi=2847327220(0xa9b6c3f4)
    2014-02-01 20:04:12: [rv220w][IKE] INFO:  an undead schedule has been deleted: 'pk_recvupdate'.
    2014-02-01 20:04:12: [rv220w][IKE] INFO:  Purged IPsec-SA with proto_id=ESP and spi=2847327220(0xa9b6c3f4).
    2014-02-01 20:04:12: [rv220w][IKE] INFO:  Purged ISAKMP-SA with proto_id=ISAKMP and spi=5fbfcd9413b4c0f5:76e81b7495bfa7c8.
    2014-02-01 20:04:13: [rv220w][IKE] WARNING:  no phase2 found for "happy00"
    2014-02-01 20:04:13: [rv220w][IKE] INFO:  IPSec configuration with identifier "happy00" deleted sucessfully
    2014-02-01 20:04:13: [rv220w][IKE] INFO:  ISAKMP-SA deleted for 192.168.0.10[4500]-99.101.94.86[4500] with spi:5fbfcd9413b4c0f5:76e81b7495bfa7c8
    2014-02-01 20:04:13: [rv220w][IKE] WARNING:  no phase2 bounded.
    2014-02-01 20:04:13: [rv220w][IKE] INFO:  Sending Informational Exchange: delete payload[]
    2014-02-01 20:04:13: [rv220w][IKE] INFO:  Purged IPsec-SA with spi=2920045730(0xae0c5ca2).
    2014-02-01 20:04:13: [rv220w][IKE] INFO:  Purged IPsec-SA with spi=267963700(0xff8cd34).
    2014-02-01 20:04:13: [rv220w][IKE] INFO:  Purged IPsec-SA with spi=43713598(0x29b043e).
    2014-02-01 20:04:13: [rv220w][IKE] INFO:  Purged ISAKMP-SA with spi=c45d81319a7961c2:df7f2a51e8084be5.
    2014-02-01 20:04:13: [rv220w][IKE] INFO:  an undead schedule has been deleted: 'purge_remote'.
    2014-02-01 20:04:13: [rv220w][IKE] INFO:  IKE configuration with identifier "happy00" deleted sucessfully
    2014-02-01 20:04:13: [rv220w][IKE] ERROR:  sainfo identifier not found ("happy00")
    2014-02-01 20:04:13: [rv220w][IKE] ERROR:  Failed to Delete the IPSec configuration with identifier "happy00"
    2014-02-01 20:04:13: [rv220w][IKE] ERROR:  remote identifier not found ("")
    2014-02-01 20:04:13: [rv220w][IKE] ERROR:  Failed to Delete the IKE configuration with identifier ""
    2014-02-01 20:06:01: [rv220w][IKE] INFO:  Adding IPSec configuration with identifier "happy00"
    2014-02-01 20:06:01: [rv220w][IKE] INFO:  Adding IKE configuration with identifier "happy00"
    2014-02-01 20:06:07: [rv220w][IKE] INFO:  Using IPsec SA configuration: 10.0.0.0/8<->166.142.243.242/32
    2014-02-01 20:06:07: [rv220w][IKE] INFO:  Configuration found for 166.142.243.242.
    2014-02-01 20:06:07: [rv220w][IKE] INFO:  Ignoring request for negotiation to 166.142.243.242 as Local is configured as Responder.
    2014-02-01 20:07:25: [rv220w][IKE] INFO:  IPSec configuration with identifier "happy00" deleted sucessfully
    2014-02-01 20:07:25: [rv220w][IKE] WARNING:  no phase1 found for "happy00"
    2014-02-01 20:07:25: [rv220w][IKE] INFO:  IKE configuration with identifier "happy00" deleted sucessfully
    2014-02-01 20:07:25: [rv220w][IKE] ERROR:  sainfo identifier not found ("happy00")
    2014-02-01 20:07:25: [rv220w][IKE] ERROR:  Failed to Delete the IPSec configuration with identifier "happy00"
    2014-02-01 20:07:25: [rv220w][IKE] ERROR:  remote identifier not found ("")
    2014-02-01 20:07:25: [rv220w][IKE] ERROR:  Failed to Delete the IKE configuration with identifier ""
    2014-02-01 20:09:58: [rv220w][IKE] INFO:  Adding IPSec configuration with identifier "happy00"
    2014-02-01 20:09:58: [rv220w][IKE] INFO:  Adding IKE configuration with identifier "happy00"
    2014-02-01 20:10:11: [rv220w][IKE] INFO:  Configuration found for 99.101.94.86[500].
    2014-02-01 20:10:11: [rv220w][IKE] INFO:  Received request for new phase 1 negotiation: 192.168.0.10[500]<=>99.101.94.86[500]
    2014-02-01 20:10:11: [rv220w][IKE] INFO:  Beginning Identity Protection mode.
    2014-02-01 20:10:11: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 20:10:11: [rv220w][IKE] INFO:  Received Vendor ID: MS NT5 ISAKMPOAKLEY
    2014-02-01 20:10:11: [rv220w][IKE] INFO:  Received Vendor ID: RFC 3947
    2014-02-01 20:10:11: [rv220w][IKE] INFO:  Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
    2014-02-01 20:10:11: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 20:10:11: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 20:10:11: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 20:10:11: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2014-02-01 20:10:11: [rv220w][IKE] INFO:  For 99.101.94.86[500], Selected NAT-T version: RFC 3947
    2014-02-01 20:10:11: [rv220w][IKE] INFO:  NAT-D payload does not match for 192.168.0.10[500]
    2014-02-01 20:10:11: [rv220w][IKE] INFO:  NAT-D payload does not match for 99.101.94.86[500]
    2014-02-01 20:10:11: [rv220w][IKE] INFO:  NAT detected: ME PEER
    2014-02-01 20:10:12: [rv220w][IKE] INFO:  Floating ports for NAT-T with peer 99.101.94.86[4500]
    2014-02-01 20:10:12: [rv220w][IKE] INFO:  ISAKMP-SA established for 192.168.0.10[4500]-99.101.94.86[4500] with spi:1e81ce312812da50:569671b6b2a1ad6a
    2014-02-01 20:10:12: [rv220w][IKE] INFO:  Sending Informational Exchange: notify payload[INITIAL-CONTACT]

Maybe you are looking for

  • Error while starting the sun application server 8

    when ever i start the default server i get the following server............. can any one tell me where shoud i specify the correct path or is the error related to something else................. [#|2005-06-29T14:27:32.250+0530|WARNING|sun-appserver-p

  • Can't see video on dvd only audio

    I do not get video when I play my dvd only audio.  I played this exact dvd yesterday and it was fine.  I also played it on my t.v. and it played fine.  Any ideas?

  • Sony HDR-CX7 and Final Cut Studio 2 ???

    Hey there people, I live in Australia and I am new to this forum & couldn't actually locate a specific thread for my questions so hopefully anyone could be of assistance. Basically, I have just bought a Macbook Pro 2.4ghz notebook, Final Cut Studio 2

  • How to use the PTDatePicker control

    This was a solution I wanted to post to old question referenced in DEV2DEV forums, thought I would post it here for now: Running WCI 6.1 MP1 PTDatePicker parameters: PTDatepicker = function(divName, varName, formName, textBoxName, buttonName, default

  • MacBook Pro 15" ~2009-10 won't boot

    Last night by MacBook Pro 15" froze and manually shut it down (holding down the power button.) Now it won't boot up. I get the Apple symbol and nothing else happens. I've tried holding the shift key and the c key and nothing happens. I have a relativ