similar to: [4.8] unix extensions negotiation and os x

On Tue, Apr 03, 2018 at 12:09:52PM +0200, Aurélien Aptel via samba wrote: > Dan Janowski via samba <samba at lists.samba.org> writes: > > > [ Unknown signature status ] > > Does os x (10.13) support negotiation of unix extensions/CIFS? > > > > When hard links didn’t work I dug in and while I found info on CAP_UNIX, and added ‘unix extensions = yes’ globally,

Dan Janowski via samba <samba at lists.samba.org> writes: > [ Unknown signature status ] > Does os x (10.13) support negotiation of unix extensions/CIFS? > > When hard links didn’t work I dug in and while I found info on CAP_UNIX, and added ‘unix extensions = yes’ globally, the Negotiation makes no mentions: > I’m far from sure I’m looking at this the right way. Any hints

That’s very awesome. I’ll take a stab at getting it set up > On Apr 3, 2018, at 2:16 PM, Jeremy Allison <jra at samba.org> wrote: > > On Tue, Apr 03, 2018 at 12:09:52PM +0200, Aurélien Aptel via samba wrote: >> Dan Janowski via samba <samba at lists.samba.org> writes: >> >>> [ Unknown signature status ] >>> Does os x (10.13) support negotiation

Hi, Is there a place where I can specify defaults options a for "mount -t cifs"? I would like to change the default protocol version to vers=2.1 Is there something like a cifs.conf or such...? MJ

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

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

Re-sending with right email... msdfs root is set to "no" by default and is per-share. [myshare] msdfs root = no path = ... Should do the trick. Otherwise if mounting on linux you can also use the 'nodfs' mount option (mount.cifs //host/share/... /mnt/ -o ...,nodfs) to disable DFS resolving and automatic sub-mounting. Chad W Seys <cwseys at

> Which smb version are you using (mount option)? Support for DFS on smb2+ > was only added in linux 4.11. smbstatus shows the connection as NT1. DFS links do work like this: serverA_msdfsrootYES => serverB_msdfsrootNO But not like this: serverA_msdfsrootYES => serverB_msdfsrootYES Somehow the destination having 'msdfsroot yes' prevents the cifs kernel module from

On Wed, Apr 04, 2018 at 08:52:58AM -0400, Dan Janowski via samba wrote: > That’s very awesome. I’ll take a stab at getting it set up Just to clarify, "working" doesnt' yet mean the client side, only the server parts :-). Once I've finished the symlinks/device files work then I'll work on fixing up the smbclient test code.

Hi, I rarely deal with kerberos but everytime I do it's painful... I have a Windows Server 2016 VM at foo-ad.foo.com. It has the AD role and it owns the FOO.COM domain. I added a *AD* account FOO\aaptel%aaptel. PS C:\share> get-aduser aaptel DistinguishedName : CN=aaptel,CN=Users,DC=foo,DC=com Enabled : True GivenName : Name :

(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: [...]

"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,

I think a network trace would tell us for use whether the server is responding or not. You can follow the instruction here to make one: https://wiki.samba.org/index.php/Bug_Reporting#cifs.ko -- 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, Germany GF: Felix Imendörffer, Mary Higgins, Sri Rasiah

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

On Sat, 13 Jan 2018, Rowland Penny wrote: >> I have a samba file server that I created about 20 years ago and in >> the time I have done the little updates needed to new server (when I >> move to a new server I copy config and adapt if needed). >> It only do public file sharing. >> >> Some weeks ago a client stopped to connect to the share. >> Only this

Hi Aurélien, is there some documentation around where I can read about that? Where can I find the information, that I need Kernel 4.11 or above to get DFS with SMB2.0 / 2.1 / 3.0 and above working? Regards, Christian Am 12.06.2017 um 12:46 schrieb Aurélien Aptel: > Hi Christian, > > Christian Garling via samba <samba at lists.samba.org> writes: >> a few days ago we

> > When you provide an exact vers= then no auto-negotiation happens (unless > you pass "vers=3" which essentially means 3.x: use 3.0 or above). You > either get the connection or mount fails. None the less, you can dump > the current SMB ressources managed by the kernel by looking at > /proc/fs/cifs/DebugData if your kernel is recent enough it should show > the SMB

> > I tried looking at the network capture using `tcpdump -A -X` but wasn't > able to understand anything. I tried installing wireshark on a throwaway > cloud instance, but realised that it's a GUI program. Can you please help > be with the network trace at > https://www.dropbox.com/s/r8cn0qggrvmrpc3/dump.pcap?dl=0 ? It's capturing > the network chatter for ~1min