similar to: Acess from windows to share get closed..

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)

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.

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

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

I have setup samba to share a local filesystem with the following config: [global] smb ports = 139 workgroup = WORKGROUP server string = %h server (Samba, Ubuntu) dns proxy = no log level = 255 debug timestamp = yes log file = /var/log/samba/log.%m max log size = 1000 syslog = 1 panic action = /usr/share/samba/panic-action %d encrypt passwords = no security = user obey pam restrictions = yes

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

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 -

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

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

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

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.

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

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 <

Hi everyone; I'm having some trouble with samba on a centos 5 box; the box has been configured to authenticate against an ldap server via authconfig....authentication for normal use (console, ssh) works great....I'm having some trouble with samba using single ldap users or local users....It's rather weird, shares in which access restrictions are based upon ldap groups are working