After Updating to the current release (184.108.40.20600) I get an error attempting to monitor local paths. The error is a logon failure: the network path was not found. Is this a known/expected issue?
Thank you very much for using PRTG. We are not aware of any issues with the Folder Sensors in the current version. May I ask, from which version did you update? Does it help to restart the target or the Probe Service? Please also see the troubleshooting tips in this article: folder sensor works erratically, multiple error codes.
I was running 220.127.116.1110 I also have an unrelated issue I think. My SSL expiry probes are also not working. they show Could not create SSL/TLS secure channel
and no restarting probes, server or target does not fix the issue
So the sensor was working prior to the update? Can you verify that you can open the UNC path you entered in the sensor configuration is still reachable for the PRTG server (i.e. can you open the path in the explorer on your PRTG server)?
The path is not a UNC but a local folder on the prob.
And the path does indeed exist? That's weird. Can you pass me the entire sensor configuration including the sensor that you're using? As for the SSL expiry sensor, have you tried all of the sensors security settings?
Yes, the folder exist and the sensor did work before the update. now it gives me this error Logon failure: A specified logon session does not exist. It may already have been terminated(1312) (code: PE029) The folder does have read permissions configured.
here are the settings
Folder Name : C:\inetpub\mailroot\Queue
Do not recurse subfolders
Do not check File Ages
Primary Channel File Count
On the SSL issue I finally traced it to the sensor not supporting TLS 1.1 or 1.2
For the folder sensor, please see if any of the tips in the following KB-Article does help: folder sensor works erratically, multiple error codes
That was informative. here is what I am seeing when tracing with procemon
Date & Time: 2/3/2015 10:16:44 AM
Event Class: File System
Result: BAD NETWORK NAME
;RdpDr\;:0\127.0.0.1\ipc$\ TID: 2964 Duration: 0.0000647 Desired Access: Read Attributes Disposition: Open Options: Open Reparse Point Attributes: n/a ShareMode: Read, Write, Delete AllocationSize: n/a
The path looks to be the issue. But to be fair I do not have a working version of the sensor to test against.
Did you try the the other tips in the article? Make sure that there are no other SMB-Based connections towards this target, etc.?
I did not see much in the article that I can try. This is the only folder being monitored on the server. The server is on the probe so I cannot change the host name. Timing is not an issue since it is a immediate error, plus the trace of the app clearly indicates that it is a problem with the server name\server path used in the call.
Can you post a screenshot then showing the settings of the sensor please?