"A duplicate name exists on the network"

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

Upon boot up, a Windows-System Error appears stating "A duplicate name exists
on the network". I appears that the duplicate name is actually my server
workstation. Windows Explorer lists two sets of identical My Computer and My
Network Places under a single Desktop. It appears that my computer has set up
a mirror image of itself both of which appear when setting up the Network
Connections.

The workstation name is different than the workgroup name which is just
WORKGROUP. Just a little background: I have a dual processor (Supermicro)
PIII 1.26MHz motherboard with an Intel onboard 10/100 LAN chipset adapter
(connected to Cox Cable ISP with dynamic IP addressing) and an Intel
EtherExpress Pro/100 PCS LAN Adaptec (connected to NAS IDSL with five static
IP addresses). The cable modem is connected to a Netgear Super 108 Wireless
router with both wireline and wireless connection to desktops. The ISDL modem
is connected to a Linksys 10/100 Hub. My server/workstation is connected to
both the router and the hub. Other connections to the hub include an HP
printer, Intel Netport Express print server, another workstation and a laptop
all with assigned static IP addresses. Everything worked fine until I
disconnected the server/workstation from the hub and/or router as I was
attempting to rearrange the jumper cables. Upon reconnecting the jumpers a
message appeared that the computer had found a new network. I performed a
warm reboot since I was unable to escape out of that message. Now I am unable
to connect to the cable service, cannot locate the print server and must
manually re-establish the connection to the other computers. The duplicate
network only appears upon boot up when both LAN connections are plugged into
their respective LAN adapters. I am hoping to be able to correct the problem
without reinstalling the operating system.

How do I remove this second/duplicate name/image?

.

Relevant Pages

  • Re: Daily Server Report (Critical Errors, Event ID: 537)
    ... Does this issue happen on client workstation or server? ... Does your server and all clients' workstation work well now? ... issue in your Network? ...
    (microsoft.public.windows.server.sbs)
  • Re: Daily Server Report (Critical Errors, Event ID: 537)
    ... Also, Logon type of 3 is a network logon, this is considered a ... Does this issue happen on client workstation or server? ... Does your server and all clients' workstation work well now? ... issue in your Network? ...
    (microsoft.public.windows.server.sbs)
  • Re: Daily Server Report (Critical Errors, Event ID: 537)
    ... Also, Logon type of 3 is a network logon, this is considered a ... Does this issue happen on client workstation or server? ... Does your server and all clients' workstation work well now? ... issue in your Network? ...
    (microsoft.public.windows.server.sbs)
  • Re: [Fwd: Re: Mainframe not a good architecture for interactive was Re: What is the future of COBOL
    ... programmers do not understand the inner working of CICS and that CICS ... does not keep track of ALL terminals in a mainframe network. ... >> to a Web Server, this means that for an equal number of clients, a Web ... >>server is keeping track of 5 times the connections. ...
    (comp.lang.cobol)
  • Strange Connection Issues with Win2003 Server & XP Client
    ... System Error 53 Has Occured - The network path was not found - this was ... I can ping the server, I can "net view" & "net view server" the server ... shares, but not the actual shares, I get the same messages as above. ... workstation on the same network, ...
    (microsoft.public.windowsxp.help_and_support)