Unable to monitor 3389 with TCP Connection test

All questions related to installations, configurations and maintenance of Advanced Host Monitor (including additional tools such as RMA for Windows, RMA Manager, Web Servie, RCC).
Post Reply
Gavin
Posts: 58
Joined: Thu Sep 24, 2009 8:44 am

Unable to monitor 3389 with TCP Connection test

Post by Gavin »

Not sure if I am using the correct test here. 3389 is the port used for RDP, I'd like to check on a host that is is up and responding correctly. The equivalent test would be say a telnet servername 3389 if that responds it is working, if it doesn't it is not. What's the equivalent test?
KS-Soft Europe
Posts: 2832
Joined: Tue May 16, 2006 4:41 am
Contact:

Post by KS-Soft Europe »

TCP test should work for any TCP server, including RDP.
What other settings do you use for TCP test (Send data, Alert when) ?
What Timeout is specified for TCP test ?
Gavin
Posts: 58
Joined: Thu Sep 24, 2009 8:44 am

Post by Gavin »

I have alert when no reply and for send date I have put nothing (timeout of 10000msec)
KS-Soft Europe
Posts: 2832
Joined: Tue May 16, 2006 4:41 am
Contact:

Post by KS-Soft Europe »

You should disable "alert when" option.
Post Reply