Okay, I'm stumped. I've spent hours Googling around and searching archives and FAQs and HOWTOs, and I haven't found anything describing the problem I'm having. I'm hoping someone can point me in the right direction. Background: I was trying to connect my 9.1Pro laptop to a share on my employer's all-M$ network, and having trouble. I could connect to the 'top' of the share, but if I went more than two subdirectories deep, Konq would give me a "does not exist" error, and smbclient spat out a weird error code. Googling that error code gave me *one* hit that suggested it was a problem related to DFS. I'd never even heard of DFS before, but since the top-level share was named dfsroot$, I figured I'd hit the jackpot. YAST said my Samba was up to date, but apt dl'd and installed a newer version. Voila! I could now access the entire DFS directory tree via smbclient. But Konq still won't see it. That confuses me, b/c I thought that Konq routed its SMB:// requests through Samba. But I let it slide, since with smbclient I could still get access. Now, though, I need to try and mount that same share -- we're doing a lot of groupware-ish stuff on files located on the network, and the general company standard is to have the DFS share mounted on every computer as a particular drive letter. I'd never used smbmount/mount-t smbfs before, but it didn't look too hard. So I created a mount point on my machine that matched the drive letter all these company URLs point to, and did a mount command. The result, no matter how many varations on mount I try, always comes up like this: WARNING: The "printer admin" option is deprecated cli_negprot: SMB signing is mandatory and we have disabled it. 12341: protocol negotiation failed SMB connection failed I tried setting 'client signing = yes' in my smb.conf, but that didn't help either. I eventually found hints that SMB signing can be turned off in W2k3 servers, which is what the company is running. Then I found a suggestion to use cifs instead of smbfs. *That* got the share mounted -- whoopee! But... Konq still couldn't get below the top level of the share. It kept giving me "does not exist" errors. And cd'ing to the mount point in a shell worked, but doing an ls gave me "permission denied," even though I was using the correct username and password (which work if I'm using smbclient), and cd'ing down one level blindly changed the ls response to "Stale NFS file handle" (which can't be valid, b/c none of the conditions that error message is described as being related to have happened to the network). I couldn't cd any lower than one layer, even though I know this network tree like the back of my hand. And just to ice the cake, I can't umount the blasted thing -- I keep getting a busy error. I combed the samba.org site and samba ml, and came up with only two mentions of this problem, both posted about 10 months ago, and neither one ever responded to. I'm stumped. All I can think of is that this W2k3 server setup has something going on that makes using anything other than smbclient impossible. Since smbclient still works, I can get by (but going twenty directories deep is hard on my carpal tunnel, let me tell you!), but I really wish I understood what's going on.