dmbonilla4
asked on
DC Replication and "The RPC server is not available"
Hello,
I am running Windows Server 2k3 SP1 on 6 DCs. I have two DNS servers and I am having problems with my Primary DNS server. When I open up the primary DNS in AD Sites and Services and "Replicate Now" with my other DNS server or any of the other DC's for that matter, I get the following error:
"The RPC server is not available."
I have check with the suggested links and cannot find a solution.
Also, when I run dcdiag /test:replications, I get the following error:
DC Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial non skippeable tests
Testing server: Default-First-Site-Name\DC
Starting test: Connectivity
MARS's server GUID DNS name could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
......................... DCName failed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\DC
Skipping all tests, because server DCName is
not responding to directory service requests
Running enterprise tests on : domain name
I am thinking that the two are related. Thanks in advance for any insight anyone could provide.
I am running Windows Server 2k3 SP1 on 6 DCs. I have two DNS servers and I am having problems with my Primary DNS server. When I open up the primary DNS in AD Sites and Services and "Replicate Now" with my other DNS server or any of the other DC's for that matter, I get the following error:
"The RPC server is not available."
I have check with the suggested links and cannot find a solution.
Also, when I run dcdiag /test:replications, I get the following error:
DC Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial non skippeable tests
Testing server: Default-First-Site-Name\DC
Starting test: Connectivity
MARS's server GUID DNS name could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
......................... DCName failed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\DC
Skipping all tests, because server DCName is
not responding to directory service requests
Running enterprise tests on : domain name
I am thinking that the two are related. Thanks in advance for any insight anyone could provide.
Mazaraat
How is the DNS service configured (integrated?) forwarders? how about the NIC properties primary DNS server? can you ping by name AND IP both from and to the server? Is the secondary DNS server forwarding to the primary?
what other errors are created in your event logs?
any idea how long this issue has been going on?
any idea how long this issue has been going on?
ASKER
Hopefully this will answer all the questions.
1. DNS service is AD intregrated and we are using two forwarders, (these are on our mother campus domain).
2. The primary DNS NIC properties have proper IP settings, our secondary DNS listed as its preferred DNS and one of the forwarders as the alternate. In the advanced properties it has 2 IP addresses listed and the one that is not assigned to the server, does not answer a ping. It has the secondary and the two forwarder dns servers listed under the DNS tab (should the primary be listed here as well?). Our domain suffix and the 2 from our mother campus are listed in "Append these DNS suffixes in order". We have a WINS server defined and no other options set.
3. Yes I can ping to and from the server using both IP and name.
4. Yes the secondary is forwarding to the primary.
Answering Jay Jay70.
There are no other errors in the DNS event logs and I don't know how long this has been going on. I am brand new to this shop.
Thanks.
1. DNS service is AD intregrated and we are using two forwarders, (these are on our mother campus domain).
2. The primary DNS NIC properties have proper IP settings, our secondary DNS listed as its preferred DNS and one of the forwarders as the alternate. In the advanced properties it has 2 IP addresses listed and the one that is not assigned to the server, does not answer a ping. It has the secondary and the two forwarder dns servers listed under the DNS tab (should the primary be listed here as well?). Our domain suffix and the 2 from our mother campus are listed in "Append these DNS suffixes in order". We have a WINS server defined and no other options set.
3. Yes I can ping to and from the server using both IP and name.
4. Yes the secondary is forwarding to the primary.
Answering Jay Jay70.
There are no other errors in the DNS event logs and I don't know how long this has been going on. I am brand new to this shop.
Thanks.
Primary DNS server config:
nic properties:
should have itself listed as the primary
service:
DNS service forwarders tab should list secondary DNS server and then ISP DNS servers....do not put the primary in the forwarders list.
--Remove any other DNS entries--
Secondary DNS server:
nic properties:
should have itself listed as the primary dns server
service:
DNS serivce forwarder tab should have the Primary DNS server listed
nic properties:
should have itself listed as the primary
service:
DNS service forwarders tab should list secondary DNS server and then ISP DNS servers....do not put the primary in the forwarders list.
--Remove any other DNS entries--
Secondary DNS server:
nic properties:
should have itself listed as the primary dns server
service:
DNS serivce forwarder tab should have the Primary DNS server listed
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Mazaraat,
Thank you, I am now getting replication to work between all of my DC's. After I made the suggested changed and also checked the box to register the connections address in DNS, I tried to run 'netdiag'. I get the following error:
The procedure entry point DnsGetPrimaryDomainName_UT
Any suggestions? Thanks you've earned every point.
Thank you, I am now getting replication to work between all of my DC's. After I made the suggested changed and also checked the box to register the connections address in DNS, I tried to run 'netdiag'. I get the following error:
The procedure entry point DnsGetPrimaryDomainName_UT
Any suggestions? Thanks you've earned every point.
Try running netdiag /fix let me know if you get error
ASKER
Yes,
I get the same error.
I get the same error.
Hmm I remember getting that error when I was usingth ewrong version of the utility, try installing netdiag from the CD (cdrom:\support\tools\setu
or download windows 2003 version from : http://www.computerperformance.co.uk/ScriptsGuy/netdiag.zip
or download windows 2003 version from : http://www.computerperformance.co.uk/ScriptsGuy/netdiag.zip
Link to download latest versions:
Resource kit:
http://www.microsoft.com/downloads/details.aspx?FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd&displaylang=en
support tools:
http://www.petri.co.il/software/win2003_support_tools.zip
It looks like windows 2003 resource kit doesn't include the newer version of netdiag.....go figure...
Resource kit:
http://www.microsoft.com/downloads/details.aspx?FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd&displaylang=en
support tools:
http://www.petri.co.il/software/win2003_support_tools.zip
It looks like windows 2003 resource kit doesn't include the newer version of netdiag.....go figure...