Bobcares

wesupport

CLIENT AREACall Us 1-800-383-5193
Bobcares

wesupport

Call Us 1-800-383-5193
Bobcares

wesupport

Call Us 1-800-383-5193

Need help?

Our experts have had an average response time of 13.52 minutes in October 2021 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

WMI Error: Login to remote object in Nagios – How to solve it

by | May 16, 2021

WMI Error: Login to remote object

Generally, we receive this error when we run the WMI Configuration Wizard.

As part of our Server Management Services, we assist our customers with several Nagios queries.

Today, let us see how we can resolve the WMI error, Login to remote object.

 

WMI Error: Login to remote object

WMI can provide management data and operational information about Windows systems.

Nagios Core and Nagios XI are capable of monitoring Windows machines via WMI.

When we run the WMI Configuration Wizard, we receive the error:

UNKNOWN – The WMI query had problems. The error text from wmic is: [wmi/wmic.c:196:main()]
ERROR: Login to remote object.
NTSTATUS: NT code 0x800706ba – NT code 0x800706ba

It is possible that the Windows Firewall is not allowing the traffic through. This can be the cause of the error.

 

How to solve the error?

In Windows Firewall, under Allowed Programs, we ensure WMI is enabled.

Windows Server 2008/2012/2016 Firewall Rules

To check firewall settings, we select Start and search firewall and open Windows Firewall with Advanced Security.

In Server 2012/2016, we can find it at Server Manager > Tools > Windows Firewall with Advanced Security.

Here, in the left-hand pane, we click Inbound Rules. In the right-hand pane, we click Filter by Group and then select WMI.

WMI Error: Login to remote object in Nagios

Then we will see the available firewall rules. We ensure to enable the DCOM-In and WMI-In rules.

If the WMI rule group does not exist, Microsoft suggests the below method.

In the command prompt we enter:

netsh advfirewall firewall add rule dir=in name=”DCOM” program=%systemroot
%\system32\svchost.exe service=rpcss action=allow protocol=TCP localport=135

netsh advfirewall firewall add rule dir=in name =”WMI” program=%systemroot
%\system32\svchost.exe service=winmgmt action = allow protocol=TCP localport=any

netsh advfirewall firewall add rule dir=in name =”UnsecApp” program=%systemroot
%\system32\wbem\unsecapp.exe action=allow

netsh advfirewall firewall add rule dir=out name =”WMI_OUT” program=%systemroot
%\system32\svchost.exe service=winmgmt action=allow protocol=TCP localport=any

Windows Server 2003 Firewall Rules

By default, DCOM communicates with the client on a random port, so in order to write firewall rules, we can specify a port range.

  1. To do so, we click Start, choose Run, type DCOMCnfg.exe, and click OK.
  2. Then we expand Component Services > Computers > right-click My Computer > Properties.
  3. In the Default Protocols tab > Properties > Add.
  4. We add a port range for COM services. For example, a range from 5000-5020.
  5. Once done, we click OK.

Eventually, we allow the port range through the windows firewall.

  1. The below command will open ports from 5000-5020 to match the COM Internet Services Range.
  2. FOR /L %I IN (5000,1,5020) DO netsh firewall add portopening TCP %I “COM”%I
  3. Lastly, we open DCOM port 135.
  4. Then in the command prompt, we type:
    netsh firewall add portopening TCP 135 “DCOM”

[Need help with the procedures? We’d be happy to assist]

 

Conclusion

In short, we saw how our Support Techs fix the WMI error for our customers.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Reviews