User Tools

Site Tools


ubuntu:samba:test_nmbd

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
ubuntu:samba:test_nmbd [2020/07/15 09:30] – external edit 127.0.0.1ubuntu:samba:test_nmbd [2023/06/09 16:52] (current) peter
Line 14: Line 14:
 </code> </code>
  
-If nmbd does not appear in the list reported by ps, it should be started as root using the normal means (/usr/local/samba/bin/nmbd -D).+<WRAP info> 
 +**NOTE:**  If **nmbd** does not appear in the list reported by ps, it should be started as root using the normal means
 + 
 +<code bash> 
 +/usr/local/samba/bin/nmbd -D 
 +</code> 
 + 
 +</WRAP> 
 + 
 +---- 
 + 
 +===== Use the __SAMBA__ NetBIOS Name =====
  
 Samba servers have a special NetBIOS name, **<nowiki>__SAMBA__</nowiki>**, to which they will always respond. Samba servers have a special NetBIOS name, **<nowiki>__SAMBA__</nowiki>**, to which they will always respond.
  
-By querying the server for this name, we can verify that nmbd is working correctly. The **-U** flag is used to specify the address to which the query should be sent.+  * By querying the server for this name, we can verify that nmbd is working correctly. 
 +  * The **-U** flag is used to specify the address to which the query should be sent.
  
 <code bash> <code bash>
Line 32: Line 44:
 </code> </code>
  
-If nmbd is not running, the following error message will be shown:+<WRAP info> 
 +**NOTE:**  If **nmbd** is not running, the following error message will be shown:
  
 <code bash> <code bash>
Line 38: Line 51:
 </code> </code>
  
-This can also be caused by not including the loopback interface name for the interfaces parameter in smb.conf and setting bind interfaces only = yes+  * This can also be caused by not including the loopback interface name for the interfaces parameter in smb.conf and setting **bind interfaces only = yes**. 
 + 
 +</WRAP>
  
 ---- ----
Line 56: Line 71:
 </code> </code>
  
-If an domain was not found by nmbd the result would be:+<WRAP info> 
 +**NOTE:**  If an domain was not found by nmbd the result would be:
  
 <code bash> <code bash>
Line 65: Line 81:
 A possible reason for a failure is that the server was unable to register its NetBIOS name. A possible reason for a failure is that the server was unable to register its NetBIOS name.
  
-If this is the case, you can locate the host that currently owns the name by sending a name query request to the broadcast address of the local subnet.+</WRAP> 
 + 
 +---- 
 + 
 +===== Use the Broadcast Address ===== 
 + 
 +If the NetBIOS name is unregistered, you can locate the host that currently owns the name by sending a name query request to the broadcast address of the local subnet.
  
 <code bash> <code bash>
Line 78: Line 100:
 </code> </code>
  
-In this example, the name ShareWiz has been registered by a host at address 192.168.1.3 and not our Samba server.+<WRAP info> 
 +**NOTE:**  In this example, the name ShareWiz has been registered by a host at address 192.168.1.3 and not our Samba server.
  
-To correct this problem is to rename the rogue machine.+  * To correct this problem is to rename the rogue machine.
  
 If it failed the result would be: If it failed the result would be:
Line 88: Line 111:
 name_query failed to find name ShareWiz name_query failed to find name ShareWiz
 </code> </code>
 +
 +</WRAP>
  
ubuntu/samba/test_nmbd.1594805433.txt.gz · Last modified: 2020/07/15 09:30 by 127.0.0.1

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki