<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> PRTG Manual: PRTG Administration Tool on Remote Probe Systems

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 affect the way 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 (global ID (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. You cannot change the GID for a local probe.

You can deny GIDs under System Administration—Core & Probes in the PRTG web interface. If you remove a remote probe from the device tree or if you deny a remote probe after installation, its global ID (GID) will be automatically entered in the Deny GIDs list.

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 the System Administration—Core & Probes section for more information.

Check also allowed and denied IPs in System Administration—Core & Probes 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 the ... button to choose another folder on your system.

Before you change the path, make sure you stop both the core server and the probe services and copy all data to the new location.

<your language>

Choose the language for the PRTG Administration Tool on your remote probe from the dropdown list. Default is English.

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 PRTG will use for outgoing monitoring requests of certain sensor types.
• This setting will be used for sensors using the following connection types: HTTP, DNS, FTP, IMAP, POP3, Port, Remote Desktop, SMTP, and SNMP.
• The setting is valid for all monitoring requests sent from this PRTG probe.
• This setting is useful for devices that expect a certain IP address when queried.
• Default setting is auto. PRTG will select an IP address automatically.

This feature does not support all sensor types for technical reasons.

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 the IPv6 section.

This setting is not available for local probes in PRTG on demand.

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): We recommend this setting, although it is not set by default. Enter a schedule below. We recommend that you restart Windows servers once a month for best performance.

Restart Schedule

You can only see this setting 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 day of the week and a time below.
• Once per month (recommended): Select a day of the month and a time below.

Specify Day

You can only see this setting if you selected a schedule option above. Select a specific day of a week (Monday to Sunday) or month (1st to 30th or 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.

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

You can only see this setting if you selected a schedule option above. Select the time of day when PRTG will perform the restart.

You will get a Windows warning message 10 minutes before the restart to inform you if you are a currently logged in user. The actual restart time can differ up to 30 minutes from the settings you enter here.

Open Log Folder...

Open the PRTG Network Monitor data directory on your hard disk drive to access all logfiles that PRTG creates.

Send Logs to Paessler...

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

You can send logfiles more easily with the support bundle via Contact Support in the PRTG web interface.

Open Support Ticket...

This will open the support form on the Paessler website in a browser window.

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 a valid email address. You can provide any of your addresses, but we recommend that you use the email address of your PRTG account, which is entered by default.

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 you want to include the configuration file in the data. PRTG will remove all passwords from the config file before sending it to our support team.