>> And For what it's worth, noone in their right minds should be allowing JRandomEndUser to access the default administrative shares on another box, but that's a personal issue. At a minimum, they should be using a separate and distinct share that's not an administrative default because of the potential security liabilities. I can really nail someone's system through the default share of their boot partition.


Good point. I agree. Except for the members of Administrators group, noone should be able to access the default admin shares.

In my case unfortunatelly, Netmeeting is not an option.

Can you think of some other non-programmatic way to achieve this? (This being: from 1 workstation look on some other workstation's list of the drives and their mapping). BTW, all workstations including are runnning on W2K.


TIA,

Sasha


>>Is there a way to find out where is some particular drive letter on another workstation being mapped to?
>>
>>I.e. A "G:" is a drive letter on some workstation in a domain. It is a Mapped Network Drive and I want to see from my worksstation by using ADSI where is that G drive letter being mapped to (I.e. \\DomainName\C$).
>>
>
>Not without domain administrative permissions, AD and WMI; ADSI runs in your context, not theirs. You'd need to use WMI to inquire about a session on another box, and that's going to require things not readily accessible on older systems where WMI isn't available and the workstation is not an active participant in the domain's directory database (IOW, they're going to need to enable remote administration and have all the goodies; you aren't going to get there trivially with Win9x/WinNT boxes, or without careful planning and administration of a Win2K and later native network environment.)
>
>Your best bet is going to be to enable NetMeeting on all stations running Remote
>Desktop Sharing on demand, log into the box and check the mappings under My Computer if you haven't done a solid job of planning this in advance.
>
>And FWIW, noone in their right minds should be allowing JRandomEndUser to access the default administrative shares on another box, but that's a personal issue. At a minimum, they should be using a separate and distinct share that's not an administrative default because of the potential security liabilities. I can really nail someone's system through the default share of their boot partition.