All of the devices used in this document started with a cleared (default) configuration. The information in this document was created from the devices in a specific lab environment. The information in this document is based on the Cisco 881 Series Router. There are no specific requirements for this document. What's curious is that there are dozens of other devices in that group, all using the exact same windows credentials inherited from the group level all working without any problem whatsoever.This document describes how to recover the enable password and the enable secret passwords. I did try re-setting the Windows credentials to be re-inherited from the group level and the same two sensors fell immediately back into error mode PE015. Same account, same password, and it's once again working correctly. I changed this and defined the windows credentials at the device level and that allowed the sensors to check without error. They had been defined at the group level. Still lots of other sensors on the same device, all using WMI all worked correctly.ĭoing the reverse of what some of the others here suggested, I changed my windows credentials on this device. I went as far as creating new sensors of the same type on the same device but the new ones likewise reported the same PE015 errors. The two with the error were Memory and Disk Space. Other WMI sensors on the same device were working correctly. Hi, I had a PE015 error on just two WMI based sensors on a single device. "Sammelcredentials" für mehrere nicht Domainmitglieder ohne Wert im Feld "Domäne oder Computername" sollte man lieber mal sein lassen. Erst nachdem ich die Credentials inklusive dem PC Namen in den Credentials der Device erfasst hatte, fingen die WMI Sensoren wieder an korrekt zu arbeiten. Ich hatte eine Gruppe von 2 nicht Domain PCs (Windows 2000) für die ich das Passwort über die Gruppe ohne Angabe eines PC/Domain Namen definiert hatte.ĭie WMI Sensoren der beiden PCs lieferten nach dem Update auf 7.3.5 den oben beschriebenen WMI Fehler. Zur Version 7.3.5 habe ich auch noch eine Anmerkung: So my advice is to avoid defining credentials on group level for devices when entering no data in the "Domain or computer name" field, but in this case enter the credentials for each device individually, including the computer name. Only after I had entered the credentials including the PC name directly in the devices' settings, the WMI sensors began working correctly again. I had a group of two non-domain PCs (Windows 2000) for which I had defined the credentials on group level without entering a PC/domain name.Īfter the update to version 7.3.5, the WMI sensors of the two PCs showed the WMI error described above. Post translated by Paessler Support Team One comment for version 7.3.5 Maybe unrelated but I know in the past I've also seen issues with connecting to shares around windows networks where sometimes a name won't work but an IP will and sometimes the IP won't but the name will. I've checked both DNS and WINS lookups and they resolve fine to all machines involved but then I'd expect that since it's the names that actually work in this WMI connection. So this is not a PRTG implementation issue but purely some oddity with WMI. Using the machine name the script connected and using the IP it would not. I then tried a bit of WMI code VBS script via cscript from the WF1's probe machine MON1. In all cases I also tried various authentications to no avail including a device configured authentication (no inheritance). I moved that WF1 device+sensors to the root probe (MON2) here in my home office and the device and all sensors worked via IP. WF3 has worked from the local subnet's probe (MON1) all along and it's being addressed by IP from the probe MON1. The target server in question (WF1) is identical in every way to another one (WF3). I've had a troublesome WMI connection also and I used Nick's Name-not-IP method and it worked.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |