Re: IP IPSEC Policy blocking ping
- From: "Steven L Umbach" <n9rou@xxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 23 Mar 2006 17:38:57 -0600
The link below may help and be sure to read the link in the article on
dynamic RPC and how you can do a registry mod to limit the ports that it
uses. Keep in mind that you can not use ipsec between domain members and
domain controllers if you are using an Active Directory domain. If you are
not going through firewalls then it usually is best to configure ipsec to be
used for all traffic between computers and will greatly simplify and rules.
If you are going through firewalls consider using a VPN connection through
the firewall and then you can use ipsec between the VPN server and end
computer if need be. --- Steve
http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B179442
http://support.microsoft.com/?kbid=254949 --- ipsec considerations for
domain computers
"Zakir" <ZakirD@xxxxxxxxx> wrote in message
news:1143147576.550521.144830@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Another question: from what I am reading, NTLM authentication seems to
use a random port? Is this true? Is there a way to allow it through
IPSEC or do I need to set it to a static port in the registry first?
.
- Follow-Ups:
- Re: IP IPSEC Policy blocking ping
- From: Zakir
- Re: IP IPSEC Policy blocking ping
- References:
- IP IPSEC Policy blocking ping
- From: Zakir
- Re: IP IPSEC Policy blocking ping
- From: Steven L Umbach
- Re: IP IPSEC Policy blocking ping
- From: Zakir
- Re: IP IPSEC Policy blocking ping
- From: Zakir
- IP IPSEC Policy blocking ping
- Prev by Date: Re: Backing up
- Next by Date: Re: IPSEC PolicyAgent Service failure on first boot of new server
- Previous by thread: Re: IP IPSEC Policy blocking ping
- Next by thread: Re: IP IPSEC Policy blocking ping
- Index(es):
Relevant Pages
|