Re: Testing RPC connectivity
- From: "Herb Martin" <news@xxxxxxxxxxxxxx>
- Date: Sun, 26 Jun 2005 15:41:43 -0500
I don't see any evidence of DNS problems in your DCDiag excerpt
below but most such problems are related to DNS.
I would go through the DNS checklist to make sure since it is so
common....
DNS for AD
1) Dynamic for the zone supporting AD
2) All internal DNS clients NIC\IP properties must specify SOLELY
that internal, dynamic DNS server (set.)
3) DCs and even DNS servers are DNS clients too -- see #2
4) If you have more than one Domain, every DNS server must
be able to resolve ALL domains (either directly or indirectly)
netdiag /fix
....or maybe:
dcdiag /fix
(Win2003 can do this from Support tools):
nltest /dsregdns /server:DC-ServerNameGoesHere
http://support.microsoft.com/kb/q260371/
Ensure that DNS zones/domains are fully replicated to all DNS
servers for that (internal) zone/domain.
Also useful may be running DCDiag on each DC, sending the
output to a text file, and searching for FAIL, ERROR, WARN.
Single Label domain zone names are a problem Google:
[ "SINGLE LABEL" domain names DNS 2000 | 2003 microsoft: ]
--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]
"Mr.B" <MrB@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3ED1D9CE-DA8B-4F19-B318-9D49EC644FE3@xxxxxxxxxxxxxxxx
> I would like to test RPC connectivity. If I tried RPC ping every test when
i
> use tcp, connect without problem in both direction. But I with the
programs
> that heavily relay on RPC do not connect, and i get error RPC is
unaveable.
> The problem with RPC is getting worse.
> I `m getting problems with replication with domains, and I use dcdiag and
I
> get the following errors:
> ________________________________________________________________________
> Starting test: KnowsOfRoleHolders
> Role Schema Owner = CN=NTDS
>
Settings,CN=ROOTDC,CN=Servers,CN=Remote-site,CN=Sites,CN=Configuration,DC=Ro
ot-domain,DC=local
> [ROOTDC] DsBind() failed with error 1722,
> Win32 Error 1722.
> Warning: ROOTDC is the Schema Owner, but is not responding to DS
> RPC Bind.
> [ROOTDC] LDAP connection failed with error 58,
> Win32 Error 58.
> Warning: ROOTDC is the Schema Owner, but is not responding to
LDAP
> Bind.
> Role Domain Owner = CN=NTDS
>
Settings,CN=ROOTDC,CN=Servers,CN=Remote-site,CN=Sites,CN=Configuration,DC=Ro
ot-domain,DC=local
> Warning: ROOTDC is the Domain Owner, but is not responding to DS
> RPC Bind.
> Warning: ROOTDC is the Domain Owner, but is not responding to
LDAP
> Bind.
> Role PDC Owner = CN=NTDS
>
Settings,CN=PRS04,CN=Servers,CN=Root-domain-Remote-DomainSite,CN=Sites,CN=Co
nfiguration,DC=Root-domain,DC=local
> Role Rid Owner = CN=NTDS
>
Settings,CN=REMOTEDOMAINDC,CN=Servers,CN=Root-domain-Remote-DomainSite,CN=Si
tes,CN=Configuration,DC=Root-domain,DC=local
> Role Infrastructure Update Owner = CN=NTDS
>
Settings,CN=REMOTEDOMAINDC,CN=Servers,CN=Root-domain-Remote-DomainSite,CN=Si
tes,CN=Configuration,DC=Root-domain,DC=local
> ......................... REMOTEDOMAINDC failed test
> KnowsOfRoleHolders
> ________________________________________________________________________
>
> And I thing these is connected with problem, that these Remote DC can not
> find GC in same site.
>
.
- References:
- Testing RPC connectivity
- From: Mr.B
- Testing RPC connectivity
- Prev by Date: Testing RPC connectivity
- Next by Date: Re: DNS-Urgent-Help -Please
- Previous by thread: Testing RPC connectivity
- Index(es):
Relevant Pages
|
