Guest User!

You are not Sophos Staff.

This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

no connection has been authorized with policy=PSK

2013:09:24-12:01:12 RRAS-01-2 pluto[14173]: | ******parse ISAKMP Oakley attribute: 

2013:09:24-12:01:12 RRAS-01-2 pluto[14173]: | af+type: OAKLEY_AUTHENTICATION_METHOD 

2013:09:24-12:01:12 RRAS-01-2 pluto[14173]: | length/value: 1 

2013:09:24-12:01:12 RRAS-01-2 pluto[14173]: | ******parse ISAKMP Oakley attribute: 

2013:09:24-12:01:12 RRAS-01-2 pluto[14173]: | af+type: OAKLEY_LIFE_TYPE 

2013:09:24-12:01:12 RRAS-01-2 pluto[14173]: | length/value: 1 

2013:09:24-12:01:12 RRAS-01-2 pluto[14173]: | ******parse ISAKMP Oakley attribute: 

2013:09:24-12:01:12 RRAS-01-2 pluto[14173]: | af+type: OAKLEY_LIFE_DURATION (variable length) 

2013:09:24-12:01:12 RRAS-01-2 pluto[14173]: | length/value: 4 

2013:09:24-12:01:12 RRAS-01-2 pluto[14173]: | preparse_isakmp_policy: peer requests PSK authentication 

2013:09:24-12:01:12 RRAS-01-2 pluto[14173]: packet from 71.194.220.141:3605: initial Main Mode message received on 192.168.168.61:500 but no connection has been authorized with policy=PSK


I get the above error whenever I try connecting with L2tp over IPsec. can someone please help me with this? Its the last thing I don't have working but most important option we need.

Thank you in advance.

I enabled Nat tranversing under IPsec and I now get the below errors

2013:09:24-12:21:57 RRAS-01-2 pluto[17788]: "L_for jimf"[2] 71.194.220.141:6939 #1: Quick Mode I1 message is unacceptable because it uses a previously used Message ID 0x816c4274 (perhaps this is a duplicated packet) 

2013:09:24-12:21:57 RRAS-01-2 pluto[17788]: "L_for jimf"[2] 71.194.220.141:6939 #1: sending encrypted notification INVALID_MESSAGE_ID to 71.194.220.141:6939


This thread was automatically locked due to age.
Parents
  • Hi, Jim, and welcome to the User BB!

    When collecting a log from an IPsec connection attempt, always do so with debug disabled.

    If you're certain that you have the correct PSK, my only other guess would be that the UTM is behind a NATting router.  If that's not it, please show the log lines (probably about 50) from a single connection attempt.

    Cheers - Bob
    PS Also, when posting a question, always state the exact version: 9.105-9?
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Reply
  • Hi, Jim, and welcome to the User BB!

    When collecting a log from an IPsec connection attempt, always do so with debug disabled.

    If you're certain that you have the correct PSK, my only other guess would be that the UTM is behind a NATting router.  If that's not it, please show the log lines (probably about 50) from a single connection attempt.

    Cheers - Bob
    PS Also, when posting a question, always state the exact version: 9.105-9?
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Children
No Data