You have setup new Server 2012 core computer and you wish to perform remote management of the server through COM+ Network Access. When you open a console such as Computer Management you receive the following error message:
Computer "SERVERNAME" cannot be connected. Verify that the network path is correct, the computer is available on the network, and that the appropriate Windows Firewall rules are enabled on the target computer.
To enable the appropriate Windows Firewall rules on the remote computer, open the Windows Firewall with Advanced Security snap-in and enable the following inbound rules.
COM+ Network Access (DCOM-In)
All rules in the Remote Event Log management group.
You can also enable these rules by using Group Policy settings for Windows Firewall and Advanced Security. For servers that are running the Server Core installation option, run the Netsh AdvFirewall command, or the Windows PowerShell NetSecurity module.
Because COM+ Network Access is not allowed you cannot use the Windows Firewall and Advanced Security MMC Snapin to remotely connect to the server. As a result you need to login to the Server 2012 core machine and run the following command from command prompt to enable remote access.
netsh advfirewall set currentprofile settings remotemanagement enable
Now you can remotely connect to the Server 2012 core machine using MMC snapins.
This article might also be of reference - Remote Disk Management of a Server 2012 core machine:
http://clintboessen.blogspot.com.au/2013/06/remote-disk-management-to-server-2012.html
Computer "SERVERNAME" cannot be connected. Verify that the network path is correct, the computer is available on the network, and that the appropriate Windows Firewall rules are enabled on the target computer.
To enable the appropriate Windows Firewall rules on the remote computer, open the Windows Firewall with Advanced Security snap-in and enable the following inbound rules.
COM+ Network Access (DCOM-In)
All rules in the Remote Event Log management group.
You can also enable these rules by using Group Policy settings for Windows Firewall and Advanced Security. For servers that are running the Server Core installation option, run the Netsh AdvFirewall command, or the Windows PowerShell NetSecurity module.
Because COM+ Network Access is not allowed you cannot use the Windows Firewall and Advanced Security MMC Snapin to remotely connect to the server. As a result you need to login to the Server 2012 core machine and run the following command from command prompt to enable remote access.
netsh advfirewall set currentprofile settings remotemanagement enable
Now you can remotely connect to the Server 2012 core machine using MMC snapins.
This article might also be of reference - Remote Disk Management of a Server 2012 core machine:
http://clintboessen.blogspot.com.au/2013/06/remote-disk-management-to-server-2012.html
You should enable COM+ Network Access when one or more of the COM+ applications on the server are called from clients or applications that reside on different computers.
ReplyDeleteIf your product collects COM+ performance data by remotely calling an object that tracks performance, you must enable COM+ Network Access.
IT Managed Services Cleveland
Deletekey windows 7 professional , office 2013 key sale , windows 10 activation 0xc004f034 , windows 8.1 pro key buy , genuine windows anytime upgrade key for windows 7 starter to ultimate , windows 10 product key cloud , windows 10 education serial key , project professional 2010 key , lF2cnP
buy office 2016 product key
windows server 2012 r2 free
rosetta stone french key sale
windows 10 product serial number offer
hmm.. this is very interesting! I'm not so familiar on this COM thinggy, thanks much for sharing this info. :) Firewall Security Consulting NY
ReplyDeleteA very helpful post on remote network access. Those who are engaged in such are surely fateful. Thanks for posting.
ReplyDelete