Check NT service vs. TCP Connection

Guest · Post by **Guest** » Tue Feb 11, 2003 1:35 pm

When setting up a test and choosing:
Check Service (2000/xp) -say for W3SVC

I seem to be forced to use a "\" before the IP Address of the machine to be checked.

When Setting up a test and choosing:
TCP Connection -say for Port 80 (http)

I cannot use a "\" before the IP Address.

deviating from either method causes the tests to fail.

Is this by design or is something else going on here??

KS-Soft · Post by **KS-Soft** » Tue Feb 11, 2003 2:11 pm

Service test and TCP test are completelly different test methods and they needs different parameters. Service test requires name of the target system in UNC format. That's why HostMonitor add '\' before name. TCP test requires host name or IP address of the target system, it cannot use UNC name.
So, what the problem?

Regards
Alex

Guest · Post by **Guest** » Tue Feb 11, 2003 2:55 pm

HM doesn't add the "\" in front of the IP address but lets you type in without it anyway. Only when you click on the drop-down list of services does a message appear.

We upgraded from an older version and all settings were retained, but tests that used to work ok were now failing. I found this and fixed them, but was curious why there were differences.

Why would someone check port 80 using TCP Connection rather than checking the W3SVC? In case of non-nt webserver?

thanks for the help.

KS-Soft · Post by **KS-Soft** » Tue Feb 11, 2003 5:30 pm

TCP test is general test for any TCP based service. If you want to check web server, better use HTTP test. For example web server accepts TCP connection but does not return any information, in this case TCP test cannot detect the problem, HTTP test can.

Regards
Alex