<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> PRTG Manual: PRTG Administration Tool on Core Server System

Select TCP Port for PRTG's Web Server

PRTG is running a web server in order to provide the web and Windows interface. Please specify on which port this web server will run. Choose between:

• Secure HTTPS server (recommended, mandatory for internet access): This is the recommended setting and needed to access the PRTG server via the internet. Use a secure HTTPS connection that is encrypted via SSL on port 443.
  Note: Although the connection is secure, you will see an SSL Certificate Warning in your browser when logging in to the PRTG web interface, because the default certificate is unknown to your browser. You can install another SSL certificate for PRTG later. Please see Using Your Own SSL Certificate.
  Note: If port 80 is free, PRTG will reserve it as well. When users try to connect on port 80 via HTTP, they will then be redirected to port 443 via HTTPS. You can change this behavior using a registry setting.
  Note: If port 443 is not available, PRTG will try port 8443 as fallback. If this port is also not available, PRTG searches from port 32000 upwards for a free port. PRTG sends a ticket that shows you the currently used port number and will switch back to 443 as soon as it is available again.
• Insecure HTTP server (standard port 80, not recommended): Use a standard web server without SSL encryption on port 80. This setting is not recommended for WAN connections.
  Note: If used on the internet, attackers could potentially spy on credentials you enter into PRTG. We strongly recommend using this option in a LAN only.
• Expert configuration: This setting allows you to specify a custom web server port and the security of the connection. This option is intended for systems with an existing web server on the standard port. Define port and encryption below.

Expert Configuration: SSL Encryption

This setting is only visible if the expert configuration is selected above. Specify if you want to use an SSL encryption. Choose between:

• Use SSL encryption (HTTPS): Use a secure HTTPS connection that is encrypted via SSL on a custom port as defined above.
  Note: Although the connection is secure, you will see an SSL Certificate Warning in your browser when logging in to the PRTG web interface, because the default certificate is unknown to your browser. You can install another SSL certificate for PRTG later. Please see Using Your Own SSL Certificate.
• Don't use encryption (not recommended): This setting is not recommended for WAN connections. Use a standard web server without SSL encryption on a custom port as defined above.
  Note: If used on the internet, attackers could potentially spy on credentials you enter into PRTG. We strongly recommend using this option in a LAN only.

Expert Configuration: Web Server Port

This setting is only visible if the expert configuration is selected above. Enter the desired TCP port number you want the PRTG web server to run on. Please enter an integer value.

Note: If you use a secure connection and port 80 is free, PRTG will reserve it as well. When users try to connect on port 80 via HTTP, they will then be redirected to the custom port via HTTPS. You can change this behavior using a registry setting.

Note: If port the defined port for a secure connection is not available, PRTG will try port 8443 as fallback. If this port is also not available, PRTG searches from port 32000 upwards for a free port. PRTG sends a ticket that shows you the currently used port number and will switch back to the original port as soon as it is available again.

Select IP Address for PRTG's Web Server

PRTG is running a web server in order to provide access via the web and Windows interface. Please specify which IP address this web server will run on. Note: Later, you can log in to PRTG by simply pointing your browser to the specified IP address.

Choose between:

• Localhost, 127.0.0.1 (PRTG will not be accessible from other computers): Use 127.0.0.1 only. PRTG's web and Windows interface will only be accessible from the computer PRTG is installed on.
  Note: Either the selected port or at least one port in the range from 8080 to 8089 has to be available on 127.0.0.1.
   

Note: If you run PRTG on localhost, please do not use the DNS name http://localhost to log in to the web server, as this may considerably slow down PRTG's web interface. Please use your local IP address or http://127.0.0.1 instead.

• All IPs available on this computer: Use all IP addresses available on this computer and enable access to the web server for all of these addresses. Note: The TCP port selected below must be free on every available IP address.
• Specify IPs: Select specific IP addresses on which the PRTG Web server will run on. A list specific to your system is shown. Add a check mark in front of every IP address you want the PRTG web server to be available at. You can also select and deselect all addresses by clicking on the check box in the table header.
  Note: Either the selected port or at least one port in the range from 8080 to 8089 has to be available on the specified IP address.

Note: Regardless of the selected setting above, one port in the range from 8080 to 8180 has to be available on the specified IP address so PRTG can create reports. The report engine will try to connect to the core server on one of these ports.

Note: If PRTG does not find a network card on startup it will switch the IP setting to Localhost. This setting will remain, even if a network card is available later on. If you disabled or removed the network card on the machine running the PRTG core server, please re-check this setting.

