Re: [pfSense] RDP port forward based on destination name.

2014-03-27 Thread Jonathan Bainbridge
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

Re: [pfSense] RDP port forward based on destination name.

2014-03-27 Thread Ermal Luçi
There is a rdpproxy package in the wild that can probably adapted to do this. Though not in priorities anyway. On Thu, Mar 27, 2014 at 2:37 PM, greg whynott 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

Re: [pfSense] RDP port forward based on destination name.

2014-03-27 Thread Moshe Katz
On Mar 27, 2014 4:22 PM, "Chris Bagnall" wrote: > On 27/3/14 8:17 pm, Walter Parker wrote: > >> That's what I would recommend. The VPN can serve as a second gateway to >> protect the RDP from the outside world, so you could pitch this solution >> as >> higher security method of network access. >>

Re: [pfSense] RDP port forward based on destination name.

2014-03-27 Thread Moshe Katz
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

Re: [pfSense] RDP port forward based on destination name.

2014-03-27 Thread Chris Bagnall
On 27/3/14 8:17 pm, Walter Parker wrote: That's what I would recommend. The VPN can serve as a second gateway to protect the RDP from the outside world, so you could pitch this solution as higher security method of network access. This. There seem to be lots of dictionary attacks against RDP s

Re: [pfSense] RDP port forward based on destination name.

2014-03-27 Thread Walter Parker
That's what I would recommend. The VPN can serve as a second gateway to protect the RDP from the outside world, so you could pitch this solution as higher security method of network access. Walter On Thu, Mar 27, 2014 at 1:09 PM, compdoc wrote: > > I'm not very familiar with TMG from Microsof

Re: [pfSense] RDP port forward based on destination name.

2014-03-27 Thread compdoc
> 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. It will be interesting to hear if someone knows a way to do what you want, but I do it

Re: [pfSense] RDP port forward based on destination name.

2014-03-27 Thread David Burgess
On Thu, Mar 27, 2014 at 1:37 PM, greg whynott wrote: > 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 If you're using pfsense's DNS forwarder you can add host overrides for those three. Thi

Re: [pfSense] RDP port forward based on destination name.

2014-03-27 Thread Jochem de Waal
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 hos

[pfSense] RDP port forward based on destination name.

2014-03-27 Thread greg whynott
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,