VPN user looped into heartbeat network Just spot that if a VPN user is using the same network address with heartbeat segment (i.e. 192.168.x.x) , they cannot route to internal network properly after authentification but receive server not responding message, apart from changing the heartbeat segment to an uncommon address, could I make heartbeat network totally transparent from firewall ? BTW, office mode is not used since we may need to upgrade the VPN client to SecuClient instead of using SecuRemote. Any suggestion ? |