similar to: Authentication problem between RH 7.3 Samba and W98

Hello, we migrate from Samba 2.2 to Samba 3.020b. We have the problem now, that some clients can not connect to the Samba Server. In the log there are messages like that: [2006/02/23 08:49:20, 2] smbd/sesssetup.c:setup_new_vc_session(704) setup_new_vc_session: New VC == 0, if NT4.x compatible we would close all old resources. [2006/02/23 08:49:20, 2] auth/pampass.c:smb_pam_auth(514)

from samba 3.0.9 to 3.0.13 I can not access my shares from a NT4 box as usual before upgrading. I can access samba shares from linux via mount //server/testuser /mnt -o username=testuser,password=testpass as before. Even the newest version (3.0.14a) from samba.org doesnt't help. What has happened to samba ??? Any hints ?? Thanks for your thoughts, G?tz.

Hi, I have just upgraded a server from Samba 2 to Samba 3 and some of the Windows clients are taking a long time to authenticate shares (1 or 2 minutes). Eventually the username/password box appears and then when you enter a correct password, all is fine - it is just the initial authentication. This is a simple UNIX password Samba server (with NIS) and I have set it to not use encrypted

Dear Samba folks, I have heard and seen nothing about this or matters like it since my posting, so I thought I would repost with some updates. My thinking at the moment is to try to recompile SAMBA (I am using a Fedora core 2 binary distribution) without PAM support, but I hate to do that. Here it is again: I very recently replaced our SGI Challenge S file server, which employed samba 2 to

Dear Samba folks, I very recently replaced our SGI Challenge S file server, which employed samba 2 to service Windows boxes, with an Intel Linux box running Fedora core 2 Linux with samba 3.0.3. When I connect to the server, it takes a number of *minutes* to get an authentication challenge window. After entering name and password, the connection proceeds, and shares are displayed normally.

Dear Samba Folks, Re the message I sent you earlier (reproduced below). The logs are also producing error messages such as this: smbd[12778]: pam_succeed_if: requirement "uid < 100" not met by user "bonomo" smbd[12821]: pam_succeed_if: requirement "uid < 100" not met by user "bonomo" smbd[12840]: pam_succeed_if: requirement "uid <

I'm using FC8 Server with Samba 3.0.30-fc8 and have an erratic problem assecing the share. I have a Share that every one can acess and I use the nobody user to acess everithing without any problem, and from time to time when user tries to acess a file the share gets closed, than we have to resart the machine and it goes wel again. the log for one user is below why does it closes the

Hello! I tried to get some help from the IRC before, but the problem seems to be too complicated to discuss it there. PLEASE, be so kind and help me solving this problem, I stuck and I must get this working as quick as possible. Here an overview and some details: In one well protected LAN (so I have no need to encrypt passwords at all, which simplifies user management on servers in turn because

Hello! I was wondering if it's possible to make Windows NT and Samba 3 work togheter. I found an old question with the same problem I have. Samba 3 is not authenticating WinNT machines. My smb.conf is: [global] workgroup = DESQ-TESTE server string = Teste (Samba %v) interfaces = 143.106.19.25/255.255.255.192, 127. bind interfaces only = Yes encrypt passwords = No password server =

I have installed Samba before on one of my Sun boxes running Solaris, but the box died and I'm back on an x86 machine running FreeBSD and now I'm getting some odd errors that I cannot track down. I've searched all the mailing lists and newsgroups and tried different solutions that were suggested but to no avail. Below are my config and log file. I am not using any authentication to

Hi, I have installed samba 2.2.8a for Sparc platform. I have configured it in this way [global] workgroup = DOMINIO null passwords = yes netbios name = SERVIDOR wins server = servidor_wins security = server password server = servidor_passwd name resolve order = wins bcast host lmhosts server string = Servidor Solaris Unix con

seems to mess up the pam for swat. [root at host67 security]# rpm -qf /etc/pam.d/samba samba-3.0.25b-1.el4_6.4 [root at host67 security]# cat /etc/pam.d/samba #auth required /lib/security/pam_stack.so service=system-auth #account required /lib/security/pam_stack.so service=system-auth auth required pam_stack.so service=system-auth account required

Greetings all, I'm working on attempting to get SAMBA to work with a product line called CryptoCard. I *should* be able to get it to work one of two ways, either through the use of CryptoCard's provided PAM module, or through RADIUS authentication. Currently, I cannot seem to get PAM authentication to work at all. This is what is in the 'samba' file for PAM: auth

Hi All, Brand new box, running FreeBSD 4.7 and 2.2.6 of SAMBA. I keep getting the following when a legit user attempts to login: > [2002/11/20 11:15:46, 0] passdb/pampass.c:smb_pam_passcheck(827) > smb_pam_passcheck: PAM: smb_pam_auth failed - Rejecting User steve ! > [2002/11/20 11:15:46, 0] passdb/pampass.c:smb_pam_passcheck(827) > smb_pam_passcheck: PAM: smb_pam_auth failed -

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

How can I stop samba from authenticating the guest? Currently, my user authenticates with PAM (ldap from Active Directory) and that is successful. But the user doesn't have any Unix account information -- so Samba falls back to the "guest" account. This is okay. Bu then Samba tries to authenticate again (via PAM) for this guest. And that fails: passdb/pampass.c:smb_pam_auth(510)

Hello, I am trying to set up a samba server for a few shared directories on AIX 5.3. It is running in a Windows 2000 domain. It now seems to share properly, but swat does not accept any login ID. I set up swat with the /etc/services and /etc/inetd.conf entries as per the manual. When I use a browser to "http://myserver:901" I get a login box for name and password, but it does not

Hello, We have recently upgraded to samba 3.0.10 (RedHat 7.3) and are now having authentication delays with some of our shares. We are using unencrypted passwords so we can use the pam system-auth...we have the plaintext registry patch on all windows machines that are connecting. The problem is that if you manually connect or browse to a share from a windows box (2k or XP), the client sends your

I've been having authentication problems with samba over the past couple of days as a try to build a new configuration. Try all the different options of using pam, not using pam, encrypted, not encrypted passwords etc. nothing works. So I strip everything (and I mean everything) out of smb.conf and try to use swat for configuration. It fails to authenticate me and finally I get a log

I have downloaded, build and installed samba-4.0.9 from source on two separate boxes running RHEL6.4. My problem is that despite having identical configurations, swat is running on one server and not on the other. Here is my xinetd conf service swat { port = 901 socket_type = stream wait = no only_from = 192.168.1.0/24 user = root server =