[ Pobierz całość w formacie PDF ]
.mistake, or the client software on the PC isn t installed, started, or bound to" If you suspect the server is not running, go back to Looking for daemon pro-TCP/IP.Double back to Chapter 2 or Chapter 3 and ensure you have a clientcesses with ps to see why the server daemon isn t responding.installed and listening to the network.Testing the server with nmblookupRepeat the command with the following options if you had any failures:This will test the advertising system used for Windows name services and brows-" If nmblookup -B client_IP_address succeeds but -B client_name fails,ing.Advertising works by broadcasting one s presence or willingness to providethere is a name service problem with the client s name; go to Troubleshoot-services.It is the part of browsing that uses an unreliable protocol (UDP), anding Name Services. works only on broadcast networks like Ethernets.The nmblookup program broad-" If nmblookup -B 127.1'*' succeeds, but -B client_IP_address fails,casts name queries for the hostname you provide, and returns its IP address andthere is a hardware problem and ping should have failed.See your networkthe name of the machine, much like nslookup does with DNS.Here, the -dmanager.(debug- or log-level) option, and the -B (broadcast address) options direct que-ries to specific machines.Testing the network with nmblookupFirst, we check the server from itself.Run nmblookup with a -B option of yourRun the command nmblookup again with a -d option (debug level) of 2 and aserver s name to tell it to send the query to the Samba server, and a parameter ofparameter of '*' again.This time we are testing the ability of programs (such as_ _SAMBA_ _ as the symbolic name to look up.You should get:nmbd) to use broadcast.It s essentially a connectivity test, done via a broadcast toserver% nmblookup -B server _ _SAMBA_ _ the default broadcast address.Added interface ip=192.168.236.86 bcast=192.168.236.255 nmask=255.255.255.0A number of NetBIOS/TCP-IP hosts on the network should respond with got aSending queries to 192.168.236.86 192.168.236.86 _ _SAMBA_ _positive name query response messages.Samba may not catch all of theYou should get the IP address of the server, followed by the name _ _SAMBA_ _,responses in the short time it listens, so you won t always see all the SMB clientswhich means that the server has successfully advertised that it has a service calledon the network.However, you should see most of them:_ _SAMBA_ _, and therefore at least part of NetBIOS nameservice works.server% nmblookup -d 2 '*'" If you get Name_query failed to find name _ _SAMBA_ _ you may haveAdded interface ip=192.168.236.86 bcast=192.168.236.255 nmask=255.255.255.0specified the wrong address to the -B option, or nmbd is not running.The -B Sending queries to 192.168.236.255Got a positive name query response from 192.168.236.191 (192.168.236.191)option actually takes a broadcast address: we re using a machine-name to getGot a positive name query response from 192.168.236.228 (192.168.236.228)a unicast address, and to ask server if it has claimed _ _SAMBA_ _.Got a positive name query response from 192.168.236.75 (192.168.236.75)Got a positive name query response from 192.168.236.79 (192.168.236.79)" Try again with -B ip_address, and if that fails too, nmbd isn t claiming theGot a positive name query response from 192.168.236.206 (192.168.236.206)name.Go back briefly to Testing daemons with testparm to see if nmbd isGot a positive name query response from 192.168.236.207 (192.168.236.207)running.If so, it may not claiming names; this means that Samba is not provid- Got a positive name query response from 192.168.236.217 (192.168.236.217)Got a positive name query response from 192.168.236.72 (192.168.236.72) 192.168.ing the browsing service a configuratiuon problem.If that is the case, make236.86 *sure that smb.conf doesn t contain the option browsing=no. 282 Chapter 9: Troubleshooting Samba The Fault Tree 283 There is a network problem you ve not yet diagnosed.Identifying what s in use There is no browse master.Add the configuration option localmaster=First, see if both the server and the client are using DNS, WINS, NIS, or hosts filesyes to your smb.conf file.to look up IP addresses when you give them a name.Each kind of machine willhave a different preference: No shares are marked browsable in the smb.conf file." Windows 95 and 98 machines will look in WINS and LMHOSTS files first, then" If you receive the message \\server is not accessible, then:broadcast, and finally try DNS and hosts files. You have the encrypted password problem" NT will look in WINS, then broadcast, LMHOSTS files, and finally hosts and The machine really isn t accessibleDNS. The machine doesn t support browsing" Windows programs using the WINSOCK standard (like PC-NFSs) will use hostsfiles, DNS, WINS, and then broadcast.Don t assume that if a different pro-Other Things that Failgram s name service works, the SMB client program s name service will!If you ve made it here, either the problem is solved or it s not one we ve seen.The" Samba daemons will use LMHOSTS, WINS, the Unix host s preference, andnext sections cover troubleshooting tasks that are required to have the infrastruc-then broadcast.ture to run Samba, not Samba itself
[ Pobierz całość w formacie PDF ]
