PC Review


Reply
Thread Tools Rate Thread

Cannot add new DC

 
 
Alvin
Guest
Posts: n/a
 
      15th Apr 2004
Hi,

While creating a child domain, I get to the point where it start to
configure AD and I get this error message:

The operaton failed because: failed finding a suitable domain controller for
the domain xxx.yyy.zzz

The specified domain either does not exist or could not be contacted.


Anyone have any idea whats going on? MSKB 257623 says this can be caused by
the Domain Controller's Domain Name System Suffix Does Not Match Domain
Name. They do match and I ran the tool to fix it anyway, and I still get
this error message.

Thanks for any help!
Alvin


 
Reply With Quote
 
 
 
 
Dusty Harper {MS}
Guest
Posts: n/a
 
      15th Apr 2004
Are you able to reach the DC's? When you do an NSLookup against the domain
name, do you get valid IPs returned? can you reach each of these IPs?


--
--
Dusty Harper
Microsoft Corporation
----------------------------------------------------------------------------
This posting is provided "AS IS", with NO warranties and confers NO rights
----------------------------------------------------------------------------

"Alvin" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi,
>
> While creating a child domain, I get to the point where it start to
> configure AD and I get this error message:
>
> The operaton failed because: failed finding a suitable domain controller

for
> the domain xxx.yyy.zzz
>
> The specified domain either does not exist or could not be contacted.
>
>
> Anyone have any idea whats going on? MSKB 257623 says this can be caused

by
> the Domain Controller's Domain Name System Suffix Does Not Match Domain
> Name. They do match and I ran the tool to fix it anyway, and I still get
> this error message.
>
> Thanks for any help!
> Alvin
>
>



 
Reply With Quote
 
Alvin
Guest
Posts: n/a
 
      15th Apr 2004
I have WINS running and replicating between the DC in the root and the
member server in the (to-be) child domain. I can ping both IP addresses, and
netbios names. I can reach the workstations in the root domain from the
member server. I added WINS to make sure I could resolve both names and
addresses. It did help with resolution but not with the problem.

Alvin


"Dusty Harper {MS}" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Are you able to reach the DC's? When you do an NSLookup against the

domain
> name, do you get valid IPs returned? can you reach each of these IPs?
>
>
> --
> --
> Dusty Harper
> Microsoft Corporation
> --------------------------------------------------------------------------

--
> This posting is provided "AS IS", with NO warranties and confers NO rights
> --------------------------------------------------------------------------

--
>
> "Alvin" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > Hi,
> >
> > While creating a child domain, I get to the point where it start to
> > configure AD and I get this error message:
> >
> > The operaton failed because: failed finding a suitable domain controller

> for
> > the domain xxx.yyy.zzz
> >
> > The specified domain either does not exist or could not be contacted.
> >
> >
> > Anyone have any idea whats going on? MSKB 257623 says this can be

caused
> by
> > the Domain Controller's Domain Name System Suffix Does Not Match Domain
> > Name. They do match and I ran the tool to fix it anyway, and I still get
> > this error message.
> >
> > Thanks for any help!
> > Alvin
> >
> >

>
>



 
Reply With Quote
 
Dusty Harper {MS}
Guest
Posts: n/a
 
      15th Apr 2004
DNS is what is being searched. Verify that NSLookup returns the proper IPs
--
--
Dusty Harper
Microsoft Corporation
----------------------------------------------------------------------------
This posting is provided "AS IS", with NO warranties and confers NO rights
----------------------------------------------------------------------------

"Alvin" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I have WINS running and replicating between the DC in the root and the
> member server in the (to-be) child domain. I can ping both IP addresses,

and
> netbios names. I can reach the workstations in the root domain from the
> member server. I added WINS to make sure I could resolve both names and
> addresses. It did help with resolution but not with the problem.
>
> Alvin
>
>
> "Dusty Harper {MS}" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
> > Are you able to reach the DC's? When you do an NSLookup against the

> domain
> > name, do you get valid IPs returned? can you reach each of these IPs?
> >
> >
> > --
> > --
> > Dusty Harper
> > Microsoft Corporation

>
> --------------------------------------------------------------------------
> --
> > This posting is provided "AS IS", with NO warranties and confers NO

rights
>
> --------------------------------------------------------------------------
> --
> >
> > "Alvin" <(E-Mail Removed)> wrote in message
> > news:(E-Mail Removed)...
> > > Hi,
> > >
> > > While creating a child domain, I get to the point where it start to
> > > configure AD and I get this error message:
> > >
> > > The operaton failed because: failed finding a suitable domain

controller
> > for
> > > the domain xxx.yyy.zzz
> > >
> > > The specified domain either does not exist or could not be contacted.
> > >
> > >
> > > Anyone have any idea whats going on? MSKB 257623 says this can be

> caused
> > by
> > > the Domain Controller's Domain Name System Suffix Does Not Match

Domain
> > > Name. They do match and I ran the tool to fix it anyway, and I still

get
> > > this error message.
> > >
> > > Thanks for any help!
> > > Alvin
> > >
> > >

> >
> >

>
>



 
Reply With Quote
 
