similar to: Migration Samba3 -> Samba4: Accessing domain member server is not working

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

Thanks for your reply, Rowland Penny <rowlandpenny241155 at gmail.com> wrote on 06.07.2015 10:03:20: > > In the first 2 lines of the log I see the SIDs dumped. > > Both for my domain and for my member server. > > > > SID for local machine OSUSE-TEST is: > > S-1-5-21-1853263269-3041869306-167322181 > > SID for domain MYDOM is:

On 06/07/15 11:33, Roland Schwingel wrote: > > Thanks for your reply, > > Rowland Penny <rowlandpenny241155 at gmail.com> wrote on 06.07.2015 > 10:03:20: > > > > In the first 2 lines of the log I see the SIDs dumped. > > > Both for my domain and for my member server. > > > > > > SID for local machine OSUSE-TEST is: > > >

Hello, I am attempting to debug an issue with my Samba configuration. It has been working fine, but we recently updated Samba from 4.6.x to 4.8.3 and are now seeing some issues authenticating. Most of our servers are still working fine after the upgrade, but one server is giving us issues. A little more environment info: The server is running Centos 7.1. Windows clients can connect OK. We are

Hello, I have a strange problem with Samba AD member: It is accessible via \\server or \\server.domain.local But when I try to access it with its IP address, ex. \\10.15.10.1 I get access denied error and prompt for user and pass. Entering username and password with or without DOMAIN\ has no effect. The server is FreeBSD 10.1. It behaves the same way with Samba 4.1.18 and now with Samba 4.2.2

Hi, I encountered a strange problem...some of my windows machines cannot be joined to an Samba 4.17 AD domain (8 of ~90 clients). These are 7 Win7 clients and one WinXP client. The message I receive in windows is: "Logon failure: unknown user name or bad password". All other Win7 and XP machines could be joined...the same OS image has been used to install both the machines that could be

Hi Davor, thanks for the answer. They were actually part of a NT4 domain called mayweg.net (the new realm name). But I did join workgroup "WORKGROUP" before I tried to join the new domain. If it's possible that they're sending the information the wrong way because they were part of a workgroup named after the new realm, is there any way to clear the old data (apart from a new

Hi Davor, most of the domain accounts were part of an old NT4 domain. I did a classicupgrade. Your theory with the NTUSER.DAT-files seemed so promising, unfortunately that was not it. I created new accounts on an XP machine and a Win7 machine and tried to join with them, but still receive the same error. One of the machines I'm not able to join with, wasn't even part of the domain

Hi Davor, I finally found it! After going through https://wiki.samba.org/index.php/Joining_a_Windows_Client_to_a_Domain , I checked the time settings on said clients and they differed from the AD DC too much. This also explains why some clients could join after a while...they synchronised with a NTP server after a day or so and then I was able to join. After that, joining the rest of clients was

I have a small home network with server and 5 clients all on an internal LAN with private IPs. Samba, Version 4.7.6-Ubuntu, file sharing is not working on the server for any of the 5 clients. I have tried both mount.cifs and smbclient. The same errors are thrown in the server's samba logs for all connection attempts, regardless of how the client tries to connect: getpwuid(1000) failed,

Hi, Just a moments ago i've sent a message to other user saying that I've a working server with CUPS authentication using AD groups. Well, that authentication is not working anymore and i've not changed anything... The thursday I was configuring the server to allow the management of cups with AD groups and was working perfect. After that i've added some printer alias to samba

Hello to the Samba Mailing List, This is my first post, so please, should I commit any faux pas, nudge me in the right direction and I will adjust accordingly. I'm experiencing a complete failure of the PDC in a Samba 4 AD Domain I've deployed for a client. Samba failed a few days ago and I've been unable to resolve the issue on my own. Google searches are leading me in circles,

2015-05-04 18:16 GMT+02:00 Rowland Penny <rowlandpenny at googlemail.com>: > On 04/05/15 17:03, Daniel Carrasco Mar?n wrote: > >> Hi, >> >> Just a moments ago i've sent a message to other user saying that I've a >> working server with CUPS authentication using AD groups. Well, that >> authentication is not working anymore and i've not changed

Hi, I have a Samba4 File Server on Debian 10 I am not being able to assign permissions on shares to groups that already have the Unix attribute set. Groups without the Unix attribute are working OK. My two DC are Samba4 (migrated of the Windows 2008 Server) and my current File Servers are Windows 2008 Server. I followed "Setting up a Share Using Windows ACLs" tutorial (

Hai, The best info is missing. What are the windows event ID errors? What is the right set on the profiles folder? If you layout is : /home/samba/profiles and you shared the folder profiles, then show me getfacl /home/samba/profiles. I see your running, Samba 4.7, are you able to upgrade to 4.9.4? This: ~# cat default-rights-sysvol.acl # file: /var/lib/samba/sysvol # owner: root #

Hi all. I am running Debian jessie server with Samba, which has joined the Active Directory domain. The domain controllers are Windows Server 2012 R2. After I upgraded Samba version from 4.1.17+dfsg-2+deb8u2 to 4.2.10+dfsg-0+deb8u2, I'm facing the problem that I can't access Samba share by NetBIOS Aliases or IP Address. The Samba's NetBIOS name is mysamba, and I can access by

Hello, i have migrate a Samba (3.0.20b-3.19-1616-SUSE) to debian 9 (4.5.16-Debian). On the old suse users are created with smbpasswd -an foo On Windows (10) users have a User account with also empthy passwords. No AD or NT4-Domain (round about 10 Users) Then I try to connect to the share smbclient -NL \\192.xxx.xxx.xxx work. Connect from Windows to share with no password dosed work. Set a

Greetings, All! I'm trying final steps of my long upgrade process, but I've got hit by the unexpected. When everything seemingly run fine in the end, I'm unable to browse the local shares of the DC. # smbclient -L localhost -U% Domain=[CCENTER] OS=[Unix] Server=[Samba 4.1.11-Ubuntu] Sharename Type Comment --------- ---- ------- Error returning

Are there any logs on the client or server at a higher log level? Andrew Bartlett On Wed, 2020-05-20 at 12:39 +1200, Grant Petersen via samba wrote: > I forgot to mention that using the smbclient option > > -A /etc/cred/authfile > > behaves the same way as attempting to manually enter the password on > the command line; failing in 4.12.2 and working in 4.11.0 > >