When trying to open a specific file in PRTG network tools, for example, Paessler MIB Importer or Server Administrator, mapped network shares are not shown in open file dialogs. In addition, when trying to monitor a file on a mapped network share with PRTG’s File sensor, the file is not found. Why does this happen and what can I do regarding this issue?
Why are some network locations not shown or accessible in PRTG products?
Modified on 2025-06-10 14:24:04 +0200
Disclaimer:
The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.
The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.
This article applies to PRTG Network Monitor 12 or later
Making Mapped Network Shares Visible
It is possible that programs like PRTG and its related network tools are unable to access mapped network shares on Windows 7 or Windows Server 2012 computers. This results in network locations which are not visible in open file dialogs, or in errors when monitoring via PRTG’s File sensor when the probe is running on such an operating system.
This problem occurs if you turn on the setting User Account Control in Windows, because this option treats members of the Administrators group as standard users. For details regarding the cause and a workaround for this issue, please refer to the following Microsoft knowledge base article:
Apr, 2013 - Permalink