Windowshealth on Remote Machines

Maybe i'm toot stupid, don't know...anyway, i can't get Windowshealth working on remote machines. I tested WMI connectivity with wbemtest (as mentioned here) so the remote systems seems to be fine. The SC monitoring service runs as a local Admin...what on earth could still be wrong?



Thanks for help...

Anne

What error message do you get?



Are the ports open to remote machine? (no local firewall or firewall in between?)

Yes, right, it was a firewall issue, tried it with a local machine. So what do we need open? Already open are:



135 (TCP)

137 (UDP)

138 (UDP)

139 (TCP)

445 (TCP)

1025 (TCP)

4477 (TCP)



I found those by looking at netstat...what am i missing?

Following document from our online manual specifies which ports to open for what check:

http://wiki.serverscheck.net/index.php/Firewall

The Ports stated in that document (447 and 135) are open, still i get no connection. Is there anything else i have to do to get a connection?

As I asked in the previous post, what error message do you get when you try creating a Windows monitor?

I am having the same problem.



well sometimes I get error status 0, sometimes its a 1 or a 2.



I went through the directions step by step and checked everything that was suggested.



I can telnet to all ports that it is asking. All services are running using windows admin accounts.



here is the message



The check has been performed.



Status: DOWN?

Error returned: The RPC server is unavailable.

Value returned: 0



thanks.

0,1 or 2 being returned for WINDOWSHEALTH checks is the PING response time in ms.



Your Windows systems are not configured correctly for remote administration (and as such allow remote monitoring through the Windows WMI protocol).



See knowledge base article on RPC:

http://kb.serverscheck.com/index.php?page=index_v2&id=1&c=1

I will check it now....

I checked everything out and I can connect to every port mentioned in the supported documentation.



Any other suggestions?

Did you check the Microsoft Knowledge Base article?

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q131641

regarding multiple IP's.



If that does not help and you checked all items and you are not using a firewall and the service runs under a Windows admin account, then you need to contact Microsoft's technical support to determine the RPC issue as this is an OS issue regardless of the monitoring product you would use.

It appears that the error can also be produced when the Audit Log on the remote system is full:

http://support.microsoft.com/kb/242361/en-us



Additional Microsoft Knowledge Base articles that may help you:

http://support.microsoft.com/kb/189007/en-us

http://support.microsoft.com/kb/302323/en-us

I don't think it is an OS issue. We have other WMI software that seems to work fine.



do you have another list of ports that need to be checked or anything?



all of the ports that were in the support info above have been verified.

Under what account does the ServersCheck Monitoring Service run? Does the service have network access?



RPC errors are returned by the OS; we capture the error message from WMI communication.

servers check runs under domain admin account.

I checked the other links you sent over and they either don't apply or they were not causing the issue. I verified them.



I do think this is a firewall issue, we have hardware firewalls in place between VLANS.



But the ports you have listed all check out.

Error Solution Suggestion Tool

Reported error :



UNKNOWN





No suggestions found for the error. The error has been logged and will be reviewed for addition to the Suggestion Tool.



sometimes I get a real error, some times I get this..

Assuming you verified all knowledge base articles sent to you, can you login on the host running the ServersCheck software and then do following:

1. Select Start > Run

2. Type WBEMTEST in the text field

3. Click OK.

4. Click Connect.

5. Enter <remote machine name or IP>rootcimv2 in the ServerNamespace text field.

6. Click on the Connect button

If that works then do following; in the credentials tab enter the next 2 different profiles:



1) Try to connect to host using local administrator account (for given host)



2) Try to connect to host using domain administrator account (that is member of local Administrators group on host)

If all above work, then login as a normal network administrator on the host running the ServersCheck software.



1/ Stop the ServersCheck webserver service

2/ From the command prompt in the ServersCheck main directory type:

s-server

3/ Connect to the ServersCheck web interface at http://localhost:1272

4/ For a Windowshealth monitor giving you the RPC error, click on TEST SETTINGS



What is the result?

Number: 0x800706ba

Facility: Win32

Description: The RPC server is unavailable.



is what I get back. should I try with domain credentials?





the forum doesn't let me post as fast as I want.. I get a "no spamming message"

Number: 0x800706ba

Facility: Win32

Description: The RPC server is unavailable.



-> do you get this using the local administrator account or the domain admin?



WBEMTEST is a Microsoft component and as you see with the error message the issue is at that level. You have no Windows firewall running?

there is no windows firewall running. the ICS service isn't even started on the server(s) or the workstations.



There are hardware firewalls in place. but ports have been open according to the KB.



I ran the microsoft port scanning tool and was able to verify that the ports on the servers are listening for the port numbers listed.



Number: 0x800706ba

Facility: Win32

Description: The RPC server is unavailable.



I get this for both local and domain admin user accounts

When you try against a system in a the same network segment as where the software installed, do you then get the same error message through WBEMTEST?



Are communications in the firewall allowed from the remote host to the server running the software? Following knowledge base article from Microsoft tells you what needs to be opened on the other side:

http://support.microsoft.com/?kbid=154596



As you will see in the above knowledge base article, RPC may use dynamic ports in its reply from any port above 1024. This could be blocked by your firewall. Try allowing from remote host to server running the software all TCP connections above or equal to 1024.