Adding New DC to Server 2003 can't Authenticate.

With an existing, and working, Server 2003 domain, I've added a new box
running the same version, Server 2003 Standard Edition.

The box joined the domain just fine, and added AD. It shows up in the
Domain Controller container of the AD Users & Groups, the users and
everything replicated. I've even moved over all 5 schema, etc roles to the
new box.

When the original DC is powered down, the new DC will not authenticate users
or computers on the network. Everything acts like there is no DC available,
altho everything says it's working.

I've got to get this box up and running, so I can take down the original and
reinstall with new drives.

it could be the DNS issues. Where is the DNS? You may want to use nslookup check the DNS status. or these Microsoft articles,
MS DNS How to
Troubleshooting DNS

Don't send e-mail or reply to me except you need consulting services. Posting on MS newsgroup will benefit all readers and you may get more help.

Bob Lin, MS-MVP, MCSE & CNE
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.

"Bryan Britt, Beltane" <Bryan Britt, (E-Mail Removed)> wrote in message news:278413AF-6908-46AB-95A7-(E-Mail Removed)...
With an existing, and working, Server 2003 domain, I've added a new box
running the same version, Server 2003 Standard Edition.

The box joined the domain just fine, and added AD. It shows up in the
Domain Controller container of the AD Users & Groups, the users and
everything replicated. I've even moved over all 5 schema, etc roles to the
new box.

When the original DC is powered down, the new DC will not authenticate users
or computers on the network. Everything acts like there is no DC available,
altho everything says it's working.

I've got to get this box up and running, so I can take down the original and
reinstall with new drives.

It also needs to have a copy of the Global Catalog.

Robert L [MS-MVP] wrote:
> it could be the DNS issues. Where is the DNS? You may want to use
> nslookup check the DNS status. or these Microsoft articles,
> MS DNS How to
> Troubleshooting DNS
>
> Don't send e-mail or reply to me except you need consulting services.
> Posting on MS newsgroup will benefit all readers and you may get more
> help.
>
> Bob Lin, MS-MVP, MCSE & CNE
> How to Setup Windows, Network, VPN & Remote Access on
> http://www.HowToNetworking.com
> Networking, Internet, Routing, VPN Troubleshooting on
> http://www.ChicagoTech.net
> This posting is provided "AS IS" with no warranties.
>
> "Bryan Britt, Beltane" <Bryan Britt,
> (E-Mail Removed)> wrote in message
> news:278413AF-6908-46AB-95A7-(E-Mail Removed)...
> With an existing, and working, Server 2003 domain, I've added a new
> box
> running the same version, Server 2003 Standard Edition.
>
> The box joined the domain just fine, and added AD. It shows up in
> the
> Domain Controller container of the AD Users & Groups, the users and
> everything replicated. I've even moved over all 5 schema, etc
> roles to the
> new box.
>
> When the original DC is powered down, the new DC will not
> authenticate users
> or computers on the network. Everything acts like there is no DC
> available,
> altho everything says it's working.
>
> I've got to get this box up and running, so I can take down the
> original and
> reinstall with new drives.

I did replicate the Global Catalog while attempting to solve the problem.
But it didn't help. I was under the impression that it wasn't important
given the one-forest, one-domain topology, anyway, altho I may be wrong. But
it didnt help.

What records should I be looking for in the DNS? DNS server is running on
the new box, as is DHCP.

Bryan Britt


"Bryan Britt, Beltane" wrote:

> With an existing, and working, Server 2003 domain, I've added a new box
> running the same version, Server 2003 Standard Edition.
>
> The box joined the domain just fine, and added AD. It shows up in the
> Domain Controller container of the AD Users & Groups, the users and
> everything replicated. I've even moved over all 5 schema, etc roles to the
> new box.
>
> When the original DC is powered down, the new DC will not authenticate users
> or computers on the network. Everything acts like there is no DC available,
> altho everything says it's working.
>
> I've got to get this box up and running, so I can take down the original and
> reinstall with new drives.

How are you assigning the client's TCP DNS entry? Manually? Automatically?

Is the new DNS server auto-assigning the old DNS server's IP to the clients?

Is the manual old DNS IP entry still in the clients?

-Frank

"Bryan Britt, Beltane" <(E-Mail Removed)> wrote
in message news:E74D67A5-F8DC-4719-A459-(E-Mail Removed)...
>I did replicate the Global Catalog while attempting to solve the problem.
> But it didn't help. I was under the impression that it wasn't important
> given the one-forest, one-domain topology, anyway, altho I may be wrong.
> But
> it didnt help.
>
> What records should I be looking for in the DNS? DNS server is running on
> the new box, as is DHCP.
>
> Bryan Britt
>
>
> "Bryan Britt, Beltane" wrote:
>
>> With an existing, and working, Server 2003 domain, I've added a new box
>> running the same version, Server 2003 Standard Edition.
>>
>> The box joined the domain just fine, and added AD. It shows up in the
>> Domain Controller container of the AD Users & Groups, the users and
>> everything replicated. I've even moved over all 5 schema, etc roles to
>> the
>> new box.
>>
>> When the original DC is powered down, the new DC will not authenticate
>> users
>> or computers on the network. Everything acts like there is no DC
>> available,
>> altho everything says it's working.
>>
>> I've got to get this box up and running, so I can take down the original
>> and
>> reinstall with new drives.

Correction...

"Is the new DNS server auto-assigning the old DNS server's IP to the
clients?"

should read...

"Is the DHCP server auto-assigning the old DNS server's IP to the clients?"

-Frank


"Frankster" <(E-Mail Removed)> wrote in message
newsfCdnQk5PJ9AiD7fRVn-(E-Mail Removed)...
> How are you assigning the client's TCP DNS entry? Manually?
> Automatically?
>
> Is the new DNS server auto-assigning the old DNS server's IP to the
> clients?
>
> Is the manual old DNS IP entry still in the clients?
>
> -Frank
>
> "Bryan Britt, Beltane" <(E-Mail Removed)> wrote
> in message news:E74D67A5-F8DC-4719-A459-(E-Mail Removed)...
>>I did replicate the Global Catalog while attempting to solve the problem.
>> But it didn't help. I was under the impression that it wasn't important
>> given the one-forest, one-domain topology, anyway, altho I may be wrong.
>> But
>> it didnt help.
>>
>> What records should I be looking for in the DNS? DNS server is running
>> on
>> the new box, as is DHCP.
>>
>> Bryan Britt
>>
>>
>> "Bryan Britt, Beltane" wrote:
>>
>>> With an existing, and working, Server 2003 domain, I've added a new box
>>> running the same version, Server 2003 Standard Edition.
>>>
>>> The box joined the domain just fine, and added AD. It shows up in the
>>> Domain Controller container of the AD Users & Groups, the users and
>>> everything replicated. I've even moved over all 5 schema, etc roles to
>>> the
>>> new box.
>>>
>>> When the original DC is powered down, the new DC will not authenticate
>>> users
>>> or computers on the network. Everything acts like there is no DC
>>> available,
>>> altho everything says it's working.
>>>
>>> I've got to get this box up and running, so I can take down the original
>>> and
>>> reinstall with new drives.
>
>