Alvin
Guest
Posts: n/a
 
      16th Apr 2004
NSLookup ran from the member server doesn't find DNS.


"Dusty Harper {MS}" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> DNS is what is being searched. Verify that NSLookup returns the proper

IPs
> --
> --
> Dusty Harper
> Microsoft Corporation
> --------------------------------------------------------------------------

--
> This posting is provided "AS IS", with NO warranties and confers NO rights
> --------------------------------------------------------------------------

--
>
> "Alvin" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > I have WINS running and replicating between the DC in the root and the
> > member server in the (to-be) child domain. I can ping both IP addresses,

> and
> > netbios names. I can reach the workstations in the root domain from the
> > member server. I added WINS to make sure I could resolve both names and
> > addresses. It did help with resolution but not with the problem.
> >
> > Alvin
> >
> >
> > "Dusty Harper {MS}" <(E-Mail Removed)> wrote in message
> > news:%(E-Mail Removed)...
> > > Are you able to reach the DC's? When you do an NSLookup against the

> > domain
> > > name, do you get valid IPs returned? can you reach each of these IPs?
> > >
> > >
> > > --
> > > --
> > > Dusty Harper
> > > Microsoft Corporation

> >

>
> --------------------------------------------------------------------------
> > --
> > > This posting is provided "AS IS", with NO warranties and confers NO

> rights
> >

>
> --------------------------------------------------------------------------
> > --
> > >
> > > "Alvin" <(E-Mail Removed)> wrote in message
> > > news:(E-Mail Removed)...
> > > > Hi,
> > > >
> > > > While creating a child domain, I get to the point where it start to
> > > > configure AD and I get this error message:
> > > >
> > > > The operaton failed because: failed finding a suitable domain

> controller
> > > for
> > > > the domain xxx.yyy.zzz
> > > >
> > > > The specified domain either does not exist or could not be

contacted.
> > > >
> > > >
> > > > Anyone have any idea whats going on? MSKB 257623 says this can be

> > caused
> > > by
> > > > the Domain Controller's Domain Name System Suffix Does Not Match

> Domain
> > > > Name. They do match and I ran the tool to fix it anyway, and I still

> get
> > > > this error message.
> > > >
> > > > Thanks for any help!
> > > > Alvin
> > > >
> > > >
> > >
> > >

> >
> >

>
>



 
Reply With Quote
 
Dusty Harper {MS}
Guest
Posts: n/a
 
      16th Apr 2004
In you IPConfig, you need to have the DNSServers for your Domain listed.
You can verify which ones have the name you are trying to resolve by
changing the server.

i.e

C:\>nslookup
Default Server: DC.Domain.com
Address: 192.168.0.1

> MachineName

Default Server: DC.Domain.com
Address: 192.168.0.1

Name: MachineName.Domain.com
Address: 192.168.0.5
>Server DC2.Domain.com

Default Server: DC2.Domain.com
Address: 192.168.0.2

The machine needs to find the DNS entries, so point its DNS to those servers
that can resolve the domain name.

--
--
Dusty Harper
Microsoft Corporation
----------------------------------------------------------------------------
This posting is provided "AS IS", with NO warranties and confers NO rights
----------------------------------------------------------------------------

"Alvin" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> NSLookup ran from the member server doesn't find DNS.
>
>
> "Dusty Harper {MS}" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > DNS is what is being searched. Verify that NSLookup returns the proper

> IPs
> > --
> > --
> > Dusty Harper
> > Microsoft Corporation

>
> --------------------------------------------------------------------------
> --
> > This posting is provided "AS IS", with NO warranties and confers NO

rights
>
> --------------------------------------------------------------------------
> --
> >
> > "Alvin" <(E-Mail Removed)> wrote in message
> > news:(E-Mail Removed)...
> > > I have WINS running and replicating between the DC in the root and the
> > > member server in the (to-be) child domain. I can ping both IP

addresses,
> > and
> > > netbios names. I can reach the workstations in the root domain from

the
> > > member server. I added WINS to make sure I could resolve both names

and
> > > addresses. It did help with resolution but not with the problem.
> > >
> > > Alvin
> > >
> > >
> > > "Dusty Harper {MS}" <(E-Mail Removed)> wrote in message
> > > news:%(E-Mail Removed)...
> > > > Are you able to reach the DC's? When you do an NSLookup against the
> > > domain
> > > > name, do you get valid IPs returned? can you reach each of these

IPs?
> > > >
> > > >
> > > > --
> > > > --
> > > > Dusty Harper
> > > > Microsoft Corporation
> > >

> >

>
> --------------------------------------------------------------------------
> > > --
> > > > This posting is provided "AS IS", with NO warranties and confers NO

> > rights
> > >

> >

>
> --------------------------------------------------------------------------
> > > --
> > > >
> > > > "Alvin" <(E-Mail Removed)> wrote in message
> > > > news:(E-Mail Removed)...
> > > > > Hi,
> > > > >
> > > > > While creating a child domain, I get to the point where it start

to
> > > > > configure AD and I get this error message:
> > > > >
> > > > > The operaton failed because: failed finding a suitable domain

