Remote Desktop Gateway, built into Windows 2008 and 2012. Put it behind the pfSense, port forward the rdp port to the RDG. It authenticates the user and the user can connect to any internal machine. In the Remote Desktop Connection you can enter the information for the RDG. Protect using an SSL on the RDG. Bonus, you can also setup Remote Desktop Web Services so you can have programs on Terminal Services available... Note, that part DOES require IE. On Mar 27, 2014 2:37 PM, "greg whynott" <[email protected]> wrote:
> Hello, > > I'm not very familiar with TMG from Microsoft but a client I am helping > migrate to pfsense from TMG has asked me if they'll be able to use the RDP > port forward in the same way as TMG handles it. > > > Apparently there is a function within TMG which acts similar to named > based virtual web hosts, where it parses the DNS name from the request and > makes a forwarding decision based on that bit of information. > > For example, the firewall only has 1 public IP facing the internet. > > if you RDP to: you'll land on the internal server: > > host1.foo.com 10.101.1.2 > host2.foo.com 10.101.3.4 > host3.foo.com 10.101.1.8 > > > host1,2 and 3 all resolve to the same public IP. And we are not > specifying ports. > > That is the behaviour he is hoping to achieve, where he can RDP to > various internal machines without referencing ports. > > > Sound do-able? If pfsense can not do this, are you aware of anything > out there that can aside from TMG? > > -g > > > > > > > > _______________________________________________ > List mailing list > [email protected] > https://lists.pfsense.org/mailman/listinfo/list >
_______________________________________________ List mailing list [email protected] https://lists.pfsense.org/mailman/listinfo/list
