VPN users unable to connect to Internal Servers with Public IP address

[Tiftadmin]

Thanks in advance for any help.

Having an issue when users connected to our vpn they cannot access the local ip address of the servers that have natted public ip addresses via remote desktop. They can access via RDP any server that doesn't have a public static ip natted to the internal server. Firewall log shows the connection is built but then I get the following error message "Routing failed to locate next hop for TCP from Outside:<vpn ip address> to inside:<public ip address of server>

[PatWruk]

Are you using a full tunnel vpn? Can they connect using the internal IP of the same server? 
My guess is it's a full tunnel vpn that is avoiding the NAT. Are you using an ASA or a router? If ASA try doing a packet trace and that should show where the error lies.

[MHM Cisco World]

can you share the config?

[Tiftadmin]

It is a split tunnel...Internal users have no issue connecting via RDP, etc. And the issue is only with servers who have a outside public ip address assigned to them.

[RachelGomez161999]

Troubleshooting Steps to Reconnect Your VPN
Check your internet connection.
Check your login credentials.
Change the VPN server connection. 
Restart the VPN software or browser plug-in. 
Check that your VPN software is up-to-date.
Check that your browser is up-to-date. 
Reinstall the latest VPN software package.

Greeting,

Rachel Gomez