similar to: mount with NULL password

Hi, I failed to mount samba 3.0.6's share with NULL password: # mount -t smbfs -o username=alpha,password="" //192.168.3.101/pub /mnt And what samba log say: [2004/08/24 16:30:08, 2] auth/auth.c:check_ntlm_password(312) check_ntlm_password: Authentication for user [alpha] -> [alpha] FAILED with error NT_STATUS_WRONG_PASSWORD But it is ok when using samba 2.2.8a! Best

Can anybody answer me?! Thanks in advance!!! I have patch 3.0.6 with all patchs in http://samba.org/~jerry/patches/post-3.0.6/ , and set null passwords = yes in smb.conf. It works well to mount samba share in linux box when user alpha have non-empty password. But when set alpha's passwork as NULL, I get the follow messages: # mount -t smbfs -o username=alpha,password=""

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

Hi everybody, I want to use my samba-shared Homedirectory from my Linux-Server on my Linux-workstation. I was using smbfs until now, but since i upgraded my hardware i'm not any more able to use smbfs, i get error-messages (timeouts) in the kernel logs and I/O-Errors on the console. Having this problems i read about cifs and that's much better, nicer, sexyer and faster than smbfs.

Hello im trying to migrate from Samba 2.2.8a to 3.0.9. The Server is a PDC using ldap and winbind. I used the convertSambaAccount script to convert the ldap schema from old to new. I shut down the old smb server and started the new one. The share one the new server are accessible from my still running W2k machine. If I start another machine und log in as a user, that was logged in before from

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

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]

This is really bizarre. Running Samba 3.0.4 on SuSE 9.1. The password backend is smbpasswd. Each user has a system and samba account and everything has worked as expected until recently. But now, every new user I create is unable to log into Samba server (older users are still able to log in). Inspecting log.smbd the following messages are displayed: [2004/07/22 11:44:56, 2]

Hi all, In short, how do you force smbclient not to use Lanman passwords ? I specify these in my smb.conf lanman auth = no min protocol = NT1 Trying smbclient from the same host, root@localhost root]# smbclient //fileservertest/private -U somebody Password: Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.0.2a] tree connect failed: NT_STATUS_WRONG_PASSWORD Here are the logs, [2004/03/17

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

I have a Redhat Enterprise Linux (v3.0) box running Samba 3.0.9-1.3E.3. This box only has two Samba shares created on it, each of them with a single "valid user" entry. The relevant smb.conf information is included below. The problem is that when user1 tries to connect to \\server\user1 and authenticate via AD, the connection fails with a "unknown username or bad

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

Hi, Can anybody confirm the following problem: Sequence: bash-2.05# grep ankerpos /usr/samba.moonrock/private/smbpasswd ankerpos:921:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:[U ]:LCT-0 bash-2.05# /usr/samba.moonrock/bin/smbpasswd -c /usr/samba.moonrock/lib/smb.conf ankerpos New SMB password: Retype new SMB password: bash-2.05# grep ankerpos

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

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

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

Hi, all: The follow parameters work well in samba 2.2.8a, But I updated samba from 2.2.8a to the latest samba 3.0.5 , I can't write 'test' share! What is the ploblem? [test] path = /pub/test force user = abc write list = jacky valid users = jacky,abc create mode = 0664 directory mode = 0775 Best Regards! Jacky Kim .

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