ss showing socket stuck in SYN-SENT with no traceable PID

On a client I see the following: [root@redacted_local ~]# ss | grep -i syn SYN-SENT 0 1 redacted_local_ip:792 redacted_server_ip:nfs This status has remained the same. I'm unable to actually track port 792/SYN_SENT statuses to a PID: [root@redacted_local ~]# netstat -pnt | grep -i syn tcp 0 1 redacted_local_ip:792 redacted_server_ip:2049 SYN_SENT - How can I tell what is actually holding this port open and what PID exists that needs to be killed? The client is using autofs to go to the NFS server and mount user directories, such that when a user logs into the client, they will have their home directory mounted from the NFS server. Is something even "stuck" in the first place that can be killed?