similar to: MSDFS redirection WinXP SP2

Hello, we have a Samba 3.2.8 msdfs root server. From time to time the connection from a Windows 2003 SP2 system will fail with the message that the server name could not be found. On Windows XP it seems to work. On Windows we open the folder user1/folder/subfolder with the explorer. In the failure log I can't see anything about the subfolder. If I compare the samba log (debug level 10)

We did some tests with msdfs on HP/UX with samba version 2.2.1.a and we found a strange problem. We create a msdfs root on a HP/UX system with samba version 2.2.1.a and create a link in it to an HP/UX system with samba version 2.0.7. We mapped the link in the msdfs root on a NT4 system to drive F. The share contains the source of samba and in explorer we went to :

Hello list, I am trying to get a DFS share to work here, linking to a few Windows 2000, XP and NT machines. Using Samba 3.0.6 on Debian. I followed the instructions in chapter 17 of the official HOWTO collections and set it up like this: [global] ... netbios name = fileserver host msdfs = yes [dfs] path = /home/data/shares/postdfs valid users = @post force group = +post read only = No force

Hi!! We are trying to configure a Debian Linux Server as Samba Server (Domain Controller) and a Windows XP (with Service Pack 2) as client. We have configured Windows into the Samba Domain (in other words, we have been able to agregate the machine into the domain), but when we restart Windows and try to login with a samba user (from linux server) (selecting the Domain), we received a message

I think I've set up my msdfs correctly, but I keep getting the following message when I try to connect to it: [2008/01/07 05:00:45, 0] smbd/service.c:make_connection_snum(1003) '/etc/samba/xyz' does not exist or permission denied when connecting to [beaufort] Error was No such file or directory I have kahn in both hosts and lmhosts. Any suggestions on what I am doing wrong?

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

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

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:59, Michael Tokarev 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. Nope. Things are more interesting than that. I've a 4.19 installation where msdfs links works both in listing and when specified directly. There are 2 other installations of 4.19 where msdfs links

Can I have folders in the msdfs root? >From the docs I do not see a mention of this and in the past it did not work for me however with samba-3.0.28 it appears to be working. img_dfs_root # ls -alR .: total 0 drwxrwsr-x 3 root honestbrokers 264 Feb 28 14:11 . drwxr-xr-x 4 root root 104 Oct 22 10:35 .. lrwxrwxrwx 1 root honestbrokers 27

Hi I downloaded samba 3.3.12 and installed it in Aix6l with following configuration option: ./configure --without-libaddns --without-libsmbsharemodes --with-acl-support --without-ldap --without-utmp --with-libiconv=/usr --with-winbind. Now When I am trying to set host msdfs = yes ,and want to use MSDFS feature It doesn't show me any message but also it does not work. My conf file is

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 =

Just an idea: Why dont us msdfs just pointing to the netapp with ln -s msdfs: And in the smb.conf ex: [netapp] root preexec= yourscript path=yourpath msdfs root=yes EDV Daniel M?ller Leitung EDV Tropenklinik Paul-Lechler-Krankenhaus Paul-Lechler-Str. 24 72076 T?bingen Tel.: 07071/206-463, Fax: 07071/206-499 eMail: mueller at tropenklinik.de Internet: www.tropenklinik.de

Hello, I'm trying to use msdfs links on more than one server. I am hoping to be able to add pointers on any server to any other server. This would make reorganization of data less difficult. (e.g. If one server (not the original msdfs root) fills up a subdir could be moved to another server and then a msdfs link pointed the relocated subdir.) I thought it might work to set

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

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

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

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

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 as a path that includes a sub-folder under the root share. So, given the following share

Good Morning and thank you for your input. I had and still do understand what both preexec and root preexec do. I had also and still do understand the paths you had explained. I, however, had also already explained on 18 May 2015 15:31:55 CEST why your first solution was _not_ a viable option for us (server2 == NETAPP under warranty). I had also already explained on 21 May 2015 22:41:17 CEST