similar to: Next Problem: windows 10 as samba domain member

Good Morning Marc, Marc Muehlfeld <mmuehlfeld at samba.org> wrote on 09.07.2015 17:49:36: > Am 09.07.2015 um 14:35 schrieb Roland Schwingel: > > I got windows 10 pro build 10159 running in a vm. I added the 2 well > > known registry changes I always add to windows 7 also to windows 10. So > > far so good. I joined the machine to my samba 4.2.2 PDC. Heureka! It >

Hi.... Some days ago I installed windows 8 pro from MSDN on one of my machines. I got a serious problem with it. I cannot logon as domain user. I first tried joining my domain from win8 with an unchanged win8 installation. This did fail. Afterwards I applied the usual windows 7 registry patches to allow a samba domain join and rebooted. Afterwards I could join my domain with no trouble. I

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

Hello Rowland and Christian Thanks for your replies... Yes ONEVISION and MYDOM are the very same here. Copy/Paste. "Christian Naumer" <christian.naumer at greyfish.net> wrote on 18.04.2023 20:12:35: > Am 18. April 2023 14:29:29 MESZ schrieb Roland Schwingel via samba > <samba at lists.samba.org>: > >Hi... > > > >We are still using NT4 classic

Hello John, Am 09.07.2015 um 17:08 schrieb John Drescher: > Hmm. On 2 test boxes I am now getting no login servers available on > 10162 (while it worked for previous builds and I do not experience > that on my windows 7 or 8.x machines). 10130 crashed just after the > login was accepted if the network cables were connected ( I have 2 > networks at work gigabit private to samba

Hi... We are still using NT4 classic domain with a couple of samba server but want to upgrade step by step to AD as a distant goal. We tried to upgrade to samba 4.17.7 as in intermediate step and keep LDAP for now but fail as we could not find a suitable example for id mapping. Hope someone can help! Previously we did run samba 4.7 on CentOS 7 without problems as domain controller and member

On Thu, Jun 13, 2019 at 07:02:27PM +0100, Rowland penny via samba wrote: > On 13/06/2019 18:21, Stefan Froehlich via samba wrote: > >File server and Linux clients shall use the AD-backend, so I read > >and followed <https://wiki.samba.org/index.php/Idmap_config_ad>. > >There it says: > > > >"Whichever setting you use, the group (or groups) set as the

Am 18. April 2023 14:29:29 MESZ schrieb Roland Schwingel via samba <samba at lists.samba.org>: >Hi... > >We are still using NT4 classic domain with a couple of samba server but >want to upgrade step by step to AD as a distant goal. >We tried to upgrade to samba 4.17.7 as in intermediate step and keep LDAP >for now but fail as we could not find a suitable >example for

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

What is the minimum version of Samba supported on AIX version 5.1. I have installed version 2.0.7.0. Will this work? Thanks in advance. Ron Schwingel Technical Support NDS Solutions 303.755.4411(phone) 303.755.4545(fax) rschwing@ndsltd.com

Hi ... Rowland Penny wrote on 06.07.2015 13:22:57: > > Is there no way to detect on my PDC what is the problem. Why is my PDC > > Samba rejecting my samba member server...? > > > > Permissions ?? Is the join correct ? Yes... net rpc testjoin returns OK. > It has been sometime since I did anything major with an LDAP PDC and > even then I used smbldap tools. It

If I setup a samba 4 PDC (not AD) like I do with samba 3, I still have to change the follow registry key on Win 7/8/?/10 for join it to samba domain ? > [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanWorkstation\Parameters] > "DomainCompatibilityMode"=dword:00000001 > "DNSNameResolutionRequired"=dword:00000000 > >

Hi Roel, Thanks for your reply... Roel van Meer <roel at 1afa.com> wrote on 09.07.2015 15:00:07: > Roland Schwingel writes: > [snip] > > > So the problem is appearing here: > > [2015/07/06 08:02:47.188335, 0] ../source3/auth/auth_domain.c: > > 302(domain_client_validate) > > domain_client_validate: unable to validate password for user roland in

I prepared samba PDC and not able to join windows 10 clients. Please suggest any windows 10 registry settings.

Hi, I got the same problem with Build 10162. I dont think it's an Samba issue. It seems that Windows 10 dont like "\\....\netlogon". Our Samba 3.5.6 PDC works like a charm for win 7. From my Win10 PC i can access everything except \\dc1\netlogon Symptoms: Accessing \\dc1\netlogon -> Auth fail Accessing \\dc1\netlogon2 -> Works (same config!!!) Accessing \\dc1\s1\netlogon

On 13/06/2019 19:57, Stefan Froehlich via samba wrote: > On Thu, Jun 13, 2019 at 07:02:27PM +0100, Rowland penny via samba wrote: >> On 13/06/2019 18:21, Stefan Froehlich via samba wrote: >>> File server and Linux clients shall use the AD-backend, so I read >>> and followed <https://wiki.samba.org/index.php/Idmap_config_ad>. >>> There it says: >>>

Hi all, some years ago i configured a `Primary Domain Controller` through Samba and LDAP (slapd) on an Ubuntu machine (13.10) at 192.168.69.203 which should be accessible by the string/name `SRV1`. I must note i did not installed winbind. I've never had any issue and it looks like it's working fine as about 10 Windows machines joined the PDC and Windows users can login against PDC on

Hi... Out of sudden our samba file servers are no longer honoring secondary group membership. I appears that the fileservers are no longer seeing groups. When I do a 'net -U <domUser> rpc group list' on the PDC everything is fine. I can see all groups. When I do this on the fileservers I do not receive anything. We operate samba 4.3.9 both as classic PDC (for a couple of reason

On 14/05/16 05:10, Ram Prasad Bikkina wrote: > ---------- Forwarded message ---------- > From: Ram Prasad Bikkina <parvathiprasadb at gmail.com> > Date: Sat, May 14, 2016 at 9:39 AM > Subject: Re: [Samba] Not able to join windows 10 clients to samba 3.6.23 > NT4 Style PDC > To: gaiseric.vandal at gmail.com > > > Hi Gaiseric Vandal, > > I applied these

If this is an NT4-style domain, then DNS is not essential. Things like SRV records aren't relevant since a lot of the NT4 is back from the NetBios days. It looks like your Win 10 machine thinks it is trying to join an AD domain. Windows clients machines typically are using DNS to resolve server names to IP addresses. However DNS does not provide info on locating PDC's