Shared folders, sessions mmc What we cannot see is that a specific computer has a specific file open and locked. Anyone know of a way to get to this? Thanks - Rob. Improve this question. RobW RobW 2, 1 1 gold badge 15 15 silver badges 22 22 bronze badges. Not quite what you are asking, but an alternative approach would be to create a separate account for each system. Add a comment. Active Oldest Votes. Improve this answer. Community Bot 1. Thanks for this - I tried Sharewatch. In my situation - more than a dozen clients with the same login names - it combines the open files and workstations into the same list.
You cant tell which workstation has it open. Also, selecting Properties simply reports that a workstation has x files open, and not their file names. Selecting Properties for the file gives similar info. Openfiles gives largely the same output as net session from the server console. It doesn't give the computer name who has opened the file.
My issue was to locate the computer from which the file was opened. Do you have any ideas on how to do that? Identifying and closing the file is simple, and there are lots of ways to engineer this outcome. I appreciate the response, and your commercial offer gave me an early morning chuckle ;- — RobW. My apologies, I wasn't aware that the openfiles process was not the solution. From what you described it seems that would have resolved your need to take a further look at the system as it does not close the file, but just removes that locked setting.
In fact, I built the application for my company and it is able to be automated to run every little bit to avoid such complications. I guess that's beside the point, though. To answer your direct question: Yes, there should be a way to audit those systems for their access to that file. Please see my next post for further details. Actually, going back and re-reading your post Give it a shot before writing it off as a non-solution.
If you're not interested in a programmer, create a batch file to run every few minutes. I'm leaving my solution to your question below as to not waste time in case my understanding of the situation is not thorough. Apologies, but I dont feel that my question is being addressed by you. I needed help determining which computer held the file open. I'm really interested in determining the computer name.
All the rest, while interesting, does not tell me the finite thing I'm after. If the latter would help then there are two things I would look at: Check the AV that is installed on your clients - I've seen multiple Client side AV cause seriously nasty anomolous locking behavior on shares. Helvick Helvick Thanks Helvick! Disabling opportunistic locking is an interesting approach. Server I assume? Yep it's on the server - this prevents clients requesting opportunistic locking so they can locally cache parts of files.
The performance hit from disabling opportunistic locking would most likely be unacceptable for us. We'll need to look at this in our testbed. That is definitely a risk with this - I'd be interested in what you find.
It may be useful to setup the Security log to clear every few days. Thomas Thomas 21 2 2 bronze badges. Thanks for this. I set auditing on that directory shortly after the initial issue. As the problem is intermittent, the signal to noise ratio was huge, and I didnt see a clear way of linking a particular computer to a file event. Search related threads. Remove From My Forums. Answered by:.
Archived Forums. Windows Server General Forum. Sign in to vote. Hi, I have "app. I tried to use process monitor, but it can not find this file, just dll's. Thursday, August 16, AM. Friday, August 17, AM. Use Process Explorer from Sysinternals.
Friday, August 17, PM. Hello, Use process explorer to find it out. Once connected, click on "Shared Folders" to expand the hierarchical menu and then select "Open Files". You should now be provided with a list of files and associated directories that are currently being accessed on the available network shares. All files that are currently being accessed and which users are currently accessing them should now be displayed; as well as the "Type", " Locks", and "Open Mode" for each specific file.
Once it has been determined which user has unintentionally locked access to the file, the issue can be resolved by either contacting them directly and requesting they close the file or right-clicking on the file and choosing "Close Open File".
Home Windows Windows Server How-tos. Determine who is locking access to a file on a Windows-based file server. Rambling Biped. Feb 01, 1 Minute Read.
0コメント