I was delivering a quick session on the wonder that is Multi-Server Management for WIndows Server 2012 and I got asked the question – What Ports are required to be open when managing a system remotely.
ARGH… I always forget the port number – as it’s a non-standard port in the 5000 range.
Well – some quick Bing’ing – and I found this great article that lays out ALL the details on remote management capabilities using ServerManager. Lots of details on managing all sorts of systems and methods of managing them remotely.
Scroll down to the bottom and you’ll see the port:
Windows Remote Management (WinRM) listener settings
Server Manager relies on default WinRM listener settings on the remote servers that you want to manage. If the default authentication mechanism or the WinRM listener port number on a remote server has been changed from default settings, Server Manager cannot communicate with the remote server.
The following list shows default WinRM listener settings for managing by using Server Manager.
- The WinRM service is running.
- A WinRM listener is created to accept HTTP requests through port number 5985.
- Port number 5985 is enabled in Windows Firewall settings to allow requests through WinRM.
- Both Kerberos and Negotiate authentication types are enabled.
The default port number is 5985 for WinRM to communicate with a remote computer.
For more information about how to configure WinRM listener settings, at a command prompt, type winrm help config, and then press ENTER.
2 thoughts on “Ports and More for Remote Management of Server 2012”
I think it is RPC Port 135. You will need permissions to the machine to connect though. bye the way good understanding blog to everyone. Really interesting post, Give more details about this post.
Actually you do not need port 135 open for this to work as it is all done via WinRM and powershell.
Comments are closed.