![check point vpn client logs check point vpn client logs](https://4.bp.blogspot.com/-OeAxb_FC94w/UbjYOo3HOnI/AAAAAAAAEdY/36nB3u_rbK4/s1600/2013-06-12_203507.jpg)
I edited the userc.C file manually and located the interface information of the remote gateway and deleted all the interface information (not the whole topology information). We cannot do the changes in the remote gateway. So as for the article the change should be done at the Remote Gateway's object_5.0.C file, so that the gateway interface information is not downloaded to the client.
#Check point vpn client logs full#
Provides full access to the corporate network with a VPN client. It seems that the Remote Gateway is running an older version of Check Point. Configure client-to-site VPN or set up an SSL VPN Portal to connect from any browser. When I searched in the Check Point usercenter I found the following article sk26189. 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.
![check point vpn client logs check point vpn client logs](https://i.imgur.com/m5G8aDJ.png)
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" Both of them must be used on expert mode (bash shell). "Negotiation with gateway xxxx at site x.x.x.x has failed. Check Point commands generally come under CP (general) and FW (firewall). 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.
![check point vpn client logs check point vpn client logs](https://sc1.checkpoint.com/sc/SolutionsStatics/sk98126/sk98126-31710020643.png)
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.