Autor |
Sõnum |
martj
Uus kasutaja
Liitunud: 02.09.2009
Postitused: 11
Asukoht: Tallinn
|
|
Tere. Olen suht värske Linuxi kasutaja ja enamike probleemidega siiski käesoleva foorumi abiga hakkama saanud. Kuid nüüd hakkab mõistus otsa saama.Nimelt üritan kodust serverit tekitada, mille ülesandeks oleks printeri kui ka failide jagamine kohtvõrgus Vista ja Ubuntu -ga. Masinas endas on Xubuntu ning Samba. Seni, kuni Samba lubab välja jagatud kataloogile ligi kõiki kasutajaid - asi toimib. Hätta jään aga siis, kui proovin tekitada eraldi kasutajaid ning määrata neile katalooge. Sel juhul Vista kui ka Ubuntu teatavad mõlemad, et ligipääs keelatud, kasutajanimi või parool vale.
Siit ka küsimused:
kas omab siin kohtvõrgu nimi mingit tähtsust (Vistal workgroup) ? Ilmselt mitte määravat, sest kataloogid ise on ju teistest masinatest näha sõltumata töögrupi nimest...
Ega ometi kohtvõrgus oleva masina kasutajanimi ei pea ühtima Sambas olevaga..? selleks ju ikkagi avaneb mingi dialoogiaken, mis küsib kasutajanime ja parooli
Pole ka kusagilt välja lugenud, et Samba vajaks mingit taaskäivitamist peale muudatuste tegemist, ta vähemalt ei küsi midagi sellist
Kuhu siis lõppudelõpuks need kasutajakontod moodustatakse, kes serverile ligi pääseda tohivad? Kas on veel midagi, mille olen kas kahe silma vahele jätnud või valesti teinud..?
Lisainfoks veel, et jagatav ketas on FAT formaadis ning asub ..dev/sdb1 kuna haakisin selle külge peale linuxi installi. Pärineb teine Win masinast kuid sisaldab mingit vana materjali, mida ei tahaks kuhugi ümber kantida
Igatahes kõikvõimalikud vihjed oleks abiks!
ette tänades:
Mart
|
|
|
|
|
|
|
|
spott
Admin
Vanus: 43
Liitunud: 04.06.2005
Postitused: 8857
Distributsioon: Ubuntu
|
|
alustaks sellest, et näita oma samba confi.
kas FAT ketast linuxile paremini vastuvõtlikumale kettale kopeerida ei saa - nimelt pole ma kindel, kuidas seal see kasutajaõiguste asi on lahendatud.
|
|
|
|
_________________ Tellige endale sünnipäevaks, sõbrapäevaks või muuks tähtpäevaks kingitus: Kingitused internetist - NetiKink.eu
|
|
|
|
laur
Vana Pingviin
Vanus: 39
Liitunud: 22.01.2006
Postitused: 1195
Asukoht: Tallinn
Distributsioon: Estobuntu, Kubuntu, Mandriva, OpenSUSE
|
|
Kas ma panen väga puusse kui ma pakun et asi on selles et FAT ei toeta ju failiõigusi, ehk et saabki olla kas ligipääs avatud kõigile või ligipääs suletud kõigile, äkki selletõttu süsteem niimoodi käitubki?
|
|
|
|
_________________
|
|
|
|
obundra
Vana Pingviin
Vanus: 50
Liitunud: 04.08.2005
Postitused: 1213
Asukoht: 127.0.0.1
Distributsioon: RHEL, Solaris, Debian, Gentoo
|
|
Kui sa lisasid eraldi kasutajaid, kas sa siis lisasid nad ainult süsteemi või ikka Sambale ka?Umbes nii: Kood: | # smbpasswd –a onuaugust
New SMB password: ********
Retype new SMB password:******** |
|
|
|
|
_________________ IT teenused
|
|
|
|
martj
Uus kasutaja
Liitunud: 02.09.2009
Postitused: 11
Asukoht: Tallinn
|
|
See on conf fail..
Kood: |
[global]
## Browsing/Identification ###
# Change this to the workgroup/NT-domain name your Samba server will part of
workgroup = server
# server string is the equivalent of the NT Description field
server string = %h server (Samba, Ubuntu)
# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
# wins support = no
# 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
# This will prevent nmbd to search for NetBIOS names through DNS.
dns proxy = no
# What naming service and in what order should we use to resolve host names
# to IP addresses
; name resolve order = lmhosts host wins bcast
#### Networking ####
# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
; interfaces = 127.0.0.0/8 eth0
# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself. However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
; bind interfaces only = yes
#### Debugging/Accounting ####
# This tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/log.%m
# Cap the size of the individual log files (in KiB).
max log size = 1000
# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
# syslog only = no
# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
syslog = 0
# Do something sensible when Samba crashes: mail the admin a backtrace
panic action = /usr/share/samba/panic-action %d
####### Authentication #######
# "security = user" is always a good idea. This will require a Unix account
# in this server for every user accessing the server. See
# /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html
# in the samba-doc package for details.
# security = user
# You may wish to use password encryption. See the section on
# 'encrypt passwords' in the smb.conf(5) manpage before enabling.
; encrypt passwords = yes
# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.
passdb backend = tdbsam
obey pam restrictions = yes
# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
unix password sync = yes
# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for
# sending the correct chat script for the passwd program in Debian Sarge).
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
pam password change = yes
# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
map to guest = bad user
########## Domains ###########
# Is this machine able to authenticate users. Both PDC and BDC
# must have this setting enabled. If you are the BDC you must
# change the 'domain master' setting to no
#
; domain logons = yes
#
# The following setting only takes effect if 'domain logons' is set
# It specifies the location of the user's profile directory
# from the client point of view)
# The following required a [profiles] share to be setup on the
# samba server (see below)
; logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
# logon path = \\%N\%U\profile
# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
; logon drive = H:
# logon home = \\%N\%U
# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
; logon script = logon.cmd
# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe. The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u
# This allows machine accounts to be created on the domain controller via the
# SAMR RPC pipe.
# The following assumes a "machines" group exists on the system
; add machine script = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u
# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe.
; add group script = /usr/sbin/addgroup --force-badname %g
########## Printing ##########
# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
# load printers = yes
# lpr(ng) printing. You may wish to override the location of the
# printcap file
; printing = bsd
; printcap name = /etc/printcap
# CUPS printing. See also the cupsaddsmb(8) manpage in the
# cupsys-client package.
; printing = cups
; printcap name = cups
############ Misc ############
# 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 = /home/samba/etc/smb.conf.%m
# Most people will find that this option gives better performance.
# See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/speed.html
# for details
# You may want to add the following on a Linux system:
# SO_RCVBUF=8192 SO_SNDBUF=8192
# socket options = TCP_NODELAY
# The following parameter is useful only if you have the linpopup package
# installed. The samba maintainer and the linpopup maintainer are
# working to ease installation and configuration of linpopup and samba.
; message command = /bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s' &
# Domain Master specifies Samba to be the Domain Master Browser. If this
# machine will be configured as a BDC (a secondary logon server), you
# must set this to 'no'; otherwise, the default behavior is recommended.
# domain master = auto
# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
; idmap uid = 10000-20000
; idmap gid = 10000-20000
; template shell = /bin/bash
# The following was the default behaviour in sarge,
# but samba upstream reverted the default because it might induce
# performance issues in large organizations.
# See Debian bug #368251 for some of the consequences of *not*
# having this setting and smb.conf(5) for details.
; winbind enum groups = yes
; winbind enum users = yes
# Setup usershare options to enable non-root users to share folders
# with the net usershare command.
# Maximum number of usershare. 0 (default) means that usershare is disabled.
; usershare max shares = 100
# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
usershare allow guests = yes
security = user
guest ok = yes
; guest account = nobody
username map = /etc/samba/smbusers
#======================= Share Definitions =======================
# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares. This will share each
# user's home directory as \\server\username
;[homes]
; comment = Home Directories
; browseable = no
# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
; read only = yes
# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
; create mask = 0700
# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
; directory mask = 0700
# By default, \\server\username shares can be connected to by anyone
# with access to the samba server. Un-comment the following parameter
# to make sure that only "username" can connect to \\server\username
# This might need tweaking when using external authentication schemes
; valid users = %S
# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
; comment = Network Logon Service
; path = /home/samba/netlogon
; guest ok = yes
; read only = yes
; share modes = no
# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
; comment = Users profiles
; path = /home/samba/profiles
; guest ok = no
; browseable = no
; create mask = 0600
; directory mask = 0700
; wins support = no
[printers]
comment = All Printers
browseable = no
path = /var/spool/samba
printable = yes
; guest ok = no
; read only = yes
create mask = 0700
# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
comment = Printer Drivers
path = /var/lib/samba/printers
; browseable = yes
; read only = yes
; guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
; write list = root, @lpadmin
# A sample share for sharing your CD-ROM with others.
;[cdrom]
; comment = Samba server's CD-ROM
; read only = yes
; locking = no
; path = /cdrom
; guest ok = yes
# The next two parameters show how to auto-mount a CD-ROM when the
# cdrom share is accesed. For this to work /etc/fstab must contain
# an entry like this:
#
# /dev/scd0 /cdrom iso9660 defaults,noauto,ro,user 0 0
#
# The CD-ROM gets unmounted automatically after the connection to the
#
# If you don't want to use auto-mounting/unmounting make sure the CD
# is mounted on /cdrom
#
; preexec = /bin/mount /cdrom
; postexec = /bin/umount /cdrom
[Documents]
path = /home/martj/Documents
writeable = yes
; browseable = yes
valid users = martj
[Documents]
path = /home/martj/Documents
writeable = yes
; browseable = yes
valid users = martj
[alot]
path = /home/alot
writeable = yes
; browseable = yes
valid users = alo
|
Veel tähelepanekuid: Kasutajad tekitasin kõigepealt süsteemi ja siis Sambale. Kas Samba tahab taaskäivitamist enne, kui muudatused jõustuvad? tundus, nagu oleks abiks... kuid võibolla on ikkagi tegu xp poolse kapriisiga.
Siis veel - XP masinaga saan sisse korraga ühe kasutajana, teist kataloogi avades ütleb, et ei saa ligi. Ka teisest samas võrgus olevast XP -st ei lase mujale, kui ühe kasutaja poolt avatud kataloogi.. Mis võib olla põhjuseks..?
Igatahes tekitan omale kõrvale ühe Linuxi masina ja vaatan, mis siis juhtuma hakkab..
FAT kasutajaõiguse probleemi lahendasin hetkel nii, et linkisin ta kättesaadavasse kataloogi ja sealt asi toimetab.
|
|
|
|
|
|
|
|
|
|