similar to: :Re: Unknown PAM failiure in WIN2003/ Active Directory + samba

Damn, 2.6.13.4 i REALLY mean! :) (i probably need a holliday!) Huh....2.6.16.4....i mean! :) In smb.conf, i removed obey pam restrictions and now it works... What does "obey pam restrictions" do ? Cheers, Phil. - Hash: SHA1 Philippe Dhont (Sea-ro) escreveu: > Hello, > I have an existing windows 2003 network and now try to add a new linux > server with samba/kerberos

Hello, I have an existing windows 2003 network and now try to add a new linux server with samba/kerberos support for unified logon authentication. Normally, everything is installed & this is the configuration: - Debian with 2.6.16.4 kernel - heimdal kerberos - samba log info: log.smbd: [2005/10/17 10:48:26, 0] smbd/server.c:main(798) smbd version 3.0.14a-Debian started.

Hi all, I use Samba 3.0.9 on Debian Woody. I use it as domain member server: workgroup = testdomen security = domain When I join it to domain, it seems it is ok: newhas1:~# net rpc join -U dj.dule%pass Joined domain TESTDOMEN. wbinfo -u lists users, getent passwd also works fine. But when I try to access server from XP comp logged onto a domain, i cannot. I found this in logs: [2004/10/20

Hello all, we currently do have a problem with samba 3.3.4 on AIX 5.3. We have set up the samba system to integrate in our AD Domain. Integration was successfull (net ads join), wbinfo executes with parameters -ugt without any problems. Our smb.conf content follows at the end of this mail. We have defined just one share as follows: [smbtest] writeable = yes path = /gpfs/fbb/ls/cip valid users

Hi all I have set my Samba server up to join an AD realm. Winbind is working fine and I am able to use it for authentication as needed. When I try to connect to one of my shares via a Windows client, I get the following error: [2004/11/04 11:57:54, 0] auth/pampass.c:smb_pam_account(573) smb_pam_account: PAM: UNKNOWN PAM ERROR (9) during Account Management for User: MYDOMAIN+room1 [2004/11/04

Hi, I'm configuring samba-3.0.2a-Debian. I have it configured with LDAP. I get samba decline access for a W98 clinet when using user authentication (NT domain), and the following entries get into /var/log/smb/machine.log: -------------------------------------------------------------------- [2004/05/07 13:46:07, 3] smbd/sesssetup.c:reply_sesssetup_and_X(772) Domain=[WORKGROUP]

Has anybody had this problem before? If not, where should i start digging? I'm running Samba 3.0.24 on Debian stable with slapd-2.2.23 backend. smb.conf is attached below. When two different users log in at the same moment, the login process seems to freeze for a minute and the client (win2k) complains about missing profile or missing access to profile. A single user login works perfectly.

Hi I'm having problems implementing a domain member server using winbind. I've setup a test share on the server (BERTHOG) and test user (alex) on the PDC (RODNEY). Winbind seems to be running fine: berthog:/srv$ wbinfo -n alex S-1-5-21-2502943273-132007109-1129902423-3006 User (1) But when I try to connect to the share: berthog:/srv$ smbclient //BERTHOG/shared -U alex Password:

I posted this plea for help last week, but received no responses, so I figured I'd re-send. Since posting this message I upgraded to 3.0 stable using the package posted on the samba.org site, and the behavior remains the same. I should also mention, if I try smbclient -U guest and enter an empty password, I can successfully get a browse list fromt the server. Is there an increased

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm having a problem getting a browse list from my Samba box. I'm running debian testing with the 3.0beta2-1 package. Winbind appears to be installed properly and functioning properly: root@dbs1:~# wbinfo -t checking the trust secret via RPC calls succeeded root@dbs1:~# wbinfo -a Administrator%xxxxx plaintext password authentication

Hi all I have set my Samba server up to join an AD realm. Winbind is working fine and I am able to use it for authentication as needed. When I try to connect to one of my shares via a Windows client, I get the following error: [2004/11/04 11:57:54, 0] auth/pampass.c:smb_pam_account(573) smb_pam_account: PAM: UNKNOWN PAM ERROR (9) during Account Management for User: MYDOMAIN+room1 [2004/11/04

So many people have posted this problem! The steps to debug need to be in a FAQ. The short question is: Can there be a disconnect between the short and long REALM names, leading to winbind-to-AD authentication errors? and How do I fix it? I can access windows shares or join a AD Domain with: mount -t smbfs -o username=johns,workgroup=ms //library/Source_Safe tmp/ --or-- net ads

My pam_ldap works for authenticating against Active Directory. I want to use Samba 2.2 to allow printing if the user authenticates via Active Directory even if the user doesn't have local account. My problem with logs: PAM is successful for authenticating via AD. [2002/07/03 18:14:53, 4] passdb/pampass.c:smb_pam_auth(534) smb_pam_auth: PAM: User jdoe Authenticated OK [2002/07/03

I do not understand the following output. The actual command and error are: juliet:/mnt # smbmount //compaq/mastertools /mnt/dos -o username=alan password=eunice Password: 10300: tree connect failed: ERRSRV - ERRbadpw (Bad password - name/password pair in a Tree Connect or Session Setup are invalid.) SMB connection failed It seems the user validates at the os level , but later fails when

Hello everybody, I have to face a problem here with a samba share disconnecting after about 10 minutes. Situation: - debian woody, samba 3.0.14a - server configured as PDC - typically 100-150 smbd processes running everything runs smoothly but one client (W2K SP4) that obviously needs a quasi static connection to the PDC. The client runs a software that stores regularly data on a dedicated

Hi all, recently I asked for help with a problem Samba had to write files (http://lists.samba.org/pipermail/samba/2002-November/085003.html, http://lists.samba.org/pipermail/samba/2002-November/085083.html). Since that hasn't solved, and since it occurs regardless of changes of the smb.conf, I'd like to post some passages of the smb log file (log level 4) of the attempt to copy a file to

Hi all, I'm having a problem with an upgrade of Samba running on a Redhat4 Update 4 system. The default installation provides only 3.0.10 which doesn't include the privilege model or a number of fixes including some in 3.0.21a and 3.0.23 which it looks like we'll need. The system runs in PDC mode with user accounts in an ldap database. On a test system which I'm using to

I fixe it Client use spnego had to be off (thnx andrew, i remembered your mail yesterday) Now, could someone please give me a little bit advise ? It's for the following This is now only in testphase. I installed windows2003 server as PDC I installed samba 3.0.0 alpha 2.4 This should come in our networks, the win2003 on a site and the samba on another site and on another site also another

Hello everyone! After running Samba on several machines for some years, I just came accross a rather strange problem. The short story is that the special user home shares are readable, but not writeable. Here's the long story: The system is a freshly set-up Debian Squeeze, right out of the box. This is the Samba config: -------------------------------- 8<

Hi, I'm using SuSE 8.2 and I got the source for samba 3.0.2a and I tried to install it. ./configure (w/o any arguments) went ok so I type make and it gives me the following errors: Linking bin/smbd auth/pampass.o(.text+0x59): In function `smb_pam_error_handler': : undefined reference to `pam_strerror' auth/pampass.o(.text+0xcb6): In function `smb_pam_end': : undefined reference