similar to: Samba 4.2.0rc4 can't authenticate users

Adding a section of a debug level 5 log at the end that looks like it might have some usefull information. > This problem shows up on both Linux and Solaris. I am going to show > the logs from a Fedora 2.6.25-14.fc9.i686 machine. > > We are using 'security = domain' with a Windows 2000 domain controller. > We are setting 'password server = starfish2' dispite the

> Submitted bug 11098. Debug level 5 logs are attached to the bug along > with the smb.conf file used. > > I am assuming that the problem is with the Wondows 2000 DC because I > assume that 4.2.0rc4 would not have been made available if it could > not authenticate against any domain controller. > > For us this is a fatal bug. > > > This problem shows up on both

I am trying to join a Fedora Linux box running Samba 4.1.5 to a Windows Server 2000 domain controller as an additional domain controller. I should mention that our realm is the same as our domain name, adi.com. This is a 15 year old mistake. And the Windows DC does not have all of our machines listed. To work around that I have delegated _msdcs, _sites, _tcp and _udp to the Windows DC with name

> On Thu, 2015-02-12 at 11:44 -0500, Thomas Schulz wrote: > > This problem shows up on both Linux and Solaris. I am going to show > > the logs from a Fedora 2.6.25-14.fc9.i686 machine. > > > > We are using 'security = domain' with a Windows 2000 domain controller. > > We are setting 'password server = starfish2' dispite the fact that the > >

> > On Thu, 2015-02-12 at 11:44 -0500, Thomas Schulz wrote: > > > This problem shows up on both Linux and Solaris. I am going to show > > > the logs from a Fedora 2.6.25-14.fc9.i686 machine. > > > > > > We are using 'security = domain' with a Windows 2000 domain controller. > > > We are setting 'password server = starfish2'

Hi ... When trying to migrate from samba3 to samba 4.2.2 I am facing a severe problem that bugs me for hours now. I cannot get a samba 4.2.2 fileserver to work with a samba 4.2.2 PDC as a domain member. My scenario: Samba 3 network. PDC and fileserver where Samba 3.6.25. LDAP backend. We can't move to AD right now so I wanted to move to the current 4.2.2 at least to do this step but to

I will probably file a bug about this, but perhaps someone here will have some ideas. We have a problem with files being deleted instead of being saved when making changes in Microsoft Excel. The log shows an error of: 'Lock order violation'. This is with Samba 4.1.6 and happens on both Linux (2.6.25-14.fc9.i686) and Solaris 10. No such problem when running Samba 3.6.22. We have a setup

>>> On Thu, 2015-02-12 at 11:44 -0500, Thomas Schulz wrote: >>>> This problem shows up on both Linux and Solaris. I am going to show >>>> the logs from a Fedora 2.6.25-14.fc9.i686 machine. >>>> >>>> We are using 'security = domain' with a Windows 2000 domain controller. >>>> We are setting 'password server =

I sent this out yesterday and im still having this problem, has anyone seen this before? original email: Im having an intermittent problem with samba. Im running samba 3.0.2a on solaris 8 that i downloaded from sunfreeware.com I have my smb.conf setup to get passwords from my active directory server and it usually works fine. I ran a net join command like so to originally join the domain: root#

Im having an intermittent problem with samba. Im running samba 3.0.2a on solaris 8 that i downloaded from sunfreeware.com I have my smb.conf setup to get passwords from my active directory server and it usually works fine. I ran a net join command like so to originally join the domain: root# net join -S WIN2KSERVER -w MYDOMAIN.com -U Administrator Password: Joined domain MYDOMAIN. It will run

Hi, I am running an Ubuntu 14.04 server with Samba configured to use Quest Authentication Services for user authentication with an Active Directory infrastructure. After an Samba upgrade from version 2:4.1.6+dfsg-1ubuntu2.14.04.13 to 2:4.3.8+dfsg-0ubuntu0.14.04.2, I am facing the problem that none of the configured Samba shares is accessible anymore. The log contains the following entry:

Hello good people, I am fighting with following issue: our users are complaining about very slow/delayed displaying of main folders during accessing server using \\dns.name.of.server (using \\IP or \\netbios_name is it with same slowness). But once they are authenticated, displaying contents of (sub-)folders are getting normal. Once the user hit "enter" key on

Hi, I am running an Ubuntu 14.04 server with Samba 2:4.3.11+dfsg-0ubuntu0.14.04.14, which just provides storage services to the network. It is configured to use an existing Active Directory infrastructure based on Windows servers. Since some weeks I am experiencing issues with accessing the network shares served by Samba (no matter which client/operating system). Connection/mounting attempts

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]

On 4/23/2015 4:40 PM, Ty! Boyack wrote: > > TL;DR (or just in case someone comes across this with the same problem): > > At least with our config in our environment, the current Samba package > from the CentOS base repo fails to properly authenticate sessions > using passwords when acting as a domain member server. It will > authenticate sessions using kerberos fine.If you

Hello, Since last samba update (4.2.10) , users can't access to their share My configuration: a samba server share in ActiceDirectory for homedir, user autentication for user on a openldap server. Windows client are not registred in the AD. Samba server on centos 7.0. If I install the previous samba version, it works. Which parameters should I add to make it works with last samba version ?

Good morning Rowland and samba list ... Rowland Penny wrote on 03.07.2015 18:36:32: > From: Rowland Penny <rowlandpenny241155 at gmail.com> > To: samba at lists.samba.org, > Date: 03.07.2015 18:40 > Subject: Re: [Samba] Migration Samba3 -> Samba4: Accessing domain > member server is not working > Sent by: samba-bounces at lists.samba.org > > On 03/07/15

> hi all, > > my working samba-4.1.7 member of a samba3 domain (samba-3.5.3) failed > while updating to samba-4.2.0. Users were no longer able to access > shares because the trust account was broken. > > According to release notes (Winbindd/Netlogon improvements): > > For the client side we have the following new options: > "require strong key" (yes by

I have a new CentOS 7 installation which I joined to my domain using 'realm join mydomain.com'. That worked great. I can get a ticket with 'kinit administrator at mydomain.com'. But my samba shares don't work. In fact, when I browse (from windows 7 domain member) to the host (lserver), it just times out. Similarly, when I try from another Linux server: smbclient

Hello experts I currently have a file server running on CentOS 7. The file server is joined to the enterprise.com domain (with Samba 4.5). The enterprise.com domain (with samba 4.5) maintains a trust relationship with the example.com domain running on windows server 2012R2. The problem occurs when a user of the example.com (windows server) domain authenticates on a workstation of the