similar to: smbclient kerberos auth fails

Hi, I hit the issue described in this thread https://groups.google.com/forum/#!topic/linux.samba/VfjW9Af92Wg while testing out s4u2self and s4u2proxy in a windows service, so I wanted to share my setup. So I wrote a small windows service that's running as a local system account to impersonate an user via s4u2self (using LsaLogonUser in win32 api than calling ImpersonateLoggedOnUser) and then

After reviewing logs I found that my previous assumption was wrong. Situation: - i'm trying to start live migration from hyper-v host A (BMSRV4-HYPERV) to hyper-v host B (BM-SRV-5) from host B (logged in as user from DOMAIN ADMINS group). Kerberos constrained delegation is set in accordnance to microsoft instructions with proper SPN's set (well, proper as in with the workaround I

This issue is reproducible for this customer and a couple of others. We execute the smbclient command the same way for each instance. The null user name is valid syntax sent from the smbclient. When we send the command " smbclient -c 'cd <dir>; ls' ", samba code executes starting with Negotiate Protocol Request, and onward. I'm guessing this could be a DFS issue, but

Hello, This won't be a very helpful reply, but I can confirm I've had the exact same issue. I ran into this a few years ago and could not get HyperV migrations to work with a Samba DC. I even went so far as to install a Windows DC just to prove to myself that it is supposed to work, and it does, perfectly (with ADDC it even creates all the SPNs for you auto-magically). Unfortunately at

Hi, I'm having a problem with ssh and sssd in a samba4 ad environment. If I logon a linux client everything works fine. When entering klist I'm able to see my ticket. When I try to connect/logon to another linux client with ssh it is possible, but klist shows: klist: Credentials cache file '/run/user/$UID$/krb5cc/tkt' not found. So the ticket cache is not created during

----- On Oct 10, 2017, at 12:02 PM, samba samba at lists.samba.org wrote: > On Tue, 10 Oct 2017 11:28:09 -0500 (CDT) > Andrew Martin <amartin at xes-inc.com> wrote: > > Rowland- I've been poking at this more and think the root of the problem is a Kerberos problem. After joining this machine to the domain, it goes through a process that it calls "AD/Kerberos

On 12/01/2023 12:28, Thorsten Marquardt via samba wrote: > > Okay back to the start an I try again. This time role by role. Here I > don't get timeouts (why do they come up with role=all ?) and I'm not > prompted for password of DOMAIN\root You should never get prompted for the password for 'DOMAIN\root', if you do, then you doing something wrong or something has

I'm wondering if anyone else has any feedback on this or needs anymore info ? Mike -----Original Message----- From: samba [mailto:samba-bounces at lists.samba.org] On Behalf Of Tompkins, Michael via samba Sent: Thursday, January 19, 2017 9:19 AM To: Aurélien Aptel <aaptel at suse.com>; samba at lists.samba.org Cc: USA Xerox Samba <USA.Xerox.Samba at xerox.com>; Futrell, Earl

On 12/01/2023 12:51, Rowland Penny via samba wrote: > > > On 12/01/2023 12:28, Thorsten Marquardt via samba wrote: >> >> Okay back to the start an I try again. This time role by role. Here I >> don't get timeouts (why do they come up with role=all ?) and I'm not >> prompted for password of DOMAIN\root > > You should never get prompted for the

(Let's keep this on the list) Aurélien Aptel via samba <samba at lists.samba.org> writes: > Chad William Seys <cwseys at physics.wisc.edu> writes: >> Somehow the destination having 'msdfsroot yes' prevents the cifs kernel >> module from following the link. I've taken a look at your traces and right off the bat I see things like this: [...]

Hi Chad, Sorry for the late reply. Looking at this now. Chad William Seys <cwseys at physics.wisc.edu> writes: > I've attached traces and logs of these situations: > > msdfs root = yes, link points to share, link CAN be followed > trace_msdfsrootyes_share.* > > msdfs root = yes, link points to path, link CANNOT be followed > trace_msdfsrootyes_path.* In this one I

Sven Schwedas via samba <samba at lists.samba.org> writes: > Once again, something with Samba thirty bazillion components broke. Once > again, my choices for logging are "nothing" or "15 MB/s spread of ten > different files, because 'client authentication failed' totally needs to > be lower priority than malloc debug info". Once again, none of these

Am 12.01.23 um 14:03 schrieb Rowland Penny via samba: > On 12/01/2023 12:51, Rowland Penny via samba wrote: >> On 12/01/2023 12:28, Thorsten Marquardt via samba wrote: >>> srv-kb-dc1:~ # klist >>> Ticket cache: DIR::/run/user/0/krb5cc/tkt >> What OS is this ? the old host: srv-kb-primdc:~ # cat /etc/os-release NAME="openSUSE Leap"

Good Day, We use a lot of DFS Shares (Windows) across our Linux Servers. The DFS Shares are setup in a Cluster. Over the weekend we did a DR excercise which included shutting down one of the Servers that hosted the DFS Shares. What we found is that any Linux Server that had associated itself with the DFS Server that was shutdown did not try and connect to the remaining Server that was up. Is

Good Day, We experience the following when we have outages or perform disaster recovery exercises. Our DFS Shares come from a Windows cluster with 2 servers, each one in a different location. When the server that we have active connections to goes offline, the server has an issue connecting to the second server. This even happens under a controlled shutdown and startup situation. If we

I am wondering if anyone has had a chance to look at bug 12518? This is the context of the message: Wireshark trace gives a STATUS_INVALID_PARAMETER when running smbclient -c 'cd <dir>;ls' as a standalone program. This is a customer issue. We cannot recreate this issue so we're looking for why this may be happening. From the trace you'll see multiple sessions with

"Tompkins, Michael via samba" <samba at lists.samba.org> writes: > I'm wondering if anyone else has any feedback on this or needs anymore info ? Can you provide the output of the failing command with full debug messages (-d10)? -- Aurélien Aptel / SUSE Labs Samba Team GPG: 1839 CB5F 9F5B FB9B AA97 8C99 03C8 A49B 521B D5D3 SUSE Linux GmbH, Maxfeldstraße 5, 90409 Nürnberg,

Hi Thorsten, hi Rowland, Am Donnerstag, 12. Januar 2023, 15:57:45 CET schrieb Thorsten Marquardt via samba: > Am 12.01.23 um 14:03 schrieb Rowland Penny via samba: > > On 12/01/2023 12:51, Rowland Penny via samba wrote: > >> On 12/01/2023 12:28, Thorsten Marquardt via samba wrote: > >>> srv-kb-dc1:~ # klist > >>> Ticket cache: DIR::/run/user/0/krb5cc/tkt

Am 12.01.23 um 12:25 schrieb Rowland Penny via samba: > > On 12/01/2023 10:53, Thorsten Marquardt via samba wrote: >> Thank you so far. But unfortunately I could not fix the problems. So I >> decided to start over again at a situation where all the fsmo roles >> resides on the old controller. >> >> Here is a transcript of what I did and the errors reported:

On Mon, Sep 18, 2017 at 1:33 PM, Dale Schroeder < dale at briannassaladdressing.com> wrote: > > > Try the "vers=3.0" option. That's what fixed mine. > > I suspect my old version of cifs-utils doesn't understand that option. Note the output says "vers=3.0,ver=1": mount.cifs --verbose //192.168.254.35/projects /mnt/smb -o