search for: kleinhesselink

I've been running a NT4-style domain with a samba 3.x PDC using a LDAP back end and it's mostly worked very will for a long time. However since yesterday, clients are having problems with the domain. I saw that updates came out on all my systems - my PDC and BDC are ubuntu 12.04 LTS. The samba version there still seems to be 3.6x. A client with a problem that was working is Ubuntu

I have a samba3 domain controller and a bunch of linux/windows clients. One of my users came to me with trouble trying to access one of the linux clients. He was getting the: NT_STATUS_NO_LOGON_SERVERS error. However the client machine had no trouble with my credentials, or with another set of user credentials. I reset his password on the samba3 DC and verified that the DC would authenticate

El 20/04/16 a les 01:46, Dirk Kleinhesselink ha escrit: > > I've been running a NT4-style domain with a samba 3.x PDC using a > LDAP back end and it's mostly worked very will for a long time. > However since yesterday, clients are having problems with the domain. I > saw that updates came out on all my systems - my PDC...

I have a classic NT4 domain with the PDC also the wins server. With the recent ransomware problem, we're trying to remove SMB1 and below protocols. However when I do this, the browse list is gone. Hosts can access properly the shares, but they have to know exactly \\machine\share in order to to connect. The same thing from a linux client: smbclient -L {PDC} -m SMB2 Domain=[{MYDOMAIN}]

I have a linux server that I'm preparing to migrate our samba services to. It has been running as a stand alone server and I intend to set it up as a PDC - we have another old system working as a PDC now. Because of some problems during samba testing (quite awhile ago) I decided to upgrade the samba version running on the server - the original packaged samba was 3.0.20 and I downloaded

I very much appreciate the help thus far, but I think it has strayed a bit from the actual problem. The problem is that when I join a system to the samba domain it creates /some/ but not all of the required attributes for the computer account. The process then fails as samba looks in the wrong part of my directory server. I would strongly prefer to put the workstation accounts in their own tree

Some of my users are reporting that they are losing files when copying directories containing large numbers of files from windows machines to OS X / Linux machines. I have been able to verify this behavior with a test directory. The directory contains 1194 files for a total of about 2GB of data storage. If I mount the windows filesystem via mount_smbfs on OS X or smbmount on Linux, then cd to

With the ubuntu security updates on Monday that broke everything, I downgraded my 12.04 3.6x samba packages on my NT4 DC - now my windows 7 domain members can join and function OK and am looking into a 14.04 client that was a member and cannot now join, and the downgrade also failed. So I got 4.4.2 source and built on the system and have tried to join, but it fails. Below is some debug