Solved

ERROR_TOO_MANY_NAMES

Posted on 2000-02-15
6
383 Views
Last Modified: 2013-12-23
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?
0
Comment
Question by:swartwe
6 Comments
 
LVL 2

Expert Comment

by:red031197
ID: 2523183
what services have you got bound to your local card?
0
 
LVL 23

Accepted Solution

by:
Tim Holman earned 100 total points
ID: 2523343
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
 
LVL 8

Expert Comment

by:MaDdUCK
ID: 2523542
what card is it?
0
Zoho SalesIQ

Hassle-free live chat software re-imagined for business growth. 2 users, always free.

 
LVL 3

Expert Comment

by:klover
ID: 2525823
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
 
LVL 3

Expert Comment

by:klover
ID: 2525829
Sorry, that's LMHOSTS file (singular) and it's in c:\winnt\system32\drivers\etc
0
 

Author Comment

by:swartwe
ID: 2540848
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

Featured Post

Zoho SalesIQ

Hassle-free live chat software re-imagined for business growth. 2 users, always free.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

A common practice in small networks is making file sharing easy which works extremely well when intra-network security is not an issue. In essence, everyone, that is "Everyone", is given access to all of the shared files - often the entire C: drive …
Trying to figure out group policy inheritance and which settings apply where can be a chore.  Here's a very simple summary I've written which might help.  Keep in mind, this is just a high-level conceptual overview where I try to avoid getting bogge…
Windows 10 is mostly good. However the one thing that annoys me is how many clicks you have to do to dial a VPN connection. You have to go to settings from the start menu, (2 clicks), Network and Internet (1 click), Click VPN (another click) then fi…
Migrating to Microsoft Office 365 is becoming increasingly popular for organizations both large and small. If you have made the leap to Microsoft’s cloud platform, you know that you will need to create a corporate email signature for your Office 365…

896 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now