similar to: Samba as domain member server cannot authenticate users

Hi all, I used to run Samba 2.2.9 on Debian Woody. Yesterday I upgraded it (with all necessary packages) to 3.0.7. Since then, Samba on that server do not respond to netbios queries, only to direct access via IP. Also, when I try to resolv its name using nmblookup, I cannot find it. When I access to server via IP address everything works fine. Any idea ? TIA -- Eng. Dusan Djordjevic

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.

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

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:

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 support for unified logon authentication. > Normally, everything

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

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]

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

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 user is logged in to the Samba Server. smb.conf has the following: [homes] comment = Home Directories read only = No create mask = 0775 directory mask = 0775 browseable = No writeable = Yes The files in the user's home directory are set to chmod 777. What do I need to do to enable the user to write to her Directory?

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

Hi All, I have a member server on debian unstable using 3.0.0.final, member of 2000 AD, in ADS security mode & authenticating through winbind. XP/2000/2003 clients connect to shares OK, NT4 & DOS fail (suspect 9x the same not tested). NOT using NTLM v2. The logged error is "auth/pampass.c:smb_pam_accountcheck(781) smb_pam_accountcheck: PAM: Account Validation Failed - Rejecting

please, oh please, why do the machine acounts fail: [2016/12/22 21:06:48.172161, 0] ../source3/auth/pampass.c:797(smb_pam_accountcheck) smb_pam_accountcheck: PAM: Account Validation Failed - Rejecting User xyz-pc$! pdbedit -L for that machine account shows that the password changed some days ago: Password last set: Mon, 19 Dez 2016 14:11:20 CET As I didn't do a thing ... who or what?

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

Firstly, I've already solved the daft mistake of mine. I'm merely sending it in so the next person digging through the archives might get helped out. I've configured Samba v2.2.8a, alot of default settings. No LDAP interaction, no winbindd. Accounts were created both in '/etc/passwd' && 'smbpasswd', but whenever I tried to mount a share from my RedHat box, the

This problem was already described on a very similar way in Oct 2004 on the following message: [http://lists.samba.org/archive/samba/2004-October/094683.html] As no solution was found so far, I am re-posting it on the hope that somebody can help. ================================================= Situation: - A windows2000 domain with active directory up and running. - A Samba server with