Printable View
Hey all, been a while since I've posted here. =P
Anyway,
Does anyone here know anything about Symantec Gateway Security Appliances (SGS 320), Symantec Enterprise VPN Client 8.0, and setting up VPN's with said hardware/software? Or know where I can find specific, step-by-step setup instructions?
I'm trying to set up a VPN for my office (to connect to an application server), and can't seem to get things to work (past phase 1, I think). :(
Thanks (tons) in advance.
--<MG>
Here's a bit more info from my router/firewall's log (newer message(s) first):
Quote:
09/16/2004 15:20:05.22 WlanLan Client - !!!: max number of retransmissions 2 reached STATE_AGGR_R1
09/16/2004 15:20:05.22 WlanLan Client - !!!: handling event EVENT_RETRANSMIT for 192.168.0.7 "WlanLan Client" #0
09/16/2004 15:19:53.87 Blocked - Port Scan Attack 80.138.207.127:43973 66.15.74.149:137 UDP
09/16/2004 15:19:49.22 WlanLan Client - !!!: max number of retransmissions 2 reached STATE_AGGR_R1
09/16/2004 15:19:49.22 WlanLan Client - !!!: handling event EVENT_RETRANSMIT for 192.168.0.7 "WlanLan Client" #0
09/16/2004 15:19:45.22 WlanLan Client - !!!: handling event EVENT_RETRANSMIT for 192.168.0.7 "WlanLan Client" #0
09/16/2004 15:19:35.22 WlanLan Client - STATE_AGGR_R1: from STATE_AGGR_R0; sent AR1, expecting AI2
09/16/2004 15:19:34.87 WlanLan Client - Responding to Aggressive Mode from Remote Peer 192.168.0.7
09/16/2004 15:19:27.82 WlanLan Client - !!!: handling event EVENT_RETRANSMIT for 192.168.0.7 "WlanLan Client" #0
09/16/2004 15:19:17.72 WlanLan Client - STATE_AGGR_R1: from STATE_AGGR_R0; sent AR1, expecting AI2
09/16/2004 15:19:17.37 WlanLan Client - Responding to Aggressive Mode from Remote Peer 192.168.0.7
Meh, I got it figured out.
so you gonna tell us what you did or do you just like talking to yourself? :D
Quote:
Originally Posted by NooNoo
It ended up being a simple/stupid mistake on my part. :/
The short answer: I had mismatching data confidentiality (encryption) methods for my VPN policies because I was using VPN Policy "A" for my client, but my firewall was expecting Policy "B".
And port 500 wasn't set properly, but caught that right away, so it was a non-issue.
And yeah, I like talking to myself. It's fun! =P
you get the answers you expect then :D