Solved

Restore WMI to Default State and Port Range

Posted on 2014-01-29
2
2,165 Views
Last Modified: 2014-01-31
I followed these steps to force WMI to use one port. Now I would like to reset it back to use dynamic port allocation. Anybody know how I would do this?

This is what I did:

At the command prompt:
1. Type winmgmt -standalonehost
2. Stop the WMI service by typing the command net stop "Windows Management Instrumentation"
3. Restart the WMI service again in a new service host by typing net start "Windows Management Instrumentation"
4. Establish a new port number for the WMI service by typing netsh firewall add portopening TCP 24158 WMIFixedPort.

How do I change to use WMIDynamicPort if that exists...?
0
Comment
Question by:rawinnlnx9
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 8

Accepted Solution

by:
Ratnesh Mishra earned 500 total points
ID: 39819546
You can follow the following article from microsoft http://support.microsoft.com/kb/217351  in order to reset WMI configuration .


1. If you do not want to configure DCOM to use a range of ports, delete the registry key, and then restart your computer.
2. If you want to configure DCOM on your computer to use a range of ports, use the
HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\Internet
registry key to configure the range of ports, and follow the instructions in the following white paper:
Using Distributed COM with Firewalls
http://msdn.microsoft.com/en-us/library/ms809327.aspx

Additional Information :-
You can also follow this :

WMI runs as part of a shared service host with ports assigned through DCOM by default.
As you mentioned you followed microsoft article  http://msdn.microsoft.com/en-us/library/bb219447(v=vs.85).aspx

However based on the article http://support.microsoft.com/kb/832017 which states that
WMI ports are
In Windows Server 2008 and later versions, and in Windows Vista and later versions, the default dynamic port range changed to the following range:
Start port: 49152
End port: 65535

Windows 2000, Windows XP and Windows Server 2003 use a dynamic port range of
Start port: 1025
End port: 5000

So in order to reset you can use the Component Services Manager [comexp.msc]to set the range that the random port is allocated from to something small and then manually open each one.

Step 1 : Goto Run Command , and Type "comexp.msc" without quote.
Step 2 : Expand "Component Services" , expand "Computers" and then right click on "My Computer" and select Properties.
Step 3 : Click on the "Default Protocol" tab . and then under DCOM Protocols double click on the entry “Connection oriented TCP/IP”.
Step 4 : Use the Add button to add a suitable range of ports(as mentioned in the above said article)  and click OK. After this all COM+/DCOM services will select a port in this range of course after reboot.

Note ::
To open the ports , open the Windows Firewall, and add one entry for each port in the range mentioned and one for port 135
Random ports only need to be open on the remote machine.


Step 5: Reboot the machine.
0
 
LVL 9

Author Closing Comment

by:rawinnlnx9
ID: 39824662
Outstanding. I'd say more but how many ways can you say outstanding?
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

What to do when Windows Update is not working correctly? What tools can I use to detect the cause of the malfunction problem? What does this numeric error code mean? These and other questions that you have been asking in the past are answered here (…
Resolve DNS query failed errors for Exchange
In this Micro Tutorial viewers will learn how they can get their files copied out from their unbootable system without need to use recovery services. As an example non-bootable Windows 2012R2 installation is used which has boot problems.
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…

623 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question