Unable to access internal resources from sslvpn

Unable to access internal resources from sslvpn subnet

There can be a few reasons why you're unable to access internal resources while connected to the SANGFOR SSLVPN subnet.

Here are some troubleshooting steps you can try:

1. Check Route Configuration:

    Static Route: Verify if a static route is configured on the SSLVPN appliance to reach your internal network (192.168.x.x in your case). This route should point to the gateway that connects the SSLVPN appliance to your internal network switch.

2. L3VPN Resource Definition:

    Sangfor uses L3VPN resources to define reachable networks through the VPN. Check if the internal network you're trying to access is defined as an L3VPN resource on the SSLVPN server.

3. User Permissions:

    Ensure your user account has the appropriate role assigned. This role should have access to the L3VPN resource you created for the internal network.

As previously mentioned, the issue typically stems from absent routing configurations. Please verify that your network has established routes from the SSLVPN subnet to the internal resources subnet, and vice versa. Additionally, inspect the firewall rules to ensure that traffic from the SSL VPN subnet is authorized to reach the internal network. Could you specify if the inaccessibility concerns particular internal subnets, or is it associated with certain clients or devices? Please make sure that the resources that you can't reach from vpn ssl has the correct gateway setted.

Ensure that appropriate routes are configured to allow traffic from the SSL VPN subnet to reach the internal resources. Check firewall rules to confirm that traffic originating from the SSL VPN subnet is permitted to access the internal network. Additionally, verify DNS resolution and ensure that internal resources are reachable by hostname or IP address from the SSL VPN subnet.

Do you mean, you use Sangfor NGAF as the VPN Server?
If so, please check from your NGAF to the destination network, is it reachable or not.

And don't forget to setup proper configuration for SSL VPN, such as : define the users, define the resources, and define the roles for each/group of user(s).

thanks.

May there is wrong configuration at some end .Please follow the guide for correct configuration of ssl Vpn from support community .

HiHi,

Pls find the attached file the link - "Sangfor VPN Success Build Up But Some Subnet Cannot Ping To Other Side" for your Ref.

Sangfor VPN Success Build Up But Some Subnet Cannot Ping To Other Side.pdf (48.35 KB, Downloads: 127)

11 Jun 2024 15:24 Upload

Click file name to download attachment

For NSF models, there a new features which you can customize the routing precedence on the network.
My problem is the firewall having problem send back the packet to the SSL Subnet, the resolution was to change the routing precedence and make the SSLVPN routes next to direct routes and that resolved my issue.

Hi there,
Sorry to hear about the trouble accessing internal resources from the SSLVPN subnet. Could you provide more details about the issue? It could be related to network configurations or permissions. Let's troubleshoot together to resolve this.

can u verify if u can connect to the ssl vpn or no?

how many user are affected?