update:
I found some people with the same problem as me:
http://www.cs.washington.edu/lab/sw/uwcsesamba.html
Smbclient is not Dfs-aware. This means you can specify \\ntdfs\cs as
a share, but when you attempt to drill down past the so-called Dfs
"junction points" you will not get anywhere. In the following example
this is illustrated. You cannot get to //ntdfs/cs/cse/www using
smbclient.
% smbclient //ntdfs/cs
Password:
Domain=[CSERESEARCH] OS=[Windows Server 2003 3790] Server=[Windows
Server 2003 5.2]
smb: \> ls
. D 0 Thu Oct 16 16:17:54 2003
.. D 0 Thu Oct 16 16:17:54 2003
cse D 0 Thu Oct 28 10:25:56 2004
nt D 0 Wed Feb 25 15:28:09 2004
34522 blocks of size 1048576. 29260 blocks available
smb: \> cd cse
smb: \cse\> ls
. D 0 Thu Oct 28 10:25:56 2004
.. D 0 Thu Oct 28 10:25:56 2004
www D 0 Thu Oct 28 10:25:56 2004
www2 D 0 Thu Oct 16 16:16:58 2003
34522 blocks of size 1048576. 29260 blocks available
smb: \cse\> cd www
smb: \cse\www\> ls
NT_STATUS_PATH_NOT_COVERED listing \cse\www\\*
34522 blocks of size 1048576. 29260 blocks available
smb: \cse\www\> q
hello
a quick question: is the smbclient program a dfs-aware client? can it
access dfs points on a microsoft dfs server?
kind regards
werner
Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
