Hi,
I have a problem with Hostmon installed on Windows 2003 Server.
I tried already with different versions of hostmon, but always the result.
We have a lot of servers, with a lot of services to monitor and sometimes the checks of some servers give the status "Unknown", when they are "bad" or "OK".
Sometimes it helped to replace the into the ip of the server or in the full DNS name of the server, but this does not last long, before the problems occur again.
Can anyone help me withthis problem?
thx,
Chrisse
Problem with Hostmon installed on Windows 2003 Server
It's not only with "service"-tests only also with CPU-tests, ping-tests,...
Network too busy can be the problem, but I doubt it.
Because I ran the same HML on another machine with Win 2000 AS and on a machine win 2003 installed.
On the win 2000 machine all tests give an answer, on the other machine not all give an answer and are markes unknown.
These machines are running at the same time, so It's probably not the network which is too busy to respond.
Is there an explantion for this?
thx,
Chrisse
Network too busy can be the problem, but I doubt it.
Because I ran the same HML on another machine with Win 2000 AS and on a machine win 2003 installed.
On the win 2000 machine all tests give an answer, on the other machine not all give an answer and are markes unknown.
These machines are running at the same time, so It's probably not the network which is too busy to respond.
Is there an explantion for this?
thx,
Chrisse
H'm, even ping test works fine on W2K system and doesn't work well in Windows 2003...It's not only with "service"-tests only also with CPU-tests, ping-tests,...
Because I ran the same HML on another machine with Win 2000 AS and on a machine win 2003 installed.
On the win 2000 machine all tests give an answer, on the other machine not all give an answer and are markes unknown.
Looks like there are some problems with that system. E.g. "service" test and "ping" tests use completelly different code, different API and different DLLs. Looks like system has some problems with resolving host names (ping test can display "Unknown" status only in case system cannot get IP address by specified host name).
Sorry, I cannot say what's exactly wrong with the system (you said it doesn't work well when you specify IP address either). If you can use HostMonitor on Windows 2000 server, better install it there. We recommend Windows 2000 because in our opinion this platform has least amount of bugs.
Regards
Alex
I also have tests that go into "unkown" state for
Just today I have a service check test that checks to see if antivirus is running on a file server. There are 6 other tests for this server that are still fine but this service check is in an unknown status. I put in the FQDN and refreshed but that did not work. I replaced the hostname with the IP Address then the test responded normally. I've seen this happen on several occasions recently. I don't know what is causing it.
HM 4.16 Windows 2000 SP4
Thx,
Mark
HM 4.16 Windows 2000 SP4
Thx,
Mark