[x]
Posted via EE Mobile

Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again.
Question
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!
9.3

Sonicwall TZ170 VPN to Linksys WRVS4400N

Asked by vls-derek in Virtual Private Networking (VPN), IPSec Security Protocol

I'm attempting to connect my two office sites using a VPN. The primary office is using a Sonicwall TZ 170 running firmware SonicOS Enhanced 3.4.0.0-7e. The branch office is using a Linksys WRVS4400N Running Firmware V1.1.03.

I read another question on EE which addressed the same issue, but it referenced an article on delilama.net which appears to no longer be up. I've configured everything to the best of my knowledge and am still not able to establish the tunnel.

Here are the settings on the Linksys for VPN:
Tunnel Name: (Serial Number of Sonicwall)

Local Security Gateway Type: IP Only
IP Address: Greyed out, but it is the WAN address of the Linksys
Local Security Group Type: Subnet
IP Address: 192.168.17.1 (LAN Address of Linksys)
Subnet Masl: 255.255.255.0

Remote Security Gateway Type: IP Only
IP Address: (WAN Address of SonicWall)
Remote Security Group Type: Subnet
IP Address: 192.168.16.1 (LAN Address of Sonicwall)
Subnet Mask: 255.255.255.0

IPSec Setup---

Keying Mode: IKE with Preshared Key

Phase 1----
Encryption: 3DES
Authentication: MD5
Group: 768 bit
Key Life Time: 28800 sec

Phase 2-----
Encryption: 3DES
Authentication: MD5
Perfect Forard Secrecy: Disable
Preshared Key: 81AC279BD145
Group: 768-bit
Key Life Time: 3600 sec

Advance:
Aggressive Mode (Checked)
NetBIOS Broadcast (Checked)

________________________________________

Now the settings from the SonicWall:

General Tab----
Auth Mode: IKE using Preshared Secret
Name: (External MAC Address of Linksys)
IPsec Primary Gateway Name or Address: (WAN Address of Linksys)
IpSec Secondary Gateway Name or Address: 0.0.0.0

IKE Authentication--
Shared Secret: 81AC279BD145
Local IKE ID: SonicWall Identifier: 001c10f529CB (External MAC of linksys)
Peer IKE ID: SonicWall Identifier: 001c10f529cb (External MAC of Linksys)

Network Tab----

Local Netwrorks: Choose Local network from List (Lan Primary Subnet)
Destination Networks: Choose Destination netwrok from list (custom range that says subnet of linksys in other office) - settings from custom address object below:

Custom Address Object Name: 4314Range
Zone Assign: VPN
Type: Range
Start IP Address: 192.168.17.1
End IP Address: 192.168.17.254

Proposals Tab----

IKE (Phase 1) Proposal
Exchange: Aggressive Mode
DH Group: Group 1
Encryption: 3DES
Authentication: MD5
Life time: 28800

IKE (Phase 2) Proposal
Protocol: ESP
Encryption: 3DES
Authentication: MD5
Enable Perfect Forward Secrecy (Unchecked)
DH Group; Group 1
Life Time: 28800

Advanced Tab-----
Enable Keep Alive - Checked
Suppress automatic access rules creation for vpn policy - unchecked
Require auth of vpn clients by xauth - unchekced
user grou for xauth users - greyed out
enable windows network (netbios) broadcast - unchecked
enable multicast - unchecked
apply nat policies - unchecked
translated local network - greyed out
translated remote network - greyed out
management via this SA: (both unchekced)
user login from this sa: (both unchecked)
default lan gateway: 0.0.0.0
VPN Policy Bound to: Zone WAN



