>I may out of date here... :) The Win NT Resource Kit includes a Network Watch utility that does that. Obviously, not programatically.
>
>Vlad

Yep, and it uses NetFileEnum(), as mentioned by Pat Boens. It -can- be done programmatically, but access to it requires that the user is a member of the Administrators or Account Operators local group. It's also a bit cumbersome to program (you specify the server and base path, and then spin through using a resume handle. You can't tell it to return info on just a single file, and you must know the local path; IOW, knowing the share doesn't help (the UNC or mapped drive path on another machine is no help, you have to specify things in the server's local context.)

When you're logged into the system via a domain login, you get back ERROR_ACCESS_DENIED fairly often, even if the user has a valid account on the system. You have to be logged into the account on the NT box machine locally, and not onto the domain to make it work.

>
>>I'm not sure if there's a way to do so programmatically from a workstation, but from the server (or from a workstation logged in as a domain admin with remote administration enabled) the Server Maintenance application under Administrative Tools can be used to view the active connections of each user in the domain to any server resource.
>>
>>hth,
>>
>>Ed