Re: Add a new DC to a new branch

Hi

Network Ports Used by Active Directory Replication
By default, RPC-based replication uses dynamic port mapping. When connecting
to an RPC endpoint during Active Directory replication, the RPC run time on
the client contacts the RPC endpoint mapper on the server at a well-known
port (port 135). The server queries the RPC endpoint mapper on this port to
determine what port has been assigned for Active Directory replication on
the server. This query occurs whether the port assignment is dynamic (the
default) or fixed. The client never needs to know which port to use for
Active Directory replication.

Note

. An endpoint comprises the protocol, local address, and port address.


In addition to the dynamic port 135, other ports that are required for
replication to occur are listed in the following table.

Port Assignments for Active Directory Replication

Service Name UDP TCP
LDAP
389
389

LDAP

636 (Secure Sockets Layer [SSL])

LDAP

3268 (global catalog)

Kerberos
88
88

DNS
53
53

SMB over IP
445
445


Replication within a domain also requires FRS using a dynamic RPC port.




--
I hop that helps


Good Luck
Jorge Silva
MCSA
Systems Administrator





"Manoj" <Manoj@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2FE4D94D-B151-4D8C-BFBF-A5E1B6413582@xxxxxxxxxxxxxxxx
Thanks for your prompt reply.

I tried to fix the event log overflow and after restarting my new DC gets
hung up at "Preparing network connections". How do I get past this. I am
not
able to do a safe boot either. Any ideas.

I have another new server that I connected to site 2 - the 192.168.2.0
network. After installing server 2003, I changed the TCP/IP settings to
point
to PDC/DNS 192.168.1.100 and tried to join this server to domain. I get an
error saying the _ldap._tcp.dc._msdcs.domainname.com not found.

When I run from this new member server
nslookup
set q = srv
_ldap._tcp.dc._msdcs.domainname.com

I get time out errors.

But when I go to my PDC and run nslookup, the SRV record is found ok.

I think this is my main problem that was blocking access to PDC in case of
first new server too.

Is there any port that needs to be opened for RPC traffic in DNS. My
routers
on either site do not block any of the RPC port 135. What else might be
blocking this traffic. Any way to debug this.

Thanks for your help.
Manoj


"Jorge Silva" wrote:


Hi

There is just a single IP site link that connects site 1 and site 2.
Isn't
that just what is needed. Since I do not have more than 2 sites, I
figure
I
do not need more than 1 site link or a site link bridge. Am I right ?
Please
confirm.

That's correct.

Yes there is a Revese lookup zone for the 192.168.2.0 subnet.
The netdiag /fix did not fix it.
At one point, I did not reboot the server after ipchange.

- if you run ipconfig /registerdns does the PTR record appears in Reverse
lookup zone 192.168.2.x subnet?
- How are showing the Active Directory Sites and Services, regarding to
the
new sites created and the moved DC, is the correct information refreshed
in
both DCs?
- If no, them reconfigure it in both DCs.
-Then in bothe DCs perform the following actions:
- delete the files netlogon.dnb and netlogon.dns from
%systemroot%\system32\config
- restart the netlogon service
- confirm the creation of the files
- run netdiag /fix
- Make sure that you can ping the server in the main office by FQDN or
any
other replication partners.
- Test replication

DCDIAG /D /V /C > DCDIAG.TXT
NETDIAG /V /DEBUG > NETDIAG.TXT
Open DCDIAG.TXT and NETDIAG.TXT and check for errors and if any
troubleshoot
them


Assuming that you're talking about network places or browsing by
\\computername , you'll need Wins in both subnets replicating with
each
other.


I was trying to browse by \\ip address. I think my WINS in both subnets
was
not replicating and that is what I am going to do next.

resolve that,make sure that both Wins are replicating with each other.
might need to change the replication partners that replicate with the
moved
DC for WINS, etc.
If you have DHCP you need to reauthorize it. Don't forget to remove the
old authorization.

Aditional information for needed ports:
Service overview and network port requirements for the Windows Server
system
http://support.microsoft.com/default.aspx?scid=kb;en-us;832017


I hop that helps

Good Luck
Jorge Silva
MCSA
Systems Administrator





.

Relevant Pages

  • Re: Intersite Replication problem
    ... As for RPC The default value for the RPC Replication Timeout registry ... from Windows 2000 to Windows Server 2003, the value for the RPC Replication ... Remote Procedure Call dynamic port allocation is used by remote ...
    (microsoft.public.windows.server.active_directory)
  • Re: Intersite Replication problem
    ... I followed Antony's DNS advise and I seens to be working. ... To perform the replication I've schedule a task on the W3K server to dial ... As for RPC The default value for the RPC Replication Timeout registry ... Remote Procedure Call dynamic port allocation is used by remote ...
    (microsoft.public.windows.server.active_directory)
  • Re: Add a new DC to a new branch
    ... Systems Administrator ... have a Dell PowerEdge 2850 server. ... PortQryUI - User Interface for the PortQry Command Line Port ... RPC-based replication uses dynamic port mapping. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Add a new DC to a new branch
    ... pressing F8 at boot up, but it does not do anything and boots normally. ... have a Dell PowerEdge 2850 server. ... PortQryUI - User Interface for the PortQry Command Line Port Scanner ... RPC-based replication uses dynamic port mapping. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Add a new DC to a new branch
    ... PortQryUI - User Interface for the PortQry Command Line Port Scanner ... RPC-based replication uses dynamic port mapping. ... connecting to an RPC endpoint during Active Directory replication, ... The server queries the RPC endpoint mapper ...
    (microsoft.public.windows.server.active_directory)
Loading