>>- If you want to use UNCs, you would want to work with \\Server2003\D$, not \\Server2003\F$. There is no physical volume F: on the server, so trying to access that drive would return nothing.
>
>Thanks, the previous mentions were known. But, this last line is bugging me. From my application, the UNC \\10.10.10.10\f$ works as is. However, Win32_LogicalDisk cannot handle it. So, what does this last line says exactly? Is it just a syntax issue?

If you're using code that references \\10.10.10.10\f$ , and it's working, then there must be a physical drive F: at that IP address. I'm assuming you are providing admin credentials or privileges.

This is an unusual case, but sometimes (usually removable) devices get assigned drive letters even if there is no medium in the drive. SD/CompactFlash card readers sometimes do this. I've seen systems where multiple drive letters (e.g. F:, G:, H:, I:) get hogged up by such a reader.

Also be aware that mapped network drives can override local physical drives. Suppose, for example, you have a USB flash drive installed, and it appears as drive F:. If you subsequently issue

NET USE F: \\Server2003\SomeShare

then you will no longer be able to access your USB drive.

Bottom line:

- Admin shares such as you are using always refer to the drive letters assigned to physical volumes
- Be sure code you think is working is accessing the drives/volumes you think it is