Since the rise of the day 1:00 documentation services do want to samba, I began experiencing the pain after nearly a month of
Internet data, read, or not to get, you prawn help me, otherwise, I have too bad New Year
The following are my allocation :
Redhat 7.1 server :
Bringing their samba version 7.1
Smb.conf content of the document :
# This is the main Samba configuration file. You should read the
# Smb.conf (5) manual page in order to understand the options listed
# Here. Samba has a huge number of configurable options (perhaps too
# Many!), most of which are not shown in this example
#
# Any line which starts with a (semi-colon) or a # (hash)
# Is a comment and is ignored. In this example we will use a #
# For commentry and a; for parts of the file that you configure
Council may wish to enable
#
# NOTE : Whenever you modify this file you should run the command "testparm"
# To check that you have not many any basic syntactic errors.
#
#======================= Global Settings =====================================
[global]
Netbios name = Linux
# = NT-Domain-Name or workgroup Workgroup-Name
Workgroup = MYGROUP
= User security
Encrypt passwords = yes
Guest account = guest
Wins support = yes
Local master = yes
Os level = 99
Domain master = yes
Preferred master = yes
Netbios name = Linux
# = NT-Domain-Name or workgroup Workgroup-Name
# 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.0. 192.168.1. 127.
# If you want to automatically load your printer list rather
# Than setting them up individually and 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
# Non-standard is yours. Currently supported print systems include :
# Bsd, sysv, plp, lprng, aix, hpux, qnx
Printing = lprng
# Uncomment this if you want a guest account, you must add this to /etc/passwd
# Otherwise the user "nobody" is used
; Guest account = pcguest
# 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 kilobytes).
Max log size = 0
# Security mode. Most people will want user level security. See
# Security_level.txt for details.
; Security = user
# Use password server option only with security = server or
# = Domain security
; Password server = "NT-Server-Name>
# Password Level allows matched of characters of the password for _n_
# 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 sytsem 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
# SMB the encrypted 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 = *New*UNIX*password* %n\n *ReType*new*UNIX*password* %n\n *passwd Chat : *all*authentication*tokens*updated*successfully*
# Unix users can map to different SMB User names
Username = /etc/samba/smbusers map
# Using the following line enables you to customize 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
# 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 synchronization 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 not specified 't want to become a master Samba
# CPU on your network. Otherwise the normal election rules apply
; No local master =
# OS Level determines the precedence of this server in master CPU
# 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 election on startup CPU
# And gives it a slightly higher chance of winning the election
; Preferred master = yes
# Enable this if you want to be a domain logon server for Samba
# 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 solvents file per workstation (machine)
; Logon script = %m.bat
# Run a specific solvents file per logon username
; Logon script = %U.bat
# All NetBIOS names must be resolved to IP Addresses
# 'Name Resolve Order' allows the named resolution mechanism to be specified
# The default order is "host lmhosts wins bcast." "Host" means use the Unix
# System gethostbyname () function call that will use either /etc/hosts OR
# DNS or NIS depending on the settings of /etc/host.config, /etc/nsswitch.conf
# And the /etc/resolv.conf file. "Host" therefore is system configuration
# Dependent. This parameter is most often of use to prevent DNS lookups
# In order to resolve NetBIOS names to IP addresses. Use with care!
# The example below excludes use of name resolution for machines that are NOT
# On the local network segment
#-OR - are not deliberately to be known via lmhosts or via WINS.
; Name resolve order = wins lmhosts bcast
# 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 = wxyz
# WINS Proxy-Tells Samba to answer queries on name resolution
# 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-default for versions 1.9.17 is yes,
# This has been changed in version 1.9.18 to no.
Dns proxy = no
# Case Preservation can be handy-system default is _no_
# NOTE : These can be set on a per share basis
; Preserve = no case
; No short preserve case =
# Default case is normally upper case for all DOS files
; Default case = lower
# Be very careful with case sensitivity - it can break things!
; No case sensitive =
#============================ Share Definitions ==============================
[homes]
Comment = Home Directories
Browseable = no
Writable = yes
# Un-comment the following and create the netlogon directory for Domain Logons
; [netlogon]
; Comment = Network Logon Service
; Path = /home/netlogon
; Guest ok = yes
; No writable =
; 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 = /home/profiles
; Browseable = no
; Guest ok = yes
# NOTE : If you have a system there is no need to print BSD-style
# 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
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
# The "staff" group
;[public]
; Comment = Public Stuff
; Path = /home/samba
; Public = yes
; Writable = yes
; Printable = no
; Write list =staff
# Other examples.
#
# A private printer, usable only by fred. Spool data will be placed in fred 's
# Home directory. Note that fred must have write access to the spool directory.
# Wherever it is.
;[fredsprn]
; Comment = Fred 's Printer
; Valid users = fred
; Path = /homes/fred
; Printer = freds_printer
; No public =
; Printable = yes
# 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
; No public =
; 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
# %u Also use the option to tailor it by user name.
# The %m gets replaced with the machine name that is connecting.
;[pchome]
; Comment = PC Directories
; Path = /usr/pc/%m
; No public =
; Writable = 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 = /usr/somewhere/else/public
Public = yes
Only guest = yes
Writable = yes
Printable = no
# 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.
;[myshare]
; Comment = Mary 's and Fred' s stuff
; Path = /usr/somewhere/shared
; Valid users = mary fred
; No public =
; Writable = yes
; Printable = no
; Create mask = 0765
Adding users to use useradd dboy
Dboy join samba-use smbpasswd
Adding another smbusers dboy = dboy
The items are correct netbios etc/services
Restare restart successfully used samba
Client Windows 2000 p
Ip wins for the use of Linux machines
Linux machines were added and then hosts ip
The Working Group will be the same as the machines and Linux
Phenomenon :
CLIENT Linux machines can be seen again when system but find that the road network
Shena save me! ! Amen
|
I also tried to look at the following article, it might be helpful
NT domain simulation using Linux Samba services
Blue Forest http://www.lslnet.com at 20:09 on December 5, 2000
Now, many units are building their LAN to share resources, which is an important aspect of sharing documents. There are many options available to us at present network operating system, relatively speaking, the choice of Linux as a network operating system has a relatively good performance and low cost. Linux for the Web, e-mail services, database services, file-sharing services can do most of the basic needs of the application. This article is mainly about how to use Linux Samba services domain simulation NT LAN document sharing.
Samba is a Windows
NT's agreement with the same software. We can use the simulation services to Samba Windows NT domain, users directly from the Windows computer using a Linux server in the paper and printers. When you correctly install the Samba software, the next task is to correct the distribution of Samba, Samba /etc/smb.conf completed in the allocation of services.
Samba to a suitable domain name
Smb.conf [Global] section in the document, Workgroup items actually equivalent to the Windows NT domain, it is installed Mygroup default, we can names of units and individuals who love to give it a name, such as Sambaserver.
Windows workstations installed to allow entry
Similarly, in section [Global] Smb.conf document, setting up Domain logons items Yes, said Samba allows Windows users download services.
Setting up user authentication
After more than two-installed in Windows 95 or older versions of Lan manager for DOS, Linux by legitimate users download, we will be able to successfully download the Samba server. However, in Windows 98, you will find that there is always suggested a similar password is not correct, what are the reasons? Samba password identification of the original service provision is general acquiescence of the texts, and the Windows 98 and Windows NT 4.0 with SP3, Windows 2000 is the use of encryption password. How can we solve this problem? Can be used in three ways.
Table 1
Name meaning possible value items
Comment were sharing Notes
The share of public resources for public permission yes no
Yes no writeable can write operation
Valid users allow users, a number of users, mary;joke;hxw
Middle use the semicolon separated
Allow hosts to allow the client, many, or which hxw;moli;liping
Semicolon used as separates, can be used to 11,103,41.*;11.103.42.88 ip
Said site
Contents of the document to establish mandatory masking create mask
1. Client expressly mandatory password entry
The method uses changes in the Windows system registry closed password, encryption Login to expressly transmission password. Register in HKEY_LOCAL_MACHINE\System\Current-ControlSet\Services\VxD\VNETSETUP, add a EnablePlainTextPassword. Radio 1 (DWORD). Then, re-X.P. system.
2. Samba allow the use of encryption password
The first solution is feasible, but not practical, if too many units workstations, the system administrator, obviously is a troublesome matter. In fact, the popular Linux versions of Samba to identify encryption password, but the password identification Samba acquiescence ordinary text. Samba encrypted password to enable identification, we need to do the following tasks. Encrypt password change [Global] item for the section Yes, Smb items at the passwd file you create a version of the Samba code, the text is /etc/smbpasswd acquiescence. Next, use Cat/etc/passwd|mksmbpasswd.sh>/etc/
Table 2
Acer meaning
%u Users were required to share with shared resources
%g Sharing requirements under the respective user group with shared resources
%m Shared machines were required to provide shared resources
Smbpasswd way to create an initial version of the Samba password. Then, for all Samba Samba users to establish a password password, users if they want to establish a password Abc only dialing Smbpasswd abc.
Through this approach, you can use Linux, like Windows NT, as recorded in the paper resources, clients no longer need to do additional work.
3. Seeking third party user authentication
If the NT server in a LAN, Samba NT domain authentication through client permission to provide documentation services. In other words, as long as it is the legitimate Windows NT users can visit the Samba permit the sharing of resources. Configuration : [Global] put a specific section of the items installed for Security Server (Samba acquiescence is the User), Password Server items at NT server name, the proposed use of IP addresses. If Password Server=11.103.41.12. This approach is simple, but the Samba share on the need for more resources to set up the security set up. Samba in the public service because of the resources permitted, as long as they are legitimate users of Windows NT, whether Linux users are able to visit the resource.
Samba installed sharing resources
In Samba services, the sharing of resources set up is much more flexible than Windows NT, it is not only the same as Windows NT workstation user license and set up, the Samba also provides a macro function can request users to share the machine and the dynamic allocation of shared resources. In other words, with a shared use, and different groups of users, the client or different users, the sharing of resources will be different. The specific method is installed in Smb.conf : adding a section, subsection entitled to share the name of the section, Path is essential, it used to mean that the share of the Linux server which were mapped to the list. Such as :
[myshare]
Path=/home/samba
Myshare share for the sharing of client, and the sharing of resources on the server /home/samba catalog.
Sharing the details, the table can be used to control one of a number of items.
In Path of course, Samba can take full advantage of the macro function, common-table 2.
Usershare below the sharing of resources was based on different users mapped to the corresponding user's directory :
[usershare]
Comment= different users to share resources
Path=/home/%u
Public=yes
Writeable=yes
Printable=no
Sharing resources is installed, it is necessary to pay attention to the question is, if Lan manager for DOS workstations, which were not shared with $ symbols (which shared the NT domain name is used), as Lan manager for DOS workstations to mapping with a $ Samba share were symbols, DOS will expand wrong. Similarly, the use of Linux in Smbmount, with Windows NT $ Smclient to use a shared symbol will be the name of error. Also to be noted is that Samba is a service built on Linux, Samba Linux File System competence priority. For example, if a list of Samba to allow for write operations, but does not allow Linux, or the client can write operation. Therefore, the establishment of a share can not be written for the write operation, we should first consider whether the Linux file system is written permission.
Restart Samba services
Smb.conf done on each amendment, deletion, increase operations, you must restart Samba, you can make changes to take effect. The methods were : /etc/rc.d/init.d/smb restart.
Through the above five steps, we can build a Linux on the "NT domain." After long-term use, I feel it's stability, security is pretty good. When you want to build a file server, your choice should take into Samba.
|
I installed samba painful journey, who help out prawn
Samba is a metamorphosis of things