Hi all, I have been battling for a few days with a very peculiar NFSv4 on SUSE 10.0 problem. My System: I have one central SuSE Linux 10.0 server cluster for all data. It exports NFS shares to a number of NFS-Servers. The NFS-Servers are also clusters with heartbeat; one for Samba, another for Apache, another for ERP. The Samba server, for eg. receives all data shares from the central data cluster for a windows network over the NFS-Shares. Data-Cluster (2 x DRBD Servers) NFS Shares Export of DRBD primary device | | v |--1GB-IP--| | | | |______________________ | | v v NFS-Shares Import (Other Servers) NFS-Server Cluster (w/Samba) SMB-Shares ^ | v |--100MB-IP--| ^ | v Windows Network I use the Kernel NFS-Server of the uname -a: Linux L10-CL2 2.6.13-15-default #1 Tue Sep 13 14:56:15 UTC 2005 x86_64 x86_64 x86_64 GNU/Linux Cluster is a DRBD 1GB IP block device replication system. I have also shut it down and mounted the primary raid 5 volume for testing, to isolate a problem here. No change. Block devices have no idea what a file system is, so could be eliminated from the following problem. Problem: I can not read or write to Windows Office products (MS0) over SMB shares in the Windows Network on the Samba Server, and not with OpenOffice (OO2) products directly on the NFS-Server shares. I think that before the NFS share issue is not solved, the Samba share problem will continue; it is almost certainly related to it. I have isolated it to not being able to read or write with MS0 on Samba shares and OO2 programmes on the NFS-Server directly. If I change the *.doc file names to *.txt, I can edit them and save them as well. Otherwise the NFS shares behave normally. I have communicated with the NFSv4 group, and there does not seem to be a NFS problem in itself. Any ideas where to look? :-) Al