Red Hat 의 system-config-samba 에서 사용자를 추가하면 리스트에 등록이 되어야 하지만
기본으로 하면 등록은 되지만 사용자 박스에 사용자가 등록이 되지 않는다.
그리고 다시 똑같은 사용자로 추가를 하려고 하면 존재하는 사용자라고 등록이 안 된다.
이 문제는 samba 의 smb.conf 에 passdb backend 설정이 기본 tdbsam 으로 되어 있기 때문이다.
이 옵션을 smbpasswd 으로 바꾸면 사용자 리스트에 사용자가 등록이 된다.
smb.conf 에 들어있는 주석 내용
# Security can be set to user, share(deprecated) or server(deprecated) # # Backend to store user information in. New installations should # use either tdbsam or ldapsam. smbpasswd is available for backwards # compatibility. tdbsam requires no further configuration.
이 부분에
passdb backend = tdbsam 를 passdb backend = smbpasswd 로 변경 하면 된다.
그러면 기존 passdb.tdb 형식으로 저장되던게 smbpasswd 파일로 바뀐다.
주의 할점은 tdbsam 에서 추가한 사용자는 smbpasswd 에서 콘트롤하기 힘들다는 것 이다. 그래서 tdbsam에서 추가한 사용자를 다 삭제하고 smbpasswd 에서 새로 추가를 해줘야 한다.
If you just need to grab a file, or put a file on the server, but don't need a constant connection, it is best to either browse to the share using Gnome/KDE's built in Samba browser, or to use the command line client smbclient. This assumes you have the samba-client package installed provided by your distribution.
Using smbclient is very similar to using a command-line FTP client. Here are a few useful commands:
$ smbclient -L //hostname
Where hostname is the NetBIOS name of the machine you wish to connect to. After being prompted for a password (enter no password for anonymous login) this command will give you a list of available shares on the machine, plus some other information.
To connect to a share, you must specify the share name, in the format //hostname/sharename where sharename could be the name of a file share, or a printer, or anything else Samba can handle.
$ smbclient //joescomp/joe
After entering joe's password, you are given an smb: \> prompt where you may enter commands much like an FTP client. Some commands include ls, get, put, rm, help and quit. The help command will list all the commands, and help command will give help on a certain command.
If you need a permanent connection to your Samba server, it is best to mount the share on some local directory. This is done much like mounting any other volume, but there are some syntactical differences.
Note: It is not a good idea to mount Samba shares on a computer which might be changing networks a lot, like a laptop. If you forget to unmount the share before disconnecting from the network, you could experience some problems later if your computer tries to connect with the share, even if just to unmount it. It may think that the share is busy or take a long time to disconnect.
In order to do this you must have cifs or smbfs modules built into your kernel or available as a module. To check, execute:
# modinfo cifs
or
# modinfo smbfs
If you are mapping a share with many non-ASCII (ie: non-US or American) based file names, the legacy smbfs module can create problems accessing those files. The newer cifs (Common Internet File System) module has greater support for correctly recognizing and translating those characters.
Note: Use the cifs module as demonstrated above when connecting to a Samba or Windows 2000 and above server. smbfs is the old module used to connect to Windows 98 style shares. If one doesn't work, try the other. A noteworthy mention is Netware's CIFS implementation, which is not compatible with the cifs module. Use smbfs instead.
To mount a share one time, use the mount command as root. First you will need to create a directory to mount the share on.
# mkdir -p /mnt/joescomp/joe
# mount -t cifs //joescomp/joe -o username=joe /mnt/joescomp/joe
You will then be prompted for a password, and if connection is successful your share will now be mounted. To unmount a share, use the umount command as root.
# umount /mnt/joescomp/joe
This command will unmount the share. To unmount all mounted Samba shares, do this:
Linux can automatically mount your network shares. First it is a good idea to make sure that manual mounting works. To set your computer up to automatically mount a share whenever it boots, or so that a non-privileged user can mount the shares, you can add them to your /etc/fstab file. You must be root to edit this file.
The user option means that any user (not just root) can mount and unmount the share. For this to work, however, the mount.cifs utility must be setuid root, and the user who will do the mounting must own the mount point directory.
# chmod u+s /sbin/mount.cifs
# chown joe:joe /mnt/joescomp/joe
Note: You can leave out the password option if you do not want your password stored in this file as clear text. This way, every time you mount this share it will ask you for the password.
With newer smbfs and cifs modules, it is better to place the username/password combination in a file, and reference it with the credentials option. Create the file /etc/samba/joe.cred, make it only visible to root, and then update your /etc/fstab entry.
Tracked from Sharky's Blog 2008/02/29 11:02
Delete
http://linux-cifs.samba.org/mount -t cifs -o iocharset=utf8,codepage=cp949,username=xxx,password=yyy //111.111.111.111/test /tesCIFS (Common Internet File System)CIFS는 프로그램들이 인터넷을 통해 원격지 컴퓨터 상의 파일이나 서비스에 대한 요구를 할 수 있게 하는 프로토콜로서, 현재 표준으로 제안되었다. CIFS는 ...
[global] dos charset = 949 unix charset = euc-kr hide files = /.*/TheVolumeSettingsFolder/Network Trash Folder/Temporary Items/ workgroup = File Server #coding system = KS8 #client code page = 949
# server string is the equivalent of the NT Description field server string = File 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.100. 211.45.120.105
# 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
# It should not be necessary to spell out the print system type unless # yours is non-standard. Currently supported print systems include: # bsd, sysv, plp, lprng, aix, hpux, qnx, cups printing = cups
# Uncomment this if you want a guest account, you must add this to /etc/passwd # otherwise the user "nobody" is used # guest account = nobody
# 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 = 50
# Security mode. Most people will want user level security. See # security_level.txt for details. security = user #security = share #security = server
# Use password server option only with security = server # The argument list may include: # password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name] # or to auto-locate the domain controller/s # password server = * #; password server = <NT-Server-Name>
# Password Level allows matching of _n_ characters of the password for # all combinations of upper and lower case. ; password level = 8 ; username level = 8
# 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 is needed to keep smbclient from spouting spurious errors # when Samba is built with support for SSL. ; ssl CA certFile = /usr/share/ssl/certs/ca-bundle.crt
# 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
# Unix users can map to different SMB User names #; username map = /etc/samba/smbusers
# Using the following line enables you to customise your configuration # on a per machine basis. The %m gets replaced with the netbios name # of the machine that is connecting ; include = /etc/samba/smb.conf.%m
# 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
# Configure Samba to use multiple interfaces # If you have multiple network interfaces then you must list them # here. See the man page for details. ; interfaces = 192.168.12.2/24 192.168.13.2/24
# Configure remote browse list synchronisation here # request announcement to, or browse list sync from: # a specific host or from / to a whole subnet (see below) ; remote browse sync = 192.168.3.25 192.168.5.255 # Cause this host to announce itself to local subnets here ; remote announce = 192.168.1.255 192.168.2.44
# Browser Control Options: # set local master to no if you don't want Samba to become a master # browser on your network. Otherwise the normal election rules apply ; local master = no
# OS Level determines the precedence of this server in master browser # elections. The default value should be reasonable ; os level = 33
# Domain Master specifies Samba to be the Domain Master Browser. This # allows Samba to collate browse lists between subnets. Don't use this # if you already have a Windows NT domain controller doing this job ; domain master = yes
# Preferred Master causes Samba to force a local browser election on startup # and gives it a slightly higher chance of winning the election ; preferred master = yes
# Enable this if you want Samba to be a domain logon server for # Windows95 workstations. ; domain logons = yes
# if you enable domain logons then you may want a per-machine or # per user logon script # run a specific logon batch file per workstation (machine) ; logon script = %m.bat # run a specific logon batch file per username ; logon script = %U.bat
# Where to store roving profiles (only for Win95 and WinNT) # %L substitutes for this servers netbios name, %U is username # You must uncomment the [Profiles] share below ; logon path = \\%L\Profiles\%U
# Windows Internet Name Serving Support Section: # WINS Support - Tells the NMBD component of Samba to enable it's WINS Server wins support = yes
# WINS Server - Tells the NMBD components of Samba to be a WINS Client # Note: Samba can be either a WINS Server, or a WINS Client, but NOT both ; wins server = w.x.y.z
# WINS Proxy - Tells Samba to answer name resolution queries on # behalf of a non WINS capable client, for this to work there must be # at least one WINS Server on the network. The default is NO. ; wins proxy = 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 = yes
# Case Preservation can be handy - system default is _no_ # NOTE: These can be set on a per share basis ; preserve case = no ; short preserve case = no # Default case is normally upper case for all DOS files ; default case = lower # Be very careful with case sensitivity - it can break things! ; case sensitive = no mangle case = no preserve case = yes short preserve case = yes
#============================ Share Definitions ============================== #[homes] # comment = Home Directories # browseable = no # writable = yes # valid users = %S # create mode = 0664 # directory mode = 0775 # If you want users samba doesn't recognize to be mapped to a guest user ; map to guest = bad user
# Un-comment the following and create the netlogon directory for Domain Logons ; [netlogon] ; comment = Network Logon Service ; path = /usr/local/samba/lib/netlogon ; guest ok = yes ; writable = no ; share modes = no
# Un-comment the following to provide a specific roving profile share # the default is to use the user's home directory ;[Profiles] ; path = /usr/local/samba/profiles ; browseable = no ; guest ok = 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 guest ok = no writable = no printable = yes
# This one is useful for people to share files ;[tmp] ; comment = Temporary file space ; path = /tmp ; read only = no ; public = yes
# A publicly accessible directory, but read only, except for people in
#
# A private directory, usable only by fred. Note that fred requires write # access to the directory. #;[fredsdir] #; comment = Fred's Service #; path = /usr/somewhere/private #; valid users = fred #; public = no #; writable = yes #; printable = no
# a service which has a different directory for each machine that connects # this allows you to tailor configurations to incoming machines. You could # also use the %U option to tailor it by user name. # The %m gets replaced with the machine name that is connecting.
# 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 # 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. # 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. [Storage] comment = File Server path = /home valid users = root public = no writable = yes printable = no directory mask = 0775 create mask = 0775
(0) 
(0)
