Thanks to everyone for helpful the advice! As it turned out, my problem was both hardware and software config related. I had to publish the netbios name of the server in the smb.conf file (overlooked) and I had mistakenly connected two workstation patch cords on shared ports of my hub, negating the server when this particular workstation was running as well. Once these issues were resolved, my MDK 9 box had no problems seeing the shares. Oh, well...live and learn. :-)
BTW, LinNeighborhood does work well! I am glad it was recommended in the listserv. I do have one question, though it probably is irreverent at this point... All workstations are statically addressed with synched, corresponding 'hosts' and 'lmhosts', as they need apply. Therefore, I do not use a WINS server, or any other names resolving server. Host.conf refers to 'bind' for lookup, if 'hosts' should fail. Bind is not installed or running. Should it be? Is it necessary in a small network where everyone knows who everyone is? Thanks for the help. I feel so-o-o-o-o much better having my little baby up and running! T ----- Original Message ----- From: "Technoslick" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, November 30, 2002 11:05 AM Subject: [newbie] Using Samba With Linux Clients I finally got around to setting up my Linux server, with the main idea being to use it for file sharing on the network. As my luck would have it, I cannot get my MDK 9.0 computer to "see" what's inside of my Samba shares off the server. What makes this a concern to me is that I "can" see and use the shares off of all of my Windows PCs, which are made up of Win 2K, Win XP and Win 98 SE. I can see them from my MDK 9.0 box, just can't "see" anything within. Here's a condensed version of my 'smb.conf', with all the commented out sections removed: [global] # workgroup = NT-Domain-Name or Workgroup-Name workgroup = WORKGROUP # server string is the equivalent of the NT Description field server string = Samba Server # This option is important for security. It allows you to restrict # connections to machines which are on your local network. The # following example restricts access to two C class networks and # the "loopback" interface. For more examples of the syntax see # the smb.conf man page hosts allow = 192.168.1. 127. # this tells Samba to use a separate log file for each machine # that connects log file = /var/log/samba/%m.log # Put a capping on the size of the log files (in Kb). max log size = 0 # Security mode. Most people will want user level security. See # security_level.txt for details. security = user # 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 # The following are needed to allow password changing from Windows to # update the Linux system password also. # NOTE: Use these with 'encrypt passwords' and 'smb passwd file' above. # NOTE2: You do NOT need these to allow workstations to change only # the encrypted SMB passwords. They allow the Unix password # to be kept in sync with the SMB password. unix password sync = Yes passwd program = /usr/bin/passwd %u passwd chat = *New*password* %n\n *Retype*new*password* %n\n *passwd:*all*authentication*tokens*updated*successfully* # You can use PAM's password change control flag for Samba. If # enabled, then PAM will be used for password changes when requested # by an SMB client instead of the program listed in passwd program. # It should be possible to enable this without changing your passwd # chat parameter for most setups. pam password change = yes # This parameter will control whether or not Samba should obey PAM's # account and session management directives. The default behavior is # to use PAM for clear text authentication only and to ignore any # account or session management. Note that Samba always ignores PAM # for authentication in the case of encrypt passwords = yes obey pam restrictions = yes # 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 # 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 writable = yes valid users = %S create mode = 0664 directory mode = 0775 # 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 guest ok = no writable = no printable = yes # A publicly accessible directory, read/write to all users. Note that all files # created in the directory by users will be owned by the default user, so # any user with access can delete any other user's files. Obviously this # directory must be writable by the default user. Another user could of course # be specified, in which case all files would be owned by that user instead. [public] path = /home/public valid users = john jill stacy lisa public = no writable = yes printable = no create mask = 0765 # The following two entries demonstrate how to share a directory so that two # users can place files there that will be owned by the specific users. In this # setup, the directory should be writable by both users and should have the # sticky bit set on it to prevent abuse. Obviously this could be extended to # as many users as required. [pmbuc] comment = John's Share path = /home/john valid users = john public = no writable = yes printable = no [sally] comment = Jill's Share path = /home/jill valid users = jill public = no writable = yes printable = no [steph] comment = Stacy's Share path = /home/stacy valid users = stacy public = no writable = yes printable = no [chris] comment = Lisa's Share path = /home/lisa valid users = lisa public = no writable = yes printable = no Because I am statically addressing, 'hosts' and 'lmhosts' (on server only, in the /etc/samba directory) have been created and synced between all clients and server. Of course, SMB usernames and passwords have been created, as well as the corresponding 'home' directories and shares. In my MDK 9.0 box, I went into MCC | Mount Points, did a search for the server, mounted just my shares (to test), and made them mountable by 'user'. Then, I went into Konqueror and looked for my shares. It found them, opened them up (without asking for a password!), but they are empty here. On the server, I have a directory labeled 'Documents'. AI missing something very obvious in my setting up the Samba client in MDK? It seems strange that the Win machines would log on with no sweat, but my Linux box would not. TIA, T ---------------------------------------------------------------------------- ---- Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
