I do this using one of the Windows servers as a "Remote Desktop Gateway". This feature is built in to the Remote Desktop server and client (so no need for VPN - though you may choose to use one anyway) a you need to do is enabled it on the server and set the client to use it.
Moshe (Sorry for top-posting. On a mobile device.) On Mar 27, 2014 3:37 PM, "greg whynott" <greg.whyn...@gmail.com> 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 > List@lists.pfsense.org > https://lists.pfsense.org/mailman/listinfo/list >
_______________________________________________ List mailing list List@lists.pfsense.org https://lists.pfsense.org/mailman/listinfo/list
