Hi,
I have added a Port sensor to monitor the TCP/IP port of an application installed on one of our servers. This application uses port 55000, however, when I enable to sensor the application fails. Would you have any ideas? Does the port sensor get a lock on port?
Thanks, Noel
Article Comments
Hi, Our version is PRTG Network Monitor 12.2.1.1768. What happens is that on one of ours servers we have an application that starts as a service running on port 55000. Users connect to this application through this port. When we enable the sensor any new connections to the application on that port come up with an error. We have to restart the service and disable to sensor to stop this behaviour. Thanks, Noel
May, 2012 - Permalink
Hi,
so your application goes to error state and not PRTG? Did I get you right?
May, 2012 - Permalink
Hi, yep that's correct our application goes to error state when we activate the prtg posrt sensor.
May, 2012 - Permalink
Hi,
the PRTG Port sensor performs only a TCP Connect towards the target. No data is sent, so I'm assuming this might be the issue as your application most likely waits for data after the connection. I'm afraid this behaviour of the sensor cannot be changed but you may try sending a command (can be set up in the sensor settings) to the host.
Best regards
May, 2012 - Permalink
Hi, Just wondering if you have an example of a SEND command I can put in...any one I enter I just keep getting No Data Yet from PRTG sensor?
May, 2012 - Permalink
Hi,
when the send command option is activated a telnet session to the host is established, in this telent session a command is executed. But I'm afraid I cannot giva a example as the command and if it might get executed fully depends on the capabilities of your server / application.
Best regards
May, 2012 - Permalink
Hi,
we just tested the scenario you are describing and I'm afraid we cannot recreate it neither with V9 nor with V12 of PRTG. What precise version on PRTG are you using and what is the error message resp. error behaviour?
Best regards
May, 2012 - Permalink