Re: RPC Traffic causing Domain Controller Synchronization issues
From: Dmox (anonymous_at_discussions.microsoft.com)
Date: 06/03/04
- Next message: satinder: "logon server"
- Previous message: Carlos Magalhaes: "Re: Duplicate user name suggestion"
- In reply to: Tim Hines [MSFT]: "Re: RPC Traffic causing Domain Controller Synchronization issues"
- Next in thread: Tim Hines [MSFT]: "Re: RPC Traffic causing Domain Controller Synchronization issues"
- Reply: Tim Hines [MSFT]: "Re: RPC Traffic causing Domain Controller Synchronization issues"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 3 Jun 2004 07:08:22 -0700
Thanks for your reply,
All servers have correctly registered their SRV records
in DNS. Except for the server in SiteB that isn't
included in the DomainDNSZones. Other than that, I can
ping and the FQDN is resolved correctly for every server
either way.
The DC's point to themselves for name resolution with
127.0.0.1. They are then using Forwarders to goto the
primary DNS server.
What action am I performing when RPC fails? I don't
understand the question. Could you please clarify? I'm
not really taking any action because I don't know what
else to do. I've restarted Services, the Server itself
and kicked the box. None of them worked. Are there any
other steps I need to take to troubleshoot/resolve RPC
errors?
>-----Original Message-----
>RPC errors usually indicate a name resolution issue.
How is DNS configured
>in your environment? Where do the DCs point for DNS?
What action are you
>performing when RPC fails? Verify that the DCs are
registering their SRV
>and guid records in DNS.
>
>--
>--
>Tim Hines, MCSE, MCSA
> Windows 2000 Directory Services
>
>=====================================================
>When responding to posts, please "Reply to Group" via
>your newsreader so that others may learn and benefit
>from your issue.
>=====================================================
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>
>
>
>"Dmox" <daryl.moxham@desire2learn.com> wrote in message
>news:1745601c448df$b2956aa0$a301280a@phx.gbl...
>> We've created a domain at our local site. We have
>> recently setup a remote site with a Site to Site VPN
and
>> have tried to make a sub domain there. However, we
>> cannot synchronize the domains. There are errors in
the
>> eventlog that are stating:
>>
>> AutoEnrollment.
>>
>> Automatic certificate enrollment for the local system
>> failed to enroll for one Domain Certificate. The
>> specified domain either does not exist or could not be
>> contacted.
>>
>> Aswell as other Errors that specify that RPC is having
an
>> issue connecting.
>>
>> Basically our home office (Which we'll call SiteA) is
>> trying to connect through a VPN to the Remote office
>> (We'll call SiteB). I have verified over and over
again
>> that the VPN is not filtering RPC traffic (Or any other
>> traffic for that matter).
>>
>> I have done a portqry -n <DC IP> -e 135 from SiteA and
it
>> fails to SiteB. However, if I do a portqry from SiteB
to
>> SiteA it works. If I do a portqry from another machine
>> on SiteB to the Domain controller it succeeds.
>>
>> I have tried to DCPromo the machine back down to a
member
>> server, but it fails due to an RPC Connection error. I
>> have tried changeing Sites and Services from RPC to IP
>> but that doesn't help either (I think no matter what is
>> chosen in Sites and Services some traffic is still sent
>> over RPC).
>>
>> Is there a W32Time issue that would cause RPC Traffic
to
>> fail? Or any other troubleshooting steps that I could
>> take to see what is causing the connection to fail?
Any
>> help would be greatly appreciated as I have exhausted
all
>> other options.
>
>
>.
>
- Next message: satinder: "logon server"
- Previous message: Carlos Magalhaes: "Re: Duplicate user name suggestion"
- In reply to: Tim Hines [MSFT]: "Re: RPC Traffic causing Domain Controller Synchronization issues"
- Next in thread: Tim Hines [MSFT]: "Re: RPC Traffic causing Domain Controller Synchronization issues"
- Reply: Tim Hines [MSFT]: "Re: RPC Traffic causing Domain Controller Synchronization issues"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|