I see the following behavior without any discernable pattern and ways to reproduce them, but it happens from time to time (not very often):

If a user tries to open a folder or a file on a mapped OES-nss-share windows explorer hangs. If you do not kill explorer manually, explorer crashes (after quite a long time) and afterwards restarts - if you are lucky, or you have to start explorer.exe manually, which most of my users don't know how to do that.

To resolve the issue you have to forcibly disconnect all mappings of the affected nss-volume and disconnect from the affected server. Then you can relogin to the server and recreate the mappings via scripts or manually. If you do not disconnect but just try to reconnect or remap the affected volume, explorer will crash again.

This can happen immediately after login/logon or after several hours of a user-session. On workstations/Pcs without OES-client (which access the OES-volumes vias cifs) I do not see such hangs or crashes of explorer. And on older Windows desktop OS I do not see that either, but there are only very few PCs with older OSs in use.

I told my users to logoff/logout via ctrl-alt-del and relogon/login in such a case, but that is not the ideal solution.

Did anybody see  a similar behavior?