Log File from Linksys:
Mar 7 10:41:34 - [VPN Log]: packet from 24.39.122.206:500: ignoring unknown Vendor ID payload [da8e937880010000]
Mar 7 10:41:34 - [VPN Log]: packet from 24.39.122.206:500: received Vendor ID payload [Dead Peer Detection]
Mar 7 10:41:34 - [VPN Log]: packet from 24.39.122.206:500: received Vendor ID payload [XAUTH]
Mar 7 10:41:34 - [VPN Log]: "0006B13E9A44" #8: peer's ID_USER_FQDN contains no @
Mar 7 10:41:34 - [VPN Log]: "0006B13E9A44" #8: initial Aggressive Mode packet claiming to be from 24.39.122.206 on 24.39.122.206 but no connection has been authorized
Mar 7 10:41:34 - [VPN Log]: "0006B13E9A44" #8: sending notification INVALID_ID_INFORMATION to 24.39.122.206:500
Mar 7 10:41:40 - [VPN Log]: packet from 24.39.122.206:500: ignoring unknown Vendor ID payload [404bf439522ca3f6]
Mar 7 10:41:40 - [VPN Log]: packet from 24.39.122.206:500: ignoring unknown Vendor ID payload [5b362bc820f60006]
Mar 7 10:41:40 - [VPN Log]: packet from 24.39.122.206:500: received Vendor ID payload [RFC 3947] method set to=109
Mar 7 10:41:40 - [VPN Log]: packet from 24.39.122.206:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-03] meth=108, but already using method 109
Mar 7 10:41:40 - [VPN Log]: packet from 24.39.122.206:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-00]
Mar 7 10:41:40 - [VPN Log]: packet from 24.39.122.206:500: ignoring unknown Vendor ID payload [da8e937880010000]
Mar 7 10:41:40 - [VPN Log]: packet from 24.39.122.206:500: received Vendor ID payload [Dead Peer Detection]
Mar 7 10:41:40 - [VPN Log]: packet from 24.39.122.206:500: received Vendor ID payload [XAUTH]
Mar 7 10:41:40 - [VPN Log]: "0006B13E9A44" #9: peer's ID_USER_FQDN contains no @
Mar 7 10:41:40 - [VPN Log]: "0006B13E9A44" #9: initial Aggressive Mode packet claiming to be from 24.39.122.206 on 24.39.122.206 but no connection has been authorized
Mar 7 10:41:40 - [VPN Log]: "0006B13E9A44" #9: sending notification INVALID_ID_INFORMATION to 24.39.122.206:500
Mar 7 10:41:51 - [VPN Log]: packet from 24.39.122.206:500: ignoring unknown Vendor ID payload [404bf439522ca3f6]
Mar 7 10:41:51 - [VPN Log]: packet from 24.39.122.206:500: ignoring unknown Vendor ID payload [5b362bc820f60006]
Mar 7 10:41:51 - [VPN Log]: packet from 24.39.122.206:500: received Vendor ID payload [RFC 3947] method set to=109
Mar 7 10:41:51 - [VPN Log]: packet from 24.39.122.206:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-03] meth=108, but already using method 109
Mar 7 10:41:51 - [VPN Log]: packet from 24.39.122.206:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-00]
Mar 7 10:41:51 - [VPN Log]: packet from 24.39.122.206:500: ignoring unknown Vendor ID payload [da8e937880010000]
Mar 7 10:41:51 - [VPN Log]: packet from 24.39.122.206:500: received Vendor ID payload [Dead Peer Detection]
Mar 7 10:41:51 - [VPN Log]: packet from 24.39.122.206:500: received Vendor ID payload [XAUTH]
Mar 7 10:41:51 - [VPN Log]: "0006B13E9A44" #10: peer's ID_USER_FQDN contains no @
Mar 7 10:41:51 - [VPN Log]: "0006B13E9A44" #10: initial Aggressive Mode packet claiming to be from 24.39.122.206 on 24.39.122.206 but no connection has been authorized
Mar 7 10:41:51 - [VPN Log]: "0006B13E9A44" #10: sending notification INVALID_ID_INFORMATION to 24.39.122.206:500
Mar 7 10:42:10 - [VPN Log]: packet from 24.39.122.206:500: ignoring unknown Vendor ID payload [404bf439522ca3f6]
Mar 7 10:42:10 - [VPN Log]: packet from 24.39.122.206:500: ignoring unknown Vendor ID payload [5b362bc820f60006]
Mar 7 10:42:10 - [VPN Log]: packet from 24.39.122.206:500: received Vendor ID payload [RFC 3947] method set to=109
Mar 7 10:42:10 - [VPN Log]: packet from 24.39.122.206:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-03] meth=108, but already using method 109
Mar 7 10:42:10 - [VPN Log]: packet from 24.39.122.206:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-00]
Mar 7 10:42:10 - [VPN Log]: packet from 24.39.122.206:500: ignoring unknown Vendor ID payload [da8e937880010000]
Mar 7 10:42:10 - [VPN Log]: packet from 24.39.122.206:500: received Vendor ID payload [Dead Peer Detection]
Mar 7 10:42:10 - [VPN Log]: packet from 24.39.122.206:500: received Vendor ID payload [XAUTH]
Mar 7 10:42:10 - [VPN Log]: "0006B13E9A44" #11: peer's ID_USER_FQDN contains no @
Mar 7 10:42:10 - [VPN Log]: "0006B13E9A44" #11: initial Aggressive Mode packet claiming to be from 24.39.122.206 on 24.39.122.206 but no connection has been authorized
Mar 7 10:42:10 - [VPN Log]: "0006B13E9A44" #11: sending notification INVALID_ID_INFORMATION to 24.39.122.206:500
Mar 7 10:42:45 - [VPN Log]: packet from 24.39.122.206:500: ignoring unknown Vendor ID payload [404bf439522ca3f6]
Mar 7 10:42:45 - [VPN Log]: packet from 24.39.122.206:500: ignoring unknown Vendor ID payload [5b362bc820f60006]
Mar 7 10:42:45 - [VPN Log]: packet from 24.39.122.206:500: received Vendor ID payload [RFC 3947] method set to=109
Mar 7 10:42:45 - [VPN Log]: packet from 24.39.122.206:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-03] meth=108, but already using method 109
Mar 7 10:42:45 - [VPN Log]: packet from 24.39.122.206:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-00]
Mar 7 10:42:45 - [VPN Log]: packet from 24.39.122.206:500: ignoring unknown Vendor ID payload [da8e937880010000]
Mar 7 10:42:45 - [VPN Log]: packet from 24.39.122.206:500: received Vendor ID payload [Dead Peer Detection]
Mar 7 10:42:45 - [VPN Log]: packet from 24.39.122.206:500: received Vendor ID payload [XAUTH]
Mar 7 10:42:45 - [VPN Log]: "0006B13E9A44" #12: peer's ID_USER_FQDN contains no @
Mar 7 10:42:45 - [VPN Log]: "0006B13E9A44" #12: initial Aggressive Mode packet claiming to be from 24.39.122.206 on 24.39.122.206 but no connection has been authorized
Mar 7 10:42:45 - [VPN Log]: "0006B13E9A44" #12: sending notification INVALID_ID_INFORMATION to 24.39.122.206:500
Mar 7 10:42:50 - [VPN Log]: packet from 24.39.122.206:500: ignoring unknown Vendor ID payload [404bf439522ca3f6]
Mar 7 10:42:50 - [VPN Log]: packet from 24.39.122.206:500: ignoring unknown Vendor ID payload [5b362bc820f60006]
Mar 7 10:42:50 - [VPN Log]: packet from 24.39.122.206:500: received Vendor ID payload [RFC 3947] method set to=109
Mar 7 10:42:50 - [VPN Log]: packet from 24.39.122.206:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-03] meth=108, but already using method 109
Mar 7 10:42:50 - [VPN Log]: packet from 24.39.122.206:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-00]
Mar 7 10:42:50 - [VPN Log]: packet from 24.39.122.206:500: ignoring unknown Vendor ID payload [da8e937880010000]
Mar 7 10:42:50 - [VPN Log]: packet from 24.39.122.206:500: received Vendor ID payload [Dead Peer Detection]
Mar 7 10:42:50 - [VPN Log]: packet from 24.39.122.206:500: received Vendor ID payload [XAUTH]
Mar 7 10:42:50 - [VPN Log]: "0006B13E9A44" #13: peer's ID_USER_FQDN contains no @
Mar 7 10:42:50 - [VPN Log]: "0006B13E9A44" #13: initial Aggressive Mode packet claiming to be from 24.39.122.206 on 24.39.122.206 but no connection has been authorized
Mar 7 10:42:50 - [VPN Log]: "0006B13E9A44" #13: sending notification INVALID_ID_INFORMATION to 24.39.122.206:500
Mar 7 10:42:59 - [VPN Log]: packet from 24.39.122.206:500: ignoring unknown Vendor ID payload [404bf439522ca3f6]
Mar 7 10:42:59 - [VPN Log]: packet from 24.39.122.206:500: ignoring unknown Vendor ID payload [5b362bc820f60006]
Mar 7 10:42:59 - [VPN Log]: packet from 24.39.122.206:500: received Vendor ID payload [RFC 3947] method set to=109
Mar 7 10:42:59 - [VPN Log]: packet from 24.39.122.206:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-03] meth=108, but already using method 109
Mar 7 10:42:59 - [VPN Log]: packet from 24.39.122.206:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-00]
Mar 7 10:42:59 - [VPN Log]: packet from 24.39.122.206:500: ignoring unknown Vendor ID payload [da8e937880010000]
Mar 7 10:42:59 - [VPN Log]: packet from 24.39.122.206:500: received Vendor ID payload [Dead Peer Detection]
Mar 7 10:42:59 - [VPN Log]: packet from 24.39.122.206:500: received Vendor ID payload [XAUTH]
Mar 7 10:42:59 - [VPN Log]: "0006B13E9A44" #14: peer's ID_USER_FQDN contains no @
Mar 7 10:42:59 - [VPN Log]: "0006B13E9A44" #14: initial Aggressive Mode packet claiming to be from 24.39.122.206 on 24.39.122.206 but no connection has been authorized
Mar 7 10:42:59 - [VPN Log]: "0006B13E9A44" #14: sending notification INVALID_ID_INFORMATION to 24.39.122.206:500
Mar 7 10:43:17 - [VPN Log]: packet from 24.39.122.206:500: ignoring unknown Vendor ID payload [404bf439522ca3f6]
Mar 7 10:43:17 - [VPN Log]: packet from 24.39.122.206:500: ignoring unknown Vendor ID payload [5b362bc820f60006]
Mar 7 10:43:17 - [VPN Log]: packet from 24.39.122.206:500: received Vendor ID payload [RFC 3947] method set to=109
Mar 7 10:43:17 - [VPN Log]: packet from 24.39.122.206:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-03] meth=108, but already using method 109
Mar 7 10:43:17 - [VPN Log]: packet from 24.39.122.206:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-00]
Mar 7 10:43:17 - [VPN Log]: packet from 24.39.122.206:500: ignoring unknown Vendor ID payload [da8e937880010000]
Mar 7 10:43:17 - [VPN Log]: packet from 24.39.122.206:500: received Vendor ID payload [Dead Peer Detection]
Mar 7 10:43:17 - [VPN Log]: packet from 24.39.122.206:500: received Vendor ID payload [XAUTH]
Mar 7 10:43:17 - [VPN Log]: "0006B13E9A44" #15: peer's ID_USER_FQDN contains no @
Mar 7 10:43:17 - [VPN Log]: "0006B13E9A44" #15: initial Aggressive Mode packet claiming to be from 24.39.122.206 on 24.39.122.206 but no connection has been authorized
Mar 7 10:43:17 - [VPN Log]: "0006B13E9A44" #15: sending notification INVALID_ID_INFORMATION to 24.39.122.206:500
Mar 7 10:43:51 - [VPN Log]: packet from 24.39.122.206:500: ignoring unknown Vendor ID payload [404bf439522ca3f6]
Mar 7 10:43:51 - [VPN Log]: packet from 24.39.122.206:500: ignoring unknown Vendor ID payload [5b362bc820f60006]
Mar 7 10:43:51 - [VPN Log]: packet from 24.39.122.206:500: received Vendor ID payload [RFC 3947] method set to=109
Mar 7 10:43:51 - [VPN Log]: packet from 24.39.122.206:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-03] meth=108, but already using method 109
Mar 7 10:43:51 - [VPN Log]: packet from 24.39.122.206:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-00]
Mar 7 10:43:51 - [VPN Log]: packet from 24.39.122.206:500: ignoring unknown Vendor ID payload [da8e937880010000]
Mar 7 10:43:51 - [VPN Log]: packet from 24.39.122.206:500: received Vendor ID payload [Dead Peer Detection]
Mar 7 10:43:51 - [VPN Log]: packet from 24.39.122.206:500: received Vendor ID payload [XAUTH]
Mar 7 10:43:51 - [VPN Log]: "0006B13E9A44" #16: peer's ID_USER_FQDN contains no @
Mar 7 10:43:51 - [VPN Log]: "0006B13E9A44" #16: initial Aggressive Mode packet claiming to be from 24.39.122.206 on 24.39.122.206 but no connection has been authorized
Mar 7 10:43:51 - [VPN Log]: "0006B13E9A44" #16: sending notification INVALID_ID_INFORMATION to 24.39.122.206:500
Mar 7 10:43:57 - [VPN Log]: packet from 24.39.122.206:500: ignoring unknown Vendor ID payload [404bf439522ca3f6]
Mar 7 10:43:57 - [VPN Log]: packet from 24.39.122.206:500: ignoring unknown Vendor ID payload [5b362bc820f60006]
Mar 7 10:43:57 - [VPN Log]: packet from 24.39.122.206:500: received Vendor ID payload [RFC 3947] method set to=109
Mar 7 10:43:57 - [VPN Log]: packet from 24.39.122.206:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-03] meth=108, but already using method 109
Mar 7 10:43:57 - [VPN Log]: packet from 24.39.122.206:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-00]
Mar 7 10:43:57 - [VPN Log]: packet from 24.39.122.206:500: ignoring unknown Vendor ID payload [da8e937880010000]


