New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

200.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free PRTG
Download >>

 

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

 

Top Tags


View all Tags


FTP sensor behavior and logging

Votes:

0

Your Vote:

Up

Down

We notice that FTP sensors switch from explicit to implicit mode when the sensor doesn't receive data or when the connection time-outs.

There is then made an log entry: Connection established using implicit mode.

We have 2 nodes for checking. This message applies for one of the two nodes, the other node stays using port 21 explicit mode. However the node isn't noted down in the message. When PRTG (or the single node) switches to implicit mode it uses port 990 instead of 21 and keeps using this until the sensor gets paused. So it doesn't seem to reset or detect that port 21 explicit mode becomes functional again. The only way to assure that port 990 isn't used is to choose "Do not use Transport-Level Security" bu this completely disables ssl.

This comes down to these requests:

FIX: Correct logging; noting down the Node that switched mode. IMPROVE: Detection that port 21 explicit is working again and switching back from explicit. ADD: Have the ability to configure the sensor to use implicit or explicit mode. As an alternative; force to always use the configured port.

The last one is the most important for us because it gives us to control how measurements are done and also makes them more predictable (or less unpredictable).

explicit ftp implicit logging

Created on Jan 22, 2016 11:02:36 AM by  Poort80 Hosting Services (0) 1



6 Replies

Votes:

0

Your Vote:

Up

Down

Thanks for the request! I'll forward this to our developers and let you know what they said :)

Created on Jan 25, 2016 12:58:53 PM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

So I talked to the devs; this "workaround" won't get implemented. Sorry! :/

Created on Jan 28, 2016 1:02:24 PM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hmm I don't think that is fully understood that these shortcomings of PRTG and FTP sensors is a serious production issue for us. Also, I invested quit some time in making this post so there is enough information to do something about this. Expecting to get at least a decent reply back. A short reply with only that this "workaround" won't get implemented isn't then very professional to my opinion.

So: 1. Could you please explain to me what is meant with a "workaround"? 2. What do the devs have to say about PRTG not honoring the configured port in the FTP sensor settings and just randomly using another port when switching modes?

Created on Jan 28, 2016 5:27:06 PM by  Poort80 Hosting Services (0) 1



Votes:

0

Your Vote:

Up

Down

Sorry for the late reply. Just so we're on the same page here - are you using the most recent PRTG version? Because this sounds like old behaviour of the FTP sensor...

Created on Feb 3, 2016 5:19:40 PM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

We are currently at v16.1.21.1422+ Before that the most recent version of v15. Both are having the same issues.

Created on Feb 5, 2016 3:21:06 PM by  Poort80 Hosting Services (0) 1



Votes:

0

Your Vote:

Up

Down

Sorry that it took a while to get back on this. We talked about this in our development team and the problem itself originates in the sensor timing out. Is there a way for you to fix this? Because unfortunately, there is no easy way to fix this within the sensor as this is their "fallback" method. Other customers don't have any trouble with it so far (this feature is implemented since mid 2014).

Created on Feb 18, 2016 2:54:33 PM by  Stephan Linke [Paessler Support]

Last change on Feb 18, 2016 2:55:12 PM by  Stephan Linke [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.