Hello,

My local probe has just started to continuously disconnect. I am currently running a trial version pending full purchase within a week. In fact I just had a meeting regarding this new monitoring solution with my COO and was adding sensors and geo-map locations so I could do a final presentation to them and get the project funding approval, however now I'm unable to do so. It had been running fine for the past 15 days without a hiccup. I am running the probe currently on my desktop since I was just evaluating the product, however it doesn't seem to be overtaxing the systems resources. Any help is extremely appreciated as we are up against very tight time constraints to place a monitoring solution into production. Can you please assist?

Article Comments

Hello,

Could you please forward us your system log files for analysis? You can find the same under

XP/2003: C:\Documents and Settings\All Users\Application Data\Paessler\PRTG Network Monitor\Logs (System)

Vista/2008: C:\ProgramData\Paessler\PRTG Network Monitor\Logs (System)

Please send the Logs(System) folder as a zip file if possible.

If you have changed the location of the data folder in the past or if you can not find current log files in the above location, please check your data path in the PRTG Server Administrator Tool on the PRTG server.

please send the logs to

support@paessler.com

add a relation to this KB article!


Jan, 2014 - Permalink

Moderator:

Please edit original post to delete poster's name and contact info. Was unaware it would be a forum post. Was told it was a support contact form. I tried to edit post but get a 500 Internal Server error.

Thanks in advance...


Jan, 2014 - Permalink

Just an FYI,

I tried the NoMacScan registry entry... no change. Tried to reinstall and installation failed, (errored out complaining about finding the path for nomacscan). Rebooted... services for PRTG would not start. Kept failing due to NoMacScan. I deleted the NoMacScan registry entry, then reinstalled. Manually started PRTG services. All sensors as well as local probe are no longer disconnected. All are online and seem to be functioning as they should. I'll keep monitoring and troubleshooting as I'm not sure what the initial cause was for the repeated disconnecting of local probe.


Jan, 2014 - Permalink

OK, keep us updated.


Jan, 2014 - Permalink