Log File from SonicWall:

 04/03/2009 13:09:14.816 Notice Network Access Web management request allowed 192.168.16.253, 4257, LAN, VLS-TERMSERVER (admin) 192.168.16.1, 80, LAN TCP HTTP  
2 04/03/2009 13:09:09.848 Info VPN IKE IKE Initiator: Start Aggressive Mode negotiation (Phase 1) 24.39.122.206, 500 72.43.96.194, 500, rrcs-72-43-96-194.nyc.biz.rr.com VPN Policy: 001C10F529CB  
3 04/03/2009 13:09:09.848 Info VPN IKE IKE negotiation aborted due to timeout 24.39.122.206, 500 72.43.96.194, 500, rrcs-72-43-96-194.nyc.biz.rr.com VPN Policy: 001C10F529CB  
4 04/03/2009 13:08:57.336 Info Network Syslog Server cannot be reached 192.168.16.2, 3, LAN, vls-server.vincentlimousines.local 192.168.16.2, 514, vls-server.vincentlimousines.local    
5 04/03/2009 13:08:33.864 Info VPN IPSec Illegal IPSec SPI 72.43.96.194, rrcs-72-43-96-194.nyc.biz.rr.com 24.39.122.206 Inbound: SeqNum=0, SPI=0x0  
6 04/03/2009 13:08:33.848 Info VPN IKE IKE Initiator: Remote party timeout - Retransmitting IKE request. 24.39.122.206, 500 72.43.96.194, 500, rrcs-72-43-96-194.nyc.biz.rr.com VPN Policy: 001C10F529CB  
7 04/03/2009 13:08:14.848 Info VPN IKE IKE Initiator: Remote party timeout - Retransmitting IKE request. 24.39.122.206, 500 72.43.96.194, 500, rrcs-72-43-96-194.nyc.biz.rr.com VPN Policy: 001C10F529CB  
8 04/03/2009 13:08:05.896 Notice Network Access Web management request allowed 192.168.16.253, 4228, LAN, VLS-TERMSERVER (admin) 192.168.16.1, 80, LAN TCP HTTP  
9 04/03/2009 13:08:03.848 Info VPN IKE IKE Initiator: Remote party timeout - Retransmitting IKE request. 24.39.122.206, 500 72.43.96.194, 500, rrcs-72-43-96-194.nyc.biz.rr.com VPN Policy: 001C10F529CB  
10 04/03/2009 13:07:58.848 Info VPN IKE IKE Initiator: Start Aggressive Mode negotiation (Phase 1) 24.39.122.206, 500 72.43.96.194, 500, rrcs-72-43-96-194.nyc.biz.rr.com VPN Policy: 001C10F529CB  
11 04/03/2009 13:07:58.848 Info VPN IKE IKE negotiation aborted due to timeout 24.39.122.206, 500 72.43.96.194, 500, rrcs-72-43-96-194.nyc.biz.rr.com VPN Policy: 001C10F529CB  
12 04/03/2009 13:07:53.352 Info Network Syslog Server cannot be reached 192.168.16.2, 3, LAN, vls-server.vincentlimousines.local 192.168.16.2, 514, vls-server.vincentlimousines.local    
13 04/03/2009 13:07:25.864 Info VPN IPSec Illegal IPSec SPI 72.43.96.194, rrcs-72-43-96-194.nyc.biz.rr.com 24.39.122.206 Inbound: SeqNum=0, SPI=0x0  
14 04/03/2009 13:07:25.848 Info VPN IKE IKE Initiator: Remote party timeout - Retransmitting IKE request. 24.39.122.206, 500 72.43.96.194, 500, rrcs-72-43-96-194.nyc.biz.rr.com VPN Policy: 001C10F529CB  
15 04/03/2009 13:07:05.848 Info VPN IKE IKE Initiator: Remote party timeout - Retransmitting IKE request. 24.39.122.206, 500 72.43.96.194, 500, rrcs-72-43-96-194.nyc.biz.rr.com VPN Policy: 001C10F529CB  
16 04/03/2009 13:06:54.848 Info VPN IKE IKE Initiator: Remote party timeout - Retransmitting IKE request. 24.39.122.206, 500 72.43.96.194, 500, rrcs-72-43-96-194.nyc.biz.rr.com VPN Policy: 001C10F529CB  
17 04/03/2009 13:06:50.192 Info Network Syslog Server cannot be reached 192.168.16.2, 3, LAN, vls-server.vincentlimousines.local 192.168.16.2, 514, vls-server.vincentlimousines.local    
18 04/03/2009 13:06:49.176 Info VPN IKE IKE Initiator: Start Aggressive Mode negotiation (Phase 1) 24.39.122.206, 500 72.43.96.194, 500, rrcs-72-43-96-194.nyc.biz.rr.com VPN Policy: 001C10F529CB  
19 04/03/2009 13:06:40.880 Notice Network Access Web management request allowed 192.168.16.253, 4205, LAN, VLS-TERMSERVER (admin) 192.168.16.1, 80, LAN TCP HTTP  
20 04/03/2009 13:06:37.848 Info VPN IKE IKE Initiator: Remote party timeout - Retransmitting IKE request. 24.39.122.206, 500 72.43.96.194, 500, rrcs-72-43-96-194.nyc.biz.rr.com VPN Policy: 001C10F529CB  
21 04/03/2009 13:06:27.848 Info VPN IKE IKE Initiator: Remote party timeout - Retransmitting IKE request. 24.39.122.206, 500 72.43.96.194, 500, rrcs-72-43-96-194.nyc.biz.rr.com VPN Policy: 001C10F529CB  
22 04/03/2009 13:06:19.912 Info VPN IPSec Illegal IPSec SPI 72.43.96.194, rrcs-72-43-96-194.nyc.biz.rr.com 24.39.122.206 Inbound: SeqNum=0, SPI=0x0  
23 04/03/2009 13:06:19.848 Info VPN IKE IKE Initiator: Start Aggressive Mode negotiation (Phase 1) 24.39.122.206, 500 72.43.96.194, 500, rrcs-72-43-96-194.nyc.biz.rr.com VPN Policy: 001C10F529CB  
24 04/03/2009 13:06:19.848 Info VPN IKE IKE negotiation aborted due to timeout 24.39.122.206, 500 72.43.96.194, 500, rrcs-72-43-96-194.nyc.biz.rr.com VPN Policy: 001C10F529CB  
25 04/03/2009 13:05:45.848 Info VPN IKE IKE Initiator: Remote party timeout - Retransmitting IKE request. 24.39.122.206, 500 72.43.96.194, 500, rrcs-72-43-96-194.nyc.biz.rr.com VPN Policy: 001C10F529CB  
26 04/03/2009 13:05:44.624 Info Network Syslog Server cannot be reached 192.168.16.2, 3, LAN, vls-server.vincentlimousines.local 192.168.16.2, 514, vls-server.vincentlimousines.local    
27 04/03/2009 13:05:28.848 Info VPN IKE IKE Initiator: Remote party timeout - Retransmitting IKE request. 24.39.122.206, 500 72.43.96.194, 500, rrcs-72-43-96-194.nyc.biz.rr.com VPN Policy: 001C10F529CB  
28 04/03/2009 13:05:18.848 Info VPN IKE IKE Initiator: Remote party timeout - Retransmitting IKE request. 24.39.122.206, 500 72.43.96.194, 500, rrcs-72-43-96-194.nyc.biz.rr.com VPN Policy: 001C10F529CB  
29 04/03/2009 13:05:12.912 Info VPN IPSec Illegal IPSec SPI 72.43.96.194, rrcs-72-43-96-194.nyc.biz.rr.com 24.39.122.206 Inbound: SeqNum=0, SPI=0x0  
30 04/03/2009 13:05:12.848 Info VPN IKE IKE Initiator: Start Aggressive Mode negotiation (Phase 1) 24.39.122.206, 500 72.43.96.194, 500, rrcs-72-43-96-194.nyc.biz.rr.com VPN Policy: 001C10F529CB  
31 04/03/2009 13:05:12.848 Info VPN IKE IKE negotiation aborted due to timeout 24.39.122.206, 500 72.43.96.194, 500, rrcs-72-43-96-194.nyc.biz.rr.com VPN Policy: 001C10F529CB  
32 04/03/2009 13:04:37.848 Info VPN IKE IKE Initiator: Remote party timeout - Retransmitting IKE request. 24.39.122.206, 500 72.43.96.194, 500, rrcs-72-43-96-194.nyc.biz.rr.com VPN Policy: 001C10F529CB  
33 04/03/2009 13:04:35.688 Info Network Syslog Server cannot be reached 192.168.16.2, 3, LAN, vls-server.vincentlimousines.local 192.168.16.2, 514, vls-server.vincentlimousines.local    
34 04/03/2009 13:04:20.848 Info VPN IKE IKE Initiator: Remote party timeout - Retransmitting IKE request. 24.39.122.206, 500 72.43.96.194, 500, rrcs-72-43-96-194.nyc.biz.rr.com VPN Policy: 001C10F529CB  
35 04/03/2009 13:04:10.848 Info VPN IKE IKE Initiator: Remote party timeout - Retransmitting IKE request. 24.39.122.206, 500 72.43.96.194, 500, rrcs-72-43-96-194.nyc.biz.rr.com VPN Policy: 001C10F529CB  
36 04/03/2009 13:04:05.912 Info VPN IPSec Illegal IPSec SPI 72.43.96.194, rrcs-72-43-96-194.nyc.biz.rr.com 24.39.122.206 Inbound: SeqNum=0, SPI=0x0  
37 04/03/2009 13:04:05.848 Info VPN IKE IKE Initiator: Start Aggressive Mode negotiation (Phase 1) 24.39.122.206, 500 72.43.96.194, 500, rrcs-72-43-96-194.nyc.biz.rr.com VPN Policy: 001C10F529CB  
38 04/03/2009 13:04:05.848 Info VPN IKE IKE negotiation aborted due to timeout 24.39.122.206, 500 72.43.96.194, 500, rrcs-72-43-96-194.nyc.biz.rr.com VPN Policy: 001C10F529CB  
39 04/03/2009 13:03:32.848 Info VPN IKE IKE Initiator: Remote party timeout - Retransmitting IKE request. 24.39.122.206, 500 72.43.96.194, 500, rrcs-72-43-96-194.nyc.biz.rr.com VPN Policy: 001C10F529CB  
40 04/03/2009 13:03:24.160 Info Network Syslog Server cannot be reached 192.168.16.2, 3, LAN, vls-server.vincentlimousines.local 192.168.16.2, 514, vls-server.vincentlimousines.local    
41 04/03/2009 13:03:13.848 Info VPN IKE IKE Initiator: Remote party timeout - Retransmitting IKE request. 24.39.122.206, 500 72.43.96.194, 500, rrcs-72-43-96-194.nyc.biz.rr.com VPN Policy: 001C10F529CB  
42 04/03/2009 13:03:03.848 Info VPN IKE IKE Initiator: Remote party timeout - Retransmitting IKE request. 24.39.122.206, 500 72.43.96.194, 500, rrcs-72-43-96-194.nyc.biz.rr.com VPN Policy: 001C10F529CB  
43 04/03/2009 13:02:56.928 Info VPN IPSec Illegal IPSec SPI 72.43.96.194, rrcs-72-43-96-194.nyc.biz.rr.com 24.39.122.206 Inbound: SeqNum=0, SPI=0x0  
44 04/03/2009 13:02:56.848 Info VPN IKE IKE Initiator: Start Aggressive Mode negotiation (Phase 1) 24.39.122.206, 500 72.43.96.194, 500, rrcs-72-43-96-194.nyc.biz.rr.com VPN Policy: 001C10F529CB  
45 04/03/2009 13:02:56.848 Info VPN IKE IKE negotiation aborted due to timeout 24.39.122.206, 500 72.43.96.194, 500, rrcs-72-43-96-194.nyc.biz.rr.com VPN Policy: 001C10F529CB  
46 04/03/2009 13:02:22.848 Info VPN IKE IKE Initiator: Remote party timeout - Retransmitting IKE request. 24.39.122.206, 500 72.43.96.194, 500, rrcs-72-43-96-194.nyc.biz.rr.com VPN Policy: 001C10F529CB  
47 04/03/2009 13:02:13.848 Info Network Syslog Server cannot be reached 192.168.16.2, 3, LAN, vls-server.vincentlimousines.local 192.168.16.2, 514, vls-server.vincentlimousines.local    
48 04/03/2009 13:02:04.848 Info VPN IKE IKE Initiator: Remote party timeout - Retransmitting IKE request. 24.39.122.206, 500 72.43.96.194, 500, rrcs-72-43-96-194.nyc.biz.rr.com VPN Policy: 001C10F529CB  
49 04/03/2009 13:01:55.848 Info VPN IKE IKE Initiator: Remote party timeout - Retransmitting IKE request. 24.39.122.206, 500 72.43.96.194, 500, rrcs-72-43-96-194.nyc.biz.rr.com VPN Policy: 001C10F529CB  
50 04/03/2009 13:01:50.912 Info VPN IPSec Illegal IPSec SPI 72.43.96.194, rrcs-72-43-96-194.nyc.biz.rr.com 24.39.122.206 Inbound: SeqNum=0, SPI=0x0  





