second domain controller

My Scenario:

I installed my first domain controller ( Windows 2003
Standard Edition )with AD, DNS and DHCP.
Then i installed Windows 2003 standard edition on another
computer then used the wizard to add the AD role and to
have this second computer as the additional domain
controller. Once i had done that during login i was
prompted to login to the first server ( so i thought it
was good ). Then i found that their was no DNS settings on
the second server. So i configured the DNS using the
wizard and added it as the second DNS server but by coping
from the first. After that i could see all the entries of
the DNS in the first server in the second server.( I
thought now everything looks good )
The purpose of my second server was that if my first
server is down or out of network, the second server should
have the same functionality of the first server.

Problem:
Once i shut down my first server
Some clients couldn't get authenticated from the second
server, but some get authenticated. Even if they get
authenticated they couldnot use any LAN resources.
In the second server i noticed that Active Directory users
and computers cant be accessed.
What am i doing wrong?
Appreciate a quick response
I have DHCP running only in the first server.
But i have given static ips to both the first and second
server.
So i am still wondering whether i did something wrong
during the AD installation or DNS in the secondary server.
I also checked the Global catalog under NTDS Settings for
the second server under Active Directroy Sites and
Services.
Actually i have a very small network and i really dont
require a dhcp.
I have all my local users using a static ip ( private )
Domain name is not a public domain name.

when i do a ipconfig/all on my clients i could see both
the ips listed under DNS

My clients can get authenticated to get into windows when
the first server is down. But they cant access any
resources on the lan, not even connect to the second
server ( but can be pinged to the server ). One thing i
noticed is that if i login as local administrator in the
client machine then i am able to access the resources on
the second server or any client machine which has logged
in as local administrator. But if i try to map any drive
of any other lan resources, it doesn't get authenticated
with any of the domain users.
Also i noticed that in the second server if i try to
access Active directory Sites and Services then it gives
an error - Naming information cannot be located because:
The specified domain either does not exists or could not
be contacted. Contact your administrator to verify that
your domain is properly configured and is currently online.

What all tests and configurations i should do on the
second server to ensure that it was installed properly to
serve as a back up server when the first server is down.

Hi,

I answered in microsoft.public.windows.server.setup.

Don't multi-post, it makes it hard to track questions and answers. Next time
rather cross-post (enter all newsgroups that you want to post to under
"Newsgroups:" field.

Mike

"idsi" <(E-Mail Removed)> wrote in message
news:3a6501c48f88$79431460$(E-Mail Removed)...
> My Scenario:
>
> I installed my first domain controller ( Windows 2003
> Standard Edition )with AD, DNS and DHCP.
> Then i installed Windows 2003 standard edition on another
> computer then used the wizard to add the AD role and to
> have this second computer as the additional domain
> controller. Once i had done that during login i was
> prompted to login to the first server ( so i thought it
> was good ). Then i found that their was no DNS settings on
> the second server. So i configured the DNS using the
> wizard and added it as the second DNS server but by coping
> from the first. After that i could see all the entries of
> the DNS in the first server in the second server.( I
> thought now everything looks good )
> The purpose of my second server was that if my first
> server is down or out of network, the second server should
> have the same functionality of the first server.
>
> Problem:
> Once i shut down my first server
> Some clients couldn't get authenticated from the second
> server, but some get authenticated. Even if they get
> authenticated they couldnot use any LAN resources.
> In the second server i noticed that Active Directory users
> and computers cant be accessed.
> What am i doing wrong?
> Appreciate a quick response
> I have DHCP running only in the first server.
> But i have given static ips to both the first and second
> server.
> So i am still wondering whether i did something wrong
> during the AD installation or DNS in the secondary server.
> I also checked the Global catalog under NTDS Settings for
> the second server under Active Directroy Sites and
> Services.
> Actually i have a very small network and i really dont
> require a dhcp.
> I have all my local users using a static ip ( private )
> Domain name is not a public domain name.
>
> when i do a ipconfig/all on my clients i could see both
> the ips listed under DNS
>
> My clients can get authenticated to get into windows when
> the first server is down. But they cant access any
> resources on the lan, not even connect to the second
> server ( but can be pinged to the server ). One thing i
> noticed is that if i login as local administrator in the
> client machine then i am able to access the resources on
> the second server or any client machine which has logged
> in as local administrator. But if i try to map any drive
> of any other lan resources, it doesn't get authenticated
> with any of the domain users.
> Also i noticed that in the second server if i try to
> access Active directory Sites and Services then it gives
> an error - Naming information cannot be located because:
> The specified domain either does not exists or could not
> be contacted. Contact your administrator to verify that
> your domain is properly configured and is currently online.
>
> What all tests and configurations i should do on the
> second server to ensure that it was installed properly to
> serve as a back up server when the first server is down.