Monday, January 16, 2012

Solution of “Networking is not installed or is not properly configured” have been show in “Computer name” tab

When you receive the message “Networking is not installed or is not properly configured” in the “Computer name" tab and also, cannot access network resource. (E.g. share printer and network drive)

image

When you check the service of the computer, you will find the “Workstation” service cannot be start.

When you check the error in the event viewer, you will find

DCOM error - Event ID: 10010
Description:
The server {9B1F122C-2982-4E91-AA8B-E071D54F2A4D} did not register with DCOM within the required timeout

Solution:

There are three solution, I fix the problem by using the solution 3. (I run the solution 1 and 2 before I run the solution 3)

1. fix the problem by removing and re-installing the machine's Client for Microsoft Networks, as follows:

  • From the Control Panel, open Network Connections.
  • Right-click on my active Local Area Network connection and choose Properties.
  • In the Local Area Connection Properties dialog, select Client for Microsoft Networks, then click Uninstall. Close the dialog and reboot when prompted.
  • After rebooting, bring up the Local Area Connection Properties again.
  • Re-install the Client for Microsoft Networks by clicking the Install button, selecting Client from the Select Network Component Type dialog, then selecting Client for Microsoft Networks from the Select Network Client dialog. Click OK all the way back out, then reboot the machine once more when prompted.


2. sfc /scannow

3. Run the following command
net stop wuauserv
regsvr32 /s wuaueng.dll
regsvr32 /s wuaueng1.dll
regsvr32 /s wucltui.dll
regsvr32 /s wups.dll
regsvr32 /s wups2.dll
regsvr32 /s wuweb.dll
regsvr32 /s jscript.dll
regsvr32 /s atl.dll
regsvr32 /s softpub.dll
regsvr32 /s msxml3.dll
net start wuauserv

Reboot the machine.

Print Friendly and PDF
Share/Bookmark

7 comments:

  1. I used solution #1, which worked perfectly! Thank you very much!

    ReplyDelete
  2. How did this occur anyway to prevent it from happening again?

    ReplyDelete
    Replies
    1. As I know, restrict the user privilege (e.g. The domain user is the member of local group users only) will be helpful to prevent it from happeneing.

      Delete
  3. THANK YOU! I had tried 1 as well as restarting the server service to no avail. Your full solution did the trick!

    ReplyDelete
  4. Thank You Billy. The issue resolved by Solution #1

    ReplyDelete
  5. The first method worked for me. Thanks

    ReplyDelete