Ошибка unable to connect to the remote server

Unable to connect to the server by using windows powershell remoting

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Asked by:

Question

We are trying to install RDS on one of the server OS 2016. But facing below error

Unable to connect to the server by using Windows Powershell Remoting

— We are installing all RDS Role on the same server, there is no remote server involve in it.

— We ran below command but no luck.

— Disable windows firewall

— Further we tried to install the RDS from DC but when we tried to add the server **3 in server manager group it shows below error.

Error **3 : Configuration refresh failed with the following error: The metadata failed to be retrieved from the server, due to the following error: The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: «winrm quickconfig». 7/19/2017 5:03:36 AM

— We provide local admin rights to user «helpdesk» but no result.

Источник

RDS: Unable to connect to the server by using Windows Powershell Remoting

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

» data-medium-file=»https://rlevchenko.files.wordpress.com/2015/05/rds_compatibility_error.jpg?w=300″ data-large-file=»https://rlevchenko.files.wordpress.com/2015/05/rds_compatibility_error.jpg?w=768″ src=»https://rlevchenko.files.wordpress.com/2015/05/rds_compatibility_error.jpg?w=544&h=383″ alt=»rds compatibility error» width=»544″ height=»383″/>

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

Like this:

12 thoughts on “RDS: Unable to connect to the server by using Windows Powershell Remoting”

This worked for me, I also uninstalled a network adapter that was no longer in use which may have been causing the issue.

Nice to hear that! Thanks for your feedback.

Источник

Unable to connect to the server by using windows powershell remoting

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Asked by:

General discussion

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).

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.

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

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.

Источник

Unable to connect to the server by using windows powershell remoting

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

Trying to install RDS on 2012 I get the following error.

«Unable to connect to the server by using Windows Powershell Remoting» On the «Checking Compatibility» window. I’m just trying to install the «Quick Start: option

enabled «allow remote server management through WinRM» in group policy also, still same problem.

Thanks ahead of time.

Answers

I would like to know how did you install the role, by Windows Powershell remoting or use Server manager to manage remote Server?

After enable both server’s psremoting, please restart them and try again.

TechNet Community Support

I would like to know how did you install the role, by Windows Powershell remoting or use Server manager to manage remote Server?

After enable both server’s psremoting, please restart them and try again.

TechNet Community Support

Hey there, did you ever get an answer to this?

I am having the same issue.

psremoting IS already enabled on this server.

I am using server manager to install roles.

Add Roles and Features Wizard > Remote Desktop Services Installation > Quick Start > Session-based desktop deployment, Select my server > click next > «Unable to connect to the server by using windows powershell remoting»

Andrew Huddleston | Hillsong Church | Sydney

After working for weeks with M$ Support level 2 and higher on this issue below is the fix and reason for the issue.

Set-Item WSMan:localhostShellMaxMemoryPerShellMB 1000

I added the ‘Windows Remote Management’ rule to my firewall and that fixed the problem.

Although I disabled the FW, allowed WinRM and Remote Powershell, I used two different NT accounts: one from a trusted forest and a 3nd one from the same forest as the server, gpupdate the policy to allow Remote Management, Set-Item WSMan:localhostShellMaxMemoryPerShellMB I was trying to configure with RDS I still got the:

«Unable to connect to the server by using Windows Powershell Remoting» On the «Checking Compatibility»

It is a little bit silly that for «Server Manager» the elevation is not proposed even.

Still not working for me

tried services and PS enable and PS expand Shell size. nothing

had same issue fixed it by
clearing the proxy

netsh winhttp reset proxy

None of this worked for me 🙁

I’m Trying in W Azure Scenario with 1subnet.

I had the same issue, none of the above worked for me.

I decided to see what my FQDN was resolving to and it was using the IPV6 address FE80 etc, I disabled IPV6 and retried and it worked for me.

Reference following article,

In case you’re using a Hyper-V based scenario: for me it helped to disable «Integration Services > Time Synchronization» within the Hyper-V settings for the virtual machine I tried to deploy remote desktop services on.

Here’s what I’ve found. Adding RDS with the «Quick Start» option, followed at some point later removing RDS, seemed to give me the «Unable to connect to the server by using Windows Powershell Remoting».

I did the powershell fix. «Set-Item WSMan:localhostShellMaxMemoryPerShellMB 1000″, reboot and retry didn’t do it for me.

Also the Server Manager SHIFT runas Administrator (not sure how it’s even possible NOT to run as Administrator really?) didn’t do it for me.

I had my firewall turned off, so no issues there. I did reset it and turn it off again. Still nothing.

Re-adding back IIS along with RPC for HTTP Proxy, rebooted. Was able to add the RDS and Quick Start role again.

Not 100% sure how that’s the case. But I removed them. Got the same error. Readded them (rebooting between add and removal) it worked again.

Hope this saves someone some frustration.

I tried all the above but did not succeed. But after I had changed my network from public to domain network it worked.

I have a separate domain controller server in my network and also a NAT/Firewall. This NAT/Firewall is setup as DHCP server so I have set my DNS towards this server. 10.0.0.1 As a secondary server I have set my Domain controller’s IP 10.0.0.10 and now the network changed to Domain-Network and I am able to install RDP services.

Hope this helps you guys.

The link from Anonymous2992 helped me to this solution. Thanks!

This silly error wasted my 1 precious day

In my case i restarted the DC and RDS server to resolve this issue.

Hope this may help someone.

had same issue fixed it by
clearing the proxy

netsh winhttp reset proxy

Ur solution worked in my case.

Using server 2012 with exchange 2010 so something has gone awry with permissions. Domain admin can’t seem to do anything so added another admin account (with local admin rights) then running the RDS Deployment from an elevated Server Manager session did the trick for me.

Hope this helps someone!

Have tried all the above and none have worked for me on Windows 2012 R2 RDS.

On Windows 2012 RDS servers it works fine without any problem

Have you managed to resolve the issue yet?

All the solutions mentioned before didn’t solve our problems. Finnaly we decided to uninstall Powershell completely from our newly installed RDS Server. the site affect of this is that the GUI also will be unistalled. After te uninstall of powershell we rebooted the server. Via our DC’s Server Manager we installed Powershell remotely again along with the GUI and this solved our problem. Because the other newly installed servers didn’t have this problem I guess that this problem is introduced after installing a feature (my guess is the Desktop Experience Feature, but i’m not sure and will test this later this week).

Removing SPN HTTP/myserver.mydomain.org from service account for sharepoint solved my problem.

i found another possible reason, this solution worked for me:

I tried to set up powershell remoting on a server and kept getting this error:

After a bit of troubleshooting I discovered that the problem was that the authentication packets was to big (over 16k), this will cause WinRM to reject the request. The reason for authentication packets getting too big can be because the user is member of very many security groups or in my case because of the SidHistory attribute.

The solution was to increase the MaxFieldLength and MaxRequestBytes keys in the registry under HKEY_LOCAL_MACHINESYSTEMCurrentControlSetservicesHTTPParameters

If the keys does not exists you can create them, be sure to use the DWORD type.

I sat MaxFieldLength to DEC value 40000 and MaxRequestBytes to DEC value 32768 and rebooted the server. Problem solved.

Same problem, but what worked for me was deleting stored credentials for the RDVH via cmdkey.

Same here, tried everything else. Turning IPv6 off finally worked.

Despite the error text I was able to connect fine using Enter-PSSession [servername] from a remote host. What FINALLY fixed it for me, was pulling the server out of it’s OU, putting it in the default «Computers» OU so almost no GPOs would apply to it, did a gpupdate /force, rebooted, and I was able to run the install without issue, so there’s something wonky with one of my GP settings that breaks the RDS install.

your solution worked for me!

I realize this is old, but I’d like to add my solution since I came across this just as frustrated as many others.

Very simply, disabling IPv6 resolved the problem for me as well.

I did the Set-Item WSMan:localhostShellMaxMemoryPerShellMB 1000.

But now i cant logon the server annymore.

Tami Jones solution worked for me Windows server 2012 Datacenter Edition in Windows Azure:

— by clicking server manager.. local server and enabling «remote management»

Finally, disable IPv6 work for me.

This resolves the issue on my Windows Azure Server

Nandha Kumar J Techincal Consultant Chennai, India

Disabling IPV6 via the hotfix found here: https://support.microsoft.com/en-us/kb/929852

^ that resolved my issue.

Windows Server 2012 R2 Standard on VMWare 5.1

Because we were not using IPv6 we did not add an IPv6 Filter so it simply blocked everything on that protocol. It, of course, was working for everything else because we were using IPv4.

Hi, in my case the problem was that our DC is based on Samba 3.

