Inappropriate error? 64:the specified network name no longer avail



I have a Windows 2000 Advanced Server SP4 (Server1), which is a member of a
network workgroup, and a Windows Server 2003 SP1 (Server 2), which is a
member of an active directory on one MS Windows 2000 Advanced Server SP4
(Server 3).

On the Server1 I got this error:

Event Type: Error
Event Source: NetBT
Event Category: None
Event ID: 4319
Date: 2006.07.21.
Time: 4:34:30
User: N/A
Computer: Server1
A duplicate name has been detected on the TCP network. The IP address of
the machine that sent the message is in the data. Use nbtstat -n in a command
window to see which name is in the Conflict state.
0000: 00040000 00540001 00000000 c00010df
0010: 00000101 00000000 00000000 00000000
0020: 00000000 00000000 0a0a0509

The IP address in the data belongs to yet another Windows 2000 Server (SP4)
(Server4), which apparently was the one to start the conflict and which
belongs to the same workgroup as the Server1. The thing is that the servers
actually have different computer names. A colleague of mine suggested that
the name conflict occured because at some stage both the Server1 and the
Server4 were master browsers for the workgroup at the same time and the
master browser NetBIOS name conflict arised.

After that I got another error message:

Event Type: Warning
Event Source: MRxSmb
Event Category: None
Event ID: 8005
Date: 2006.07.21.
Time: 4:34:31
User: N/A
Computer: Server1
The browser has received a server announcement indicating that the computer
Server1 is a master browser, but this computer is not a master browser.
0000: 00000000 00580002 00000000 80001f45
0010: 00000000 00000000 00000000 00000000
0020: 00000000 00000000

which kinda confirms my colleague's suggestion.

Now, the problem. After I got the error on the Server1 a script ran on it
and tried to map a network drive on the Server2:

net use u: \\10.Server2.IP.Address.\ShareName DomainUserPassword

The command returned this error:

System error 64 has occurred. The specified network name is no longer

I suspect that the error was caused by the name conflict, which I observed
earlier. But then, why did it occur if the server name isn't used in the

Maybe the errors aren't related?

Any suggestions on how to avoid situations like this in the future?

-- Many thanks, Oskar


Thanks Adrian. I'll chek that out.

I would also like to add to my original message that the problem was with
the first run of the script - there were no errors in the subsequent runs and
I did nothing (the name conflict wasn't long).

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question