IPv6 issue

Fr00pFr00p
edited November 2010 in Monitoring Software v12 and lower
Hi,



after installing the IPv6 protocol on seven of our Servers ServerCheck gets some errors with rules wich worked before.



Before installing the IPv6 protocol SERVICE, PROCESS an DRIVESPACE rules worked normaly and after the installation we got errors like "xxx not found as service", "The RPC Server is unavailable".



I checked the suggested solution from the "Error Solution Suggestion Tool" but it didn't solve the problem.



Strange is, that the problem only exist on three of our seven servers which were switched to IPv6.



Any ideas where the problem could lie?



Kind regards



Fr00p


Comments

  • AdministratorAdministrator
    Have you tried following?



    http://wiki.serverscheck.com/index.php/Testing_wmi
  • Fr00pFr00p
    Hi, thanks for the link.

    It seems that Port 135 isn't open on the servers where the errors occour.

    The windows firewalls on the server are disabled. Do you know how i could open port 135 without activating the firewall?



    The command netsh firewall add portopening TCP 135 DCOM_TCP returns "The service wasn't started".



    Kind regards



    Fr00p
  • AdministratorAdministrator
    Hello,



    Did you try starting the service with net start rpcss?
  • Fr00pFr00p
    Hi,



    the rpcss service is started already but the port isn't open.
  • AdministratorAdministrator
    If it doesn't work with Microsoft Windows native WMI testing application, then it is a configuration issue of the servers being monitored. Unfortunately we can't help any further than this.



    If you have a Windows system administrator, then contact him to check the settings of the server. If you don't have one, then contact Microsoft tech support by explaining what you did with the WMI Tester from Microsoft. They know their products better than we do.
This discussion has been closed.