Re: Error Message About Domain Controller

Tech-Archive recommends: Fix windows errors by optimizing your registry

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: DNS & w2k3
    ... Server A Primary DNS ... NIC 1 DNS pointing to each other ... The replicaiton folder was created, ...
    (microsoft.public.windows.server.dns)
  • Re: Recommended setting for Preferred and Alternate DNS
    ... What is the recommended Preferred and Alternative DNS server ... I have one DC with Preferred DNS pointing to itself and Alternate DNS ... My preference would be to use the other DC as the preferred, ...
    (microsoft.public.windows.server.dns)
  • Re: DC Dependencies with 2 win 2003 DCs
    ... The first DC starts with errors because its own DNS service is not available ... then turn on dc2, theen reboot dc1. ... My thought is that DC1 should be able to start without any interaction ... Prefeered DNS pointing to itself ...
    (microsoft.public.windows.server.general)
  • Re: cant join xp sp2 to ad domain
    ... > I noticed I was having quite a few DNS related errors in the event ... > My network now looks like this.... ... > to the internal server. ... > The external NIC on the server is set to auto IP with DNS pointing to ...
    (microsoft.public.windows.server.networking)