I am trying to run PRTG on a server that is running another web server (ScreenConnect not IIS).

I have created 2 local IP's and 2 external IP's for each (PRTG and ScreenConnect) webserver to use port 80.

ScreenConnect is bound to 10.1.1.50:80 PRTG is configured to use 10.1.1.51:80

If I start the ScreenConnect service and run netstat -an I see the it is listening only on 10.1.1.50:80

When I run the PRTG administration tool I select 10.1.1.51 as the address for the web server and port 80. Saving the configuration resets the PRTG port to 8080.

If I stop the SC service I am able to use the PRTG admin tool to set the web server port to 80 listening on 10.1.1.51 and confirmed using netstat -an.

If I attempt to start PRTG while the SC service is running the PRTG port is changed back to 8080.

Thoughts?

Article Comments

Hello,

By default, PRTG perform a redirect to 8080 if port 80 is used by another software. It seems that ScreenConnect still use 10.1.1.51:80 if another program try to bind this port. So you might either change the used port in the PRTG Administrator tool to another port than 80 or you might check the configuration in ScreenConnect.


May, 2016 - Permalink

If ScreenConnect is the only web service running, netstat -an 10.1.1.50 is the only IP displayed as listening on port 80. Is it possible that netstat could be providing incomplete information? Is it possible that ScreenConnect could be binding 10.1.1.51:80 in a hidden process?

If PRTG is running netstat -an shows only 10.1.1.51 is the only IP listening on port 80. ScreenConnect will also fail if attempting to start while PRTG is running.


May, 2016 - Permalink

If netstat shows the port as free it can be possible that ScreenConnect tries only to bind this port if another software tries to bind this port. You should contact ScreenConnect about this issue.


May, 2016 - Permalink

Do you mean that if ScreenConnect is not using port 80 it binds it to an unused IP when PRTG tries to start? Almost as if it is watching the other IP waiting for another service to bind the port then takes it as soon as PRTG attempts to bind port 80 on the other IP?

Then once PRTG gives up and uses 8080, ScreenConnect unbinds port 80 on the other IP?


May, 2016 - Permalink

Yes, that's maybe possible, but this is what you have to clarify with the ScreenConnect support.


Jun, 2016 - Permalink