Select System Language

Choose the system language from the drop down list. Default is English. Depending on your installation, you may be able to choose other languages here. This setting defines the language of the Ajax web interface, as well as of the PRTG Administration Tool.

Probe Connection Management

Define how PRTG will handle incoming connections from probes. Choose between the following options:

• Accept connections from the Local Probe only (default setting, does not allow remote probes): This is the default setting. Only local probe connections will be accepted by the PRTG core server. You cannot use remote probes with this setting enabled.
• Accept connections from remote probes on all IPs: Incoming connections from remote probes will always be accepted, no matter on which IP address of the core server they come in.
• Accept connections from remote probes on selected IPs only: Incoming connections from remote probes will only be accepted on the selected IP address(es) of the core server. In the list, select the IP addresses by adding a check mark in front of the desired IPs.

You can also change this setting in the PRTG web interface under System Administration—Core & Probes.

Local Storage of Data Files and Monitoring Database

Define the data folder to which PRTG will store configuration and monitoring data. Click on the ... button to choose another folder on your system.

Note: Before changing the path, make sure you stop both services and copy all data to the new location.

Click on the Revert to default folder to reset to default.

Cluster Settings

Depending on the current cluster settings you will see different information here.

• Cluster Mode: Shows which cluster mode the current installation is running. This setting is shown for your information only and cannot be changed here. Possible values are Standalone (no cluster mode), Cluster Mode: Master Node, or Cluster Mode: Failover Node.
• Cluster Port: This field is only shown when PRTG is running in a cluster mode. This setting is shown for your information only and cannot be changed here.
• Cluster Access Key: This field is only shown when PRTG is running in a cluster mode. This setting is shown for your information only and cannot be changed here.
• Own Node ID: This field is only shown when PRTG is running in a cluster mode. This setting is shown for your information only and cannot be changed here.

Cluster Mode Actions

Depending on the current cluster settings, you see different active buttons here. For details, see below.

Email Address

Enter a valid administrator's email address. By default, PRTG will send notifications and important messages to this address.

Login Name

Enter a name for the PRTG System Administrator login; this is your default login. You use it when you log in to the PRTG web interface or Windows Enterprise Console.

Note: The default login name is prtgadmin

Password

Enter a password for the PRTG System Administrator login; this is your default login. You use it when you log in to the PRTG Web- or  Windows Enterprise Console.

Note: The default password is prtgadmin

Confirm Password

If you change your password, re-enter the password for the PRTG System Administrator login to confirm it.

Name of Probe

Enter a meaningful name to identify the probe. PRTG shows this name, for example, in the device tree, and in all alarms by default. Please enter a string.

Reconnect Time

Define the time that PRTG will wait until the probe tries to reconnect to the core server if the connection fails. Please enter an integer value.

These settings will affect how the probe will connect to the core server. A probe is either a local probe or a remote probe. PRTG will automatically detect the type of probe and show the correct setting options.

Server (IPv4 address or DNS name)

If this probe is configured as the Local Probe of the PRTG core installation, it will connect to the core via 127.0.0.1 which you cannot change.

If this probe is configured as a Remote Probe, enter the IP address or DNS name of the core server.

Probe GID

The Probe GID is a unique identifier for the probe. We recommend that you do not change it.

Exception: Only if you substitute an existing remote probe from a different computer, you have to copy the GID from the old probe to the new probe. To do so, click on the Edit GID... button and confirm the warning with Yes. You can then change the value. It is not possible to change the GID for a local probe.

Note: You can deny GIDs under System Administration—Core & Probes in the PRTG web interface.

Probe Access Key

You do not need an access key for Local Probe connections.

On a Remote Probe, the Probe Access Key must match one of the access keys configured in your PRTG core server installation. If it does not match, the remote probe will not be able to connect to the core server. Please see System Administration—Core & Probes section for more information.

Note: Also check allowed and denied IPs there to ensure that the core server accepts the IP address of the remote probe.

Confirm Access Key

If you enter an access key for a remote probe, enter it in this field again to assure correctness.

Path

Define the data folder to which PRTG will store configuration and monitoring data. Click on the ... button to choose another folder on your system.

Note: Before changing the path, make sure you stop both services and copy all data to the new location.

Define the IP address used for outgoing monitoring requests.

