Windows XP Client registers Wins 00h and 1Eh record with the same name as NT 4.0 domain

Posted on 2004-10-21
Last Modified: 2013-12-28
When I build an XP professional machine on my network, the machine registers a 00h and a 1Eh WINS record with the name of the NT 4.0 domain.  Thus users can not login because this new workstation has regitered itself as the name holder for the domain.  After deleting these records, all is well again until another machine is built on the network.

Any help would be great.

Question by:Charles_R_Irvin
    LVL 7

    Expert Comment

    does this help?;en-us;102878

    1Eh is the "Browse Master" - but this does not replace the PDC for the domain.  Your new machine is probably winning because it's faster than the server.

    See;en-us;136712 for details of registry settings to modify the server's behaviour and increase its chance of winning an election.
    LVL 7

    Expert Comment

    Another note - are the machines that can't log in registered with wins?  Setting the node type to 0x08 (hybrid) (in the DHCP server) is usually as safe bet.  This link has details of how to to this:;en-us;193789


    Author Comment


    None of those have helped.  i am using unattened intallation, and this happens during the gui 39 minute window.  I tried installing wins on a new server, and still did not fix the issue, so i do believe it is with the XP pro machine.  I also moved DHCP to another server, with 0x8 as the node type.  Still, clients are registering even after the build as ooh, and 1eh.

    Thank you, I'll kep trying on this end.

    LVL 7

    Expert Comment

    Are you putting these machines straight into the domain of your PDC, or are they somehow in a workgroup of the same name?

    How many machines are on the network?

    Are they all on the same subnet? are the servers the other side of a slow router or switch?  Is the PDC actually registered with WINS?

    There should be no issue with them being a browse master since on a network with more than 32 desktops there will be one for each 32 machines, including the PDC.  I still think believe the issue may be with the PDC or the network itself.

    Are all of your desktop machines windows XP - or do you have 9x as well?


    Author Comment

    The machines join the domain.  There is a joindomian statement in the unattend.txt.  Also machines thatr are already on the dommain and not built using the unattened method are doing the same thing.  So, I no longer think it is a client side issues any more.

    Ther are only 75 to 80 machines.  

    Same subnet.  Servers on seperate but recent (bought within last 6 months) Nortel switch.  not sure of model, but capable to 1Gbs.

    PDC is registered in wins.

    All clients are XP.  AD domain is on same Subnet but with different name.  No 9x machines.  Win2k3 servers for AD.

    I  did find a rouge  wins server that was not a replication partner, in fact two of them.  Also, moved wins and dhcp on a new server. and deactivated it from the old server.  

    Still same problem.  However, did find this article.  Q161432  this describes the problem very well.  However, moving the wins service and not the database to a new server should have solved this.


    Author Comment

    I also noticed that there wasn't a 1bh record - Domain master browser.  Now there is a 1bh record, but i still can not ping the name of the domain.
    LVL 7

    Accepted Solution

    Is it possible that there's a rougue second DHCP server in the network in a broadband router or something stopping your normal DHCP server from activating properly - you do only have one DHCP server (forgive me if this sounds obvious) - right, because you only have one subnet?  Is the DHCP server also set to do the DDNS registration too for the AD domain too?  The AD domain will use DDNS instead of WINS which causes some anomalies:;en-us;255923

    Are DDNS for your AD domain and WINS talking to each other - sureley they should be.

    Alternately - Could this be it:;en-us;224131

    Clients cannot log on to the domain controllers. Additional NetBIOS traffic problems are: • Loss of connectivity between servers resulting in servers being unavailable in Server Manager.
    • Trust relationships failing to work and failing to be created.
    • Other connectivity where sessions for two-way are required.
    The primary domain controller (PDC) forces a browsing election every 12 minutes and generates the following event:
    Event ID: 8003

    Description: The master browser has received a server announcement from the Windows NT client that believes that it is the master browser for the domain on transport (NetBT). The master browser is stopping or an election is being forced.
    The client computer is located in a different subnet, and UDP 137 and 138 broadcasts are not being forwarded.
    This problem occurs when network logon validation is prevented over a network switch. "

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    Course: From Zero to Hero with Nodejs & MongoDB

    Interested in Node.js, but don't know where to start or how to learn it properly? Confused about how the MEAN stack pieces of MongoDB, Expressjs, Angularjs, and Nodejs fit together? Or how it's even possible to run JavaScript outside of the browser?

    To find the source of an account lockout, look in the local Event Viewer>Security, and look at the Failure Audits, for any that match either SYSTEM, or the UserID in question. If you find any, open the log entry, and you will see a Logon Type entr…
    Recently Microsoft released a brand new function called CONCAT. It's supposed to replace its predecessor CONCATENATE. But how does it work? And what's new? In this article, we take a closer look at all of this - we even included an exercise file for…
    The viewer will learn how to download, install and use CrashPlan from on Windows 7. Open your browser and go to Click get started, it’s free then Click the Download CrashPlan button: Click save in Internet Explorer, the…
    Windows 8 came with a dramatically different user interface known as Metro. Notably missing from that interface was a Start button and Start Menu. Microsoft responded to negative user feedback of the Metro interface, bringing back the Start button a…

    913 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    17 Experts available now in Live!

    Get 1:1 Help Now