Powershell – how to connect to server in remote domain with winrm

powershellwinrm

I have winrm enabled on a remote server and from a member of that server's domain, I am able to run Powershell commands using PSSession. However, from a client in another domain, I get "Connecting to remote server … failed with the following error message : The connection to the specified remote host was refused.
+ CategoryInfo : OpenError: (server FQDN:String) [], PSRemotingTransportException"

I did put the remote server into my client's TrustedHosts list. Here's an example command:

icm -comp ServerFQDN {dir} -cred domainShortName\MyUserID

Can anyone tell me what I need to do to make this work?

Best Answer

The client in another domain must management rights. Check this link: Configure Windows Remote Powershell Access

You may also to try to enable PSRemoting, if not enabled.

Enable-PSRemoting -Force

Take a look at this link: Enable Powershell Remoting and WinRM

Related Solutions

Powershell Remote Execution Error on EC2

The server and client do not need to be in the same domain, however, the error message you are getting seems to me to indicate not an authentication error, just a basic networking error. Are there firewalls between you and the WinRM server that may be preventing this communication? Can you telnet to port 5985 on the WinRM server? 5985 is the HTTP port that WinRM uses in 2008 R2.

edit: Also note that you're going to need to add the WinRM server to the TrustedHosts list on your client, but I don't think you've gotten to that point yet.

WinRM Failures – How to Fix Remote PowerShell Issues on Windows Server 2012 R2

Finally solved it, helped by the evidence I recently added to the question:

netsh http show iplist

IP addresses present in the IP listen list:
-------------------------------------------

127.0.0.1

On systems where this was working, that list was empty. This seemed rather counter-intuitive to me at first. Nevertheless, I gave this a go:

> netsh http delete iplisten ipaddress=127.0.0.1

Immediately after, I notice this output from netstat:

>netstat -anp tcp

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:3389           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:5985           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:47001          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49152          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49153          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49154          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49155          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49175          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49179          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49190          0.0.0.0:0              LISTENING
  TCP    10.115.63.107:139      0.0.0.0:0              LISTENING
  TCP    10.115.63.107:3389     10.115.13.25:64873     ESTABLISHED
  TCP    10.115.63.107:49235    192.168.40.146:445     ESTABLISHED
  TCP    10.115.63.107:49291    192.168.40.45:8014     ESTABLISHED
  TCP    169.254.34.30:139      0.0.0.0:0              LISTENING

And indeed, WinRM works like it should.

I surmise, via testing, that if no HTTP listener is configured, then all HTTP listeners will bind to the default entity: 0.0.0.0. Because a loopback address was configured as a listener address, the listener was binding to this address instead.

At some point, I must have taken some action that caused this configuration, though I'm not sure how. At any rate, it's working fine now. Thanks all.

Best Answer

Related Solutions

Powershell Remote Execution Error on EC2

WinRM Failures – How to Fix Remote PowerShell Issues on Windows Server 2012 R2

Related Topic