similar to: guest account beyond my grasp

Hi, I'm using 3.0.21b and I cannot get the guest account to work. some of smb.conf: ------------------------------ security = user hosts allow = 192.168.2. 127. guest account = visiteur log level = 2 log file = /var/log/samba/samba.%m max log size = 1024 socket options = TCP_NODELAY [publique] path = /vol2/samba/publique browseable = yes guest ok = yes

Hi All, I installed samba 3.0.22 and join it to Win2003 AD domain. Users from my domain can access the samba shares successfully. My problem is that users from trusted domains can not access to my samba shares Wbinfo -m - show all the trusted domains Wbinfo -u - show all the users include the trusted domains users. Any Idea? My smb.conf global parameters: # Global parameters

I just migrated my SMB pdc to a new server (was running 3.0.21c, now 3.0.22). Some things seems to be ok. net rpc list; net rpc testjoin seem to work. But if I attempt to join a windows system to the domain I get "The following error occured while attempting to join to domain "DOMAINNAME": The user name could not be found". The machine name is getting loaded into ldap.

Hi, I have a AIX 5.3 machine with Samba 3.0.24c joined into one Windows 2003 ADS server OK. I can request basic information, user lookup, domain lookup(wbinfo, id, net groupmap). When I want to acces the share \\node05\brom from one Windows station I receive a popup window password. In the log of the samba for that machine I found: [2007/04/27 10:48:27, 2] auth/auth.c:check_ntlm_password(319)

Hello Samba users, I'm trying to configure my samba server as a PDC for some Win2k machines. I'm running Red Hat 8.0 and samba-3.0.0rc4. Everything seems to be ok, when using workgroup configuration, all the shares works fine. But I cant get the Win2k clients to log in the Domain. It says I have a unknown user or an incorrect password. But at least it prompted me for a user/password, so I

Hello, I'm having some difficulty trying to join a WinXP client to our Samba domain. When I try to join the client to the domain and I submit the computer name and the domain name in the computer identification control panel, I'm prompted for the root user and password on the server, so I enter root and the root password on our Samba server. I then get a message saying that it

I've been trying to have Samba 3.0.1 work as a primary domain controller using LDAP as the authentication mechanism. However I am unable to get any of my Windows XP Pro machine join the domain. When prompt for an account with permissions to join the domain by the XP client, I give it the Administrator account which is granted Full access to the LDAP directory (BTW this is poor security,

I'm trying to set it up so I can join the domain with a regular user that is part of the domain admin group. I have a user dsonenberg that is in the domain admin group(512), but I can't join the domain with that account. For the record I can login with that account and Administrator can join the domain. The PDC has an LDAP backend. Here's the log. 2005/02/08 10:26:25, 2]

Specifics samba-3.0.0beta1-1.i386.rpm on RedHat 9 and smbpasswd authentication, the machine is the PDC and security is set for user. The machine account was setup on the fly and it appears in passwd, shadow, and smbpasswd files as it should. However it seemed to take a very long time to join the domain, about 1-1/2 minutes. I can browse the Samba PDC machine and access the shares, etc. After

Hi guys, Thanks for those of you whole kept reading after seeing the subject line -- I know, it's like a flashback to about 2000 or so, but for mostly uninteresting reasons, I've got a situation that I wanted to run by the list just in case there's a work around. I have an NT 4 server that's the PDC that my new Samba box, running 3.4.0 w/ "security = domain" uses to

Hello all, I have some problems to make work a configuration like Samba and OpenLDAP as domain controller. My operative system is OpenSuSE 11.3. Here is my testparm: [global] workgroup = MEDIADC netbios name = MEDIADC map to guest = Bad User passdb backend = ldapsam:ldap://afs-test.mediaservice-test.pri log level = 2 printcap name = cups

I am trying to upgrade our fully functional Samba domain from v3.0.2 to v3.0.7 or v3.0.8. My question is, do I have to upgrade every server in the domain in order for it to work or should I be able to upgrade one server at a time, test it, and move on to the next server? Or should I upgrade the domain controller first, then upgrade the member servers one at a time? I've tried to upgrade

Good day all Newbie problem again... I?ve been setting up a samba box for a few days now and have been quite successful in most respects. I can get the win2000 machines to join the domain and I can see the password being authenticated too. I can even see the shared drives. The problem I?ve having is that after a few log on and log off I can?t seem to logon again. At the win2000 login

Hi, first time poster. I am having trouble getting one of my servers to list all the files in the directory. Consequently, it is failing to work with email when users create new sub folders ( main problem). background: we have two servers -old solaris 10 system running as server not smb master which is mail server -new linux CentOS 5.9 system running as master that also serves as

Hi, I have installed Samba 3.5.5 on a Sparc Solaris 10 system and it's the PDC of a domain mainly consisting of other Sun boxes. On the other hand, I have a PC with Windows 7 that I don't want to put in the same domain (it's in a workgroup) When I try to connect some share (user's home) from the Windows box, I get strange results : - If the share is on the PDC, I can connect

after setting up a PDC with ldap according to the book samba 3 by example, almost everything worked out fine, the validations listed in the books turned out as expected with minor differences, but these are the problems : 1. According to the book the account that can be used to join a domain is the Administrator account with the password set from the ldap admin dn which is secret is my

I'm running 3.4.6 (was running 3.0.28a but upgraded in hopes to fix this issue). Clients running Windows 7 that are NOT joined to the AD domain (samba authenticates against it via "security = server") cannot authenticate to access the server. Clients running Windows 7 that are on the domain as well as Windows XP, Windows 2003 on and off the domain work as expected. Any help would

Hello all, I am doing some tests with Windows 7 and a Samba Domain, but into a working SAMBA domain, where windows XP joins without problems, when i try with 7 i recieve an error like "The trust relationship between this workstation and the primary domain failed.". I use OpenSuSE 11.3 with samba 3.5.4-5.1.2 and openldap 2.4.21-9.1. My config of samba: [global] workgroup =

I have an issue with getting my students access to the samba shares for our lab's server. I am using authentication through our university's active directory. I followed the directions for getting this set up using winbind. I am using winbind for both samba authentication as well as user logins through pam. The trouble is this: I have no problems logging in and getting access to the

Using LDAP and the smbldap-tools. When attempting to join the domain with an administrative user, the computer gets added to the Computers list in LDAP with the following attributes: cn: workstation75$ description: Computer gecos: Computer gidNumber: 515 homeDirectory: /dev/null loginShell: /bin/false objectClass: top, account, posixAccount uid: workstation75$ uidNumber: