share is not visible we are running samba 3.3.10 with configured DFS. It works fine. If I enable vfs-module expand_msdfs, there is no visible link in my share. When vfs-module is disabled, the msdfs-links are visible. --- configuration Samba: 3.3.10 OS: RHEL 5.4 --- rpm-packages samba3-3.3.10-40.el5 samba3-cifsmount-3.3.10-40.el5 samba3-client-3.3.10-40.el5 samba3-winbind-32bit-3.3.10-40.el5 samba3-utils-3.3.10-40.el5 samba3-winbind-3.3.10-40.el5 examples attached ... '''smb.conf [global] # DFS settings host msdfs = yes # expand_msdfs settings vfs objects = expand_msdfs [test-share] path = /usr2/people/caesamba/test_share read only = yes browseable = yes guest ok = yes msdfs root = yes '''/etc/samba/tablefile.map 192.168 samba1.domain.de 192.178 samba2.domain.de defaultsamba.domain.de '''content of /usr2/people/caesamba/test_share on 'samba.domain.de' lrwxrwxrwx home -> msdfs:@tablefile@\up lrwxrwxrwx home2 -> msdfs:@tablefile.map@\up lrwxrwxrwx new_test -> msdfs:@/etc/samba/tablefile.map@/up lrwxrwxrwx new_test2 -> msdfs:@/etc/samba/tablefile.map@\up -rw-r--r-- test-share lrwxrwxrwx u2p -> msdfs:evebe631\u2p '''content of share with enabled vfs-module #01: smbclient -k //samba.domain.de/test-share . D 0 Fri Mar 5 12:12:12 2010 .. D 0 Thu Mar 4 13:24:47 2010 test-share 0 Thu Mar 4 14:55:04 2010 '''content of share with disabled vfs-module #02: smbclient -k //samba.domain.de/test-share . D 0 Fri Mar 5 12:12:12 2010 .. D 0 Thu Mar 4 13:24:47 2010 u2p D 0 Thu Mar 4 15:03:26 2010 new_test D 0 Fri Mar 5 12:11:44 2010 new_test2 D 0 Fri Mar 5 12:12:12 2010 test-share 0 Thu Mar 4 14:55:04 2010 home2 D 0 Thu Mar 4 14:54:47 2010 home D 0 Thu Mar 4 13:27:31 2010 '''content new_test2 (msdfs-link) 121#: smbclient -k //samba.domain.de/test-share -c "ls new_test2" OS=[Unix] Server=[Samba 3.3.10] Connection to @ failed (Error NT_STATUS_BAD_NETWORK_NAME) Unable to follow dfs referral [\@\etc] do_list: [\new_test2] NT_STATUS_PATH_NOT_COVERED
Same as #5998?
(In reply to comment #1) > Same as #5998? #5998 -> BUG#5998
*** This bug has been marked as a duplicate of bug 5998 ***