We started using Connect and like it so far. We have a number of office locations all connected via IPSEC VPN and they all talk perfectly for normal LAN traffic.
When outside the LAN the Connect auto connect works great. And when we are on the main office LAN Connect sees we are on the LAN and doesnt connect. Perfect!
Main office 192.168.1.x (LAN) 50.x.x.x (WAN)
The problem is when you are in another office ex: 192.168.5.x (LAN) auto connect doesn't think you are on the LAN and tries to start the tunnel. We set up the Auto Connect tunnel option in Connect admin to an accessible spot on 192.168.1.x and you can ping that resource perfectly from the remote offices, but Connect decides you are not on the LAN network and tries to connect via the VPN.
The only thing i noticed was that when you are on the "home office" LAN the autoconnect resource takes <1 ms to ping. When you are at a remote office it takes 20-30 ms to ping
We have all employees regardless of remote office location connecting to the main office (thats where all the servers are)
Any ideas?
This thread was automatically locked due to age.
