Windows System Error - A duplicate name exists on the netw..

[jtretired]

i just installed a belkin wireless router and at start up of the pc i receive the error message windows error "a duplicate name exists on the network" How do i f ix?

 

[Cyberat_88]

If you know nothing about networking, run the wizard software included with the router. It may add a startup app. but it's usually ok.

 

[Hawkeye22]

Right-click on my computer and select properties. Select the "computer name tab". make sure the name doesn't match other computers on the network. If it does, click the "change" button and rename the computer.

 

[vinothmams]

Otherwise You have to Change The Static Ip to Dynamic Ip.. START---- CONTROL PANEL ---- NETWORK CONNECTIONS---- RIGHT CLICK --- PROPERTIES ---- DOUBLE CLICK TCP/IP/ PROTOCOL--- CHANGE TO IP AUTOMATICALLY..

 

[Hawkeye22]

Otherwise You have to Change The Static Ip to Dynamic Ip.. START---- CONTROL PANEL ---- NETWORK CONNECTIONS---- RIGHT CLICK --- PROPERTIES ---- DOUBLE CLICK TCP/IP/ PROTOCOL--- CHANGE TO IP AUTOMATICALLY..

The error said "duplicate name", not "duplicate IP address".

 

[Christopher Pilot]

I just had this issue occur myself on my own home network.

The problem was only presenting (completely out of the blue) on my wife's notebook computer, and then only she had the wireless connection and wired LAN connection going at the same time. I assumed it was her workstation getting two IP addresses using the same NetBios name. Yes, I realize that should not be a problem, but it seemingly was. It disabled all network printing/filesharing from/to this computer as well. I tried a variety of different solutions (page after page of Google results) to resolve this problem to no avail.

The problem turned out to be that my home workgroup had the same name as one of my wireless routers. For example, my workgroup name was BUBBANET and I named one of my wireless routers BUBBANET (and then the other two wireless routers were named BUBBANET2 and BUBBANET3). My home network has been setup this way for almost six years now, so I'm not sure why it was a problem all of sudden and why it was only with her notebook, because my desktop computer never encountered this error even though it is in the same workgroup.

I suspect it was a Windows update somewhere along the line that caused this to start happening out of the blue. Anyway, my suggestion would be to think about more than just workstation name, because it apparently can possibly be a lot more complicated than that. I would verify the name of all devices, workgroups, etc., and make sure there are not duplicates.

Good luck and hope this helps someone.