Andreas Ntaflos
2005-Jan-04 10:15 UTC
[Samba] msdfs: links to shares not visible/accessible in dfs root
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 create mode = 0770 browseable = Yes msdfs root = Yes an ls -/home/data/shares/postdfs looks like this: lrwxrwxrwx 1 root root 19 4. Jan 10:44 testlink -> msdfs:pc030\install (post stands for post production) I can access \\pc030\install manually and the permissions seem to be correct. However, none of the clients see anything when I connect to the \\fileserver\postdfs share. The folder just appears empty. I've set the log level to 10 and see some funny things, for example: [2005/01/04 10:48:56, 10] smbd/msdfs.c:parse_processed_dfs_path(90) temp in parse_processed_dfs_path: .fileserver/dfs/desktop.ini. after trimming \'s [2005/01/04 10:48:56, 10] smbd/msdfs.c:parse_processed_dfs_path(99) parse_processed_dfs_path: hostname: fileserver [2005/01/04 10:48:56, 10] smbd/msdfs.c:parse_processed_dfs_path(111) parse_processed_dfs_path: servicename: dfs [2005/01/04 10:48:56, 10] smbd/msdfs.c:parse_processed_dfs_path(116) parse_processed_dfs_path: rest of the path: desktop.ini [2005/01/04 10:48:56, 10] smbd/msdfs.c:resolve_dfs_path(307) resolve_dfs_path: Conn path = /home/data/shares/postdfs req_path = desktop.ini [2005/01/04 10:48:56, 5] smbd/filename.c:unix_convert(109) unix_convert called on file "desktop.ini" [2005/01/04 10:48:56, 10] smbd/statcache.c:stat_cache_lookup(249) stat_cache_lookup: lookup failed for name [DESKTOP.INI] ... [2005/01/04 10:48:56, 8] lib/util.c:is_in_path(1498) is_in_path: testlink [2005/01/04 10:48:56, 8] lib/util.c:is_in_path(1525) is_in_path: match not found ... [2005/01/04 10:48:56, 5] smbd/msdfs.c:is_msdfs_link(244) is_msdfs_link: desktop.ini does not exist. ... [2005/01/04 10:48:56, 5] smbd/msdfs.c:is_msdfs_link(244) is_msdfs_link: * does not exist. I don't know if it has anything to do with it, but why does Samba keep looking for a desktop.ini file, which doesn't (and shouldn't?) exist? Anyway, it is the last line I posted that seems most wrong, saying "* does not exist". Also, the only occurence of "testlink" in the log file is the one I posted above. Something is definately not right there. Does anybody have any ideas? What am I overlooking? I'd really appreciate your help, this is kind of urgent. Thanks a lot in advance! -- Andreas "daff" Ntaflos daff AT dword DOT org Vienna, Austria
Gerald (Jerry) Carter
2005-Jan-06 15:12 UTC
[Samba] msdfs: links to shares not visible/accessible in dfs root
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Andreas Ntaflos wrote: | 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: Make sure you reboot the clients after enabling dfs support on the Samba server since the client will cache information about dfs referrals. There is a win32 tool for clearing the cache as well buit I don't remember what it is right now. I would also test 3.0.10 since there were some dfs bugs in the past. Check the release notes for details. And finally I have one report of Windows XP sp2 breaking Samba's dfs support but I have not confirmed that yet. cheers, jerry - --------------------------------------------------------------------- Alleviating the pain of Windows(tm) ------- http://www.samba.org GnuPG Key ----- http://www.plainjoe.org/gpg_public.asc "If we're adding to the noise, turn off this song"--Switchfoot (2003) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFB3VVGIR7qMdg1EfYRAtD9AKDrnf5cJddrMq80wEPT7lUPQBCqqwCeKPZd anILpi3uZohi7+eUfTJTdCg=CKcW -----END PGP SIGNATURE-----