![]() ![]() So the vpn-client tries to connect to one of the internal IPs and eventually ends up by trying to terminate the connection in our gateway. When I observed the file I saw that some of the interface IPs of the remote gateway are the exact same as our firewall interface IPs. It also stores the interface addresses of the remote gateway. The problem was, once the site is created in the VPN client, it automatically downloads the topology information and stores it in the userc.C file in the SecuRemote/database directory. When we observed the firewall logs (using SmartView Tracker) we observed that the IKE connection was sent to one of the interfaces of our Check Point gateway, which should not be the case. Received notification: invalid id information" ![]() "Negotiation with gateway xxxx at site x.x.x.x has failed. ![]() When they use an ADSL connection or a HSPA connection they can connect to that particular gateway but when they try to establish the same connection through our perimeter Check Point gateway the connection fails stating, Some of the staff members want to establish Remote Access VPN connections with another Check Point gateway. Recently we encountered a strange SecureClient behaviour in some internal users. Our company's head-office is running a Check Point UTM-1 firewall cluster at the perimeter.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |