Remote Desktop Connection Disabled for all computers in WHS

[Pavy]

Sponsored Links

I am running Windows Home Server on my computer and I have been trying to get a proper connection over my remote PCs. Right now the Home server is running With Windows Home server 2011. I am switched to it very recently. Today I was checking the remote connections to my Remote PCs one after another. When I log on, I have noticed that all computers status showed up as Connection Disabled. I am quite sure that Remote Connection is activated. Double checked the Windows Firewall and everything is fine there. Can anyone tell me why Remote Computers all Have Connection Disabled?

[Upendra]

It is already known that Windows Home Server disables the connection from the web interface. So there is no way to get it back and you might be really out of luck now. But I have found a way to enable Remote Desktop Connection on Windows Vista computers and for that you will need following things:

• Remote Desktop Connection or Advanced Admin Console
• Registry Editor - Or "regedit.exe"
• Terminal Services Hack - There are two versions: the Vista RTM version and the Vista SP1.
• Notepad

First on the On the Client Computer extract all the files and run them as Admin. Open up firewall and make sure that port 3389 open. Otherwise it is not possible. Reboot the compute
On the Serveruse Remote Desktop Connection or Advanced Admin Console to run the registry editor. Find the following entry:

"HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Home Server\Transport\Clients"

It should have a string called "MachineName"
Now open notepad, on server and add this line:

"HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Home Server\Transport\Clients\{00000000-0000-0000-0000-000000000000}" /v "TerminalServicesSupport" /D "Yes" /f

Change the 0's to the correct string of letters and number as for your Vista computer.
If there are multiple computers make multiple lines indicating computer and save this file as "TermSrv.cmd" in "C:\".

[strongArm]

I also had the same kind of issue with 3 windows XP systems. But I have solved it by following this step:

• First thing you have to ensure that your "Services" has starting "Remote Desktop" automatically.
• The "remote Desktop" must "Enabled" through - "My computer"> "Properties" > "remote" tab.
• Now go back to "My computer>"Properties> Computer Name tab. Go after the "Network ID" wizard and finally reboot the computer.
• If you are using a Wireless router, you have to disable the DHCP and need to assign it a a static IP address outside the DHCP range of ADSL router.

[IkhyThed]

I know how to fix this problem.

• Go to the windows Remote Settings on your comptuer
• Under Remote Desktop , you have to change the setting to "Allow connections from computers running any version of Remote Desktop (less secure)" from already selected "Allow connections only from computers running Remote Desktop with Network Level Authentication (more secure)".
• Click Apply and then select the Advanced tab.
• In that you have to Uncheck the box that says "Create invitations that can only be used from computers running Windows Vista or later".
• Here also don’t forget to click on the “Apply" button.
• Finally you have to reboot WHS and client PC for settings take affect and get the connection back. It took me several hours to find these settings in order to get the connection back. Everytime I am getting "connection disabled" message listed next to client PC's which are connected for WHS

[Vrushabha]

Are you using a Wifi router? If so, you must know that it has a built-in firewall. Disable it and then see if you can connect now. If the connection is authenticated now, then turn on the Firewall and add the rules to the firewall in order to allow the ports. I have also heard that some routers have a DMZ arrangement. I am currently using a NetGear and in my case I need to place the DMZ server to the same server IP address. I can use homeserver name to ping from any remote system.

[Usha Kiran]

• Open the Start menu of Windows Home Server and click on "Terminal Services Configuration" (Start -> Programs -> Administrative Tools).
• A window opens with some content.
• Click with the left mouse button on "RDP - tcp" and that opens the context menu on "Properties".
• There click on "Start the following program when the user logs on," so that we can fill in the two lines below.
• Under "Program path and file name" you wear% windir% \ explorer.exe. As a result, when an application is started via RDP always explorer.exe. "Start in" I "C: \" specify, but you can also specify any other directory.
• With one click on "Apply" and "OK" to close the window. The underlying window may also be closed. We have already managed.

[Avikshit Sinha]

In your Windows 7 system, you may have Network Level Authentication (NLA) enabled but the problem with this is Windows Home Server (the RD activex control) can't handle it. In order to disable the Network Level Authentication, you have to go through the following settings:

• Go to Control Panel > System and Security > System
• On the left side click on Remote settings
• Under Remote Desktop, choose “Allow connections from computers running any version of Remote Desktop (less secure)"
• Re-run C:\Program Files\Windows Home Server\ClientInfo.exe from command prompt (elevated).

[Jacques25]

Did you try configuring Windows Home Server with a Static IP Address? The IP address is always unique assigned by router to every computer on the Home network. But it may be changed due to several reasons and it can cause problem to the network and also for connection. For that reason you have to configure the Windows Home Server always rely the same IP address. You can do it in two ways. The first method is setting up a reserved IP address in the DHCP section for your router. This means the router always provide or assign reserved IP address to the WHS. Setting up reserved IP address in the DHCP section in router is completely depends on the model of router. You need to refer manual for that. The second method is configure static IP address in the WHS itself.