Firewall ports to join a domain (RPC)
hi
we have following scenario in 1 of our customer network (see picture below) and havent been able find detailed information these questions have. think have found of needed ports able succed there still som concerns dynamic rpc ports. perhaps customer have change design because firewall need lot of openings.
questions
1a. able join server or client domain ports need opened if dc located behind firewall?
b. also need dynamic rpc actiion?
2 able run different administration tools active directory user , computers need enable dynamic rpc?
3. if domain mode in windows 2003 correct rpc port have in scope of 1025-5000 default? know might possible change scope
regards
thomas z
-------------------------------------------------------------------------------------------------------------
thomas z
hi,
http://support.microsoft.com/kb/832017 shows windows services , related ports.
http://support.microsoft.com/kb/179442 shows rpc requirements specific domains.
in short, these protocols , ports absolutely need separate clients , dc's:
dns (53/tcp , 53/udp)
kerberos-adm (749/udp)
kerberos-sec (88/tcp)
kerberos-sec (88/udp)
ldap (389/tcp)
ldap udp (389/udp)
ldap gc (global catalog) (3268/tcp)
microsoft cifs (tcp) (445/tcp)
microsoft cifs (udp) (445/udp)
ntp (udp) (123/udp)
ping (icmp type 8)
rpc (135/tcp) + dynamic range
note xp/2003 need able ping dc slow link detection, otherwise applying gpo might fail.
i don't know exact requirements requirements aduc, i'm sure relies on rpc. connect dc
the default dynamic range windows upto 2003 1025->5000, 2008 , 49152->65535. can change (and in opinion recommended if insist traversing firewall). http://support.microsoft.com/kb/154596, http://support.microsoft.com/kb/224196
mcp/mcsa/mcts/mcitp
Windows Server > Security
Comments
Post a Comment