I appreciate any guidance that you have to offer. Thanks!
 
Related Solutions
Keywords: Sonicwall TZ170 VPN to Linksys WR…
Title
1 PPTP VPN w/Cisco 2801 & Windo…
2 L2TP fails after a few days but only f…
3 Home Office using RoadRunner Cable …
 
Loading Advertisement...
 
[+][-]04/04/09 07:14 AM, ID: 24067493Accepted Solution

View this solution now by starting your 30-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

About this solution

Zones: Virtual Private Networking (VPN), IPSec Security Protocol
Sign Up Now!
Solution Provided By: arnold
Participating Experts: 1
Solution Grade: A
 
[+][-]04/04/09 09:44 AM, ID: 24068068Author Comment

Often, when Experts are collaborating with members who have asked questions, they will request additional information about the problem. Askers respond with an author comment like this one.

Start your 30-day free trial to view this Author Comment or ask the Experts your question.

 
[+][-]04/04/09 10:31 AM, ID: 24068242Expert Comment

At Experts Exchange, members can ask their questions to thousands of technology professionals, also known as Experts. Experts compete and collaborate to answer those questions by leaving comments like this one.

Start your 30-day free trial to view this Expert Comment or ask the Experts your question.

 
[+][-]04/04/09 11:55 AM, ID: 24068587Author Comment

Often, when Experts are collaborating with members who have asked questions, they will request additional information about the problem. Askers respond with an author comment like this one.

Start your 30-day free trial to view this Author Comment or ask the Experts your question.

 
 
Loading Advertisement...
20091021-EE-VQP-81 - Hierarchy / EE_QW_3_20080625