Getting wmic login to remote object error? Here's what you can do [fix]

Nearly all of us are familiar with Wmic, a command line and scripting interface that simplifies the use of Windows Management Instrumentation (WMI) and systems managed through WMI.

However, keep in mind that Microsoft manufacturers recently reported that they will no longer develop WMIC command line functionality.

So, starting now, this feature will be removed from Windows 10, Windows 11, and Windows Server editions, in case you were wondering.

That being said, you can add this feature back to your PC as an optional feature, or access it via PowerShell.

Many users reported receiving the Login to Remote Object error, which usually pops up when we run the WMI Configuration Wizard.

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

We will show you what to do if you encounter this situation to avoid any problems.

How to fix wmic login to remote object error?

Before we explore how to solve this problem, we must also understand its roots. Windows Firewall may not allow any traffic through, hence the error.

First we have to make sure that in Windows Firewall, under Allowed Programs, WMI is actually enabled.

How to fix errors on Windows Server 2008, 2012 and 2016?

1. Press the Windows key, search for Command Prompt and click Open.
2. Type wf.msc to turn on Windows Firewall with Advanced Security.
3. Click Inbound Rules on the left panel.
4. Click Filter by Group on the right panel.
5. Find WMI and click on it.
6. Find DCOM-In and WMI-In rules.
7. Right click on them and select Enable Rules.

However, if the WMI rule group does not even exist, Microsoft recommends a method that we are going to describe for you now.

Open a command prompt and enter the following command:

netsh advfirewall firewall add rule dir=in name=”DCOM” program=%systemroot%\system32\svchost.exe service=rpcss action=allow protocol=TCP localport=135netsh advfirewall firewall add rule dir=in name =”WMI” program=%systemroot%\system32\svchost.exe service=winmgmt action = allow protocol=TCP localport=anynetsh advfirewall firewall add rule dir=in name =”UnsecApp” program=%systemroot%\system32\wbem\unsecapp.exe action=allownetsh advfirewall firewall add rule dir=out name =”WMI_OUT” program=%systemroot%\system32\svchost.exe service=winmgmt action=allow protocol=TCP localport=any

How do I resolve this issue for Windows Server 2003?

1. Press the Windows key R and type DCOMCnfg.exe, then click OK.
2. Click to expand Component Services, and then click Computers.
3. Right clickClick on My Computer and select Properties.
4. In the Default Protocols tab, double-click Connection Oriented TCP/IP.
5. Press the Add button.
6. Enter the 5000-5020 port range for the COM service and press OK.

Now, use the following command to allow the port range through Windows Firewall, this will open ports 5000-5020 to match the COM Internet service range.

FOR /L %I IN (5000,1,5020) DO netsh firewall add portopening TCP %I “COM”%I

Finally, open DCOM port 135 and type the following command in the command prompt:

netsh firewall add portopening TCP 135 “DCOM”

In order to solve your problem, this is pretty much all you have to do. However, this is not the only wmic error that keeps users up at night.

People have also been reporting wmic access denied and wmic alias not found errors. If you need help, we can help you with both situations.

The above is the detailed content of Getting wmic login to remote object error? Here's what you can do [fix]. For more information, please follow other related articles on the PHP Chinese website!