similar to: currently no logon servers available to service logon request

Hi, Hope can someone give insights or what to do next, regarding with issue encountered regarding with the upgrade of Samba3 to Samba4 NT4-style domain with OpenLDAP backend. It seems the upgrade went well as I could join the domain on the Windows 7 workstations, except adding still the registry mentioned on the link: https://wiki.samba.org/index.php/Required_settings_for_NT4-style_domains and

On Thu, 29 Dec 2016 17:21:19 +0100 Marc Muehlfeld via samba <samba at lists.samba.org> wrote: > Hello Bruno, > > Am 29.12.2016 um 17:01 schrieb Bruno Miguel Martins via samba: > > I've migrated from Samba NT4 to Samba AD, joined other Windows > > DC's to the domain and then demoted my Samba DC. > > > > I am not being able to login from client

Hi Rowland, Samba server was demoted, but it was 4.5.x. Latest one from Ubuntu 16.04 repos. Windows DC's are 2012 R2 and clients vary from 7 to 10, still same problem. Thanks! -----Original Message----- From: samba [mailto:samba-bounces at lists.samba.org] On Behalf Of Rowland Penny via samba Sent: 29 de dezembro de 2016 16:25 To: samba at lists.samba.org Subject: Re: [Samba] Samba AD -

Hello Bruno, Am 29.12.2016 um 17:01 schrieb Bruno Miguel Martins via samba: > I've migrated from Samba NT4 to Samba AD, joined other Windows > DC's to the domain and then demoted my Samba DC. > > I am not being able to login from client computers with the > error stated on the subject. I've tried everything, from making > sure replication is OK, client DNS

On Thu, 29 Dec 2016 16:01:22 +0000 Bruno Miguel Martins via samba <samba at lists.samba.org> wrote: > Hi guys, > > I've migrated from Samba NT4 to Samba AD, joined other Windows DC's > to the domain and then demoted my Samba DC. > > I am not being able to login from client computers with the error > stated on the subject. I've tried everything, from making

All, i have this very weird and annoying problem in my clustered setup: every ~24 hours the vista clients cant login, or even unlock there screens anymore. The error they receive is "currently no logon services available" this is very odd, because i have 2 samba 3.5.8 servers available, running and configured to handle login requests. in the mean time the people that are logged in

Hi people, I have a problem and I need so much of your help. I have a login script in \\server1\netlogon\script.bat (on my PDC and BDC) that runs "net use" commands to map some shares in time of the logon. This login tries to map share in another server (samba member of domain \\server2). So, I put the result at a log and appears these lines: " System error 1311 has occurred.

Hi guys, I've migrated from Samba NT4 to Samba AD, joined other Windows DC's to the domain and then demoted my Samba DC. I am not being able to login from client computers with the error stated on the subject. I've tried everything, from making sure replication is OK, client DNS configuration also. Registry modifications from prior Samba NT4 domain were reverted in the client. Are

Greetings, I am trying to join a EMC Celerra NS502 CIFS server to our Samba 3.0.21a domain controller. According to EMC, I was told that we need to manually create the machine account first. How is the best way to do this? We are using an openLDAP backend, using the idealx scripts. Joining a windows machine from the computer properties dialog of that machine works perfectly. Things I have

On Thu, 29 Dec 2016 18:15:33 +0100 Marc Muehlfeld <mmuehlfeld at samba.org> wrote: > Am 29.12.2016 um 17:34 schrieb Rowland Penny via samba: > > I mis-read that, I thought he had removed the old NT4-style PDC, > > but if he now has (as Marc thinks) no Samba DCs and is only using > > windows DCs, I fail to see how this can be a Samba problem or how > > it can be

Uninstalling MS16-101 fixed our issue. https://technet.microsoft.com/library/security/MS16-101 I ran "wusa /uninstall /kb:3167679", rebooting, and now we are back to normal. On Wed, Aug 17, 2016 at 1:43 PM, Bill Baird <bill.baird at phoenixmi.com> wrote: > Hi All, > > Our users started having issues late last week when trying to change their > passwords. They

Hi All, Our users started having issues late last week when trying to change their passwords. They receive the following message: "The system detected a possible attempt to compromise security. Please ensure that you can contact the server that authenticated you." Client computers are running Windows 7 Ultimate & Enterprise x64. We are still running (I know, I know) and NT4-style

Hello: I am operating a Samba server as the only domain controller in a network consisting of 8 Windows 2000 clients and two Windows 98 clients. The server is running as a virtual machine in Xen and connects to the network over a bridged interface (I mention this because it may be relevant to the problem). 1. If the Samba server is configured thusly: [global] domain master = yes local master =

On Thu, 6 Jun 2024 13:33:04 +0200 Havany via samba <samba at lists.samba.org> wrote: > - Classisupgrade is destructive for the NT4 Domain, but we can keep > data of the old NT4 Domain and we can rollback to this with ours > Ansible playbooks. We will loose all change between migration and > rollback and we will improve a possible long downtime. > > - With "Big

No takers thus far. These are the Samba 4.2 changes to which I previously referred (https://www.samba.org/samba/history/samba-4.2.0.html) : For the client side we have the following new options: "require strong key" (yes by default), "reject md5 servers" (no by default). E.g. for Samba 3.0.37 you need "require strong key = no" and for NT4 DCs

Hi Darin, Le 05/06/2024 ? 17:34, Darin via samba a ?crit?: > > > Hello Havany, > I am just going to jump into this discussion. > Welcome! >> We try 2 scenarios : - A "Big bang" migration to an new domain made from scratch : but we need to migrate all users, computers, laptops, filers without loosing profiles, files server access... In a short time (1-2 weeks

Hello, Le 06/06/2024 ? 15:40, Rowland Penny via samba a ?crit?: > On Thu, 6 Jun 2024 13:33:04 +0200 > Havany via samba <samba at lists.samba.org> wrote: > > >> - Classisupgrade is destructive for the NT4 Domain, but we can keep >> data of the old NT4 Domain and we can rollback to this with ours >> Ansible playbooks. We will loose all change between migration

I'm currently building a Samba3-based domain (DomA) that has a trust relationship with an existing production NT4 domain (DomB). DomA uses an LDAP backend. The LDAP server is local on the PDC and is dedicated to such use. DomA runs Samba 3.5.6 on Debian 6.0. DomB is an old-timer: NT4 domain that's running for ages. The trust relationship has been established: DomA trusts DomB. Clients

When a password must be changed during logon (pdbedit <user> --pwd-must-change-time=0) then this is impossible on NT4 SP6a machines; we always get this error: "Unable to change the password on this account (C00000BE). Please consult your system administrator.". At that time we get these messages in log.smbd: <<<< log.smbd <<<< [Tue May 9 10:46:17 2006 ,

Hi, we are using SAMBA 3.6.1-1 (updating this archlinux machine is tooo ugly) and 3.6.6-1 on archlinux with the LDAP (Server version is 2.4.26-3) backend and manage the users, groups and computer by using the smbldap-tools. Currently we are experiencing the following problems: 1. changing the passwords takes longer than 30 seconds <- That's bad because we are using a gigabit ethernet