> > controller
> > > > for
> > > > > the domain xxx.yyy.zzz
> > > > >
> > > > > The specified domain either does not exist or could not be

> contacted.
> > > > >
> > > > >
> > > > > Anyone have any idea whats going on? MSKB 257623 says this can be
> > > caused
> > > > by
> > > > > the Domain Controller's Domain Name System Suffix Does Not Match

> > Domain
> > > > > Name. They do match and I ran the tool to fix it anyway, and I

still
> > get
> > > > > this error message.
> > > > >
> > > > > Thanks for any help!
> > > > > Alvin
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >

> >
> >

>
>



 
Reply With Quote
 
Alvin
Guest
Posts: n/a
 
      17th Apr 2004
Here is my output from NSlookup:

***Default servers are not available
Default Server: Unknown
Address: 127.0.0.1

If I add the IP address of the DNS in the root, to the member server in the
child domain, I can run dcpromo. What I was trying to do was let Windows
create a DNS server in the child domain during dcpromo. I also tried
creating DNS manually on the member server, configure it with the IP
address, and ran dcpromo, but I still get an error mesage that it cannot
find a suitable DC in the root. It only works if I configure the member
server with the IP address of the DNS server in the root. Why is that?

Thanks,
Alvin



"Dusty Harper {MS}" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> In you IPConfig, you need to have the DNSServers for your Domain listed.
> You can verify which ones have the name you are trying to resolve by
> changing the server.
>
> i.e
>
> C:\>nslookup
> Default Server: DC.Domain.com
> Address: 192.168.0.1
>
> > MachineName

> Default Server: DC.Domain.com
> Address: 192.168.0.1
>
> Name: MachineName.Domain.com
> Address: 192.168.0.5
> >Server DC2.Domain.com

> Default Server: DC2.Domain.com
> Address: 192.168.0.2
>
> The machine needs to find the DNS entries, so point its DNS to those

servers
> that can resolve the domain name.
>
> --
> --
> Dusty Harper
> Microsoft Corporation
> --------------------------------------------------------------------------

--
> This posting is provided "AS IS", with NO warranties and confers NO rights
> --------------------------------------------------------------------------

--
>
> "Alvin" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > NSLookup ran from the member server doesn't find DNS.
> >
> >
> > "Dusty Harper {MS}" <(E-Mail Removed)> wrote in message
> > news:(E-Mail Removed)...
> > > DNS is what is being searched. Verify that NSLookup returns the

proper
> > IPs
> > > --
> > > --
> > > Dusty Harper
> > > Microsoft Corporation

> >

>
> --------------------------------------------------------------------------
> > --
> > > This posting is provided "AS IS", with NO warranties and confers NO

> rights
> >

>
> --------------------------------------------------------------------------
> > --
> > >
> > > "Alvin" <(E-Mail Removed)> wrote in message
> > > news:(E-Mail Removed)...
> > > > I have WINS running and replicating between the DC in the root and

the
> > > > member server in the (to-be) child domain. I can ping both IP

> addresses,
> > > and
> > > > netbios names. I can reach the workstations in the root domain from

> the
> > > > member server. I added WINS to make sure I could resolve both names

> and
> > > > addresses. It did help with resolution but not with the problem.
> > > >
> > > > Alvin
> > > >
> > > >
> > > > "Dusty Harper {MS}" <(E-Mail Removed)> wrote in message
> > > > news:%(E-Mail Removed)...
> > > > > Are you able to reach the DC's? When you do an NSLookup against

the
> > > > domain
> > > > > name, do you get valid IPs returned? can you reach each of these

> IPs?
> > > > >
> > > > >
> > > > > --
> > > > > --
> > > > > Dusty Harper
> > > > > Microsoft Corporation
> > > >
> > >

> >

>
> --------------------------------------------------------------------------
> > > > --
> > > > > This posting is provided "AS IS", with NO warranties and confers

NO
> > > rights
> > > >
> > >

> >

>
> --------------------------------------------------------------------------
> > > > --
> > > > >
> > > > > "Alvin" <(E-Mail Removed)> wrote in message
> > > > > news:(E-Mail Removed)...
> > > > > > Hi,
> > > > > >
> > > > > > While creating a child domain, I get to the point where it start

> to
> > > > > > configure AD and I get this error message:
> > > > > >
> > > > > > The operaton failed because: failed finding a suitable domain
> > > controller
> > > > > for
> > > > > > the domain xxx.yyy.zzz
> > > > > >
> > > > > > The specified domain either does not exist or could not be

> > contacted.
> > > > > >
> > > > > >
> > > > > > Anyone have any idea whats going on? MSKB 257623 says this can

be
> > > > caused
> > > > > by
> > > > > > the Domain Controller's Domain Name System Suffix Does Not Match
> > > Domain
> > > > > > Name. They do match and I ran the tool to fix it anyway, and I

> still
> > > get
> > > > > > this error message.
> > > > > >
> > > > > > Thanks for any help!
> > > > > > Alvin
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >

> >
> >

>
>



 
Reply With Quote
 
 
 
Reply

Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off



Features
 

Advertising
 

Newsgroups
 


All times are GMT +1. The time now is 02:44 AM.