Announcing the Saviynt Knowledge Exchange unifying the Saviynt forums, documentation, training,
and more in a single search tool across platforms. Read the announcement here.
This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject
Help
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Restarting VPN or restarting SC2 client breaks the connection

ekorh
Regular Contributor
Regular Contributor

‎09/29/2023 05:09 AM

Hi,

One of our clients has noticed that every time, if there's the need of, restarting VPN or restarting SC2 client it makes the connection break. 

First time this was resolved by updating the DNS on SC2 client side.

And the second time the connectivity issue was eventually resolved by updating SNAT rules on our customers SC2 server.  

Asking for our customer, why is this happening and is there something that could be done to prevent this?

Thanks already in advance!

0 Kudos
2 REPLIES 2

DixshantValecha
Saviynt Employee
Saviynt Employee

‎09/30/2023 02:23 AM - edited ‎09/30/2023 02:24 AM

Hi @ekorh,

We are checking on this and we will provide you an update shortly on this.

0 Kudos

DixshantValecha
Saviynt Employee
Saviynt Employee

‎09/30/2023 03:28 AM

Hi @ekorh ,

The issues you've described with the SC2 client connection breaking when restarting either the VPN or the SC2 client could be due to various factors. Let's break down each issue and potential solutions.

DNS Issues with SC2 Client:When you restart the VPN or SC2 client, it might trigger DNS resolution problems. Here are some steps to consider:

  • DNS Configuration: Ensure that the DNS settings on the SC2 client are correctly configured. It's possible that the SC2 client is not using the correct DNS server after the VPN restart. Update the DNS settings on the SC2 client to use reliable DNS servers.

  • DNS Cache: Clear the DNS cache on the SC2 client. This can help resolve any lingering DNS resolution issues.(This needs to be checked with your internal Infra team first).

SNAT Rules on SC2 Server:Updating SNAT (Source Network Address Translation) rules on the customer's SC2 server suggests that there may be issues with how the server is handling network traffic. Here are some considerations:

  • SNAT Configuration: Review the SNAT rules on the SC2 server. Ensure that they are correctly configured to handle NAT for VPN connections.Misconfigured SNAT rules can disrupt traffic when the VPN or client restarts.
  • Connection Timeout: Check if there are connection timeouts or session limits set in the SNAT rules. These limitations could cause disruptions when the connection is reset. Adjusting the timeout settings may help.

Preventing Future Issues:

  • Documentation: Maintain detailed network configuration documentation.

  • Testing: Periodically test VPN/SC2 client connections after changes.

  • Redundancy: Implement redundancy for critical network components.

We trust that these recommendations will assist in resolving the existing concerns and contribute to the overall stability and reliability of your network infrastructure.Should you require further assistance or clarification on any of these points, please do not hesitate to reach out.

Copyright © 2024 Khoros, LLC