We are using Connect for our end user connection to HQ.
It seems like once a week (sometimes more) a number of clients lose their Connect connections.
I look on the FW and see they are actually connected to the FW, but they have two connections. One is the external home IP address and the other is their internal home network IP address.
Ex: I see Dave listed as talking to the FW
first connection is 192.168.1.10 (his internal home IP address)
2nd connection is 50.XXX.XXX.XXX (external home IP address)
When in reality a "good" connection reads as the FW issued IP of 192.168.100.X the The XG issues to people
Obviously those remote people cant connect to anything at HQ.
The "fix" is to restart the XG box or get into the console and restart the VPN service. This is NOT a good long term solution
This happened on v17 and v18
Any ideas?
This thread was automatically locked due to age.
