|
 |
|
| |
We'll start with testing the reliable connection first. From the server, try listing its own shares via
smbclient with a
-L option of your server's name. You should get:
server%
smbclient -L server
Added interface ip=192.168.236.86 bcast=192.168.236.255 nmask=255.255.255.0 Server time is Tue Apr 28 09:57:28 1998 Timezone is UTC-4.0
Password:
Domain=[EXAMPLE]
OS=[Unix]
Server=[Samba 1.9.18]
Server=[server]
User=[davecb]
Workgroup=[EXAMPLE]
Domain=[EXAMPLE]
Sharename Type Comment
--------- ---- -------
cdrom Disk CD-ROM
cl Printer Color Printer 1
davecb Disk Home Directories
This machine has a browse list:
Server Comment
--------- -------
SERVER Samba 1.9.18
This machine has a workgroup list:
Workgroup Master
--------- -------
EXAMPLE SERVER
-
If you didn't get a Sharename list, the server is not allowing you to browse any shares. This should not be the case if you've tested any of the shares with Windows Explorer or the NET USE command. If you haven't done the
smbclient
-L
localhost
-U% test yet (see
Section 9.2.5.2"), do it now. An erroneous guest account can prevent the shares from being seen. Also, check the
smb.conf file to make sure you do not have the option
browsable
=
no anywhere in it: we suggest a minimal
smb.conf file (see
Section 9.2.5.1, A minimal smb.conf file") for you to steal from. You need to have
browseable enabled in order to be able to see at least the
[temp] share. -
If you didn't get a browse list, the server is not providing information about the machines on the network. At least one machine on the net must support browse lists. Make sure you have
local
master
=
yes in the
smb.conf file if you want Samba be the local master browser. -
If you got a browse list but didn't get
/tmp, you probably have a
smb.conf problem. Go back to
Section 9.2.4.5." -
If you didn't get a workgroup list with your workgroup name in it, it is possible that your workgroup is set incorrectly in the
smb.conf file. -
If you didn't get a workgroup list at all, ensure that
workgroup
=EXAMPLE is present in the
smb.conf file. -
If you get nothing, try once more with the options
-I
ip_address
-n
netbios_name
-W
workgroup
-d3 with the NetBIOS and workgroup name in uppercase. (The
-d
3 option sets the log /debugging level to 3.)
If you're still getting nothing, you shouldn't have gotten this far. Double back to at least
Section 9.2.3.1, Testing TCP with FTP ," or perhaps
Section 9.2.2.4." On the other hand:
-
If you get "SMBtconX failed. ERRSRV - ERRaccess," you aren't permitted access to the server. This normally means you have a
valid
hosts option that doesn't include the server, or an invalid hosts option that does. -
If you get "Bad password," then you presumably have one of the following:
-
An incorrect
hosts
allow or
hosts
deny line -
An incorrect
invalid
users or
valid
users line -
A lowercase password and OS/2 or Windows for Workgroups clients -
A missing or invalid guest account -
Check what your guest account is (see
Section 9.2.5.2") and verify your
smb.conf file with
testparm
smb.conf
your_hostname your_ip_address (see
Section 9.2.4.5") and change or comment out any
hosts
allow,
hosts
deny,
valid
users or
invalid
users lines. -
If you get "Connection refused," the
smbd server is not running or has crashed. Check that it's up, running, and listening to the network with
netstat, see step
Section 9.2.4.5." -
If you get "Get_Hostbyname: Unknown host name," you've made a spelling error, there is a mismatch between Unix and NetBIOS hostname, or there is a name service problem. Start nameservice debugging with
Section 9.2.5.4." If this works, suspect a name mismatch and go to step
Section 9.2.10, Troubleshooting NetBIOS Names." -
If you get "Session request failed," the server refused the connection. This usually indicates an internal error, such as insufficient memory to fork a process. -
If you get "Your server software is being unfriendly," the initial session request packet received a garbage response from the server. The server may have crashed or started improperly. Go back to
Section 9.2.5.2," where the problem is first analyzed. -
If you suspect the server is not running, go back to
Section 9.2.4.2, Looking for daemon processes with ps" to see why the server daemon isn't responding.
|
|
|
