IP Sec VPN negotiation Failed

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

IP Sec VPN negotiation Failed

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
IP Sec VPN negotiation Failed
IP Sec VPN negotiation Failed
2020-01-18 04:28:35 - last edited 2021-04-19 11:35:08
Model: TL-R600VPN  
Hardware Version: V3
Firmware Version: 1.3.0 Build 160803 Rel.64469n

phase2 negotiation failed due to time up waiting for phase1. ESP xxx.xxx.xxx.xxx[0]->192.168.27.253[0]

 

VPN connection not establish when router reboot. 

  0      
  0      
#1
Options
1 Reply
Re:IP Sec VPN negotiation Failed
2020-01-19 08:54:11 - last edited 2021-04-19 11:35:08

@Chanax 

 

192.168.27.253 is a private network IP address. If your VPN tunnel cross the public internet, please use the public IP address. Support that your topology is as follows.

Router A--------internet--------(WAN- IP 1.1.1.1)Router B------(192.168.27.253)Router C

If Router C want to establish IPsec VPN with Router A, then you need to fill in 1.1.1.1 as remote gateway on Router A. And you need to open UDP500 and UDP4500 on Router B.

Please note that R600VPN V3 doesn't support client to LAN IPsec VPN. It means that you cannot use a PC as IPsec VPN client to connect R600VPN.

  0  
  0  
#2
Options

Information

Helpful: 0

Views: 1602

Replies: 1

Related Articles