I am have added backup domain controllers to our SBS network. The domain
controllers are replicating correctly as I am able to add/change user account
information from any controller and it propagates to all domain controllers.
However, when the SBS 2000 server is down it wont let anyone log onto the
network and gives an error message about the domain controller not be
found....

Shouldn't the other domain controllers allow users to login even if the SBS
2000 server is down? What do I need to do to resolve this problem?...

Re: Backup Domain Controller In SBS 2000 by Dave

Dave
Tue Oct 19 12:10:27 CDT 2004

What I've seen is that if there is no DC available to authenticate logins,
win2k and later will log in with cached credentials. Login with cached
credentials fails if the SBS is online but not responding, apparently
because the workstation knows the SBS is there but it's not getting an
answer.

Are you getting login failures if the SBS is completely shut down so that it
won't even respond to a ping? What OS are the desktops running?

"Grecko" <Grecko@discussions.microsoft.com> wrote in message
news:D3FE467B-3A26-46AB-AA0E-11051C3158F4@microsoft.com...
>I am have added backup domain controllers to our SBS network. The domain
> controllers are replicating correctly as I am able to add/change user
> account
> information from any controller and it propagates to all domain
> controllers.
> However, when the SBS 2000 server is down it wont let anyone log onto the
> network and gives an error message about the domain controller not be
> found....
>
> Shouldn't the other domain controllers allow users to login even if the
> SBS
> 2000 server is down? What do I need to do to resolve this problem?...



Re: Backup Domain Controller In SBS 2000 by Grecko

Grecko
Tue Oct 19 12:47:04 CDT 2004

Yes. We are using windows 2000 and XP. I just want people to be able to
login into the network even if the SBS200 server is completely down for some
reason. I am pretty sure I have setup the other domain controllers
correctly. All of them are set as Global Catalog Servers. The only thing I
can think of is that the DNS is setup incorrectly. Right now, I have the SBS
2000 setup as the primary DNS and one of the other Domain controllers setup
as the secondary DNS on our network....an other ideas...


"Dave Nickason [SBS MVP]" wrote:

> What I've seen is that if there is no DC available to authenticate logins,
> win2k and later will log in with cached credentials. Login with cached
> credentials fails if the SBS is online but not responding, apparently
> because the workstation knows the SBS is there but it's not getting an
> answer.
>
> Are you getting login failures if the SBS is completely shut down so that it
> won't even respond to a ping? What OS are the desktops running?
>
> "Grecko" <Grecko@discussions.microsoft.com> wrote in message
> news:D3FE467B-3A26-46AB-AA0E-11051C3158F4@microsoft.com...
> >I am have added backup domain controllers to our SBS network. The domain
> > controllers are replicating correctly as I am able to add/change user
> > account
> > information from any controller and it propagates to all domain
> > controllers.
> > However, when the SBS 2000 server is down it wont let anyone log onto the
> > network and gives an error message about the domain controller not be
> > found....
> >
> > Shouldn't the other domain controllers allow users to login even if the
> > SBS
> > 2000 server is down? What do I need to do to resolve this problem?...
>
>
>

Re: Backup Domain Controller In SBS 2000 by Dave

Dave
Tue Oct 19 13:10:47 CDT 2004

I'm stumped - DNS was going to be my next suggestion.

When you run ipconfig /all on a workstation, do both DNS servers show up?
In any case, what I've seen with improperly configured DNS is not that a
login would fail, but rather that it would take a long time to authenticate.

What's the exact text of the message you receive when the login fails?


