ERROR_TOO_MANY_NAMES

I have an NT 4.0 Workstation SP5 which is generating the message "The name limit for the local computer adapter card was exceeded", often when attempting to map to a remote machine's drive.  Technet says that this error is ERROR_TOO_MANY_NAMES with a number of 68.  However, Technet offers no details as to the cause of this problem.  Re-booting the machine typically helps.

Can anyone tell me what the cause of this message is?
swartweAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
Tim HolmanConnect With a Mentor Commented:
Too many NetBIOS names ?
Type NBTSTAT -c
If this list is too big - ie >68 entries, then this could cause the error.
Do you run a lot of NetBIOS applications ?
What's the most common name occurence when you type this command ?

If you type NBTSTAT -R when this problem occurs, what happens ?
(this should clear the cache)
0
 
red031197Commented:
what services have you got bound to your local card?
0
 
MaDdUCKCommented:
what card is it?
0
Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
kloverCommented:
Any time you map a drive to another computer you first have to resolve it's name to an IP address.  Once this address is resolved, your computer stores it in it's NetBIOS name cache so it does not have to be resolved again.  A NBTSTAT -c|more will show you the contents of the cache.

I've looked for, but can't find the registry entry that controls the size of the NetBIOS name cache.  I know it exists and can be increased above 100.  The lifetime of each cache entry can also be changed in the registry.  You may be loading a bunch of names unnecessarily.  Check in the LMHOSTS files for entries with a #PRE after them and delete any you don't need.  Or at least delete the #PRE part.
0
 
kloverCommented:
Sorry, that's LMHOSTS file (singular) and it's in c:\winnt\system32\drivers\etc
0
 
swartweAuthor Commented:
Although the problem has not occurred since I submitted the question (it figures), Tim Holman's explanation sounds reasonable.  I don't want to keep the question open forever.  I also wish to thank klover for the input.  I awarded the points to Tim Holman since he was the first to respond with what I believe to be the answer.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.