Re: Error Message About Domain Controller

yeah, i think our company may be getting rid of the second server or else
getting windows server 2003 standard edition. Instead of 2 SBS 2003's. I had
spoke to a network engineer last night and he basically told me the same
thing you did. So we will see what happens. But thank you very much i do
appreciate your time.

Sincerely
Jeremy Himmelreich
Computer Project Coordinator / Network Administrator
Willits Footwear Worldwide Inc.
Email: JeremyH1982@xxxxxxxxxxx


"SuperGumby [SBS MVP]" wrote:

> You cannot have a trust between an SBS domain and another domain (neither
> vanilla windows nor SBS).
> You cannot have two SBS's in the same domain.
>
> Base limitations of the product.
>
> A 'hack' method has been publicised to negate the first limit but it
> directly violates the EULA and I have always had my doubts about the long
> term functioning of it.
>
> SIDs are just unique identifiers. When a Windows Domain is created a random
> (pseudorandom?) alphanumeric sequence is created, this is the domain SID. As
> each user is created they appear to us as 'John Smith' but internally
> Windows knows them by their user SID. Devices in the domain have a machine
> SID. There are other SIDs but we don't need to go into it here.
>
> I'm wondering how you have managed to get the two SBS's into the same domain
> (sortof). I'll guess that you have installed both to the same domain name
> (say company.local), one SBS believes is in the domain SID1, the other is in
> SID2, even though the name displayed to us is company.local on both.
>
> "JeremyH1982" <JeremyH1982@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:0A024A17-8D5A-4FEE-B147-9B2293BC3479@xxxxxxxxxxxxxxxx
> > SuperGumby--
> >
> > That was exactly the problem. I didn't have the DNS Pointing to the
> > server's
> > IP Address.
> >
> > But now i have another problem. I am trying to connect two SBS 2003
> > together
> > but i keep getting emails about Fileserv2 is trying to connect to
> > Fileserv1
> > through the trusted delegation...
> > Exact Message Follows:
> > The computer FILESERV2 tried to connect to the server \\FILESERV1 using
> > the
> > trust relationship established by the SMALLBUSINESS domain. However, the
> > computer lost the correct security identifier (SID) when the domain was
> > reconfigured. Reestablish the trust relationship.
> >
> > What is the Security Identifier? (That may be a stupid question but i
> > would
> > really like to know the answer.) Thank You
> >
> > "SuperGumby [SBS MVP]" wrote:
> >
> >> <snip> pc's IP is obtained automatically; I believe all the pc's are
> >> pointing to the
> >> > SBS IP for Primary DNS and to the ISP for Secondary DNS.;<snip>
> >>
> >> This is probably the problem. All members of an AD should look _only_ to
> >> AD
> >> DNS integrated DNS servers.
> >>
> >>
> >>
>
>
>
.

Relevant Pages

  • Re: Error Message About Domain Controller
    ... You cannot have a trust between an SBS domain and another domain (neither ... When a Windows Domain is created a random ... Windows knows them by their user SID. ...
    (microsoft.public.windows.server.sbs)
  • Re: gdm and network-manager issues SOLVED
    ... up order is wrong How can I fix this? ... Once I start X and log on as my user I have no DNS service. ... Lenny using netinstaller then dist-upgraded to Sid. ...
    (Debian-User)
  • Re: Problems with giving the Domain Users group access to folders
    ... You certainly don't want to have computers with the same sid. ... Any fatal error is not good with netdiag. ... First thing to check is dns ... configuration in that domain controllers should point to the first domain controller ...
    (microsoft.public.win2000.security)
  • Re: Active Directory
    ... > red arrow next to them and what looks like a SID number, ... Since SBS doesn't generally support trusts, ... I would doubt that entries here would have any impact on regular SBS ... Steve Foster [SBS MVP] ...
    (microsoft.public.windows.server.sbs)
  • Re: New Server (Hardware Upgrade), SBS 2003 to SBS 2003 Same Domain Na
    ... as for the data transfer from one box to the other the OP is correct, having the same named (different SID) AD on two DCs on the same ethernet segment is bound to cause problems and in the better case of www.sbsmigration.com's Swing IT process where you migrate the domain you _really_ don't want to connect OriginSBS and TargetSBS to the same wire at any time, having two copies of a same named same SID AD on one wire is worse than the other. ... For data transfer either HDD or Tape is best. ... SBS remote support services. ... In either case, not only will it be the same domain when you're done, you'll have the same server name and everything else. ...
    (microsoft.public.windows.server.sbs)