Re: Never Saw Something This Weird

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Much better said. To add, when the logon box pops up, it is the netbios name
of the domain that appears in the domain list. If a domain is "domain.org",
usually (but not always) the netbios name will be "DOMAIN". Since you
mentioned a migration and the fact that the "'correct' domain isn't an
option in the domain list", it suggests that the netBIOS name may a leftover
from the old domain. If the old domain was "old.com" with NetBios name
"OLD", the new domain could very well be "new.com" with NetBIOS name "OLD".

....kurt


"Herb Martin" <news@xxxxxxxxxxxxxx> wrote in message
news:O97VMQh3GHA.4392@xxxxxxxxxxxxxxxxxxxxxxx
"Kurt" <lorentzenkurt@xxxxxxxxxxxxxxxxxx> wrote in message
news:12h6md9nhs9kf32@xxxxxxxxxxxxxxxxxxxxx
The NetBIOS name of the domain could have been completely different from
it's DNS name. In fact, that's exactly what happens when you "upgrade"
migrate an NT4 domain to AD. You give the AD domain a "something.suffix"
FQDN, but the netBIOS name stays the same as the old NT4 domain.

Well, in that sense practically ALL NetBIOS names are different
from the Domain's DNS name since one really should not use
special characters (including "."s) in NetBIOS names so a domain
named "DOMAIN" in NetBIOS is almost always going to be
"DOMAIN.com" in DNS.

(And one must/should never use a single tag DNS name either.)

What most people do, is to use the MAIN tag for the NetBIOS
version (the default is to use the Leftmost tag when DCPromo
does it) and use the full DNS name for the DNS version of course.

This is generally true on upgraded domains if people think it
through but is not actually a requirement -- just confusing if they
do not.



--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

...kurt

"Absolutely" <nospam@xxxxxxxxxxx> wrote in message
news:eJqhZUZ3GHA.5000@xxxxxxxxxxxxxxxxxxxxxxx
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: A g;lobal catalog cannot be located to retrieve the icons from the member list
    ... Please post your Netbios domain name, the AD domain name and the DNS ... Server has eveng logging set to no events, and I am unable to change ... Attr: subschemaSubentry ...
    (microsoft.public.windows.server.active_directory)
  • Re: Browsing Subnets
    ... Another server at the 2nd site also provides the DNS. ... Name resolution possibly (although inefficiently for NetBIOS names) ...
    (microsoft.public.win2000.dns)
  • Re: WHY WINS
    ... uses Netbios names. ... This is not really about DNS and WINS servers, ... does Network Neighborhood depend on the computer browser service ... WINS server must exist fot the DNS server to integrate with (which is why ...
    (microsoft.public.windows.server.networking)
  • Re: Browsing Subnets
    ... [phone number on web site] ... Another server at the 2nd site also provides the DNS. ... Name resolution possibly (although inefficiently for NetBIOS names) ...
    (microsoft.public.win2000.dns)
  • Re: Please help refresh my memory on AD DC
    ... I have 4 Server 2003 Enterprise ... caused the installation wizard to change the NetBIOS name from WEB308 ... I assume you mean the logon window with USERNAME, PASSWORD and the "LOGON TO" which now shows only "web30380", the Netbios name of the domain, this is NOT longer the computer name as on a workgroup server. ... you do not logon to the domain controller, you logon to the domain and a domain can have multiple domain controllers which share one database that is stored on all DC's and updates itself automatically. ...
    (microsoft.public.windows.server.active_directory)