Re: New Server problem with AD

Tech-Archive recommends: Speed Up your PC by fixing your registry

anonymous_at_discussions.microsoft.com
Date: 03/04/04 

Date: Thu, 4 Mar 2004 00:47:23 -0800

>-----Original Message-----
>| John,
>|
>| Is the new server pointing to the internal DNS Server (
probably one of
>the
>| existing DCs )? This would be in the TCP/IP settings.
If it is not ( or,
>| worse, pointing to the ISP's DNS Server ) go ahead and
add it / change it.
>|
>| Does this help you?
>|
>| Cary
>|
>| "John H" <john.headley@stroudhigh.gloucs.sch.uk> wrote
in message
>| news:633d01c40134$ed98fc90$a401280a@phx.gbl...
>| > Just adding a new server to domain and when using the
AD
>| > wizard while adding server as 'Additional domain
>| > controller for existing domain' get the following
error
>| > message after it has found domain 'The operation
failed
>| > because : Failed to find a suitabled domain
controller for
>| > the domain. The specified domain either does not
exist or
>| > could not be contacted.'
>| > Everything else is fine, server is seen by DC and can
see
>| > DC and everyone else.
>| >
>| > Please help.
>|
>|
>|
>
>To follow up with Cary, you need to make sure both DC's
are only pointing
>to the internal DNS server. They should never point to
the ISP's DNS
>server. The ISP's DNS needs to be added as a forwarder.
Once they are both
>pointing to the internal DNS server, make sure the first
DC is registering
>its SRV record. You will find this in DNS under the
forward lookup zone.
>Expand the domain and under it will be an _MCDSC folder.
In there you will
>find the SRV records for all DC's in the domain. This is
what the newly
>promoted DC will be looking for in order to locate
another DC to replicate
>with.
>
>Chad A. Lacy
>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.
>
>.
>

Chad

Thanks for the help.
The new DC was pointing at the internal DNS but the old DC
was pointing to the ISP DNS in networking and forwarders,
once I changed it as you suggested it worked like a charm.

Thanks again

John Headley

Relevant Pages

  • Re: Slow connectivity on web
    ... then u should have read that you should NEVER put ANY DNS Entry on ... your Internal DNS Server to forward requests. ... MVP -- ISA Firewalls ... "Daniel" wrote: ...
    (microsoft.public.isa)
  • Re: Cannot access admin share
    ... most likely an AUTHENTICATION problem. ... First goal is to prove authentication, and along with it correct DNS ... What happens if you map the drive explicitly with an Admin ... Ensure that every computer uses STRICTLY the internal DNS server ...
    (microsoft.public.windows.server.general)
  • RE: Securing DNS Server
    ... Unless this DMZ DNS system will provide name lookups for public clients, ... Subject: Securing DNS Server ... However the internal DNS server has the DMZ DNS server as its ...
    (Security-Basics)
  • Re: Adding domain users to local Administrator group
    ... Thanks for the update Brad. ... I have created A records in our internal DNS server that point to ...
    (microsoft.public.windowsxp.security_admin)
  • Re: RPC server Unavailable joining domain
    ... Where is the remote box pointing for DNS? ... Suffix setup? ... If you have both the internal DNS server and a public one defined, ...
    (microsoft.public.windows.server.active_directory)