Hola,
Be, primer t'he d'avisar que fa com uns 3 anys que no toco el samba,
aix� que potser alguna  persona d'aquesta llista et podr� ajudar m�s o
completar la meva informaci�.

A veure si ens aclarem:
        1) Els teus PC's amb Linux veuen correctament els directoris
        compartits per altres PC's amb guindous ==> ok.
        
        2) Els teus PC's amb guidous NO VEUEN els recursos compartits   pels
teus PC's amb Linux.==> Problema!!
        
        B�, primer dir que NO CAL INSTALAR CAP CLIENT. El samba del     linux �s
un 'servidor de xarxa guindous' per tant qualsevol 
        producte de la familia de M$ cont� el client per aquest servei.         Si els
        teus Pc's amb guindous es veuen entre si, ja el tenen   correctament
configurat.
        
        Els punts que s'han de verificar son:

                - /etc/samba/smb.conf => T'adjunto un que vaig fer              servir.
                Est� configurat per generar un fitxer de log
                per cada m�quina que es configuri a             
/var/log/samba/nom_maquina.log,
aix� que si tens problemes              per conectar des d'una m�quina, pots veure
al log alguna           pista de qu� pasa
                Aix� mateix fa servir con a fitxer de passwords el
                /etc/samba/smbpasswd.
                I NO FA SERVIR EL /etc/smbusers. 
                
                Si no recordo malament aixo fa que t'hagis de conectar          al 
servidor
samba amb un usuari que existeixi al unix               (/etc/passwd) i que tingui
un password definit a           /etc/samba/smbpasswd.


                - USARI / PASSWORD: Amb la meva configuraci� has de             donar 
d'alta
l'usuari que fa servir el client guindous a             unix (/etc/passwd) i amb
la comanda  smbpasswd pots              afegir els passwords dels usuaris que
vulguis que tinguin             acc�s al samba al /etc/samba/smbpasswd.

                No ho he fet mai pero crec que amb la comanda:

                cat /etc/passwd | mksmbpasswd.sh > /etc/samba/smbpasswd

                et gener�s un smbpasswd amb tothom

                - MAQUINA CLIENT ??? Ho sento,pero no recordo. Hem sona                
 que s'havia
de fer alguna cosa per cada m�quina que                 es  conecta per� no estic
segur. Si alg� de la            llista pot dir alguna cosa al respecte estaria
be. Si          has fet lo anterior i no et funciona, pot ser es perque has de
                s'ha de configurar alguna cossa per la m�quina client.
                si no et funciona i ning� et diu res, envia'm alte mail                
 que m'ho
mirar�.
                
                - CAP ALTRE PUNT A VERIFICAR ??? Si alg� te alguna cossa               
 a dir o
corregir.....

Be, que tinguis sort i si et puc ajudar el alguna cossa, ja saps!!





El jue, 23-01-2003 a las 01:44, Alfons Nonell i Canals escribi�:
> Hola!.
> A casa fa temps ja que tinc Linux instal�lat al meu PC i, per agafar
> fitxers dels altres PCs que tinc a la xarxa (tots amb Win98) monto la
> unitat que els altres tinguin compartida amb SAMBA i cap problema!.
> 
> Ara per�, a la feina he aconsegit fer que alguns dels PCs els treguin el
> Window$$ XP per posar Linux (el tipus de feina requereix ser polivalent
> pel que fa a SO, i si puc usar Linux millor!). Hem instal�lat doncs el
> Mandrake 9 a alguns dels PCs. Tot sovint per� compartim informaci� entre
> alguns directoris que tenim compartits, amb Window$ no hi ha problema i,
> amb Linux, per veure els altres tampoc.
> 
> El problema arriba quan vull fer que els de Wido$ tb vegin certs
> directoris "compartits" al Pc que t� Linux. Ara venen les meves
> preguntes...
> 
> �Tinc ent�s que per compartir amb SAMBA cal instal�lar samba client als
> PCs de windows, oi? i, cal doncs instal�lar el Samba Server al Linux?, o
> poden anar tots amb els client?.
> 
> �Com determino al Linux quins directoris vull que em vegin i quins no?..
> 
> En resum, m'agradaria que els PCs que poso amb Linux puguin esdevenir un
> Pc m�s de la xarxa i aix�,poc a poc, anar fent el canvi cap a Linux. Per
> convence'ls peo necessito fer que els PCs que van amb Linux puguin estar
> plenament integrats a la xarxa. Si us plau.. ajuda!!!!!
> 
> Gr�cies,
> Alfons.

# 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 config file that you
# 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]

# workgroup = NT-Domain-Name or Workgroup-Name
   workgroup = MYGROUP

# 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. 192.168.2. 127.

# 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
   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 Kb).
   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
# security = domain
;   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 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
#        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*UNIX*password* %n\n *ReType*new*UNIX*password* %n\n 
*passwd:*all*authentication*tokens*updated*successfully*

# 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

# 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

# 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
# dependant. 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 = 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 = no 

# 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

#============================ Share Definitions ==============================
[homes]
   comment = Home Directories
   browseable = no
   writable = yes

[web]
  comment = Carpeta de Desarrollo Web
  browseable = yes
  writable = yes
  path=/root/web
  printable = no

[web_svr]
 comment = Carpeta de Desarrollo Web
  browseable = yes
  writable = yes
  path= /usr/local/softasp/apache-bundle
  printable = no



  
; Un-comment the following and create the netlogon directory for Domain Logons
; [netlogon]
;   comment = Network Logon Service
;   path = /home/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 = /home/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
   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
;   public = no
;   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
;   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.
;[pchome]
;  comment = PC Directories
;  path = /usr/pc/%m
;  public = no
;  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
;   public = no
;   writable = yes
;   printable = no
;   create mask = 0765


Responder a