similar to: smbclient socket options

Displaying 20 results from an estimated 30000 matches similar to: "smbclient socket options"

2024 Dec 31
2
ef205f6b52e "s3:gse: get an explicit ccache_name" breaks kerberos auth in smbclient
FWIW, samba 4.20 broke kerberos auth in smbclient. Namely, this commit: commit ef205f6b52ea1fec13e647e15e4f3edf536fd93e Author: Stefan Metzmacher <metze at samba.org> Date: Thu Apr 14 15:23:13 2022 +0200 s3:gse: get an explicit ccache_name from creds and kinit if required This means we may call kinit multiple times for now, but we'll remove the kinit from the callers
2025 Jan 01
1
ef205f6b52e "s3:gse: get an explicit ccache_name" breaks kerberos auth in smbclient
Am 31.12.24 um 21:49 schrieb Michael Tokarev: > FWIW, samba 4.20 broke kerberos auth in smbclient.? Namely, this commit: > > commit ef205f6b52ea1fec13e647e15e4f3edf536fd93e > Author: Stefan Metzmacher <metze at samba.org> > Date:?? Thu Apr 14 15:23:13 2022 +0200 > > ??? s3:gse: get an explicit ccache_name from creds and kinit if required > > ??? This means we
2025 Jan 01
2
ef205f6b52e "s3:gse: get an explicit ccache_name" breaks kerberos auth in smbclient
01.01.2025 10:43, Stefan Metzmacher via samba wrote: .. >> This is still happening in current master. >> >> I guess this wasn't an intended behavior :) > > No, this is wanted. > > Currently this should work > > smbclient //tsrv/mjt -k -d5 Aha. This works indeed. Thank you! > We'll hopefully get a --use-default-krb5-ccache option in future, >
2024 Nov 06
1
Slow reply to "smbclient -NL localhost" : strace
On 06/11/2024 08:04, Michael Tokarev wrote: > Take a closer look at strace.? You've already noticed > the recv() call takes a noticeable time, - find all of > them. > > BTW, in your strace output you omitted some important > pieces, for example, it isn't visible what FD#5 corresponds > to, since you omitted its creation/open. > > The prob might not be the (host)
2024 Nov 06
2
Slow reply to "smbclient -NL localhost" : strace
On 05/11/2024 18:16, Michael Tokarev wrote: > If smbclient were just to run usleep() function, it will > show exactly the same behavior. > > What's happening here, most likely, is that smbclient is > making some network calls and is waiting for the reply. > > It might be a DNS problem or samba (configuration) problem, > depending on where and what it is waiting for.
2024 Nov 05
2
Slow reply to "smbclient -NL localhost" : strace
On 04/11/2024 15:11, Rowland Penny via samba wrote: > As I said previously, I do not think this has anything to do with > Samba. In an earlier post, you had this output when you ran the same > command using 'time': > > real 0m12.500s > user 0m0.732s > sys 0m0.102s > > The 'real' time is the total time it took to run the command, but >
2003 May 15
2
smbclient -c options
I'm trying to get a recursive file listing with smbclient: smbclient //host/share -Uusername%password -c "ls -alFR" But I get an error: NT_STATUS_NO_SUCH_FILE listing \-alFR Evidently, smbclient thinks I'm asking for a file mask. Is there a way to get a recursive file listing on a samba share so I can pipe it to wc -l for a file count? Ideally, I'd like to: (This won't
2024 Jun 07
1
4.20: case (in)sensitive is broken
On Fri, Jun 07, 2024 at 08:21:26PM +0300, Michael Tokarev wrote: >But samba applies too much smartness here and breaks things badly. Fair enough. Can you post a minimal smb.conf and directory setup that reproduces the problem and how to demo it with smbclient command lines please ? I know I'm asking to be spoon-fed but my time for Samba these days is quite limited and this would aid
2023 Jan 08
1
Issues demoting a samba DC.
Hello! I'm trying to remove a DC from our samba domain (samba 4.17.4). It was the primary controller (with FSMO roles), - I successfully transferred the roles to another DC. Now it's time to demote: ai# samba-tool domain demote -U mjt-adm Using svdcp.tls.msk.ru as partner server for the demotion Password for [TLS\mjt-adm]: Deactivating inbound replication Asking partner server
2024 Nov 06
1
Slow reply to "smbclient -NL localhost" : strace
06.11.2024 08:59, Gilles via samba wrote: >>> FWIW, there's no delay after I run it once? but only for a couple of minutes. >> >> This suggests it might be a name resolution issue. > > What files could help find the source of the problem? That's a strange question. Without understanding what the actual problem is, it's hardly possible to point to the
2024 May 25
1
classifying samba componens and sorting into debian binary packages
Hi! I'm evaluating how various binaries and components are split into different binary packages in Debian. And am having issues classifying these. Initially there has been request to remove dependency on python3-samba package (this is AD-related stuff) from samba-the-file-server package, to be able to use it on smaller devices. And at the same time, there has been another request to move
2024 Nov 06
1
Slow reply to "smbclient -NL localhost" : strace
06.11.2024 12:32, Gilles via samba ?????: > On 06/11/2024 08:04, Michael Tokarev wrote: >> Take a closer look at strace.? You've already noticed >> the recv() call takes a noticeable time, - find all of >> them. >> >> BTW, in your strace output you omitted some important >> pieces, for example, it isn't visible what FD#5 corresponds >> to, since
2024 Nov 05
1
Slow reply to "smbclient -NL localhost" : strace
05.11.2024 12:36, Gilles via samba wrote: > On 04/11/2024 15:11, Rowland Penny via samba wrote: >> As I said previously, I do not think this has anything to do with >> Samba. In an earlier post, you had this output when you ran the same >> command using 'time': >> >> real??? 0m12.500s >> user??? 0m0.732s >> sys???? 0m0.102s >> >> The
2024 Jun 07
1
4.20: case (in)sensitive is broken
On 6/7/24 9:34 AM, Michael Tokarev via samba wrote: > I had to downgrade samba from 4.20.1 to 4.19.6 because 4.20 > broke case insensitive file access entirely.? Only exact case > filename works, no matter which value is set in "case sensitive" > parameter. hm, can't reproduce: $ bin/smbclient -U "slow%x" //localhost/test smb: \> ls foo foo N
1998 Apr 03
4
smbclient (1.9.18p3) dies or needs killing when used for backups (via Amanda)
Has anyone noticed that there appears to be a few problems with regards to Samba and in particular the usage of smbclient, which can do one of the following : 1) Complete & udder death of the NT networking subsystem (which requires a reboot to cure) 2) smbclient appears to lose its connection with the host being contacted and eventually needs to be killed. I'm not too sure how
2000 Nov 05
0
Socket options not properly set for ssh and sshd.
I'm sending this only to openssh-unix-dev at mindrot.org (since I'm using the ported version of OpenSSH) and not to openssh at openssh.com, even though I believe this to be a general problem. Please advise if you think I should redirect this to the other mailing list. Version: OpenSSH_2.2.0p1 Keywords: setsockopt keepalive hang masquerade Symptom: For protocol 2, socket options
2017 Dec 03
2
PJSIP OPTIONS
Hello Everyone, How to configure PJSIP to reply 200 OK from upstream sip proxy on keepalive packet ? proxy ~> Keepalive OPTIONS ~> asterisk <~ 200 OK <~ volga629 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20171203/8b9bc701/attachment.html>
2002 Jul 17
1
smbclient 2.2.5 segfaults on Solaris 7 x86 (long article)
i'm running samba on solaris x86 only for accessing NT shares. samba is not running as a domain master or anything. the problem is that when i try to upload 18mb file to NT share, smbclient crashes. $ smbclient //<box 1>/<share A> added interface ip=x.x.1.30 bcast=x.x.255.255 nmask=255.255.0.0 Domain=[ACCORD] OS=[Windows NT 4.0] Server=[NT LAN Manager 4.0] smb: \> put
2001 Jan 12
0
Socket options not properly set for ssh and sshd.
I mentioned this problem in a previous post (in November). This time I'm including a patch. Version: OpenSSH_2.3.0p1 Keywords: setsockopt keepalive hang masquerade interactive Symptom: For protocol 2, socket options (especially keepalive) are not being properly set for OpenSSH_2.3.0p1, even when request in the config files. Furthermore (for either protocol), keepalive is only set for
2024 Jun 10
2
4.20: case (in)sensitive is broken
On Fri, Jun 07, 2024 at 09:59:14PM +0300, Michael Tokarev via samba wrote: >07.06.2024 20:52, Jeremy Allison wrote: > >>Fair enough. Can you post a minimal smb.conf and directory >>setup that reproduces the problem and how to demo it with smbclient >>command lines please ? I know I'm asking to be spoon-fed but my time for >>Samba these days is quite limited and