No, you may not be able to find which specific system has the file locked, but with the tools provided, you can disconnect that user from the file.
![open ps2 loader cannot see nas share open ps2 loader cannot see nas share](https://i.postimg.cc/Tw24DBCM/after.png)
Search for the file name within the list given, the data will show which item has the read & write enabled, and along with it will provide a specific ID number. You will need to reference the locked ID number via the "openfile /query /v" (verbose) command as it will supply you with the data you need. I believe you are going to want to refer back to Sky100's post as he is correct, not in providing you with what you asked, but in providing you with what you need to resolve your issue.
![open ps2 loader cannot see nas share open ps2 loader cannot see nas share](https://i.ytimg.com/vi/DH6eIFHrsQI/maxresdefault.jpg)
What we cannot see is that a specific computer has a specific file open and locked. That a particular computer generally has a file open. What logon has a specifc file open or locked. There appears to be a gap in the information we can get from the server: I've been looking for which kiosk device is responsible for the locking, and to detect it quickly when it happens. The unreleased lock issue has happened several times in the last month.
![open ps2 loader cannot see nas share open ps2 loader cannot see nas share](https://i.ytimg.com/vi/weLWA3EbOSg/maxresdefault.jpg)
We can close the file when this happens, but several minutes or longer elapses, and this is an unacceptable outage. Recently, we have experienced one of the clients locking a file exclusively, and then not releasing the file. The rate is several locks and releases a minute. We have several dozen kiosk machines each with the same logon name who occasionally and briefly a file on a share.