similar to: Upgrade to 3.0.14 breaks NT4 client login

NT4.0 SP4 gives me this error when trying to access a Samba 3.0.23c server. \\Omega300\files is not accessable The specific network password is not correct. omega300 is the samba server, running samaba 3.0.23.c on SCO Openserver 5.0.7. omg180 is a Windows NT4 SP4 box. omega is a Windows 98 box. Passwords are not encrypted. We are also using VisionFS (SCO's smb product, which they no longer

Hi, I'm using 3.0.21b and I cannot get the guest account to work. some of smb.conf: ------------------------------ security = user hosts allow = 192.168.2. 127. guest account = visiteur log level = 2 log file = /var/log/samba/samba.%m max log size = 1024 socket options = TCP_NODELAY [publique] path = /vol2/samba/publique browseable = yes guest ok = yes

Hello all, I'm trying to set up my Samba server to use share mode security and tried to protect a share with a password. I've done the following on smb.conf [global] workgroup = WORKGROUP netbios name = %h server string = Servidor Samba %h security = share client lanman auth = yes log level = 0 auth:10 [publico] path = /tmp

Vista32 3.0.25pre2 (I understand vista patches for "share level" are already in) security = share (with "valid users" on share definition) host msdfs = no user/pass in smbpasswd file. If I use "connect network drive..." method with "connect as another user", then it will always work. If I use start, search , \\server\share and then type user/pass in

Hi, I have several servers in separate networks currently running samba 2.2.5. Each server can have aliases and I'm using the %L macro in share path, so that each appear as a separate 'virtual' server - depending on how the client calls it. There is at least one SMB users defined in 'smbpasswd' file. Here is the current config: > [global] > workgroup = MYGROUP

Hi, I'm using 3.0.21b and I cannot get the guest account to work. some of smb.conf: ------------------------------ security = user hosts allow = 192.168.2. 127. guest account = visiteur log level = 2 log file = /var/log/samba/samba.%m max log size = 1024 socket options = TCP_NODELAY [publique] path = /vol2/samba/publique browseable = yes guest ok = yes

Hi, I've just installed Samba-3.0.0 on a Sun Ultra 5 Solaris 8. >From the Sun, smbclient //MySun/MyName runs OK. >From Windows 2000, I can open shares like \\MySun\MyName. >From Windows NT4, opening \\MySun\MyName doesn't work. In the Samba logfile, setting debug level to 3, I can read : check_ntlm_password: Authentication for user [correge] -> [correge] FAILED with error

3.0.25rc1 has the same issue. On Fri, 06 Apr 2007 22:52:05 +0200, Giulio <giulioo@gmail.com> wrote: >Vista32 >3.0.25pre2 (I understand vista patches for "share level" are already in) >security = share (with "valid users" on share definition) >host msdfs = no > >user/pass in smbpasswd file. > > >If I use "connect network

I have really weird problem with XP Pro and Samba 3 (I tried 3.0.1 and 3.0.2). Samba 2.2.8a works with no problem. I can login with no problems. But when I login and logout few times (sometimes one, sometimes five times) then XP can not load roaming profile from the server (login still works). I can access to all shares with no problems. The only way to fix that is to restart XP machine. And then

We have a client machine (Windows 2000) that runs an application which spawns separate processes with each authenticate separately to the SAMBA server (3.0.13) When several of these processes run at the same time, SOME of the authentications fail with NT_STATUS_WRONG_PASSWORD written to the log.smbd file (error level 2)...I've attached a snippet of the log file to the end of this message All

Hi all, I have a domain member server 3.6.6 running on debian7, authenticating against another debian7 + samba 3.6.6 in DC-mode. Both servers have user-accounts and groups on LDAP and resolve posix users using libnss-ldap. The groupmap is living on LDAP as well. The domain member server serves a share with ACL enabled. I got the upgrade to 3.6.X and idmap-updates working, but the old

Dear list subscribers, Recently I upgraded my samba version from 2.0.5 to 3.0.8-2. The setup I use is basically very simple: a W 98 box should be able to access some disk-shares and a printed, connected to a Linux box, running Debian's sarge distribution. Accessing the disks is no problem, but the printer can't be accessed any more. My log.smbd logfile shows lines suggesting

I have two SAMBA PDC's with an OpenLDAP backend. My goal is to establish an interdomain trust between the two domains so that users from each backend can login to Windows systems by specifying accounts from either domain. I've followed the steps to establish the trusts and I can see accounts and groups using wbinfo and getent. I can access resources/shares from each domain but I'm

I've setup a samba-3.0.11 share with [General] guest account = ftp security = domain [pub] comment = pub path = /pub read only = yes browseable = no guest ok = yes And attempts to access the share from WinXP(sp2) clients anonymously fail, Appended is the (log level 2) samba.log entries (names changed to protect the innocent): [2005/02/08 13:34:30, 2]

Hi here, I have the following problem: I have win98 / Win XP pro / Win2k Pro clients and a samba 3.0.2a server. When i try and change passwords from a win98 client it all works fine, but when i try to change a pw from a win2k or win XP pro client i get a message: "The system cannot change your password now because the domain GENERAL is not available" (our domain is called GENERAL)

I really don't know where to start on this one... We have an XP Pro workstation. The user on this workstation is, say, 'bob'. Earlier this year, bob would log in to his workstation with a different password than was on the Samba machine. I /think/ that's what's causing the problems, but I'm not sure. Anyhow, we had specifically mapped drives on bob's workstation

Hai, Have you seen : https://wiki.samba.org/index.php/Authenticating_Freeradius_against_Active_Directory Test with : ntlm_auth --allow-mschapv2 --request-nt-key --domain=COMPANY --username=domainuser --password=userpassword Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens Oleg > Blyahher via samba > Verzonden:

Q#1. What SAMBA related object classes and attributes I must add to a POSIX user in LDAP (SunOne DS 5.2) before it can be used by SAMBA for authentication? Q#2. Why does the SAMBA log for the user show the error ?FAILED with error NT_STATUS_WRONG_PASSWORD? even before the user is prompted for username and password on the SAMBA client? Also in this log, I saw another error ?NT MD4 password

Hi, Samba 3.0.8 installed on Debian Linux server and setup to authenticate with Windows 2000 ADS. The samba config as follows. [global] workgroup = TEST_NT_DOMAIN realm = TEST-NT.ORG server string = TEST SAMBA security = ADS obey pam restrictions = Yes password server = 10.10.20.253 10.10.20.227 passwd program = /usr/bin/passwd %u

Greetings samba list, I'm running into an issue when attempting to use "map unknown to domain" on a samba servers bound to my AD domain. When a client maps a share and is not part of the domain, the domain is properly mapped for the user (according to the logs), but the domain controllers report that the password is wrong. I've copied my password out of notepad and pasted it