samba:test_nmbd
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
samba:test_nmbd [2016/07/10 10:28] – peter | samba:test_nmbd [2020/07/23 19:02] (current) – old revision restored (2016/07/10 11:19) 192.99.15.199 | ||
---|---|---|---|
Line 38: | Line 38: | ||
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 | ||
- | |||
- | ===== Check if nmbd was able to successfully register the domain name ===== | ||
- | |||
- | <code bash> | ||
- | nmblookup -U 127.0.0.1 ShareWiz | ||
- | </ | ||
- | |||
- | Result: | ||
- | |||
- | < | ||
- | querying ShareWiz on 127.0.0.1 | ||
- | 192.168.0.2 ShareWiz< | ||
- | 192.168.1.2 ShareWiz< | ||
- | </ | ||
- | |||
- | If an domain was not found by nmbd the result would be: | ||
- | |||
- | < | ||
- | querying xyz on 127.0.0.1 | ||
- | name_query failed to find name xyz | ||
- | </ | ||
- | |||
- | 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. | ||
- | |||
- | <code bash> | ||
- | nmblookup -B 192.168.1.255 ShareWiz | ||
- | </ | ||
- | |||
- | Result: | ||
- | |||
- | < | ||
- | querying SHAREWIZ on 192.168.1.254 | ||
- | name_query failed to find name SHAREWIZ | ||
- | </ | ||
- | |||
- | In this example, the name ShareWiz has been registered by a host at address 192.168.1.3 and not our Samba server. | ||
samba/test_nmbd.1468146482.txt.gz · Last modified: 2020/07/15 09:30 (external edit)