mount.nfs4: access denied by server while mounting (when same configs previously worked fine)

Trying to remount a set of nfs folders onto a server that was restarted, am now getting "access denied by server" errors. On client server (clientserver.co.local) I ran:

and got the error you see above. (Notice it tries all the different versions of nfs and still fails). Not sure which security flavor to use (I don't recall ever specifying this before and we use SSSD to link our Windows AD accounts to both client and nfs servers, so I assume it's the default), but in any case I've tried with both -o sec=sys and -o sec=krb5 options and got the same results.

I ran tcmpdump to monitor the packet traffic during the mount command (based on the advice here), but have no idea how to interpret the logs (could post something like last 10 lines if that would help).

Checking the mounts on the network from the hosting nfsserver.co.local server on the client, I saw:

So everything looks like how I would think it's supposed to (showmount does show the nfs folder I am trying to mount).

After running the mount command, the what I see in the /var/log/messages stream file is just a bunch of messages like

Not sure what this means, but did check the gssproxy.conf file and it shows

Not sure what this means either, since I don't recall ever interacting with this in the past (when the nfs mount still worked).

We do use SSSD (did not set this up) to link our Windows AD accounts to the machine, but IDK if that would even be related here or if this is just something else. In any case, the sssd.conf is shown below

But other than that nothing in the logs seems to be more info than what I was already seeing from the command error...

I can ping the nfsserver machine by both name and IP address from the client (and vice versa from the nfsserver machine).

Checking the SE Linux settings, I see...

I did not set these (or really have much experience with SE Linux), but the "permissive" makes me think that it should not be a firewall problem.

I've heard that there could port issues that can cause this kind of thing. When I use rpcinfo I see

but I really don't know much about networking stuff to say if this is normal of not.

Looking on the nfsserver server, I see:

So again, everything seems to be configured as needed. (I have seen some answers that recommend a specific configuration for /etc/exports but I'd prefer to keep as is and this configuration was working up until now). And changing the DNS name to the IP in the nfsserver's /etc/exports file and running exportfs -rav did not change the situation.

Anyone with more experience know what could be going wrong here? Any further debugging advice / info to add that would make this question better (eg. anyone see anything in this post where further investigation into a certain possibility should be done)?