Votes:
I want to monitor a disk share with PRTG, but the sensor is showing the Down status, even though I can access the share with my Windows Explorer. What can I do to troubleshoot the issue?
Created on Feb 4, 2010 12:09:41 PM by
Last change on Jan 4, 2023 11:43:48 AM by
3 Replies
Votes:
This article applies as of PRTG 22
In general, a network share is a system object that you can access from another system via LAN. This way, you can virtually use the respective object as an object that belongs to the local machine. Although PRTG is able to monitor these shares with File, Folder , and SMB Share sensors, we received multiple user reports that say that this type of access does not work properly in some instances.
We cannot precisely explain why users get errors when they add shares. In most cases, the errors stem from the Windows API. Although it is sometimes possible to connect to the shares with Windows Explorer, this does not automatically mean it works with PRTG as well. However, there are a few things you can try in such situations:
If all of the steps above do not work, search for the exact error message (without the error number in parentheses). You will get a large number of results that might help you find the actual cause for the respective issue.
There are no settings in PRTG except the host name (device), the share name (sensor), and the Windows credentials (device or inherited from groups that are higher up in the object hierarchy) that actually affect sensors that use SMB shares.
Here are some error messages you might get and the solutions to the respective issues:
| Problem | Solution |
|---|---|
| Logon failure: The network location cannot be reached. For information about network troubleshooting, see Windows Help (1231). (code: PE029) | Make sure that the Server Windows service is running on the target system and that you are allowed to access the share with the credentials provided. |
| Cannot access folder: The folder doesn't exist. (code: PE032) | Make sure that you entered the correct network path in the sensor settings. When monitoring a share, create a device with the system name or IP address in the IP Address/DNS Name field, and in the sensor's Folder Name settings, enter only the path. For example, enter MyComputer in the device, and C$\Inetpub\mailroot in the sensor's Folder Name field to monitor the network path \\MyComputer\C$\Inetpub\mailroot. See also Folder sensor - Cannot access folder: The folder doesn't exist. (code: PE032) |
| Logon failure: A specified logon session does not exist. It may already have been terminated(1312) (code: PE029) | The drive that you are trying to map needs a specified logon session, even if user name and password are correct. In the Credentials for Windows Systems settings of the device, explicitly enter a value in the Domain or Computer Name field. This can be the system name (if you are using a local login) or the domain name of the user account. Note: After changing credentials, it may take several minutes until the connection is successful. |
Created on Feb 4, 2010 12:10:55 PM by
Last change on Jan 3, 2023 9:22:59 AM by
Votes:
Just a note to all having trouble accessing a folder with a sensor. (error PE032)
We also suddenly were unable to monitor the Spool folder of a new print server like we always have on the previous print server and received PE032 errors.
I could access the
PRINTERNAME\$E\Spool without issues from other servers/probes and the account used in PRTG had full access rights. (on the new server, oddly enough
IP ADDRESS\$E\Spool did also not work)
When I created a Temp folder on E:, like we have on C:, I could also not access it. When I changed the sensor to monitor the Temp folder on C: instead (so C$\Temp) we had no trouble accessing it and the sensor went green.
Change it back to E$\Temp and the sensor errored out again...
Finally I was able to solve this (or work around this rather) by changing the Spool folder hosting Server settings in PRTG to use the FQDN rather than the IP address in the "IPv4 Address/DNS Name" section and the same in the "Service URL" section. No more errors after that.
Last change on May 30, 2018 7:51:22 AM by
Add comment