• If there is more than one IP on the current system available, you can specify the IP address that will be used for outgoing monitoring requests of certain sensor types.
• The setting is valid for all monitoring requests sent from this PRTG probe.
• This setting will be used for sensors using the following connection types: HTTP, DNS, FTP, IMAP, POP3, Port, Remote Desktop, SMTP, and SNMP. Note: This feature does not support all sensor types for technical reasons.
• This is useful for devices that expect a certain IP address when queried.
• Default setting is auto. PRTG will select an IP address automatically.

Note: If you change this setting, some sensors might stop working. For example, sensors might show a Down status if the selected IP address is blocked on the way to or directly on the monitored device.

Outgoing IPv4

Define the IP address for outgoing requests using the IPv4 protocol. The list shows all IP addresses available on the current system. Choose a specific IP address or select auto.

Outgoing IPv6

Define the IP address for outgoing requests using the IPv6 protocol. The list shows all IP addresses available on the current system. Choose a specific IP address or select auto. For details about the basic concept of IPv6 in PRTG, please see IPv6 section.

Restart Options

For best performance, we recommend that you regularly restart the Windows servers on which PRTG is running. To do this automatically for PRTG, you can schedule an automatic restart. Choose between the following options:

• No scheduled reboot or service restart: Do not perform any scheduled restart of services automatically. We recommend a manual restart every few weeks. You can initiate a restart of your PRTG core server and probes under System Administration—Administrative Tools in the PRTG web interface.
• Scheduled restart of PRTG services: Restart all PRTG services on the system where this probe runs on. If you choose this option on the local probe, the PRTG core server will restart as well. Define a schedule below.
• Scheduled system reboot (recommended): This is the recommended setting, although not set by default. Enter a schedule below. We recommend restarting Windows servers once a month for best performance.

Restart Schedule

This setting is only visible if you selected a schedule option above. Choose how often you want to restart PRTG services or the Windows server:

• Once per week: Select a weekday and time below.
• Once per month (recommended): Select a day of month and time below.

Specify Day

This setting is only visible if you selected a schedule option above. Select a specific day of a week (Monday to Sunday) resp. month (1st to 30th resp. Last). If you select Last, the restart will always be executed on the last day of the month, regardless of how many days the month has.

Note: If you select a date that does not exist in every month (for example, the 30th day in February), PRTG will automatically initiate the restart on the last day of this month.

Specify Hour

This setting is only visible if you selected a schedule option above. Select the time of day when PRTG will perform the restart.

Note: A Windows warning message will be displayed 10 minutes before restart to inform a logged in user. The actual restart time can differ up to 30 minutes from the settings you enter below!

Open Log Folder...

Open the PRTG Network Monitor data directory on your hard disk drive to access all log files which PRTG creates.

Send Logs to Paessler...

Open an assistant to send log files to the Paessler support team. Please see below for details.

Note: You can send log files more easily with the support bundle via Contact Support in the PRTG web interface.

Open Support Ticket...

This will open the support form on Paessler's webpage in a browser window. Note: If you need help, we recommend that you use the Contact Support option in the PRTG web interface instead.

Name

Enter your name.

Email

Enter your valid email address. You can provide any of your addresses; however, recommended and default is the email address of your PRTG account.

Ticket No.

This field is optional. If you have already opened a ticket at Paessler support, please provide the ticket number you received. Your files will then be associated with your ticket automatically.

Please enter the ticket number starting with PAE followed by four or more digits, for example, PAE12345. If you do not have a ticket number, leave this field empty.

Configuration

Define if your configuration file will be included in the data. PRTG will remove all passwords from the config file before sending it to our support team.

Name of Probe

Enter a meaningful name to identify the probe. PRTG shows this name, for example, in the device tree, and in all alarms by default. Please enter a string.

Reconnect Time

Define the time that PRTG will wait until the probe tries to reconnect to the core server if the connection fails. Please enter an integer value.

These settings will affect how the probe will connect to the core server. A probe is either a local probe or a remote probe. PRTG will automatically detect the type of probe and show the correct setting options.

Server (IPv4 address or DNS name)

If this probe is configured as the Local Probe of the PRTG core installation, it will connect to the core via 127.0.0.1 which you cannot change.

If this probe is configured as a Remote Probe, enter the IP address or DNS name of the core server.

Probe GID

The Probe GID is a unique identifier for the probe. We recommend that you do not change it.

Exception: Only if you substitute an existing remote probe from a different computer, you have to copy the GID from the old probe to the new probe. To do so, click on the Edit GID... button and confirm the warning with Yes. You can then change the value. It is not possible to change the GID for a local probe.

