Unable to connect to the server by using windows powershell remoting

RRS feed

  • Remove From My Forums

  • Question

All replies

  • For troubleshooting purpose, try Turning Off the Windows Firewall  both in the source and destination then test again. I had very similar issue and i got it resolved, turns out there are more services that needs to be allowed on the firewall to make
    it work.

    • Edited by

      Thursday, July 20, 2017 8:35 AM
      modify

  • Hi Geraldine,

    I did that , turn of the firewall but no luck.

    Thanks, Sajjan T

  • Hi,

    Please navigate to Server Manager -> Local Server, ensure that Remote management is enabled.

    If the issue persists, try to ping RDS servers via FQDN/NetBIOS, if IPv6 address returns, please disable IPv6 to see whether it works.

    In addition, similar issues were resolved by remove proxy server for some forum community members via command
    netsh winhttp reset proxy.

    Best Regards,

    Amy

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact
    tnmff@microsoft.com.

    • Proposed as answer by
      Masoun Brayez
      Monday, July 22, 2019 11:54 AM

  • it work, your answer most help full.

  • Hi,

    Kindly let me what you exactly did to fix the above issue.

    Thanks.

    Thanks, Sajjan T

  • Same error here, but I «fixed» it this way:

    I reinstalled Windows 2016 and only configured a vmxnet 3 interface by installing VMWare Tools and giving it an IPv4 address, nothing else. Rebooted. The RDS installation wizard passes the compatibility check. I didn’t install the RDS services and just renamed
    the host to what I want it to be. Restarted. The RDS installation wizard does NOT pass compatibility check anymore: «Unable to connect to the server by using Windows Powershell Remoting». Seems to be a problem there.

    I couldn’t find at which point the system uses the wrong hostname, maybe only server manager does.

    EDIT:

    In my case the problem is not the hostname, it’s the custom «Primary DNS suffix of this computer» I edited in Control Panel/System/Computer name, domain, and workgroup settings. I left the suffix blank, now it works even with the custom hostname.

    • Edited by
      kj765H-u
      Friday, February 23, 2018 2:16 PM

  • Hi,

    I had the same problem. After a lot of search in the internet, try and error I found the solution (for me):

    Just disable IPv6 and everything works well…!

    Hope this will help someone else. :)

    Alex

    • Proposed as answer by
      slacknerd
      Sunday, June 2, 2019 2:58 PM

  • EDIT:

    In my case the problem is not the hostname, it’s the custom «Primary DNS suffix of this computer» I edited in Control Panel/System/Computer name, domain, and workgroup settings. I left the suffix blank, now it works even with the custom hostname.

    Yep, this worked for me, thanks

  • run gpedit.msc

    go to Local Computer Policy > Administrative Template > Windows Components > Windows Remote Shell

    In Settings change «Allow Remote Shell Access» as Enabled and viola

Источник

Skip to content

Scenario

You are trying install RDS 2012 R2 (no matter quick or standard mode) and get error during compatibility check:

Unable to connect to the server by using Windows PowerShell remoting.

rds compatibility error

  • Server is joined to domain
  • Server is running on 2012 R2 up-to-date
  • Current user is a member of  group “Administrators”  (lusrmgr.msc  -> groups)
  • PowerShell is configured to receive remote queries (Enable-PSRemoting)
  • Remote Desktop Services are not forbidden in GPOs (default policies)
  • Remote management is enabled in Server Manager (servermanager -> local server -> remote management)
  • Firewall rules for remote management are enabled (Get-NetFirewallRule *winmgmt*|select name,enabled)
  • There are no network and time synchronization issues between this server and my environment

Solution

If you ping server you may notice IPv6 name format (in my case). Windows Server management consoles don’t like it in my case (any thoughts/comments?). So turn off IPv6 (if you are not using it) on your network adapter. I think unchecked “register this connection in the DNS”, ipconfig /flushdns work too. But did no try.

I had a lot of VDI deployments but faced with this problem for the first time.

