I have seen this too when introducing a windows 2003 DFS fileserver on our office network.
The initial folder below the share appears three levels deep, as stated above. Passing the third level gives an 'Object is Remote' error. Also, you could give any non-existent folder name in the first three levels and the initial folder was returned as that imaginary folder's content. We were mounting this share using cifs on a hardy client box. We were getting the same result for gentoo, fedora9 (with all the latest patches), and bsd clients too. We could see everything properly via smbclient. What we found is we that we needed to use the the actual name of the folder on the windows server that was shared to connect properly, not the windows share name for the folder we were given by our DFS admin. Not that this should be the case, but we needed this to work soon. Smbclient was able to work with the share name, and 'showconnect' showed the actual name of the of the share name we supplied. Something is stopping the sharename from being known by the clients when connecting to windows 2003 DFS from cifs clients. ..can give more info from colleagues if needed.. -- Navigating directories for DFS shares buggy https://bugs.launchpad.net/bugs/134080 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
