Re: IPSEC Policy to secure TS

From: Chris (firenet@optonline.net)
Date: 02/19/03


From: "Chris" <firenet@optonline.net>
Date: Wed, 19 Feb 2003 09:26:50 -0800


Thanks for responding!

The computers are not in the same network. This is for
computers accessing the TS from across the internet.

Chris

>-----Original Message-----
>Oops wrong KB. --- Steve
>
>http://support.microsoft.com/default.aspx?scid=kb;EN-
US;254949
>
>"Steven L Umbach" <n9rou@attbi.com> wrote in message
>news:Y_N4a.165146$iG3.19368@sccrnsc02...
>> Hi Chris. Are the computers in the same forest??
If not Kerberos
>> authentication will not work. If you are using a
secure server required
>> policy, try server request policy to see if that will
at least work and
>> troubleshoot from there using ipsecmon, ping, etc. Try
connecting to the
>> Terminal Server by tcp/ip address instead of name if
you have not tried
>that
>> yet. You may need to add a rule to your policy to
exempt ipsec traffic
>> to/from a domain controller per KB254728.. --- Steve
>>
>> http://support.microsoft.com/?kbid=254728
>>
>> "Chris" <firenet@optonline.net> wrote in message
>> news:093d01c2d7cc$2b976ec0$3301280a@phx.gbl...
>> > Hello,
>> > I created an IPSEC filter list to match Terminal
Service
>> > packet, created an IPSec Policy to enforce
protection and
>> > then I enabled the policy. I did all according to
the MS
>> > article 315055. But, now my Windows XP RDP client
can no
>> > longer connect to the Terminal Server on Port 3389.
Does
>> > anyone know what the problem could be? Many Thanks,
>> >
>> > Chris
>>
>>
>
>
>.
>