Re: A duplicate name has been detected on the TCP network...

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

Ok, Progress:
Our esteemed network Administrator discovered when joining an XP box to the
domain, that he got TWO messages, with a slightly different context. This
being that it was the DOMAIN NAME that was in conflict, not the computer
name. Slightly different light. We do indeed have the domain name in the NT
domain WINS static mapping. Not a normal thing to do, but we did it to
resolve a name resolution issue between the two domains. So, we are
rethinking that process now. WINS, or not to WINS for the meantime on the AD
domain, and perhaps replication between the two domains of WINS.

--Bruce D. Meyer


"Bruce D. Meyer" <bdmeyer44@xxxxxxx> wrote in message
news:%23HNcobqOFHA.2132@xxxxxxxxxxxxxxxxxxxxxxx
>
> "Gerry Hickman" <gerry666uk@xxxxxxxxxxx> wrote in message
> news:%23NIm5FiOFHA.2132@xxxxxxxxxxxxxxxxxxxxxxx
> > Hi Bruce,
> >
> > > We are getting ready to move about a 1,000 users from an NT domain to
an
> > > existing and in use AD domain.
> >
> > You are talking "users" here?
>
> Let me explain:
> We have about 1,000 users, each with a computer. When we move the user, we
> will indeed be moving the computer. To be more specific, and clear aup any
> semantic confusion, for the purpose of this problem, let's just
concentrate
> on one user/computer right now. Since it happens to all that we have
tried,
> I will assume that clearing it up on one, will clear it up on all.
> As far as using a tool, naturally, I am using a tool.
> Right click on My Computer, left click on Properties, left click on the
> network identification tab, left click on the properties button.This is
the
> identification changes tool I guess is what you are asking. I am not doing
> it from the command shell.
> Once I change the computer from the NT domain to the AD domain, the
problem
> arises upon reboot.
> The DHCP Server is on a different subnet and is an NT DHCP server.
> The AD DC's are on the same subnet as the IP given to the newly joined
> computer.
> At the time of the rejoin, before I bring the computer up, I remove the
> computer name from WINS static mapping, and the server manager tool on the
> NT omain. The computer name is not found in ad users and computers on the
AD
> anywhere in our forest. All computers names are always unique.
> The AD domain is working perfectly, but all that is in it is about 10
> servers. Every workstation we have unjoined from the NT domain, and joined
> to the AD domain (about 5 so far) have this problem.
> Their are two full one way non transitive trusts between the NT domain and
> the AD domain. (Actually the entire AD forest, not just this domain) All
> domains within the forest have two way transitive trusts.
>
> If I left anything out that is relevant don't hesitate to let me know.
>
> I am leaning towars the possibility that since elections for master
browser
> are happing in the subnet, and for reasons I am unclear of, workstations
> often win, that perhaps the name is cached by a workstaion serving as a
> master browser. i know how to shut the election process off on
workstations,
> and may do so in the interim.
>
> Bruce D. Meyer
>
>
> >
> > > When we move computers from the NT domain to
> > > the AD domain, they all get the 'A duplicate name exists on network.'
> error.
> >
> > You are now talking "computers"?
> >
> > Can you be a bit more clear on exactly what you're doing and how you're
> > doing it?
> >
> > You say you have a new AD domain which is "in use", are we to assume
> > this one is working perfectly with the computers/users that are already
> > in it?
> >
> > You then say you are going to move computers/users (we don't really know
> > at this stage) from some other domain (?)
> >
> > We don't even know the network topology of these domains, if they are on
> > the same subnet, or if there are trusts between them or anything, and we
> > don't know what you mean by "move"? Do you mean (unjoin/rejoin) or are
> > you using a fancy migration tool?
> >
> > --
> > Gerry Hickman (London UK)
>
>


.

Relevant Pages

  • Re: A duplicate name has been detected on the TCP network...
    ... The DHCP Server is on a different subnet and is an NT DHCP server. ... are happing in the subnet, and for reasons I am unclear of, workstations ... Bruce D. Meyer ...
    (microsoft.public.win2000.setup_deployment)
  • Re: Changing Corporate subnet address
    ... your workstations & servers after changing the subnet, ... Maybe my thinking is flawed but I believe after changing the subnet I ... VPN users must not be using the same IP network as the ... changes if you have no remote connectivity to them. ...
    (microsoft.public.windows.server.dns)
  • Re: Static Vs dynamic IP address in XP SP2
    ... The subnet mask got was ... If there's a DHCP server on the network, ... Please post any reply as a follow-up message in the news group ...
    (microsoft.public.windowsxp.network_web)
  • Re: VPN Drive Mapping to a Client
    ... PC's to a workstation within the SBS network. ... stored on the server, that you don't set up file sharing on your ... enabled, but it is limited to the local subnet. ... Frankly, I would probably not bother with this, as in my view, workstations ...
    (microsoft.public.windows.server.sbs)
  • Re: [SLE] Networking DHCP questions and problems
    ... > I have a Speedstream 5861 DSL modem acting as the dhcp server. ... > All computers get on network, ... I have a printer on the network that is on a different subnet ...
    (SuSE)