similar to: samba 4.13.17 ubuntu 20.04

On 26/01/2023 07:20, Marco Querci via samba wrote: > Hi everyone, > > I'm posting here because I'm facing a kerberos authentication problem after > the 2:4.13.17~dfsg-0ubuntu1.20.04.4 samba upgrade. > The clients, win10, win11, win2016 cannot login to AD anymore. > On server logs the authentication succeeded but in the Event Viewer on the > client I have this error:

Hey Andre,? Sure, we already on the latest Patch Level on Ubuntu with 2:4.13.17~dfsg-0ubuntu1.20.04.4 Installer, but the issue still exist.? The only way to resolve the issue and to make a login possible again, was the workaround in my previous mail.? The Windows clients are Windows 10 22H2 with all updates installed. We also doesn't have any special settings in smb.conf. If you have any

Hi, today we've installed latest samba update on ubuntu 20.04: 2:4.13.17~dfsg-0ubuntu1.20.04.5 Now the login issue is solved. We've rolled back the windows settings for local security for Kerberos encryption. Many thanks to the developers and support Best regards Frank -----Urspr?ngliche Nachricht----- Von: Andreas Hasenack <andreas at canonical.com> Gesendet: Donnerstag, 26.

All, is it possible to create a new KVM machine from an existing qcow (v3) image with snapshots? snapshot-list doesn't show them, when using virt-manager 1:1.5.1-0ubuntu1.1 to create the machine. * t-ad5.img: QEMU QCOW Image (v3), 42949672960 bytes chris@cd:/data/md0$ qemu-img snapshot -l t-ad5.img Snapshot list: ID TAG VM SIZE DATE VM CLOCK 1

We have the same issue with Samba 4.13.17. For Ubuntu 20.04 with Samba 4.13.17 there seems to be only a workaround to solve the login problem: Modifying the Local Security Policy -> Local Policies -> Security Options -> Network security: "Configure encryption types allowed for Kerberos" Check only DES_CBC_CRC, DES_CBC_MD5 and RC4_HMAC_MD5. ? This worked for us to login again. ?

hail, I have a 7-stable: [matheus@xxx /usr/home/matheus]$ uname -a FreeBSD xxx 7.0-STABLE FreeBSD 7.0-STABLE #2: Sun Jul 6 15:03:26 BRT 2008 root@lamneth:/usr/obj/usr/src/sys/xxx_7 i386 and there exists three geom things. gconcat status Name Status Components concat/concat0 UP ad4 ad5 gmirror status Name Status Components

i'm having intermittent issues with windows 10 clients (dont have win7/xp) on the network. i frequently get users being unable to login even when they put correct credentials. when that happens wbinfo --authenticate user completes successfully on the controller (just one on the network), same with authenticating webmail/intranet against PDC works. time is in sync. sometimes rebooting the PC

Support virtio drivers for Windows Server 2016 once they are available. Signed-off-by: Tomáš Golembiovský <tgolembi@redhat.com> --- v2v/windows_virtio.ml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/v2v/windows_virtio.ml b/v2v/windows_virtio.ml index 354aa19..334e347 100644 --- a/v2v/windows_virtio.ml +++ b/v2v/windows_virtio.ml @@ -330,6 +330,8 @@ and

On Thu, Jul 13, 2023 at 11:47?AM Bo Kersey <bo at vircio.com> wrote: > The patch on Windows Server 2012 R2 that does the same thing as kb5028166 > is KB5028228 > > > ------------------------------ > > *From: *"Philippe LeCavalier" <support at plecavalier.com> > *To: *"Bo Kersey" <bo at vircio.com> > *Cc: *"samba" <samba

I have previously written about a mountroot prompt, here are some details. I have a system with an asus m3a78-emh hdmi board, a 74 gig raptor drive, and a dual core amd am2 cpu. I have had this result with both the amd64 and i386 systems. My steps were all conducted today as follows. install 7.0 release run freebsd-update get src tree build world build and install kernel reboot and be greeted

The patch on Windows Server 2012 R2 that does the same thing as kb5028166 is KB5028228 > From: "Philippe LeCavalier" <support at plecavalier.com> > To: "Bo Kersey" <bo at vircio.com> > Cc: "samba" <samba at lists.samba.org> > Sent: Thursday, July 13, 2023 10:43:55 AM > Subject: Re: [Samba] Fwd: ComputerSecureChannel -Verbose False

Hallo, perhaps someone hat a hint vor me. My centos 7 samba Server ist working fine using Win10 Clienst with Domaine-Integration. Shares are browseable and access is possible with a sepearte login. My problem: I want to mount this shares from a centos7 client. This fails with the following mesages. I tried several variations in my fstab found in the internet. Can anyone give me a hint to to

I am attempting to install 7.1-BETA2 (from CD) onto a PC with a Promise SX4060 RAID controller and two Seagate 120GB ATA disk drives. The boot from CD keeps repeating the following (error) messages: (I'm retyping here) ============================================================================ ================== ad4: WARNING - SETFEATURES SET TRANSFER MODE task queue timeout - completing

Hi: I have a samba dc and a samba member file server. I use rfc2307 id mapping and posix acl share for windows/linux client for many years. they are simple and work fine. however in older versions of samba (maybe 5 years ago). sometimes after I create a user account at samba dc, the member file server can not recognize it (eg: "getent passwd xxxx" or "id xxxx" return

hi server role is server role = active directory domain controller i googled the error and it says that there could be two computer accounts of the same name i pulled this from the event log The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server 50wks19$. The target name used was 50WKS19$. This indicates that the target server failed to decrypt the ticket provided by the

Hi list, This might or might not be a Samba related post. Feel free to ignore it in case it is too far off-topic My current understanding is that ... a) I need those new templates in order to fully integrate Win10 clients in an AD domain (i.e. with compatible policies). b) I can only modify policies based on Win10 admx files from Win10 machines (i.e. with the RSAT tools for Win10). Are there

Hi guys, about a one or two weeks ago I've updated my samba to v4.1.7 which might or might not relate to the problem at hand. However lately we've seen some issues with users not able to login to workstations (win 7). Windows servers (2008 r2 and newer) were also affected. Sometimes one or two reboots would solve this problems, on few occasions I had to rejoin the computer account to the

Viktor, thanks again! Now that I did this (added the Win10 1511 ADMX files to the central store), I probably will have to recreate the policies that will be applied to Win10 machines, right? Ole On 21.01.2016 17:16, Viktor Trojanovic wrote: > Hi Ole, > > I've been using Samba with Win10 clients for a while now, so I'm happy > to share some of my findings. > > See

On 25.01.2016 14:13, Viktor Trojanovic wrote: > Hi Ole, > > Unless you want to add functionality that is new since 1511, I don't > think that's necessary. I have already added a Win10 machine to a domain, where only Win7 clients were joined before that. I have managed this domain from Win7 only, so far. Therefore I believe that e.g. the Windows Update policy is not fit for

Given an existing NT4 Samba 4 DC, a recently upgraded Win10 machine can no longer access NETLOGON to authenticate to the network. This lead to the research revealing that my Samba4 PDC SMB.CONF must be changed to limit MAX PROTOCOL = NT1 to avoid negotiating a version of SMB2 from Win10 that Samba4 can't resolve. Doing this broke authentication via other resources that no longer support NT1,