Re: clients separated from DC by firewall
- From: "Jay" <jay@xxxxxxxxxx>
- Date: Fri, 8 Jun 2007 09:15:13 -0400
Thanks, Svyatoslav
I am aware of the tcp/udp, I was just trying to be brief :)
Just wondering - can this be done in a simpler way? Is Ipsec a better option?
"S. Pidgorny <MVP>" <slavickp@xxxxxxxxx> wrote in message news:OaVgnHbqHHA.1208@xxxxxxxxxxxxxxxxxxxxxxx
What is missing:
* RPC endpoint mapper (135/TCP) + a fixable (http://support.microsoft.com/kb/224196/) port for login services
* LDAP to GC (3268/TCP)
* ICMP ping
Note that Kerberos is UDP by default and LDAP is using both TCP and UDP (UDP = LDAP ping); DNS also may use TCP. Protocols are important. SSL may change port requirements, too. See http://support.microsoft.com/kb/832017/
--
Svyatoslav Pidgorny, MS MVP - Security, MCSE
-= F1 is the key =-
* http://sl.mvps.org * http://msmvps.com/blogs/sp *
"Jay" <jay@xxxxxxxxxx> wrote in message news:uZO$1nUqHHA.4100@xxxxxxxxxxxxxxxxxxxxxxxstraightforward question - I have a range of PCs that are separated from their domain controller by a PIX. I need to know what ports are required for me to join these clients to the domain.
the doc 'Active Directory in Networks Segmented by Firewalls' leads me to believe I need:
445 (DS)
88 (Kerberos)
389 (LDAP)
53 (DNS)
assume both TCP and UDP for the above. The problem is I am getting and RPC error and I see 135 being dropped by my PIX. What are the ports needed to join a computer to a domain?
Is there a 'right' way to do this?
Thanks
Blake
.
- References:
- clients separated from DC by firewall
- From: Jay
- clients separated from DC by firewall
- Prev by Date: Re: clients separated from DC by firewall
- Next by Date: Re: Remote desktop: cannot copy files why
- Previous by thread: Re: clients separated from DC by firewall
- Next by thread: Re: clients separated from DC by firewall
- Index(es):
Relevant Pages
|
|