similar to: Some problems with samba 2.0.7

Hello, I've recently put Samba into production, and while I do love it, I am having a problem I can not figure out. It comes when a regular user tries to change their password. I have dug through the FAQ's I could find, and also looked through a few trouble shooting sections. Everything they suggest checks out. The server as a whole works great. If I log in as root and change a users

Hi All, I installed samba 3.0.22 and join it to Win2003 AD domain. Users from my domain can access the samba shares successfully. My problem is that users from trusted domains can not access to my samba shares Wbinfo -m - show all the trusted domains Wbinfo -u - show all the users include the trusted domains users. Any Idea? My smb.conf global parameters: # Global parameters

'llo, It was suggested that I added "nt acl support = no" to my smb.conf file, in order to get rid of the "error packet at line 588 cmd=115 (SMBsesssetupX)eclass=2 ecode=2" error. (Apparently it has something to do with Word's temporary files that are created with mode 000 which stops it from completing a file save.) I added this to my smb.conf file

Hi list, I have the problem, that a samba 2.2.8a server cannot validate the password with a samba 3.0 pdc for a client request. A samba 2.2.1 works fine. Let me explain the situation in more detail: samba 3.0 pdc machine a samba 2.2.8a server machine b (doesn't work) samba 2.2.1 server machine c (works) samba 2.2.8 client machine d Machine b and c should authenticate the passwords

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

just to verify basic facts: Did you cross check vie network sniff, on which SMB protocol versions Server + Win 7 clients agree ? Or did you pin down via registry ? AFAIK only starting with win 8 or win 10 clients you could ask with powershell, which protocol version is in use. Did you also cross check samba logs for a name resolution issue ( windows names, not DNS) if one of your boxes is an

I've battled this one for a few days now and its costing my sanity so I am hoping that someone here has an answer I am running the samba server 3.0.4 on a linux 2.4.25 server. I can connect to my share point and authenticate fine I can create files or directories in the root of the sharepoint fine I can go into subdirectories and look at all the files... But I cannot create in any

Hi! I am trying to print from an NT machine to a simple samba printer. That NT machine is the PDC and the samba box is having logins authenticated by the NT box. When I try to access the printer with my own username, it works fine. As soon as I have the account that is destined to do the printing print, it can't log in. I have included my smb.conf file and two log excerpts - one successful,

Hello Guys, Having a bit of trouble transferring an 18GB file for backup purposes to a Samba Server. I think the 2GB limit issue was resolved a long time ago? Running Version: Version 3.0.23c-SerNet-SuSE The error on the windows client side ( this is done in some type of bat script ) file creation error the network connection was aborted by the local system. tailing the samba logs, I think the

Dear all, Have managed to put myself in a small bind with regards to user authentication in Samba. Somehow (don't ask...I have NO idea), I've managed to create the situation where my Samba server denies authentication of one single user. Every other user has continued access as before, no difficulties whatsoever. When trying to login with this one user id, Windows 98 SE replies that

On Fri, Nov 03, 2017 at 01:54:10PM +0100, Dr. Peer-Joachim Koch via samba wrote: > Hi Micha, > > no, I have to this. I'm normally just check what smbstatus shows: > > 33837   BGC\pkoch    users        XXX (ipv4:XXX:51118)    SMB2_10 > > Bye the way - 45 MB/s is not so bad, I just wanted to know if it's > possible to get 90MB/s or at 10G a little bit more. >

Hi, I am running Samba 3.6.19 and making my way through all the Active Directory documentation. I have joined various Linux boxes to a Windows Server 2008 R2 Active Directory domain. Windows 7 users who log on with their domain accounts can mount the correct shares exported by the Linux boxes without having to supply any additional credentials. All working perfectly! However, I have a

Hello, I have recently installed Samba 3.0.2 on Solaris 8. All is OK except for Windows NT. I can't open the user's shares on the Samba box. I get : D:\ n'est pas accessible Erreur reseau inattendue (Unexpected network error) I have already set encrypt passwords = No unicode = No in smb.conf and the corresponding register key on NT I have a level 3

I am having problems getting samba to run on HPUX 11. Details: HPUX 11 samba 2.2.2 and 2.2.3a gcc 3.0.1 configure options: --prefix=/samba --with-pam --without-winbind Problem: 1) I am running with logging level at 3 and see many PANIC messages. PANIC: failed to set gid log entry: [2002/03/07 18:55:58, 3] smbd/server.c:exit_server(492) Server exit (normal exit) [2002/03/07 18:56:18, 3]

I'm running Windows Server 2008 and trying to connect to Samba 3.0.37 on Opensolaris. The Samba system is a member of a Windows Server 2008-based Active Directory domain - it was able to join the domain just fine - and Windows XP, Windows 2000, Windows Vista, and Windows 7 can connect, but Windows Server 2008 SP2 cannot connect. The log file is posted below - I'm guessing the key is the

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

My WinXP clients are able to map a network drive on my samba server. However, it takes 30 seconds to do so, and accessing the contents of the shared drive is also quite slow. Linux (smbclient) and Windows 2000 clients are able to map the share instantly, and access files without delay. I am using Linux 2.4.5, with samba 2.2.3a compiled from source on the server. The delay is consistent at 30

Using LDAP and the smbldap-tools. When attempting to join the domain with an administrative user, the computer gets added to the Computers list in LDAP with the following attributes: cn: workstation75$ description: Computer gecos: Computer gidNumber: 515 homeDirectory: /dev/null loginShell: /bin/false objectClass: top, account, posixAccount uid: workstation75$ uidNumber:

I have about 40 SCO 5.0.5 servers on which I am installing samba (I've tried 2.0.3 and 2.0.7, I'm having the same trouble with both). For my example, assume the following: NT domain: ORLANDO_ADMIN NT PDC: ORLANDO_PDC NT user: Administrator (I have tried other users as well) samba server: CLASS guest account (on UNIX server): nouser A generic Unix account exists called samba. My goal