On Tue, Nov 24, 2020 at 02:06:46PM -0500, Richard Kimberly Heck wrote:
This looks like the issue:
Nov 22 23:10:03 rkhstudy kernel: lockd: server 192.168.1.2 not responding,
still trying
This was working fine in Fedora 32, though, so I'm puzzled what's wrong now.
There's no firewall on the client, and nothing has changed on the server,
and I do not see any error messages there. Is lockd perhaps using a
different port, which is blocked on the server? If so, how do I find out
what that is?
'rpcinfo -p' should tell you port numbers, although it's usually
something in the firewall that causes the issue.
--
Jonathan Billings <billings(a)negate.org>