Download PRTG – Free Network Monitor 23.2.83.1760 Download

Monitor all the systems, devices, traffic and applications in your IT infrastructure. Businesses increasingly rely on their networks to move data, provide communications and enable basic operations. Loss of performance or system outages can seriously affect the bottom line of your business.

Continuous network and server monitoring allows you to find problems and fix them before they become a serious threat to your business:

• Avoid bandwidth and server performance bottlenecks
• Deliver better quality of service to your users by being proactive
• Reduce costs by purchasing bandwidth and hardware based on actual load
• Increase your profits by avoiding losses caused by undetected system errors
• Find peace of mind: As long as you don’t hear from PRTG via e-mail, SMS, pager etc., you know that everything is going well and you have more time to take care of other important matters.

Your entire network at a glance

PRTG Network Monitor covers all aspects of network monitoring: up/downtime monitoring, traffic and usage monitoring, SNMP, NetFlow, packet sniffing and many more, combined with concise reporting and analysis functions – one clear and simple solution for your entire network.

Monitoring of bandwidth and network usage

PRTG Network Monitor runs 24/7 on a Windows-based machine in your network, recording network usage parameters. Recorded data is stored in a database for historical reports.

The easy-to-use web-based user interface allows you to configure the devices and sensors you want to monitor. You can create usage reports and give colleagues and customers access to graphs and tables.

What is new

Fixed

PRTG core server

We fixed an issue with cloning and moving devices that in certain cases caused the PRTG server to freeze from PRTG 4/22/81, resulting in high CPU load and server crashes and reboots.

Fixed

HPE 3PAR sensors

The sensor types HPE 3PAR Virtual Volume, HPE 3PAR Drive Enclosure and HPE 3PAR Common Provisioning Group are working again. The sensors showed a down status with the error message 415 Unsupported Media Type after updating to the latest PRTG version 23.1.82.2074 due to an issue with HTTP POST requests via the REST API. This also affected the experimental REST Custom v2 (BETA) sensor.

HTTP push sensors

HTTP push sensors work with HTTPS again. The sensors remained in unknown status after updating to the latest PRTG version 23.1.82.2074 with HTTPS enabled in the sensor TLS settings and received no response to your sensor requests in this case. Affected sensor types were HTTP Push Data, HTTP Push Data Advanced, HTTP Push Count and HTTP IoT Push Data Advanced.

Fixed

Notification delivery

PRTG resends your email notifications when you use SMTP servers with specific TLS configurations as SMTP relay servers, such as Microsoft Office 365. In PRTG version 23.1.82.2074, email notifications did not work with certain servers and for example displayed the error message Error when sending “Email”: Connection to SMTP relay server “outlook.office365.com” failed in the logs due to a problem with TLS connections.

Fixed

License name

You can reactivate licenses when the license name contains an ampersand (&). The activation of the license failed with the message License name and key do not match the activation file. in last PRTG version 23.1.82.2074 due to a problem with coding.

known problems

Alerts

The email notification subject does not display correctly in the current PRTG version if it contains special characters such as diacritics or umlauts. If you primarily use special characters or Asian and Cyrillic characters in your email notifications, we recommend that you do not update your PRTG installation to version 23.1.82. We will provide a fix for this issue with an upcoming PRTG release.

Windows MSMQ queue length

In certain configurations, the Windows MSMQ Queue Length sensor reports an error with the message Queuename not found on the specified machine. The error may appear during authentication on the target device. We are investigating the cause of this issue.

Complete release notes here.