You can use IPSec to restrict the use of the external ip.
You set up a ipsec rule that listen to port 3389 on the external interface
and then deny connections if the client don´t have the appropiate ipsec
policy assigned. You can use either certificates or pre-shared key when you
use ipsec.
Rickard
Hi Rickard
Thank you for your reply.
I was reading your reply to Jason about the 2 NIC scenario.
That would be one of my options as well, I presume
I presume the IPsec option won'teven give the user the connection
screen, correct? so therefor a more secure and delicate way to stop
people getting to the server.
Korstiaan
> You can use IPSec to restrict the use of the external ip.
> You set up a ipsec rule that listen to port 3389 on the external interface
[quoted text clipped - 20 lines]
> >
> > Korstiaan
Rickard(Riwe) - 28 Jul 2005 16:10 GMT
Yes, that is correct, unless the client have the right ipsec response policy
it won´t connect to the TS server.
Rickard
Hi Rickard
Thank you for your reply.
I was reading your reply to Jason about the 2 NIC scenario.
That would be one of my options as well, I presume
I presume the IPsec option won'teven give the user the connection
screen, correct? so therefor a more secure and delicate way to stop
people getting to the server.
Korstiaan
Rickard(Riwe) wrote:
> You can use IPSec to restrict the use of the external ip.
> You set up a ipsec rule that listen to port 3389 on the external interface
[quoted text clipped - 21 lines]
> >
> > Korstiaan