Trying to remotely manage the computer that runs Windows XP Service Pack 2 when you receive an error message "Access Denied" or "The Network Path Was Not Found" (no network path)
Article ID: 840634 Last Update Date: November 3, 2004 Version: 5.1
This page
Symptom Cause Solution More Information
symptom
When you try to remotely manage the computer that is running Microsoft Windows XP Service Pack 2 (SP2), you may receive an error message similar to one of the following error messages:
Computer //
Computername.example.com Cannot Be Managed.The Network Path Was Not Found.
CHOOSE 'Connect To Another Computer' from The Action Menu To Manage A DiffERENT COMPUTER.
Unable to access the computer
Computername.
The Error WAS: Access is Denied.
Unable to access the computer
Computername.
The Error Was: The NetWork Path Was Not Found.
Failed to Open Group Policy Object On
Computername.you Might Not Have Appropriate Rights.
Details: The NetWork Path Was Not Found.
An Object (Computer) with the folowing name cannot be found: "
ComputerName ".check the selected object type and location for accounting and ensure That You Have Typed The Object Name Correctly, Or Remove this Object from the selection.
System Error 53 Has Occurred.The Network Path Was Not Found.
the reason
This problem may occur if you try to manage a remote computer using a Microsoft Management Console (MMC) tool.
• Certificate • Computer Management • Device Manager • Disk Management • Event Viewer • Group Policy • Index Services • Internet Protocol Security (IPSec) Monitor • IP Security Policy • Local User and Group • Removable Storage Management • Results Set • Services • Shared folders • WMI controls Also, this issue may occur if you try to use Net.exe tools to manage remote computers, or try to access remote computers from the following dialog:
• Select users, computers, or groups • Finding users, contacts, and groups • Net.exe This problem occurs because of the default configuration of Windows Firewall programs in Windows XP SP2 prevents incoming in Transmission Control Protocol (TCP) port 445. Telecommunication. The management tools listed here are to connect to a remote computer, which must allow incoming network communication on TCP port 445.
solution
To resolve this issue, use one of the following methods.
Method 1 and Method 2 describe how to solve this problem on each computer. Method 3 describes how to use group policies to resolve this issue on multiple computers.
Method 1: Use the Netsh command line tool to run on a remote computer based on Windows XP SP2
Netsh command to allow communication on TCP port 445 to pass Windows firewall:
1. Click Start, "Run" in turn, type CMD in the Open box, and then click OK. 2. Type the command below, press Enter: Netsh FireWall Set Portopening TCP 445 SMB Enable
You will receive the following message:
OK.
3. Exit the command prompt. To implement this change across the organization, please run this from the batch file or script.
Netsh command line.
Method 2: Modify the Windows Firewall using the graphical user interface to modify the Windows Firewall on a Windows XP SP2 remote computer to allow incoming TCP communication on port 445:
1. Click Start, and then click Control Panel. 2. Click Security Center, and then click Windows Firewall. 3. Click Exceptions tab, click to select the File and Printer Sharing check box, and then click Edit. 4. Click to select the TCP 445 check box, click "Change Scope", then take one of the following:
• Click "Only My Network (Subnet)". • Click Custom List and type the IP address you want to manage this computer. 5. Click "OK" four times.
Method 3: Use Group Policy Settings "Allow Remote Management Exception" policy
Note: These steps assume that all computers you want to manage in this policy are located in the same organization. For additional information on how to use Group Policy, visit the following Microsoft Web site:
http://www.microsoft.com/china/windowsserver2003/technologies/Management/grouppolicy/default.mspx
These steps assume that the Windows firewall is configured to use domain profiles. Domain profiles are most typical. For additional information about how Windows firewall configuration files and how Windows selects the configuration files you want to load, see
Deploying Windows Firewall Settings for Microsoft Windows XP with Service Pack 2 Deploys a Windows Firewall Settings for Microsoft Windows XP Service Pack 2. To get this guide, please visit the Microsoft Web site below:
Http://www.microsoft.com/downloads/details.aspx?familyid=4454e0e1-61fa-447a-bdcd-499f73a637d1&displayLANG=EN
To configure the Group Policy to allow remote management of your computer, follow these steps.
1. Create a group policy object for an organizational unit that contains Windows XP SP2-based computers to be managed:
a. Log in to the domain controller. b. Click Start, click "Run", type DSA.MSC in the Open box, and then click OK. c. Expand the domain, right-click the organizational unit you want to create, and then click Properties. d. Click the Group Policy tab, and then click New. e. Type a name for the Group Policy object and press Enter. f. Click Close. 2. Log in to a domain member computer running Windows XP SP2 with the following one or more security group members:
• Domain admins • Enterprise Admins • Group Policy Creator Owners3. Click Start, "Run", type the MMC in the Open box, and then click OK. 4. On the File menu, click Add / Delete Administration Unit. 5. On the Independence tab, click Add. 6. In the Add Independent Management Unit dialog box, click Group Policy, and then click Add. 7. In the Select Group Policy Object dialog box, click Browse. 8. Click the Group Policy object you want to use to use the new Windows firewall. For example, click the organizational unit that contains Windows XP SP2, click OK, and then click the Group Policy object created in step 1. 9. Click OK, and then click Finish. 10. Click Close, then click OK. 11. Under "Control Taound Nod", expand your group policy object you selected in step 8, then expand "Computer Configuration", "Management Template", "Network", "Network Connections", "Windows Firewall" , Then click Domain Profile. 12. In the right pane, double click on "Windows Firewall: Allow Remote Management Exceptions". 13. Click Enable, and then specify the management range in "Allows the Untunction Message" box from the following locations. For example, to allow remote management from a particular IP address, type the IP address in "Allowable Incoming Message" boxes from the following location. To allow remote management from a specific subnet, type the subnet using the Uncipline Internet Domain Routing (CIDR) format. In this scenario, type 192.168.1.0/24 to specify network 192.168.1.0 with 24-bit subnet mask 255.255.255.0. For additional information about how to specify effective management, see the "Syntax" area of the Settings tab in this policy. 14. Click OK, and then click Exit on the File menu. More information
The Client Management Tool is a Group of Microsoft Management Console (MMC) management units for managing users, computers, services, and other system components on local and remote computers.
The information in this article applies to:
• Microsoft Windows XP Service Pack 2
