Confused

  • Thread starter Thread starter nick
  • Start date Start date
N

nick

I've been reading some posts, and am fairly confused. We have one
Windows 2000 SBS serving as the DNS server, Exchange server, and
running DHCP. (It was setup that way before I got here).

We have another Windows 2000 server running as a secondary domain
controller. I thought that if the Win2K SBS server went down that
people could still log onto the network via the secondary domain
controller. Is this correct?

If not, then what would be the best solution to keep users accessign
the network if the primary domain controller goes down?
 
Ask in an SBS Group. There are about 3 million ways that SBS will screw you
and bite you in the rear-end.

1. SBS must always be the DC with the PDC "Role", although there can be more
than one DC

2. SBS cannot have trusts with other domains

3. SBS cannot join an existing domain. (can't rebuild from scratch and join
existing domain). To me this makes a second DC kind of pointless, since the
SBS cannot re-join the domain that it previously created itself once the
machine has been "flattened". Creating a new domain of the same name does
not help either.

Some people have worked out some "third-party tricks". Probably only people
dedicated to SBS (in the SBS group) will know enough about the details to
help.
 
Thanks,Phillip.

Phillip said:
Ask in an SBS Group. There are about 3 million ways that SBS will screw you
and bite you in the rear-end.

1. SBS must always be the DC with the PDC "Role", although there can be more
than one DC

2. SBS cannot have trusts with other domains

3. SBS cannot join an existing domain. (can't rebuild from scratch and join
existing domain). To me this makes a second DC kind of pointless, since the
SBS cannot re-join the domain that it previously created itself once the
machine has been "flattened". Creating a new domain of the same name does
not help either.

Some people have worked out some "third-party tricks". Probably only people
dedicated to SBS (in the SBS group) will know enough about the details to
help.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


nick said:
I've been reading some posts, and am fairly confused. We have one
Windows 2000 SBS serving as the DNS server, Exchange server, and
running DHCP. (It was setup that way before I got here).

We have another Windows 2000 server running as a secondary domain
controller. I thought that if the Win2K SBS server went down that
people could still log onto the network via the secondary domain
controller. Is this correct?

If not, then what would be the best solution to keep users accessign
the network if the primary domain controller goes down?
Click to expand...
Click to expand...
 
Good Luck!
I'm sure they guys in the SBS Groups can find a way to deal with whatever
you have there.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

nick said:
Thanks,Phillip.

Phillip said:
Ask in an SBS Group. There are about 3 million ways that SBS will screw
you
and bite you in the rear-end.

1. SBS must always be the DC with the PDC "Role", although there can be
more
than one DC

2. SBS cannot have trusts with other domains

3. SBS cannot join an existing domain. (can't rebuild from scratch and
join
existing domain). To me this makes a second DC kind of pointless, since
the
SBS cannot re-join the domain that it previously created itself once the
machine has been "flattened". Creating a new domain of the same name
does
not help either.

Some people have worked out some "third-party tricks". Probably only
people
dedicated to SBS (in the SBS group) will know enough about the details to
help.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


nick said:
I've been reading some posts, and am fairly confused. We have one
Windows 2000 SBS serving as the DNS server, Exchange server, and
running DHCP. (It was setup that way before I got here).

We have another Windows 2000 server running as a secondary domain
controller. I thought that if the Win2K SBS server went down that
people could still log onto the network via the secondary domain
controller. Is this correct?

If not, then what would be the best solution to keep users accessign
the network if the primary domain controller goes down?
Click to expand...
Click to expand...
Click to expand...
 
Back
Top