NETBIOS NAME IS IN USE ALREADY (108) [SOLUTION EXHAUSTIVE]




NETBIOS NAME IS IN USE ALREADY (108) [SOLUTION EXHAUSTIVE]

If you get this error
NetBIOS name is in use already (108) error

Ok… Whats listed below is the research I did for this issue… Listed below are faqs, solution and other ideas that might work for you…

My conclusion after doing all of that is the following…

UPDATE

AN IT PERSON FIXED THIS ISSUE BY CLEARING COPIER SETTINGS FROM FIREWALL AND CREATING AN EXCEPTION FOR THE COPIER BY PLACING IT OUTSIDE THE DHCP RANGE OF IP ADDRESS SCANNED BY THE ROUTER

1. This is a network issue…
2. Your copier has the same netbios name as some other computer on the network… in some cases this won’t stop you from scanning and printing..
3. You need to find out the ip address and mac address of your copier
4. Do an nbtstat -n, nbtstat -a hostname, nbtstat -c and look for the computer that matches your computer… I haven’t tried this so take it for what its worth… the netbios name is converted to hex so check the hex to see if yours match someone elses…
5. Note… netbios names pick the first 15 characters of hostname… don’t use any spaces or special characters or underscores… just 15 characters… if you use any more its going to be truncated and it may be truncated at sign of special character…
6. Once you find it then create any change that might be needed and scan again…
7. This should actually be number one… this is the work of the network engineer… Not copier technician level work…

If you want to try to work around netbios then try the following…

check for Ip conflict…

Disable NetBEUI and IPX in the nic card…

check for Ip conflict…

Disable NetBEUI and IPX in the nic card…

if that does not work then show the customer how to clear the error until they can fix it…

The reset is the following:

+++++++++++++++++++++++++++++
The work arround is to disconnect the network cable and reboot the machine , once fully rebooted plug in the network cable and all is well. Whenever this problem reoccures follow the same proceedure. Sometimes you may have to reset the ip address and change the hostname before reboot to clear this issue whenever it reoccurs…
+++++++++++++++++++++++++++++++++++++++++++++++++++++

If it reoccurs then try the following

The nuclear option

+++++++++++++++++++++++++++++

record all nic settings…

and clear all the nic settings…

and reinstall nic settings…
+++++++++++++++++++++++++++++

If you are still having issues its for the network engineer…

Listed below is some guidance

+++++++++++++++++++++++++++++++++++++++

lets take the stand its a netbios dos attack…

then check for netbios dos attack
Netbios dos attack windows update patch

Netbios dos attack best practice to remedy issue

It could also be a WINS Database corruption issue

Deletion of WINS Record

Check Lmhosts files and NETBIOS MAPPING

Remove WINS from DHCP SERVER

WINS SERVER AND WINDOWS SERVER 2003

HOW WINS INTERACTS WITH DNS IN WINDOWS SERVER IN ACTIVE DIRECTORY ENVIRONMENT

NETBIOS ALREADY IN USE ON DOMAIN FIX

NETBIOS FAQ I

NETBIOS FAQ II

NETBIOS NAME TOO LONG SO TRUNCATED FAQ I

NETBIOS NAME TOO LONG SO TRUNCATED FAQ II

NETWORK SCANNER TO LOOK FOR DUPLICATE NAMES

NETBIOS DISABLE VIA VBSCRIPT

NETBIOS DISABLE VIA REGISTRY

CASE STUDY OF FINDING A DUPLICATE NAME (ONLY FOR THE BRAVE NETWORK ENGINEER)

This entry was posted in Network and tagged . Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>