Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
en:guides:samba [2013/04/28 19:00] – [How does it work?] emgien:guides:samba [2013/04/30 20:12] (current) – linea
Line 18: Line 18:
 Enter User's password: **** Enter User's password: ****
 </code> </code>
-This will provide a list of the shares available on the machine called nas like the example below: +This will provide a list of the shares available on \\nas. The result should look similar to the example below: 
 <code> <code>
 Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.6.3-31a.osstech] Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.6.3-31a.osstech]
Line 39: Line 39:
 #  # 
 </code> </code>
-Although not strictly required, it is recommended to add the server name to /etc/hosts for name resolution when it has a fixed ip address. Because we are running on Linux we need to 'escape' the backslashes in the UNC path, effectively needing twice the number of them like this: +From the above example, we are interested in access to Sharename 'share'. Although not strictly required, it is recommended to add the server name to /etc/hosts for name resolution when it has a fixed ip address. Because we are running on Linux we need to 'escape' the backslashes in the UNC path, effectively needing twice the number of them. Accessing \share on \\nas goes like this: 
 <code> <code>
 # smbclient \\\\nas\\share # smbclient \\\\nas\\share
Line 45: Line 45:
 smb: \>  smb: \> 
 </code> </code>
-At this prompt you can issue ftp-style commands to browse the file system and read/write files. +At the prompt you can issue ftp-style commands to browse the file system and read/write files. Typing **help** gives you a summary of the options:  
 +<code> 
 +smb: \> help 
 +?              allinfo        altname        archive        blocksize       
 +cancel         case_sensitive cd             chmod          chown           
 +close          del            dir            du             echo            
 +exit           get            getfacl        hardlink       help            
 +history        iosize         lcd            link           lock            
 +lowercase      ls             l              mask           md              
 +mget           mkdir          more           mput           newer           
 +open           posix          posix_encrypt  posix_open     posix_mkdir     
 +posix_rmdir    posix_unlink   print          prompt         put             
 +pwd            q              queue          quit           readlink        
 +rd             recurse        reget          rename         reput           
 +rm             rmdir          showacls       setmode        stat            
 +symlink        tar            tarmode        translate      unlock          
 +volume         vuid           wdel           logon          listconnect     
 +showconnect    ..             !               
 +smb: \> quit 
 +# 
 +</code>
  
 Fortunately you can also access a Windows share by mounting it on your box like this:  Fortunately you can also access a Windows share by mounting it on your box like this: 
Line 66: Line 86:
 # #
 </code> </code>
-If there is no access-denied-message in reply to the password, it means the share is mounted and can be accesssed from your box. That's basically it! +If there is no access-denied-message in reply to the password, it means the share is mounted and can be accessed from your box. That's basically it! 
 <note tip>The password must be the admin password for your storage device. This may not work when you have enabled user-based security. In some cases the mount may be read-only. </note> <note tip>The password must be the admin password for your storage device. This may not work when you have enabled user-based security. In some cases the mount may be read-only. </note>
 Many of the problems with Samba are caused by a lack of understanding the Windows security mechanism. In its basic version, which is still used most of the time, this is user-based security so you will need a **valid windows user account** to access the file share. When in trouble, verify the access is working from a windows machine and use the same credentials under Linux.  Many of the problems with Samba are caused by a lack of understanding the Windows security mechanism. In its basic version, which is still used most of the time, this is user-based security so you will need a **valid windows user account** to access the file share. When in trouble, verify the access is working from a windows machine and use the same credentials under Linux. 
Line 80: Line 100:
  
 The procedure to add a user to your samba server: The procedure to add a user to your samba server:
-<code> 
-[a] First add Linux user using the adduser command. 
  
-[b] Then add the same user name to Samba using: smbpasswd -a+First add Linux user using the adduser command. 
 +<code># adduser smbuser01 
 +Changing password for smbuser01 
 +New password:  
 +Retype password:  
 +Password for smbuser01 changed by root 
 +</code>
  
-Use: smbpasswd --help to view the options. +Then add the same user name to Samba using: smbpasswd -a 
 +<code> 
 +# smbpasswd -a smbuser01 
 +New SMB password: 
 +Retype new SMB password: 
 +Added user smbuser01. 
 +# 
 </code> </code>
 +Use: smbpasswd -h to view the options. 
  
 The file shares and printers you want to allow your Windows clients access to can be defined in the Samba configuration file which is: **/etc/samba/smb.conf** The file shares and printers you want to allow your Windows clients access to can be defined in the Samba configuration file which is: **/etc/samba/smb.conf**
 
en/guides/samba.1367175651.txt.gz · Last modified: by emgi