Hi John. It worked well just before the upgrade. I'm not saying that
this is correct, but is the reason why users aren't accessing? Also,
should'n this give some specific error in the logs?
Tks in advance.
John H Terpstra wrote:
On 03/23/2010 02:35 PM, Leonardo Carneiro - Veltrac wrote:
Hi Dale and others. I had already checked the release notes. Only users
in eth0 (192.168.0.x) are having trouble. Here is some info and some logs:
smb.conf:
[global]
workgroup = DOMINIO
netbios name = DOMINIO
It is not at all surprizing that users are having difficulty accessing
this server! It's workgroup name and hostname are the SAME!!!!!
Please read the Samba-HOWTO. These two names MUST differ.
What you have is broken.
- John T.
server string = Samba Server
hosts allow = 192.168.1. 192.168.0. 127.
smb ports = 139
load printers = no
log file = /var/log/samba/%m.log
max log size = 50
log level = 2 winbind:3
security = user
encrypt passwords = true
username map = /etc/samba/smbusers
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
interfaces = eth0 eth1
local master = yes
os level = 90
domain master = yes
preferred master = yes
domain logons = yes
logon script = %G.bat
logon path =
name resolve order = wins bcast lmhosts
wins support = yes
dns proxy = no
ldap passwd sync = yes
ldap ssl = off
ldap delete dn = yes
passdb backend = ldapsam:ldap://127.0.0.1/
ldap admin dn = cn=root,dc=dominio,dc=com,dc=br
ldap suffix = dc=dominio,dc=com,dc=br
ldap group suffix = ou=Grupos
ldap user suffix = ou=Usuarios
ldap machine suffix = ou=Computadores
ldap idmap suffix = ou=ldapidmapsuffix
idmap backend = ldap://127.0.0.1
idmap alloc backend = ldap
idmap alloc config : ldap_user_dn = cn=root,dc=dominio,dc=com,dc=br
idmap alloc config : ldap_base_dn =
ou=Usuarios,dc=dominio,dc=com,dc=br
idmap alloc config : ldap_url = ldap://127.0.0.1
idmap uid = 10000-20000
idmap gid = 10000-20000
enable privileges = yes
nt acl support = yes
add machine script = /usr/sbin/smbldap-useradd -w "%u"
add user script = /usr/sbin/smbldap-useradd -m "%u"
delete user script = /usr/sbin/smbldap-userdel "%u"
add group script = /usr/sbin/smbldap-groupadd -p "%g"
delete group script = /usr/sbin/smbldap-groupdel "%g"
add user to group script = /usr/sbin/smbldap-groupmod -m "%u" "%g"
delete user from group script = /usr/sbin/smbldap-groupmod -x
"%u" "%g"
set primary group script = /usr/sbin/smbldap-usermod -g "%g" "%u"
dos charset = CP850
Unix charset = ISO8859-1
admin users = root
time server = yes
template shell = /bin/false
winbind use default domain = no
map acl inherit = Yes
Dale Schroeder wrote:
On 03/23/2010 1:48 PM, Leonardo Carneiro - Veltrac wrote:
Also, i found out that only users running windows xp in one of the
two interfaces that samba is being accessed are having this trouble.
Leonardo Carneiro - Veltrac wrote:
Hello everyone.
Yesterday i did an almost painless upgrade from samba pdc from 3.2.5
to 3.4.7. I'm running in a Debian Lenny (upgraded from the original
package to the backported one).
After a few tweaks i found on the web my users, including those who
run win7, where able to log in the domain. But now the cannot access
the shared folders on the server. Some users can't even open the
server share list.
There is any major change that prevent users to access the shares
that i'm skipping it?
Tks in advance and sorry for my poor english.
You could check the release notes for changes:
http://www.samba.org/samba/history/ ,
or consider posting your smb.conf.
Dale
--
*Leonardo de Souza Carneiro*
*Veltrac - Tecnologia em Logística.*
lscarne...@veltrac.com.br <mailto:lscarne...@veltrac.com.br>
http://www.veltrac.com.br <http://www.veltrac.com.br/>
/Fone Com.: (43)2105-5011/
/R. Pará 162 - CENTRO/
/Londrina- PR/
/Cep: 86010-450/
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