"Grecko" <Grecko@discussions.microsoft.com> wrote in message
news:CFE747A3-013E-4DFF-ABE4-564711AA2814@microsoft.com...
> Yes. We are using windows 2000 and XP. I just want people to be able to
> login into the network even if the SBS200 server is completely down for
> some
> reason. I am pretty sure I have setup the other domain controllers
> correctly. All of them are set as Global Catalog Servers. The only thing
> I
> can think of is that the DNS is setup incorrectly. Right now, I have the
> SBS
> 2000 setup as the primary DNS and one of the other Domain controllers
> setup
> as the secondary DNS on our network....an other ideas...
>
>
> "Dave Nickason [SBS MVP]" wrote:
>
>> What I've seen is that if there is no DC available to authenticate
>> logins,
>> win2k and later will log in with cached credentials. Login with cached
>> credentials fails if the SBS is online but not responding, apparently
>> because the workstation knows the SBS is there but it's not getting an
>> answer.
>>
>> Are you getting login failures if the SBS is completely shut down so that
>> it
>> won't even respond to a ping? What OS are the desktops running?
>>
>> "Grecko" <Grecko@discussions.microsoft.com> wrote in message
>> news:D3FE467B-3A26-46AB-AA0E-11051C3158F4@microsoft.com...
>> >I am have added backup domain controllers to our SBS network. The
>> >domain
>> > controllers are replicating correctly as I am able to add/change user
>> > account
>> > information from any controller and it propagates to all domain
>> > controllers.
>> > However, when the SBS 2000 server is down it wont let anyone log onto
>> > the
>> > network and gives an error message about the domain controller not be
>> > found....
>> >
>> > Shouldn't the other domain controllers allow users to login even if the
>> > SBS
>> > 2000 server is down? What do I need to do to resolve this problem?...
>>
>>
>>



Re: Backup Domain Controller In SBS 2000 by Grecko

Grecko
Tue Oct 19 13:35:03 CDT 2004

Yeah both ip addresses show up. No it sits there a while and says something
like "No domain controller is available for domain <domain name>. There are
currently no logon servers available to service the logon request.". However,
I can go into the non-sbs server and see the user accounts....It just wont
let us login in when the SBS 2000 server is down...Gregg

"Dave Nickason [SBS MVP]" wrote:

> I'm stumped - DNS was going to be my next suggestion.
>
> When you run ipconfig /all on a workstation, do both DNS servers show up?
> In any case, what I've seen with improperly configured DNS is not that a
> login would fail, but rather that it would take a long time to authenticate.
>
> What's the exact text of the message you receive when the login fails?
>
>
> "Grecko" <Grecko@discussions.microsoft.com> wrote in message
> news:CFE747A3-013E-4DFF-ABE4-564711AA2814@microsoft.com...
> > Yes. We are using windows 2000 and XP. I just want people to be able to
> > login into the network even if the SBS200 server is completely down for
> > some
> > reason. I am pretty sure I have setup the other domain controllers
> > correctly. All of them are set as Global Catalog Servers. The only thing
> > I
> > can think of is that the DNS is setup incorrectly. Right now, I have the
> > SBS
> > 2000 setup as the primary DNS and one of the other Domain controllers
> > setup
> > as the secondary DNS on our network....an other ideas...
> >
> >
> > "Dave Nickason [SBS MVP]" wrote:
> >
> >> What I've seen is that if there is no DC available to authenticate
> >> logins,
> >> win2k and later will log in with cached credentials. Login with cached
> >> credentials fails if the SBS is online but not responding, apparently
> >> because the workstation knows the SBS is there but it's not getting an
> >> answer.
> >>
> >> Are you getting login failures if the SBS is completely shut down so that
> >> it
> >> won't even respond to a ping? What OS are the desktops running?
> >>
> >> "Grecko" <Grecko@discussions.microsoft.com> wrote in message
> >> news:D3FE467B-3A26-46AB-AA0E-11051C3158F4@microsoft.com...
> >> >I am have added backup domain controllers to our SBS network. The
> >> >domain
> >> > controllers are replicating correctly as I am able to add/change user
> >> > account
> >> > information from any controller and it propagates to all domain
> >> > controllers.
> >> > However, when the SBS 2000 server is down it wont let anyone log onto
> >> > the
> >> > network and gives an error message about the domain controller not be
> >> > found....
> >> >
> >> > Shouldn't the other domain controllers allow users to login even if the
> >> > SBS
> >> > 2000 server is down? What do I need to do to resolve this problem?...
> >>
> >>
> >>
>
>
>