Upgrading to Samba latest version this error does not come up.

Tried everything else on this page but none worked except this.

Because we were not using IPv6 we did not add an IPv6 Filter so it simply blocked everything on that protocol. It, of course, was working for everything else because we were using IPv4.

If there is a GPO setting on the network that affects the server you are trying to install RDS on and that GPO controls WinRM listening ports and is incorrectly configured then you will get this error.

Run winrm enumerate winrm/config/listener on the target server and if ListeningOn = null is returned then check GPO on this box with gpresult /h result.html & result.html. Search this GPO output for Windows Components/Windows Remote Management (WinRM)/WinRM Service and IPv4 Filter and IPv6 Filter need to contain * or an IP range that includes this server. If the value is blank or wrong IP range then you will get the original posters error message!

This took a long time to find and fix!

Brian Reid C7 Solutions Ltd (www.c7solutions.com)

It’s always the simplest thing :/

Disabling IPv6 on ALL network adapters worked for me.

im wonderering how you did youre hyperv scenario because when i try evrything in hyper v then i get an error

hardware virtualization is not suported.

In Server Manager/Remote Management was already enabled. My fix was to disable and then re-enable Remote Management. I was then able to reinstall RDS.

Tami Jones solution worked for me Windows server 2012 Datacenter Edition in Windows Azure:

— by clicking server manager.. local server and enabling «remote management»

All the Gibber Jabber and Speculations in this Thread and your Resolution was the Correct One.

Just thought you should know that.

I tried all of the suggestions above with no success. I was trying to use New-RDSessionDeployment against a remote Server 2012 R2 instance, from a Win10 or Win8 client. The exact error I got was:

I finally used a test Server 2012 R2 instance as my client and it succeeded. Evidently the New-RDSessionDeployment cmdlet invokes the module WindowsSystem32WindowsPowerShellv1.0ModulesRemoteDesktopDeployment.psm1 behind the scenes, which initiates a New-PSSession, but somehow it is incompatible with at least Win8 and Win10 clients.

Turning IPV6 Off on the NIC worked for me:

that worked for me partially.

the other way I did, is too add localhost, and 127.0.0.1, and FQDN of the server to Internet explorer proxy bypass list

then: netsh winhttp import proxy source=ie

and wizard accepted that.

had same issue fixed it by
clearing the proxy

netsh winhttp reset proxy

Thanks you Very Much this resolved my problem. wow.

I just had this same issue. I couldn’t understand why it was giving me this error as it was being installed onto the local host.

When I ran new-pssession from powershell it told me there was a time difference between the client (rds server) and the server (dc).

Corrected the time and it worked!

Thank you so much for this answer. I have wasted 2 days trying to find a solution, this worked perfectly.

I had this problem too. The solution for me was to update the DNS servers. On this particular machine they were set to public DNS servers. Once I updated them to use the Active Directory domain DNS servers, the wizard finished without this error.

Having the same issue on Server 2016 and worked through each of the ideas in this thread. The item that has this working now on my server was a change to Policy to allow through Win RM. Note that I did implement most of the suggestions here in this thread before getting to the below fix. Firewall turned off, IPv6 disabled, memory settings.

On my server the IPv4Filter contained subnets that the Server was not in at that time.

We Did not found below.

Same error in Windows 2016 for me, in my case it seems to be a hostname problem at some point:

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.

THANKS. @Tami Jones you saved my day.

In my case I had to disable remote management and then re-enable it.

Thanks MS for keeping all of us employed with these silly bugs

had same issue fixed it by
clearing the proxy

netsh winhttp reset proxy

I’m quite stuck here, and hopefully you can come up with some nice ideas on this matter. I’ve got a VM deployed in MS Azure (Type: D2_V2) and I’d like to deploy Remote Desktop Services onto it.

When I try to run the deployment from the server manager, it gives the well known » Unable to connect to the server by using Windows Powershell Remoting» after selecting the connection broker server.

I’ve set up literally everything as it was mentioned in this thread (actually this thread helped a lot in my previous attempt on RDS and it worked, although that server was not in Azure but our company on-prem DC.)

The funniest thing is, that I am able to connect to the server with PS Remoting from my laptop, and running the PS command for » New-SessionDeployment. » gives the same error as doing it from the server manager..

Do you have any idea why this can happen? For me it seems PS remoting is obviously working on the server and this is driving me crazy.

Источник