esckeyrwm
asked on
DFS Replication error: RPC server is unavailable
Hello Experts,
I'm getting an RPC error when trying to setup the Replication service within DFS.
Here is the background of my enviornment:
All servers are Windows 2003 R2, including each DC
Two file servers are involved: File1 and File2
DFS Roots are setup on File1
One folder share (d:\shared) is being managed by Domain based DFS: \\my.domain.local\Public
I would like replication to occur between File1 and File2:
i.e.) \\my.domain.local\Public:
-- \\File1\shared
-- \\File2\shared
DFS and FRS services are enabled/installed on both File Servers
RPC and RPC Locator services are enabled/started on both File Servers
I can ping each file server from one another:
i.e.) >ping file1 <resolves to the correct IP address>
>ping file1.my.domain.local <resolves to the correct IP address>
also
>ping file2 <resolves to the correct IP address>
>ping file2.my.domain.local <resolves to the correct IP address>
I can also ping these servers from each DC as well as any client XP machine.
So here is the specific problem I am having.... When I go to setup a new DFS replication (within the DFS Management utility in Windows 2003 R2), I get an error message stating: "file1.my.domain.local: The service control manager cannot be opened. The RPC server is unavailable"
The actual DFS setup is working perfectly. It's just when I try to create a Replication group that I receive this errror and I'm not sure why. It seems like a DNS routing issue, but I can communicate between each server just fine (ping).
Any ideas?? Thanks!
500 points because it's pretty unique/difficult.
I'm getting an RPC error when trying to setup the Replication service within DFS.
Here is the background of my enviornment:
All servers are Windows 2003 R2, including each DC
Two file servers are involved: File1 and File2
DFS Roots are setup on File1
One folder share (d:\shared) is being managed by Domain based DFS: \\my.domain.local\Public
I would like replication to occur between File1 and File2:
i.e.) \\my.domain.local\Public:
-- \\File1\shared
-- \\File2\shared
DFS and FRS services are enabled/installed on both File Servers
RPC and RPC Locator services are enabled/started on both File Servers
I can ping each file server from one another:
i.e.) >ping file1 <resolves to the correct IP address>
>ping file1.my.domain.local <resolves to the correct IP address>
also
>ping file2 <resolves to the correct IP address>
>ping file2.my.domain.local <resolves to the correct IP address>
I can also ping these servers from each DC as well as any client XP machine.
So here is the specific problem I am having.... When I go to setup a new DFS replication (within the DFS Management utility in Windows 2003 R2), I get an error message stating: "file1.my.domain.local: The service control manager cannot be opened. The RPC server is unavailable"
The actual DFS setup is working perfectly. It's just when I try to create a Replication group that I receive this errror and I'm not sure why. It seems like a DNS routing issue, but I can communicate between each server just fine (ping).
Any ideas?? Thanks!
500 points because it's pretty unique/difficult.
ASKER
Yes - I was sure to run domainprep /forestprep and successfully updated the schema before I upgraded to R2. The eventlog is clear of any schema errors.
Thanks for tip... any other idears?
Thanks for tip... any other idears?
Its the old favourite but run netdiag and dcdiag and post any errors "i'm sure there " will be some. Where do the servers point for dns ? all to one server with a backup copy somewhere?
Try replmon from the support tools to get an overview of errors.
Post netdiag and dcdiag and eliminate that first
Try replmon from the support tools to get an overview of errors.
Post netdiag and dcdiag and eliminate that first
ASKER
DCdiag did not return any failures, however Netdiag did. I'm posting those failures below...
Netdiag:
Redir and Browser test . . . . . . : Failed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{FD4C2364-D6D6
The redir is bound to 1 NetBt transport.
List of NetBt transports currently bound to the browser
NetBT_Tcpip_{FD4C2364-D6D6
The browser is bound to 1 NetBt transport.
[FATAL] Cannot send mailslot message to '\\DC1*\MAILSLOT\NET\NETLO
[FATAL] Cannot send mailslot message to '\\AD*\MAILSLOT\NET\NETLOG
DC list test . . . . . . . . . . . : Failed
'DC1': Cannot find DC to get DC list from [test skipped].
LDAP test. . . . . . . . . . . . . : Failed
Cannot find DC to run LDAP tests on. The error occurred was: The specified domain either does not exist or could not be contacted.
This computer cannot be joined to the [adbdc3] domain because of one of the following reasons.
1. The DNS SRV record for [adbdc3] is not registered in DNS; or
2. A zone from the following list of DNS zones does not include delegationto its child zone.
Such zones can include [_ldap._tcp.dc._msdcs.adbd
Ask your network/DNS administrator to perform the following actions: To find out why the SRV record for [adbdc3] is not registered in the DNS, run the dcdiag command prompt tool with the command RegisterInDNS on the domain controller that did not perform the registration.
[WARNING] Cannot find DC in domain 'adbdc3'. [ERROR_NO_SUCH_DOMAIN]
Netdiag:
Redir and Browser test . . . . . . : Failed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{FD4C2364-D6D6
The redir is bound to 1 NetBt transport.
List of NetBt transports currently bound to the browser
NetBT_Tcpip_{FD4C2364-D6D6
The browser is bound to 1 NetBt transport.
[FATAL] Cannot send mailslot message to '\\DC1*\MAILSLOT\NET\NETLO
[FATAL] Cannot send mailslot message to '\\AD*\MAILSLOT\NET\NETLOG
DC list test . . . . . . . . . . . : Failed
'DC1': Cannot find DC to get DC list from [test skipped].
LDAP test. . . . . . . . . . . . . : Failed
Cannot find DC to run LDAP tests on. The error occurred was: The specified domain either does not exist or could not be contacted.
This computer cannot be joined to the [adbdc3] domain because of one of the following reasons.
1. The DNS SRV record for [adbdc3] is not registered in DNS; or
2. A zone from the following list of DNS zones does not include delegationto its child zone.
Such zones can include [_ldap._tcp.dc._msdcs.adbd
Ask your network/DNS administrator to perform the following actions: To find out why the SRV record for [adbdc3] is not registered in the DNS, run the dcdiag command prompt tool with the command RegisterInDNS on the domain controller that did not perform the registration.
[WARNING] Cannot find DC in domain 'adbdc3'. [ERROR_NO_SUCH_DOMAIN]
ASKER
I'm upping the point value because this seems to be a difficult problem...
Thanks!
Thanks!
ASKER
I've solved this issue by finding the following MS Support page:
http://support.microsoft.com/default.aspx?scid=kb;en-us;171386
The problem was that each client machine had multiple redirectors installed on our network, because we use both MS and Novell file sharing. The solution was simple - uninstall the Novell client on the effected clients or run the registry hack listed in the support page.
At any rate - the issue is now fixed.
Thanks!
http://support.microsoft.com/default.aspx?scid=kb;en-us;171386
The problem was that each client machine had multiple redirectors installed on our network, because we use both MS and Novell file sharing. The solution was simple - uninstall the Novell client on the effected clients or run the registry hack listed in the support page.
At any rate - the issue is now fixed.
Thanks!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Check the readme on the R2 disk, did you run a domainprep/forestprep schema update? R2 requires a schema update for DFS and doesnt do it for you automatically . You need to manually do it from the command line. R2 DFS wont work wihtout it. (the regular DFS will)
Check the DFS Replication eventlogs and see if you see any schema errors.
hth
RR