From: "Glenn Meadows" 

The office it came from was a One Domain controller system.  Our domains
were not "connected" into a wide multi office domain.

I'll check the settings for IP and such, as I know what they originally
were, rather than trying to use the domain here for dns and all.

As to permanent damage, there is no ultimate reason I can't nuke the
machine and start again.  Just figured I'd get the experience doing this.

--
Glenn M.


"John Beckett"  wrote
in message news:400f9188.4417532{at}216.144.1.254...
> "Glenn Meadows"  wrote in message
> news::
> > it was the only server in that domain, anyway.
>
> If so, and if you tell dcpromo that it is the last domain controller, I
> don't see why it would fail. Perhaps it just can't find itself? It wants
> the same DNS arrangements that it had before. If you changed the IP and
> DNS, you might have upset it.
>
> If this was more than a one-domain-controller operation, I would suggest
> phoning Microsoft to avoid permanent damage.
>
> John
>

--- BBBS/NT v4.01 Flag-5