Okay, let's take a look only at the variables that are set in your smb.conf file. My comments are bracketed by << and >>.
The easiest way to find out what each variable does is to ensure SWAT is running on your samba server and use your webrowser to hit SWAT http://linux:901. Of course, you'll need to have SWAT configured correctly to allow you access. Anyway, once you're in SWAT, click on the GLOBALS icon to view the Global Variables. click the "help" link next to each variable that you want to find out more information about. Otherwise, go to the samba.org website and dig up the documentation. Dwight... [global] # workgroup = NT-Domain-Name or Workgroup-Name workgroup = LIHOLIHO netbios name = linux << this workgroup should be the same as your Win2K boxes >> # server string is the equivalent of the NT Description field server string = Linux Server # if you want to automatically load your printer list rather # than setting them up individually then you'll need this printcap name = /etc/printcap load printers = yes # Uncomment this if you want a guest account, you must add this to /etc/passwd # otherwise the user "nobody" is used guest account = fileserver << this username will be used for access to services/shares that have "guest ok" set. the appropriate rights should be given to the files/directories you want this user to access. >> # this tells Samba to use a separate log file for each machine # that connects log file = /var/log/samba/log.%m # Put a capping on the size of the log files (in Kb). max log size = 50 # Security mode. Most people will want user level security. See # security_level.txt for details. security = share << share level security means that your clients don't need to log on with a valid username/password before connecting to a share...you should use this if you use usernames on the Win2K box that don't exist on the unix box. basically, the client sends a password on a per-share basis and samba does a bunch of checks to find the correct username associated with that password. since your share is configured with "guest ok" then samba verifies that the guest account username "fileserver" is being used. there's a whole pile of stuff to read in the samba documentation about security level >> # You may wish to use password encryption. Please read # ENCRYPTION.txt, Win95.txt and WinNT.txt in the Samba documentation. # Do not enable this option unless you have read those documents encrypt passwords = yes smb passwd file = /etc/samba/smbpasswd << you are using password encryption; verify that you have created usernames/passwords in the /etc/samba/smbpasswd file that matches usernames/passwords being sent from Win2K...either that or you have to set the security level to server/domain to cause samba to authenticate using a third server >> # Most people will find that this option gives better performance. # See speed.txt and the manual pages for details socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 # Windows Internet Name Serving Support Section: # WINS Support - Tells the NMBD component of Samba to enable it's WINS Server wins support = yes # DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names # via DNS nslookups. The built-in default for versions 1.9.17 is yes, # this has been changed in version 1.9.18 to no. dns proxy = no #============================ Share Definitions ============================== [homes] comment = Home Directories browseable = no writeable = yes create mask = 664 directory mask = 775 [fileserver] comment = File Server path = /var/fileserver writeable = yes guest ok = yes browseable = yes # NOTE: If you have a BSD-style print system there is no need to # specifically define each individual printer [printers] comment = All Printers path = /var/spool/samba browseable = no # Set public = yes to allow user 'guest account' to print printable = yes
