Hi, Has anyone had problems with SuSE 8.0 and mounting NetWare volumes? I didn't have this problem with SuSE 7.2 or SuSE 7.3. (Unfortunately, I only have one SuSE 8.0 machine to test this problem on.) I can successfully mount a volume using ncpmount and I can access everything if I start from the right place. Here is a few commands to demonstrate what I am talking about: (I am connecting to the NetWare server called 'hal' with by username, 'alle_lowe'. BTW: I get the same results if I mount a specific volume (-V) or If I specify no volume.) # ncpmount -S hal -U alle_lowe /NetWare/hal **<password>** I'm now connected to the server. # cd /NetWare/hal # ls ls: .: Stale NFS file handle Accessing "." (the current directory) fails. But, If I access the directory using it's absolute path, then everything works fine: # ls /NetWare/hal chip dev sys Everything here worked as expected; the proper directories are listed. Now lets jump into a subdirectory and look up the VFS tree: # cd /NetWare/hal/chip # ls .. ls: ..: Stale NFS file handle No good! I thought I saw a pattern at this point, so I started to assume that maybe it was choking on relative paths. But then I tried this: # ls ../../hal chip dev sys Which worked. Now, unless I'm missing something here, this would be a relative path that essentially reduces to "..", which failed just a few seconds ago. I think that the term "NFS" in the error message is referring to just a "Network" file system and not the just the "nfs" protocol. I really don't know at what level this message is being produced, but I assume that it is coming from the application. I tried a bunch of other command line tools (echo * (using bash), find, tar,..) and they all had similar results:: Accessing the mounted point using either "." or ".." doesn't work. I believe I can rule out any kind of 'permissions' issues since I can actually access the mount using the absolute path. I also tried the same thing using smbfs and nfs and both worked fine (as expected). I tried different mount point locations, different NetWare users, but I always had the same results. If you can confirm or deny any of these issue on your machine, please drop me a line. Any comments or suggestions are welcomed. Thanks, Lowell Alleman lowella@mfps.com