similar to: msdfs proxy and subfolders

On Thu, Jan 05, 2023 at 01:28:55PM -0500, Nick Couchman via samba wrote: >Hello, everyone, >I'm seeing some inconsistent behavior across SMB clients when >configuring shares using the "msdfs proxy" parameter, and was hoping >to get some advice from the community on this. My issue is that >various SMB clients seem to behave differently when this parameter is >pointed

I encountered strange behaviour of "msdfs" when using together with "netbios aliases". E.g I have in smb.conf: [global] netbios name = server netbios aliases = server-oldname .... host msdfs = Yes [share1] path = /var/samba/share1 [share2] msdfs root = Yes msdfs proxy = \penguin\share2 .... From a windows (XP) machine I can now see: \\server\share1 and

On Thu, Jan 5, 2023 at 1:58 PM Jeremy Allison <jra at samba.org> wrote: > > >* Would the behavior of smbclient and smbj be considered a bug, or the > >intended/correct behavior? > > Looks like a bug in smbclient to me. Can you log a bug > and I'll follow up. Thanks ! Thanks for the response, Jeremy - I have put in my Bugzilla account request and will fill in the

We restored to 3.0.23d after update to 3.0.25a because of strange dfs behavior. the detailed situation: on msdfs root server 'samba' ls -lR dfsroot/: drwxr-xr-x appl1 dfsroot/appl1 lrwxrwxrwx share1 -> msdfs:server1\share1 [dfs] comment = "SaMBa DFS root" path = /path.../dfsroot # next line does not work prior 3.0.25 !!! # hide unreadable = Yes

Hello, i got a msdfs share running and now i want to hide folders from users who got no access to them anyway. For example: List of shares: test1 test2 User sees only: test1 Is something like that possible mit samba itself or does someone know a workaround to get it running like that ? Thanks for any ideas. A.Dura

Hello, I'm setting up MSDFS feature in samba-2.2.0-alpha3. It works very great! But I'm would wish an extension to the MSDFS functionality: Is it possible to implement a feature, so I could group junction points within directories? E.g.: [pub] path = /export/publicsmb msdfs root = yes PUB | +- dir1 <- directory manually created in /export/publicsmb | | |

Hello, I am running the following OS CentOS 5.2 Samba Release samba-3.0.28 Kernel 2.6.18-92.1.22 (latest from CentOS) I also tried compiling a custom kernel with the experimental MSDFS option in kernel version 2.6.28.7 to no avail. Microsoft Server OS Windows Server 2003 R2 My Samba server has winbind enabled and the following smb.conf configuration. [global] socket options =

Hello, i got some clients (WINDOWS7 and WINDOWS10) to connect to samba shares. OS is openSUSE 12.2; 13.1; 42.1 Samba-Version: 3.6.7; 4.1.22; 4.2.4 smb.conf is shown below. The samba setup is a workgroup setup, the W7-clients are set up to the workgroup 'workgroup'. No further changes are made to the W7-clients. samba setup: groupadd workgroup chgrp -R workgroup /srv/samba chmod -R 770

I've been testing DFS roots and I'm finding that while Vista and 2008 Server clients can connect with no problems, Windows XP Pro and 2003 Server clients fail. This seems like it's the wrong way round - Samba usually has more difficulties with recent Windows versions than older ones - but I can only assume that there's some registry/policy change between the versions. If anybody

Hi, until now the users here did access the samba shares directly via \\server\share. The number of shares is rising and it should now be possible to access shares by the department they belong to. Thus the users need only one drive letter and not many in their windows explorer. To accomplish this I tried the msdfs approach and it's working very nicely. on serverA: share1 ->

I'm dealing with a Linux environment with extensive automounting, that also has DFS configurations for the Windows clients of various CIFS systems. I've got CIFS automounting working for various CIFS servers, which definitely has its uses, but I'd *love* to be able to mount the DIFS published paths for the CIFS shares? Basically, if I have shares called \\example1\share1 and

Hi, is it possible, to use DFS and show the correct values of free space? I set up a DFS-share located on filesystem1 (size 50GB) and linked shares of another server to this share (msdfs:<fs>\share): share1: size 110TB share2: size 50TB share3: size 20TB But connecting to the DFS-share, the disk size of this network drive ist 50GB. Unfortunately files larger than 50GB can not be copied

Why is that when you create a share, the default is 'msdfs root = yes'? Also, why is that a share that is set 'msdfs root = yes' -- or, rather, a share that does /not/ set 'msdfs root = no' -- advertises that it is a DFS root to the Linux CIFS client, /even /when 'host msdfs = no'? This sounds like A) a bug (ignoring 'host msdfs', and B) a misfeature (msdfs

07.06.2024 07:54, Jeremy Allison wrote: >> msdfs is broken in 4.19.? It worked fine in 4.18. This is not entirely true. >> Is no one using msdfs?? I wonder why I was the first to discover this? > > There must not be a test for your specific use-case. > > MSDFS is tested in the autobuild test suite. Can > you articulate the problem well enough we can > build a

When I setup Samba4 I already had a master and slave bind9 server so I copied the relevant dns information to my master server however I don't know how to make my existing server authoritative for the zone. It will send notifies to the slave and allow ddns updates but the slave shows this error: "slave-server named[1187]: client 1.1.1.1#22792: received notify for zone

Hi List, I am struggling a little bit with the msdfs proxy parameter. I want the samba server as a kind of a bridge between two networks, that the samba server only shares some of the shares provided by our file server to a second network. I don't want the samba srv to be a gw or give the clients a route to the internal network, because it is a total different user group. I first tried to

On Fri, Jun 07, 2024 at 07:16:06AM +0300, Michael Tokarev via samba wrote: >06.06.2024 19:33, Michael Tokarev via samba wrote: > >>For quite some time I'm trying to find what's going on with MSDFS referrals. >>Samba version is 4.19.6. >.. >>However, when opening the directory in question from client, this name is not >>shown in the listing.? Samba skips

Hi, After some experiment with MSDFS on Samba I have seen this problems and I don't know if this are caused by my possible wrong configuration or if are "feature" of MSDFS: -as described into the documentation I compiled a Samba version with --with-msdfs and this smb.conf (server 172.26.11.236). The configuration file is: [Global] host msdfs = yes [dfs] path = /mnt/disk

I tryed to use msdfs, but it doesn't work. Is it my fault, or is it a bug? log.snmd: smbd/msdfs.c:295(create_conn_struct) create_conn_struct: Can't ChDir to new conn path /mypath/host/%u. Error was No such file or directory Part of smb.conf: [global] ... host msdfs = yes ... [eb] path = /mypath/data/eb force group =smb valid users = @gruppeeb write list = @gruppeeb browseable = no

On 07-06-2024 06:59, Michael Tokarev via samba wrote: > 07.06.2024 07:54, Jeremy Allison wrote: >>> msdfs is broken in 4.19.? It worked fine in 4.18. > > This is not entirely true. > >>> Is no one using msdfs?? I wonder why I was the first to discover this? >> >> There must not be a test for your specific use-case. >> >> MSDFS is tested in the