Note: You can deny GIDs under System Administration—Core & Probes in the PRTG web interface.

Probe Access Key

You do not need an access key for Local Probe connections.

On a Remote Probe, the Probe Access Key must match one of the access keys configured in your PRTG core server installation. If it does not match, the remote probe will not be able to connect to the core server. Please see System Administration—Core & Probes section for more information.

Note: Also check allowed and denied IPs there to ensure that the core server accepts the IP address of the remote probe.

Confirm Access Key

If you enter an access key for a remote probe, enter it in this field again to assure correctness.

Path

Define the data folder to which PRTG will store configuration and monitoring data. Click on the ... button to choose another folder on your system.

Note: Before changing the path, make sure you stop both services and copy all data to the new location.

Define the IP address used for outgoing monitoring requests.

• If there is more than one IP on the current system available, you can specify the IP address that will be used for outgoing monitoring requests of certain sensor types.
• The setting is valid for all monitoring requests sent from this PRTG probe.
• This setting will be used for sensors using the following connection types: HTTP, DNS, FTP, IMAP, POP3, Port, Remote Desktop, SMTP, and SNMP. Note: This feature does not support all sensor types for technical reasons.
• This is useful for devices that expect a certain IP address when queried.
• Default setting is auto. PRTG will select an IP address automatically.

Note: If you change this setting, some sensors might stop working. For example, sensors might show a Down status if the selected IP address is blocked on the way to or directly on the monitored device.

Outgoing IPv4

Define the IP address for outgoing requests using the IPv4 protocol. The list shows all IP addresses available on the current system. Choose a specific IP address or select auto.

Outgoing IPv6

Define the IP address for outgoing requests using the IPv6 protocol. The list shows all IP addresses available on the current system. Choose a specific IP address or select auto. For details about the basic concept of IPv6 in PRTG, please see IPv6 section.

Restart Options

For best performance, we recommend that you regularly restart the Windows servers on which PRTG is running. To do this automatically for PRTG, you can schedule an automatic restart. Choose between the following options:

• No scheduled reboot or service restart: Do not perform any scheduled restart of services automatically. We recommend a manual restart every few weeks. You can initiate a restart of your PRTG core server and probes under System Administration—Administrative Tools in the PRTG web interface.
• Scheduled restart of PRTG services: Restart all PRTG services on the system where this probe runs on. If you choose this option on the local probe, the PRTG core server will restart as well. Define a schedule below.
• Scheduled system reboot (recommended): This is the recommended setting, although not set by default. Enter a schedule below. We recommend restarting Windows servers once a month for best performance.

Restart Schedule

This setting is only visible if you selected a schedule option above. Choose how often you want to restart PRTG services or the Windows server:

• Once per week: Select a weekday and time below.
• Once per month (recommended): Select a day of month and time below.

Specify Day

This setting is only visible if you selected a schedule option above. Select a specific day of a week (Monday to Sunday) resp. month (1st to 30th resp. Last). If you select Last, the restart will always be executed on the last day of the month, regardless of how many days the month has.

Note: If you select a date that does not exist in every month (for example, the 30th day in February), PRTG will automatically initiate the restart on the last day of this month.

Specify Hour

This setting is only visible if you selected a schedule option above. Select the time of day when PRTG will perform the restart.

Note: A Windows warning message will be displayed 10 minutes before restart to inform a logged in user. The actual restart time can differ up to 30 minutes from the settings you enter below!

Open Log Folder...

Open the PRTG Network Monitor data directory on your hard disk drive to access all log files which PRTG creates.

Send Logs to Paessler...

Open an assistant to send log files to the Paessler support team. Please see below for details.

Note: You can send log files more easily with the support bundle via Contact Support in the PRTG web interface.

Open Support Ticket...

This will open the support form on Paessler's webpage in a browser window. Note: If you need help, we recommend that you use the Contact Support option in the PRTG web interface instead.

Name

Enter your name.

Email

Enter your valid email address. You can provide any of your addresses; however, recommended and default is the email address of your PRTG account.

Ticket No.

This field is optional. If you have already opened a ticket at Paessler support, please provide the ticket number you received. Your files will then be associated with your ticket automatically.

Please enter the ticket number starting with PAE followed by four or more digits, for example, PAE12345. If you do not have a ticket number, leave this field empty.

Configuration

Define if your configuration file will be included in the data. PRTG will remove all passwords from the config file before sending it to our support team.