similar to: help with samba and ldap on centos 5

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 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 =

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

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)

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

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.

I was hoping to set up fail2ban to block IP addresses that generate too many Samba password failures, but it needs a syslog message with the IP address of the computer that failed password authentication. Unfortunately, Samba doesn't seem to do this in my environment. Here's a sample error message: smbd[312]: smb_pam_passcheck: PAM: smb_pam_auth failed - Rejecting User brutus ! I

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

Dear Samba gurus, I am setting up file sharing between a new linux box running RedhHat 7.3 and a W98 PC, and almost have things running but have run into a problem that is beyond my ability. I have W98 set up for PlainText password, and have set up Samba to match. Everything seems fine on the linux box. When I enter: smbclient //irisarian/rout -U Gerry%PassWd the connection succeds and

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

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 -

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

I'm running version 2.0 beta. During the initial installation, I configured Samba to authenticate with an NT server. It worked as expected. Now, I want to reconfigure Samba with security = user. I've set encryption = no (and insured that the NT client is sending plain text passwords), and I've removed the references in the smb.conf file to PASSWORD SERVER =. As I expected, the NT

Hi again, as I am finally back working on the problem, I add the smb.conf in the hope somebody can see what I am doing wrong. Samba Version is 3.0.14a from Debian Sarge. Attached is my smb.conf - there may be some unnecessary things in it meanwhile due to too much trying, but anyways. Meanwhile there are some more clients that have problems with password authentication. One thing I noticed is

We are a primarily Linux company with a NIS backend, but we keep a couple "bridge boxes" for Windows users (on a Windows PDC) to connect to their unix accounts and access data. Under Samba 2.2, this was fairly easy with "encrypt passwords = no" turned on. But I can't figure out how to make it work with Samba 3. Does Samba 3 not support a unix passwd backend, or am I

Hi, thank you for your help, but it's not the reason. The user root is not managed in the smbpasswd file. Any more ideas? Thanks, Rudi tuxx:~ # smbpasswd New SMB password: Retype new SMB password: Failed to find entry for user root. Failed to modify password entry for user root tuxx:~ # ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Rudi Labermeier IT Administrator SP3D Chip

Hi, I've setup my Mandrake 10.0 box to use winbind authentication. However, I noticed that root with local files password login fails at first try after reboot. Also there's no way I can authenticate using root when screen is locked. My nsswitch.conf looks like passwd files nis nisplus winbind Won't this first they local files then winbind? Regards, Norman

I'm running a small Linux server with samba installed on it I want to access this server from an XP client which is a member of a ad-domain but when trying to logon XP putts in ad-domain-name\username as logon name to the samba server, how can I work around this?