On Friday 30 Jul 2004 16:31 pm, Jesse Pretorius wrote: <SNIP>

...

Which filesystem are you using on the server?

ReiserFS

I'm sorry to say this may well lie at the root of your problem. No matter how much the reiserfs proponents may protest otherwise the fs is not fully compatible with nfs. I have just finished testing wether it fails on 9.1 and it does - ext3 works fine, but reiser gives (mainly) rpc timeout errors, still. Dylan

Thanks again,

Jesse

-- "I see your Schwartz is as big as mine"                                   -Dark Helmet

Try to use YaST2 to setup both the client and the server (switch off a firewall first.)

That's exactly how I did it.

On Friday 30 Jul 2004 17:44 pm, Alexandr Malusek wrote:

Jesse Pretorius writes:

...

...

Try to use YaST2 to setup both the client and the server (switch off a

firewall first.)

That's exactly how I did it.

OK, then the related services (mountd, portmap, ... ) should run. IMHO wsize=1500 and rsize=1500 are not inserted by YaST2 by default so I suspected YaST2 had not been used.

Yes, also these should be relevant multiples, try a power of 2, mine are set to 16384 which I arrived at after much experimental file copying. Dylan -- "I see your Schwartz is as big as mine"                                   -Dark Helmet

wsize=1500 and rsize=1500 are not inserted by YaST2 by default so I suspected YaST2 had not been used.

Yes, that was a troubleshooting step that I did after using YaST2 after googling around a little. Without that doesn't make a difference.

Don't you have any additional limitations in /etc/hosts.allow

Everything in there is REMmed out. Ie it has a # as the first character in every line

and /etc/hosts.deny? The default works for NFS.

Nothing in there either

What is the output of rpcinfo?

Much the same as yours: tra1:~ # rpcinfo -p 10.192.32.10 program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100003 2 udp 2049 nfs 100003 3 udp 2049 nfs 100003 4 udp 2049 nfs 100227 3 udp 2049 nfs_acl 100003 2 tcp 2049 nfs 100003 3 tcp 2049 nfs 100003 4 tcp 2049 nfs 100227 3 tcp 2049 nfs_acl 100021 1 udp 1097 nlockmgr 100021 3 udp 1097 nlockmgr 100021 4 udp 1097 nlockmgr 100024 1 udp 1097 status 100021 1 tcp 1107 nlockmgr 100021 3 tcp 1107 nlockmgr 100021 4 tcp 1107 nlockmgr 100024 1 tcp 1107 status 100005 1 udp 997 mountd 100005 1 tcp 1000 mountd 100005 2 udp 997 mountd 100005 2 tcp 1000 mountd 100005 3 udp 997 mountd 100005 3 tcp 1000 mountd More info: When I use YaST2's module to setup the mount, after putting in the IP address of the server and choosing 'select' for the 'Remote File System', it picks up the export. IT's just when it's writing the config at the stage when it restarts the service that it indicates that it can't mount the service. Trying it manually, it clearly indicates an authenticated mount in the server's /var/log/messages, but on the client side it gives the original error 'mount: RPC: Timed out' Very odd. I'll be doing an update soon and will see if updated packages don't solve the problems I'm experiencing. Meanwhile, I've been working with mounting shares using smb which seems to be working. J-)