Note:  same issue was with Active Directory mmc. There was the wrong status of Domain Controller in “change domain controller..” (was Offline). Turning IPv6 ON resolved this behavior. Agruments against disabling IPv6

Источник

When you try to install RDS role on server 2012 R2 using standard deployment, this issue may occur (Figure 1).

“Unable to connect to the server by using Windows PowerShell remoting”.


Figure 1: Unable to connect to the server by using Windows PowerShell remoting

First of all, we need to verify the configurations as it suggested:

1. The server must be available by using Windows PowerShell remotely.

2. The server must be joined to a domain.

3. The server must be running at least Windows Server 2012 R2.

4. The currently logged on user must be a member of the local Administrators group on the server.

5. Remote Desktop Services connections must be enabled by using Group Policy.

In addition, we need to check if the “Windows Remote Management “service is running and related firewall exceptions have been created for WinRM listener.

To enabling PowerShell remoting, we can run this PowerShell command as administrator (Figure 2).

Enable-PSRemoting -Force

Figure 2: Enable PowerShell Remoting

However, if issue persists, we need to check whether it has enough memory to work.

By default, remote shell allots only 150 MB of memory. If we have IIS or SharePoint App pool, 150 MB of memory is not sufficient to perform the remoting task. Therefore, we need to increase
the memory via the PowerShell command below:

Set-Item WSMan:\localhost\Shell\MaxMemoryPerShellMB 1000

Then, you need to restart the server and the issue should be resolved.

You can get more information regarding Remote Troubleshooting by below link:

about_Remote_Troubleshooting

If you need further assistance, welcome to post your questions in the

RDS forum.

Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Источник

I’ve tried many online solutions to solve this problem (Unable to connect to the server by using Windows Powershell Remoting), and none of them worked for me.

There is one of the solutions that I did and it was the final solution to my problem (Unable to connect to the server by using Windows Powershell Remoting).

The Solution is:

Synchronizing time on VMware ESXi

Time synchronization becomes necessary in the presence of time discrepancies within the environment. This synchronization can be achieved through manual adjustments or by utilizing a Network Time Protocol (NTP) server to maintain accurate time.

To set the time from vSphere Client:

  • Launch vSphere Client.
  • Go to Configuration > Time Configuration > Properties.
  • Input the correct Time and Date.
  • Click Options.
  • Click Restart on the Service Commands box.
Источник

04
Wednesday
Feb 2015

When you try to install RDS role on server 2012 R2 using standard deployment, this issue may occur (Figure 1).
“Unable to connect to the server by using Windows PowerShell remoting”.

Figure 1

Figure 1: Unable to connect to the server by using Windows PowerShell remoting
First of all, we need to verify the configurations as it suggested:
1. The server must be available by using Windows PowerShell remotely.
2. The server must be joined to a domain.
3. The server must be running at least Windows Server 2012 R2.
4. The currently logged on user must be a member of the local Administrators group on the server.
5. Remote Desktop Services connections must be enabled by using Group Policy.
In addition, we need to check if the “Windows Remote Management “service is running and related firewall exceptions have been created for WinRM listener.
To enabling PowerShell remoting, we can run this PowerShell command as administrator (Figure 2).
Enable-PSRemoting -Force

Figure 2

Figure 2: Enable PowerShell Remoting
However, if issue persists, we need to check whether it has enough memory to work.
By default, remote shell allots only 150 MB of memory. If we have IIS or SharePoint App pool, 150 MB of memory is not sufficient to perform the remoting task. Therefore, we need to increase the memory via the PowerShell command below:
Set-Item WSMan:localhostShellMaxMemoryPerShellMB 1000
Then, you need to restart the server and the issue should be resolved.

Источник

  • Ummy video downloader windows 10 ключом
  • Unassociate file types скачать для windows 10 скачать
  • Ummy video downloader windows 10 скачать торрент
  • Unassoc 1 4 zip скачать для windows 10
  • Ummy video downloader windows 10 крякнутый