similar to: windows server authentication problem

Folks: I've got several systems attached to a 2003 domain where we use kerberos to authenticate. When I upgraded a system to the latest greatest samba things stopped working. Just to find where it happened in the different versions of samba I downloaded, built, & ran 3.0.23d to 3.0.25c using the same smb.conf file. Turns out the 2.0.23d and 3.0.24 works but from 3.0.25 on it fails.

================== platform ===================== Linux version: RHEL-3 resp. Scientific Linux 305 Samba vesrion: 3.0.9-1.3E.3 Samba operating mode: security = SERVER ================== problem ===================== 'net use n: \\smbs1\public' on Windows XP, always asks for a password. 'smbmount //smbs1/public /mnt/public -o password=' does not. This all used to work fine

I did this a few years ago (RHEL 4.0 -- samba 3.0.10) and had a nice working setup... until the drive developed bad sectors and wouldn't boot. Now I'm starting with a fresh OS (ArchLinux -- samba 3.0.31) and trying to recreate what I had working before. My previous setup (which worked nicely): RHEL 4.0 running samba 3.0.10 security = server password server = <DC's IP>

Hi all, I had linux samba 3.0.10 running as PDC of my domain which does only authentication for other linux samba boxes which are providing access to shares. After upgrade of PDC to Debian Lenny + samba 3.2.5 I've lost guess access to the shares which are run by samba 3.0.x boxes, while it works on samba 3.2.5 samba box. the scheme is like following :

Just the beginning of a question to anyone who might have experienced the following issue with Samba 3.0.2[5-6] series. We currently have service accounts accessing Samba shares on AIX 5.3 servers ( from TL04 - TL06 ). Most of the processes access the shares via UNC rather than mapped drives. After completing the upgrade to Samba 3.0.26a on the production side, the service accounts started

I have a samba server that is configured in "server" mode. However, I want to share one folder to everyone - whether or not they have a real account on my system, or on the server that I am authenticating against. The [global] section of my config file has things like this: log file = /var/log/samba/%m.log load printers = no guest account = lexbig

Hi, I am new to samba. I have configured password server to authenticate centos users. But i got the following errors and not authenticating. [2007/10/29 02:48:24, 1] auth/auth_server.c:check_smbserver_security(363) password server WINDOWS rejected the password following is my smb.conf [global] workgroup = WINDOWSAD server string = Samba Server security = SERVER password

Hi Folks, Recently (I believe since recent 3.0.x releases), I have been unable to login to a Samba instance using CIFS (Linux mount) or Windows 2003. If I change the smb.conf from: security = server to security = user I _can_ login again fine. The NT PDC always replies with NT_STATUS_LOGON_FAILURE. It's event viewer shows that the proper username is being used, but that the password is

Hello list, I have trouble with a smb configuration that worked fine before I upgraded my samba to the latest stable release. I used samba 3.0.23c (Slackware11) and now I'm using samba 3.0.25b (Slackware12). The error/failure looks like this: I'm trying to connect to my HOME service and I fail. The log produces only this: [2007/08/13 10:29:33, 1]

Hi, I've some problems with one of our samba fileserver (debian stable 3.0.14a-3sarge1). Every few weeks, I get the following error messages for all users that want to access/mount a share: [2006/03/16 08:52:53, 2] auth/auth.c:check_ntlm_password(312) check_ntlm_password: Authentication for user [PID51C9] -> [PID51C9] FAILED with error NT_STATUS_LOGON_FAILURE [2006/03/16 08:52:57, 1]

Hi, periodically we are seeing the following error in our samba log. At this time nobody can connect to the shares of this server anymore. [2007/04/17 09:05:59, 2] auth/auth.c:check_ntlm_password(312) check_ntlm_password: Authentication for user [PID33C1] -> [PID33C1] FAILED with error NT_STATUS_LOGON_FAILURE [2007/04/17 09:06:03, 1] auth/auth_server.c:check_smbserver_security(263) the

Hi, I want to move from Samba 2.2.12 to 3.0.10. I downloade the 3.0.10 sources and compiled them (Solaris 8). Everything went fine. After the install, I tested the new 3.0.10 Samba with the old smb.conf from 2.2.12 (the docs say this should work). I could not log in anymore. I switched back to 2.2.12 and tried the 3.0.10 install on a Suse Linux 8.0 - with the same results. I used most parts from

Installed Samba 3.0.10 via 'pkgadd' on Solaris 2.6 workstation s080 (137.223.31.80) - previously running Samba 2.2.8 which has worked for a long time. Samba 3.0.10 smb.conf file - changed to security =DOMAIN from SERVER at 2.2.8 version password server = 137.223.33.45, 137.223.33.72 - these are DCs # Samba config file created using SWAT # from 127.0.0.1 (127.0.0.1) # Date:

We run Samba, but wish to authenticate against Windows DC. We do this using the "security = server" mode. We don't have the option of being part of the Windows setup directly. Although authentication is done against Windows DC (so users are not prompted for passwords) users do need a Unix account to use the service. We have users in multiple Windows domains, and the DCs we

I'm running 3.4.6 (was running 3.0.28a but upgraded in hopes to fix this issue). Clients running Windows 7 that are NOT joined to the AD domain (samba authenticates against it via "security = server") cannot authenticate to access the server. Clients running Windows 7 that are on the domain as well as Windows XP, Windows 2003 on and off the domain work as expected. Any help would

Hi All, since an upgrade from 3.0.24 to 3.0.25 on 2 separate sun solaris (v3.8,v3.9) boxes I have experienced an inability to authenticate. $ smbclient -L //serverbox -U username Password: session setup failed: NT_STATUS_LOGON_FAILURE My global config is as follows: workgroup = WORKGROUP server string = SERVERBOX Samba Server security = SERVER obey pam

Hello, We are currently upgrading our Windows XP PCs to Windows 7 and I'm running into some weird issues. Background: Windows XP/7 PCs connect to Active Directory on Windows 2008 R2 Samba 3.5.10-125 is installed on RHEL 6.3 Server. RHEL servers are connected to an FreeIPA (IdM) server which uses the Red Hat Password Sync tool to sync passwords. So we just started testing Windows 7 and so

And I have verified I am typing in the correct password. So it looks like there is some problem with encryption or something. smbd and nbmd are version 2.9999 (Debian packages) Thanks. --James Lamanna ------=_NextPart_000_006A_01C2864A.76DEA5C0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML

Hello! We have Mandrake Linux 9.0 system with Samba v2.27 serving as a PDC for ~400 users. (Hardware: P1800, 256Mb). The performance is acceptable- user can log in in approx. 5 sec. (Includes copying ~700Kb roaming profile). Now we've got new server (P3000HT,512Mb,SATA) with Mandrake Linux 10.1 community and Samba 3.09 (compiled from sources). And guess what? Now user on the *same* computer

Hello, i am using net-fs/samba-3.0.10 on an updated gentoo linux on x86 machine. recently i was using some older version, probably 3.0.9 i didn't change my smb.conf but now printing from windows 98 clients does not work anymore. the errormessage on win98 is (translated from german): Error when writing on \\master\stylus1160 vor printer (EPSON Stylus Color 1160): The network printer ist not