similar to: smbstatus -1 username/group

> 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

(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 Rowland, > Are you using sssd or nslcd ? I am using sssd. I can ssh into the server using credentials from either kerberos realm. E.g. ssh cwseys at PHYSICS.WISC.EDU@smb01.physics.wisc.edu (works) ssh seys at AD.WISC.EDU@smb01.physics.wisc.edu (works) PHYSICS.WISC.EDU is an MIT kerberos KDC. AD.WISC.EDU is a active directory KDC (etc). The reason I thought sssd would be best is because

On 02/03/16 20:12, Chad William Seys wrote: > Hi Rowland et al, > >>> The reason I thought sssd would be best is because I want to use the >>> /etc/passwd file for user existence and was easy to set up. >> You cannot have the same user in /etc/passwd and AD i.e. user 'foo' in >> /etc/passwd could, and probably would, be seen as the the AD user

Hi Rowland et al, > > The reason I thought sssd would be best is because I want to use the > > /etc/passwd file for user existence and was easy to set up. > > You cannot have the same user in /etc/passwd and AD i.e. user 'foo' in > /etc/passwd could, and probably would, be seen as the the AD user 'foo'. The way the system is set up, username existance and

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

The main change in this release is to address some regressions that crept in when we switched to a scheme that does not rely on walking /tmp to look for credcaches. We now will use the information from the kernel about the initiating pid, reach into that task's environment and scrape out the $KRB5CCNAME variable. This can be problematic in setuid situations, so we avoid doing that for the

On 01/03/16 23:16, Chad William Seys wrote: > Hi Rowland, > >> Are you using sssd or nslcd ? > I am using sssd. I can ssh into the server using credentials from either > kerberos realm. > E.g. > ssh cwseys at PHYSICS.WISC.EDU@smb01.physics.wisc.edu > (works) > ssh seys at AD.WISC.EDU@smb01.physics.wisc.edu > (works) > > PHYSICS.WISC.EDU is an MIT kerberos

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

Hello, >> Can more than one server have a share with 'msdfs root = yes'? Or >> can there be only one root? (Setting 'msdfs root = yes' on shares on > > yes Thanks! It works great for all clients* except the linux kernel (v4.9) mount, which was what led me astray. Any idea if this works in more recent kernels? If not where do I wish list this. :)

Hi Rowland, Below is output of testparm. Samba is set up as standalone server. # testparm Load smb config files from /etc/samba/smb.conf Processing section "[generic]" Loaded services file OK. Server role: ROLE_DOMAIN_MEMBER Press enter to see a dump of your service definitions [global] realm = PHYSICS.WISC.EDU server string = %h server server role =

Hi all, There are some surprises when trying to connect Windows 10 (up to date circa Dec 2016) to Samba (4.5.2) with 'smb encrypt = desired' as a config option. I've made a grid of some of the combinations 'smb encrypt = desired' settings below. The biggest surprise is that if 'smb encrypt = desired' is set globally and in the share, Windows 10 cannot connect at

Chad William Seys <cwseys at physics.wisc.edu> writes: > Kernel 4.13 can resolve either style of link, so I don't think we need > to spend more time with it! > gvfs in Debian 9 also works (as do Windows 7+ and Mac 10.12+). Good. I actually remember fixing something similar now, ha. If you cannot update your kernel I think disabling the unix extension might be a workaround (-o

Chad W Seys <cwseys at physics.wisc.edu> writes: >> Yep, sounds like a bug indeed. You still have the option to edit the smb.conf >> on the server side if you want to use smb2+. > > Good to keep in mind. > I'm speculating leaving 'nodfs' out of smb2+ was purposeful. Originally > it was a workaround for Samba 3.something . Maybe the cifs authors were

On 2/14/20 4:54 PM, Mike Pastore wrote: > I guess the question is: what are you streaming to? And if the answer is > streams_xattr, the question becomes: then why not just use > fruit:resource=xattr? When I tried fruit:resource=xattr appledouble files ._ were created. (I know I'm hung up on aesthetics.) Chad.

Hi Rowland, Thanks for your explanation. We have set up Samba to authenticate users against an external MIT Kerberos server and usernames match those in Unix password files. The setup was almost exactly like the Ubuntu help page: https://help.ubuntu.com/community/Samba/Kerberos#MIT_Kerberos There are others who have also set up Samba this way:

Hi all, I have observed in kernel 4.15 cifs.ko using protocol v2.1 getting confused about whether a "filesystem object" is a file or a directory. The true state in the example below is that "Alien" is directory and "alien" is a (perl) file. However, 'file' reports the type to be the same and matching the first object accessed, e.g. Both are perl

Hi all, We're having trouble with Macintosh clients (at least) being disconnected from Samba. Below is one macintosh console output when this happens, filtered by "smb". (Yeah, maybe some clues are missing...) ATM I don't see anything that stands out in the Samba log file. However one thing I don't see in the samba log file is session disconnects. Does anyone

Hello all, This is for HP CIFS Server A.01.11.03 / Samba 2.2.12, on HP-UX 11.0. I've got a problem with smbstatus: if run as root, it displays everything as expected. If run as a regular user, it displays only the following: $ smbstatus tdb(/var/opt/samba/locks/connections.tdb): Failed to create active lock file tdb(/var/opt/samba/locks/connections.tdb): Failed to create active lock file

Greetings, After recently upgrading Samba from 2.0.7 to 2.2.2 on my Solaris Unix servers, I have problems running command 'smbstatus'. When I run smbstatus as root, it correctly displays connection information for users who've mapped network drives to server shares. However, when I run smbstatus as non-root, instead of displaying connection information, it issues the message