Announcement

Collapse
No announcement yet.

IPSec for Terminal Service via ISA Server

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • IPSec for Terminal Service via ISA Server

    Hi all,

    Have you tried using IPSec for Terminal Service via ISA Server ?

    I published Terminal Server and the all Terminal Client ( external & internal ) could connect. Then I tried using IPSec with Shared Key on Terminal Server.

    In internal network, all Terminal Clients using IPSec with the same Shared Key as Terminal Server could remote OK without problem. All Terminal Clients not using IPSec couldn't make the remote connection.

    On external network ( internet ), I configured a Terminal Client to use IPSec but couldn't connect to the Terminal Server. In the log on ISA Server, I saw there're many IKE protocol with port 500 were denied. I tried to create a new Server rule which allow IKE Server protocol. And then, could make the remote connection.

    Yet, when remove IPSec from the Terminal Client, could still make the remote connection.
    Disable or Remove the rule has just been created, could still connect ?????

    Please help me .....

    Thanks
    Love in vain is better than love no one.

  • #2
    Re: IPSec for Terminal Service via ISA Server

    Did you tried to publish the TS as VPN server?

    http://www.microsoft.com/technet/pro...PNservers.mspx
    Best Regards,

    Yuval Sinay

    LinkedIn: https://www.linkedin.com/in/yuval14, Blog: http://blogs.microsoft.co.il/blogs/yuval14

    Comment


    • #3
      Re: IPSec for Terminal Service via ISA Server

      create a rule to allow terminal services to the terminal server from the external network to the TS server (create computer) on the isa server

      Comment

      Working...
      X