Phantom Domain (bad Win2k dcpromo)

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Fred Madden (anonymous_at_discussions.microsoft.com)
Date: 05/12/04 

Date: Wed, 12 May 2004 14:10:29 -0700

I finally figured out where the "phantom domain" was
coming from. It turns out that there was a Trust still
set up for it.

I still have the issue where I can't browse the network
until I do either a nbtstat -RR or (which I just figured
out and is easier) click on a mapped drive. Then browsing
works fine. If anyone has an answer for this problem,
that would be cool. (At least now that I've eliminated
the phantom domain problem I can start looking in the
right direction.)

>-----Original Message-----
>I'm in the process of cleaning up the previous sys
admin's
>mess and ran into something I haven't been able to figure
>out. Basically, when I started at this company, they had
>an NT 4.0 domain as their main domain, and a Win2k domain
>running which looked like it was an attempt to upgrade
>from, and do away with, the NT 4.0 domain.
>
>What appears to have happened, is that the previous sys
>admin (I use the term loosely) had no clue that you need
>to upgrade an NT 4.0 DC to Win2k in order for this to
work
>correctly. It appears that he just built a Win2k Server
>then dcpromo'd it and tried to add it to the NT 4.0
>domain. The result being that they now had two domains;
>one called MyDomain, and the Win2k one called MyDomain0.
>
>Since I've been here, I've cleaned this up and now have
>one Win2k domain named MyDomain. The problem that I now
>have is that when a Win2k Pro machine first boots up and
>tries to browse the network, My Network Places lists our
>current domain, MyDomain, and the failed dcpromo one of
>MyDomain0. With neither one of these being browseable.
>If I do a nbtstat -RR, then refresh My Network Places,
the
>MyDomain0 disapears and MyDomain becomes browseable.
>
>So it would seem like this would be a WINS problem. But
>everything on our WINS servers seems fine. Plus they
>didn't even have a WINS server setup here until after I
>had already done away with the failed DC. (Plus their
>only DNS server was the failed Win2k DC.) So it seems
>like there was nothing other than the NT 4.0 DC to cache
>the existance of the failed Win2k DC.
>
>So I am not sure where it is pulling this old, failed
>domain name from, and why it is causing problems. If
>anyone has any ideas of how to solve this problem, that
>would be great. TIA
>.
>

Relevant Pages

  • Cant add user permissions from folder window, can from Computer Mgmt console
    ... On a Win2k client on a network with a win2k pdc server, ... All other network functionality on the Win2k client seems ...
    (microsoft.public.win2000.security)
  • Re: Win2K admin tools for WinXP
    ... >> Does anyone know how to administer a Win2K server ... I've tried installing the Win2K ... >> 2K network from XP? ...
    (microsoft.public.windowsxp.security_admin)
  • Windows 2000 visibility
    ... machines on my local network can view it with no problem. ... see the server he logs into, but cannot see the Win2k ... using the drives it is fine, after a few minutes of no ...
    (microsoft.public.win2000.networking)
  • Re: How vulnerable are Windows servers if you can run e.g. Knoppix on one of the workstations?
    ... > I administer a number of small Win2k domains. ... > or map my way to drives on the Win2k Server and read server files as ... This is a horse of a different color, as you're wondering about a network ... > have physical access to some of her workstations and LAN ports. ...
    (comp.os.linux.security)
  • Phantom Domain (bad Win2k dcpromo)
    ... I'm in the process of cleaning up the previous sys admin's ... to upgrade an NT 4.0 DC to Win2k in order for this to work ... It appears that he just built a Win2k Server ... one called MyDomain, and the Win2k one called MyDomain0. ...
    (microsoft.public.win2000.active_directory)