LGfL VPN on 172 range not working (RAv3)

[nLinked]

RAv3 won't allow us to add 172 addresses as bookmarks. So I've added our TMG server's (our internal proxy) public facing 10. address as a bookmark into RAv3. How do I get TMG to forward VPN traffic to the correct internal machine? When I enter an IP address to connect to in RAv3, it says "Access to this resource has been denied". If I try my internal machine's hostname it says "Can not find server (hostname) or DNS error.

[RosieC]

Can you get to your tmg and do remote desktop from that? or static nat?

[nLinked]

We would also have various staff and wouldn't want them to rdc into tmg first.

 

I contacted Atomwide who said "The only way in which to do that would be configuring the NAT between are firewall and yours so that you have a one to one address that you can RDP to in the same way that you have configured the proxy server."

 

Not sure what that means...

[psydii]

You've probably solved it now.. but if not...

 

What service are your VPN users trying to reach? Unless it is a web based service You need to create a Publish Non-Web Server Protocol rule for it.

 

Another approach may be to have a secondary VPN configured and managed via TMG. Thus users use Anyconnect to get into the 10.8 range and then a second vpn client to get onto your 172.x range. If that is hard to sell to your users you might try likening it to having two keys - one to the front door of the building and another to your specific office.

 

P.

[nLinked]

Thanks, what we've done now is get LGfL to setup an RDP Gateway for us. They've bound port 3389 to our TMG public IP. They also gave us a .RDP file. This file connects us from a home computer to our internally hosted TMG server, at this point, our TMG server should accept our RDP connection on port 443.

 

Can we do this on our existing TMG server which is currently used as our proxy server too? We need to let our TMG accept RDP connections from outside, but via port 443.