What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

Running the 30 day trial - unable to connect remote probe

Votes:

0

Your Vote:

Up

Down

Runing 'RTG Network Monitor 9.2.0.2141' I am unable to connect a remote probe. have tried this on two different servers acting as remote probes, and both produce the same errors (and remote probe does not appear in 'devices'. On the remote probe log windows I get....

03/02/2012 17:38:47 
03/02/2012 17:38:47 PRTG Probe V9.2.0.2141
03/02/2012 17:38:47 PRTG Probe starting on "EMBANKMENT"
03/02/2012 17:38:48 OS: Windows Server 2003 (5.2.2 Build 3790 Service Pack 2), 1 CPUs, Intel Pentium, on VMware
03/02/2012 17:38:48 Data Path: C:\Documents and Settings\All Users\Application Data\Paessler\PRTG Network Monitor\
03/02/2012 17:38:48 System Path: D:\Program Files\PRTG Network Monitor\
03/02/2012 17:38:48 Local IP: 192.168.202.13
03/02/2012 17:38:48 Core Server IP: 192.168.192.3
03/02/2012 17:38:48 Core Server Port: 23560
03/02/2012 17:38:48 SSL Enabled
03/02/2012 17:38:48 Probe GID: {62B71B7D-8E84-41D2-A7A7-0B6A46592F95}
03/02/2012 17:38:48 Could not initialize Traffic Control API: Error reading interface list, make sure QoS Packet Scheduler is active for this interface.

connection error remote-probe

Created on Feb 6, 2012 9:52:53 AM by  ianrogers (0) 1

Last change on Feb 6, 2012 3:02:39 PM by  Torsten Lindner [Paessler Support]



1 Reply

Votes:

0

Your Vote:

Up

Down

Hello,

this message does not prevent the Probe Service from starting, this is only a message that due to the underlying OS (XP or 2003) a certain feature for the QoS-Sensor will not be available (which is to set the 'ToS'-value for this sensor's packets). The Probe should show the cause later on in the Log why it cannot/doesn't connect.

best regards.

Created on Feb 6, 2012 3:03:36 PM by  Torsten Lindner [Paessler Support]



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.