Re: Never Saw Something This Weird

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

I suspect you are correct, but why would the workstations still be logging
into an old domain that doesn't exist? If you check the workstations they
show as being joined to the 'correct' domain, but during login the 'correct'
domain isn't an option in the domain list. Only the local machine and the
old seemingly non-existent domain.

I can't even begin to describe all the crazy things that I'm seeing with
configuration of the boxes, but half the workstations can't be logged in
unless the user is an admin and on and on. nslookup resolves names to
multiple IP addresses in some cases and things such as this. Again, I can
fix all this and know why most of it is happening, but I can't quite figure
out what the deal is with the domain situation.




"Danny Sanders" <DSanders@xxxxxxxxxxxxxxx> wrote in message
news:eI6Fm5Y3GHA.324@xxxxxxxxxxxxxxxxxxxxxxx
The story goes that there was a
2000 server with AD. At some point, a 2003 server was setup and AD was
installed on that. Both servers are acting as domain controllers, but it
would appear that they are both domain controllers for the same domain,
that being the domain that was setup on the 2003 server. However, the
workstations login to a domain that I'm told was the domain that was
created on the 2000 server when AD was installed.

Possibly two separate domains w/ the same name?

hth
DDS W 2k MVP MCSE

"Absolutely" <nospam@xxxxxxxxxxx> wrote in message
news:uBt5urY3GHA.4588@xxxxxxxxxxxxxxxxxxxxxxx
Got asked to come in and take a look at a Windows Server install and saw
some things that just aren't making sense. The story goes that there was
a 2000 server with AD. At some point, a 2003 server was setup and AD was
installed on that. Both servers are acting as domain controllers, but it
would appear that they are both domain controllers for the same domain,
that being the domain that was setup on the 2003 server. However, the
workstations login to a domain that I'm told was the domain that was
created on the 2000 server when AD was installed. The whole thing is a
real mess. DNS is a mess, DHCP is a mess. Nothing is making sense. I
can fix the obvious stuff, but not sure what effect this will have on
whatever other weirdness was created behind the scenes.

It looks as if someone was trying to run dcpromo on the 2000 box at
somepoint. Perhaps this didn't complete? I'm pretty much ready to save
the data and blow out both boxes and reinstall the OS in the interest of
time.






.

Relevant Pages

  • Re: SBS 2003 Misconfigured?
    ... up one of the workstations via remote web connection, ... but why are you looking at the server rather than the workstation? ... (this will show you the DHCP lease info). ... The Netgear, or whatever you use as your gateway to get out to the Internet. ...
    (microsoft.public.windows.server.sbs)
  • RE: Windows Universal Storage Server 2003 quits working
    ... day) stops communicating with the domain controllers. ... but no other machines are affected (either servers or ... Local workstations can access files, ... The Server is a Dell NX1950 with a MD3000 Raid Enclosure. ...
    (microsoft.public.windows.server.general)
  • Re: SBS 2003 Misconfigured?
    ... When I remote back into the server and look at DHCP, ... I assume DHCP assigned it, but how can I verify that. ... the workstations, I was having connection problems with the workstations. ... The netgear has a setting for the Internet IP which is set to the ...
    (microsoft.public.windows.server.sbs)
  • Re: status of mas90 client
    ... Gregg Hill wrote: ... The Dell PE 2800 server ... The workstations are slow to open applications, slow to save files to the ... SBS BPA gives a clean report. ...
    (microsoft.public.windows.server.sbs)
  • Re: status of mas90 client
    ... Gregg Hill wrote: ... The Dell PE 2800 server ... The workstations are slow to open applications, slow to save files to the ... SBS BPA gives a clean report. ...
    (microsoft.public.windows.server.sbs)