• Announcements

    • Terry (WGS)

      WGS Forums Will Close on January 31st 2017   01/18/17

      Hi everyone, We're coming up to We Got Served's ten year anniversary and I've been taking a good look at the site to work through some plans for the future. I wanted to give you all a couple of weeks notice that I'll be closing WGS Forums at the end of this month.  As you'll be aware, the forums were opened to support Windows Home Server users and have done so brilliantly, thanks to everyone's participation. However, with each day that passes, there are fewer and fewer WHS deployments out there, meaning that forum registrations and traffic has now dwindled. I've tried a few times over the years to test some forums on related or adjacent topics, however, they simply haven't caught on. It's clear that these were always going to be predominately Windows Home Server forums and, with the passing of that platform, they've served their purpose well. So, please take some time to archive anything you need over the next two weeks. Access to the forums will end on Jan 31st 2017. Many, many thanks once again for your participation and support here. It's been a great community! Very best wishes Terry
miles267

Remote Desktop Gateway Server Temporarily Unavailable?

3 posts in this topic

Remote access web site works fine as does RDP directly to any client behind my router. However, when I attempt to login to the WHS 2011 remote access web site and CONNECT to an available PC via the web UI, it returns the remote desktop gateway server temporarily available error message. I noticed that the Remote Desktop Gateway service didn't exist, so I added this role onto the machine. Though I continue to receive the following message and was hoping someone could guide me through resolving it.

Your computer can't connect to the remote computer because the Remote Desktop Gateway server is temporarily unavailable. Try reconnecting later or contact your network administrator for assistance.

Needless to say, I don't wish to do a complete reinstall of my WHS 2011 OS. Any guidance would be appreciated.

UPDATE: unfortunately it's not possible to resolve this error nor is it possible to identify the cause. the only resolution is to do a full re-install of WHS 2011 OS.

Share this post


Link to post
Share on other sites

Upgrade to a WGS Supporter Account to remove this ad.

Got this message when I RDP into a client and rebooted the WHS. WHS came up. RDP into the client again. Got the error.

A minute later, was able to get in.

Share this post


Link to post
Share on other sites

Just encountered the same error when I tried to access pc on local network via my WHS over the internet. It was fixable and did not require a reinstall. Turns out the issue was caused by trying to remote in via WinXP SP3. I resolved my issues by downloading and running these 2 patch/fixes:

Microsoftfixit50588.msi found here:

http://www.remoteaccess.gr/index.php/download-center/doc_details/22-microsoft-windows-xp-sp3-remote-desktop-patch?FontSize=font-small

and Windowsxp-kb969084-x86-enu.exe found here:

http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=20609

After installing these patches, was able to remote access my whs 2011 server and then connect to my win7 pc on my home network.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now



Upgrade to a WGS Supporter Account to remove this ad.



  • Posts

    • I am running WSE2012 R2 and I only ever see red, yellow or green. I have never seen blue even when backing up. I can't explain what could be happening here, but maybe some feedback from other users may help us pin it down. What OS are your client PC's? Mine are all Win 10. Not sure if that may have a bearing.   
    • I made the leap from WHSv1 to WSE2012R2.  I like the new system but one thing seems to be missing.  In WHS v1, the tray icon would change colors to indicate various things blue - backing up now green - everything is healthy yellow - warnings detected (e.g. haven't backed up in a while) red - critical issues (e.g. recent backup failed) In WSE 2012 R2, however, I only get the blue and green indicators, even when there are critical errors on my home network.  For example, a server hard drive had failed for several weeks, but the connector icon in my system tray remained green.  I only discovered the issue when I happened to login to the dashboard for something else. Does anyone know if this feature has been removed in the latest WSE versions?  Or have I just mis-configured something?
    • I am building a new home server: I really want to use StableBit DrivePool and Scanner - am used to them and like the relative ease of use. Hardware = PC running Windows 7 Pro has SSD for OS and 5 additional 2TB HDDs + SansDigital Towerraid (model TR5M6G) connected by eSATA controller (pCie) with 5 2TB HDDs of varying age (2 brand new WD Red and the remaining 3 a combo of Hiatachi and Seagate of varying age - all test out fine for now). Towerraid is currently configured as JBOD, so I can't really see individual drives, and neither does StableBit drive pool - so I get a pool consisting 5 1.82 TB drives (the ones on the PC) and 1 giant 9.1TB drive. I have about 10 TB of data ready to go into this new build.  Will be adding more over time.  Not sure when but certain I'll have HDDs go bad on me, of course. My question(s): 1)  Is there a RAID configuration that will let StableBit do its thing watching individual drives and letting me identify sick drives that need to be removed/replaced?                           2)  If I decide to give up the RAID and just let DrivePool handle duplication, how do I configure the SansDig?                           3)  Am I just getting it all wrong from the get-go? Would appreciate any advice - thanks   
    • I have almost 10 TB in the storage pool so I was not surprised when my first server backup took a very long time (22 hrs.).  Lately the incremental server backups have been fast (15 - 18 min.)  Two days ago the server apparently initiated a full backup that failed twice but completed successfully this morning after about 23 hours.  An hour later the regular daily backup is back to a normal incremental backup times (18 min.) So why did the previous backup take so long, as long as a full backup would take? Does the server occasionally make a fresh start with a full backup to reduce the time a full incremental recovery takes?  (fewer increments, less processing time) I don't see a setting in the server backup options for specifying a number of increments between full backups, for example.    
    • I just posted a similar question elsewhere.  By Shadow Copies are you referring to the Windows 10 File History backups that periodically use shadow copy to backup open files? I too discovered that a huge amount of backup space was consumed by File History backups, no doubt because I was moving some large Blu-Ray files around.  That I fixed by moving the temporary and final file folders to the server, where they are backed up as part of the daily server backup.  That too, of course, uses Shadow Copies but that is another story. Has anyone done the math?  What is the equivalence .. or lack thereof ... between the traditional WS2012r2 (WHS v1 et al.) daily incremental backup :: and a Win7 System Image backup + File History backups? Restore time comparison? Which do you feel is best?
  • Popular Contributors