Re: Thoroughly confused SBS 2003 Server
- From: "Les Connor [SBS Community Member - SBS MVP]" <les.connor@xxxxxxxxxxxx>
- Date: Sun, 22 Jan 2006 11:59:07 -0600
Hi Joe,
Additional DC's are allowed, that's a common misconception that they're not.
Allthough the merits of an additional DC might be weak in many cases.
--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
----------------------
"Tell me and I'll forget. Show me and I'll remember. Involve me and I'll
understand." - Confucius
"Joe H" <JoeH@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:390FF099-025A-4D08-BD01-CB71D8623D25@xxxxxxxxxxxxxxxx
>I believe the SBS2003 documentation is fairly clear about what you can do
>on
> an SBS2003 network. You can have member servers on the SBS2003 network,
> but
> you cannot have another SBS2003 server and neither can you have another
> domain controller. You might want to review the documentation.
>
> "Al Christoph" wrote:
>
>> I'm not exactly sure how I got into the kettle of fish that I'm in sooooo
>> ..... I mention several of the worst symptoms.
>> I'm not adverse to rebuilding the system provided that I can capture the
>> user id's and transfer them to the new system AND capture the POP3
>> settings
>> on my Exchange Server. (The password it uses to get the email from the
>> ISP
>> is absolutely archaic, and I have no particularly easy way to recover
>> it:-(
>>
>> 1. The most embarassing is that when I have a second server - configured
>> as
>> Windows Server 2003 Enterprise Edition - turned on, the SBS system gives
>> me
>> a series of complaints about another SBS system being present on the
>> network, then EULA violation warnings, and then shuts itself off!!!! The
>> source of these errors is SBCore and the ultimate ID # is 1001. (There
>> are a
>> series of timed warnings before it shuts down.)
>>
>> 2. When I try to add a computer or a server, it goes through the motions
>> and
>> then says that I need to be an SBS admin or Power user to do it. Two
>> errors
>> from SAM are generated ID's 16650 and 16651.
>>
>> 3. This is the scariest one - Application / Userenv / id 1054 "Windows
>> cannot obtain the domain controller name for your computer network ..."
>>
>> There are bunches of others too, but these strike me as the ones that
>> might
>> lead me out of the mess I'm in.
>>
>> Suggestions please.
>>
>> Thanks.
>>
>> Regards,
>> Al
>> Who at this point would really like to save what he needs off this SBS
>> box
>> and move SBS to the box that now has Enterprise server on it. Then he
>> would
>> turn the current SBS box into a 64 BIT Windows XP box since that is what
>> the
>> hardware is.
>>
>>
>>
.
- References:
- Thoroughly confused SBS 2003 Server
- From: Al Christoph
- Thoroughly confused SBS 2003 Server
- Prev by Date: Re: Thoroughly confused SBS 2003 Server
- Next by Date: Re: Allowing Visitor Internet access
- Previous by thread: Re: Thoroughly confused SBS 2003 Server
- Next by thread: Re: Thoroughly confused SBS 2003 Server
- Index(es):
Relevant Pages
|
