Windows XP SP3 Update Breaks Windows Home Server Remote Access?

By on May 17, 2008 in Windows Home Server

Some Windows Home Server users are reporting Remote Access problems after updating their home computers to Windows XP Service Pack 3, although with successful installs also being reported, it is unknown at this point how widespread the issue is.

Following the update, attempting to access those home computers via Windows Home Server’s Remote Access features brings up a dialog asking the user to add their homeserver.com domain to the Trusted Sites list in Internet Explorer. However, after doing so, users are still not able to access those PCs.

The issue arises due to security changes in XP SP3 – namely, that the Terminal Services ActiveX control in Internet Explorer is disabled by default.

If you are experiencing this issue, Microsoft Forums user ColinWH has published a workaround:

Click on Tools -> Manage Add-Ons -> Enable or Disable Add-Ons in IE to enable the Terminal Services ActiveX control. If you are unable to see/enable the Terminal Services ActiveX control in IE7 on XPSP3 as a workaround can you try deleting the following registry keys:

HKCU\Software\Microsoft\Windows\CurrentVersion\Ext\Settings\{7390f3d8-0439-4c05-91e3-cf5cb290c3d0}

HKCU\Software\Microsoft\Windows\CurrentVersion\Ext\Settings\{4eb89ff4-7f78-4a0f-8b8d-2bf02e94e4b2) Once you delete these keys, the activeX control should be enabled in IE7.

Note, of course, that Microsoft have disabled the Terminal Services ActiveX control in Internet Explorer for security reasons, so run these changes with care.

Other users appear to have installed Service Pack 3 without incident – how about you? Let us know your experience with XP SP3 in the comments box below.

More Info: Microsoft Forums


Enjoyed this post? Share it.

If you enjoyed reading this post, then why not share it with your friends and followers?

About Terry Walsh

Terry Walsh is the founding editor and owner of We Got Served. Since February 2007, the site has provided detailed coverage and analysis of the emerging home server category, and has subsequently grown into a trusted outlet for digital home news and reviews.
View all posts by Terry Walsh →

Sign Up for WGS Daily News

If you don't want to miss out on the latest news from We Got Served, why not subscribe to our daily digest? You'll get the day's headlines and a short summary of each news item delivered straight to your inbox each morning.

, , ,

  • Pingback: Home Server Blog » Blog Archive » Ärger mit dem Remote Access wegen XP SP3

  • Patrick Qu

    Um!

    I was going to add to the post on the Microsoft forums however I see that that thread is now locked.

    I had previously noticed one or two posts re SP3 and impacts on WHS which is why I have not applied it to date.

    The workaround advised seems fairly straight forward however surely the WHS team will produce its own solution? Think I will wait even longer to apply SP3 – one cannot help but wonder what other unforseen impacts will arise.

    Regards

  • http://cincoamigospanama.com Steve

    Jeez! Microsoft strikes again. I wish I had a Mac environment. I already applied the SP3 update. I don’t see where I can remove that update. Only Microsoft could send a patch that would wreck their own OS. What a mess.

  • Ron

    Terry,

    I upgraged one of my machines to SP3 last week and was surprised by this post. I tested the functionality using a Vista laptop, loging on to my WHS then selecting my XP machine through the remote access app and IE. I was able to start a session on the XP machine, no problem.

    Could it be that it is the remote system, the one calling that has this issue? Reading your post I got the impression that it was the home connected XP SP3 pc that was failing.

  • Robert G. Plourde

    I have been using WHS from the first beta, and have never had a problem until last week. No matter what I tried, software I uninstalled, registry editing line by line, totally uninstalling MS SQL 5 with ever update, and still I couldn’t get my desktop computer to perform a backup. Last night I finally resolved the problem by running an utily (VSSADMIN UTILITY) located at: http://blogs.technet.com/sdoakes/archive/2006/02/03/418722.aspx
    Problem was instantly fixed. I spent one full week trying to figure out what had gone wrong, and I did see that XP pro SP3 had been upgraded at the same time the problem happen. I do not want to blame MS for poblem, but do finally feel better now after reading your Blog.

  • Thomas

    “Steve Says:
    May 17th, 2008 at 6:23 pm

    Jeez! Microsoft strikes again. I wish I had a Mac environment. I already applied the SP3 update. I don’t see where I can remove that update. Only Microsoft could send a patch that would wreck their own OS. What a mess.”

    Sorry to say this, Steve, but this happens on every OS, include Mac OSX and Linux. (I had to rebuild my Intel iMac recently after some updates killed the OS). Overall i’ve been pretty happy with SP3 so far and I would say THIS IS NOT A BUG, just an oversite. Honestly it’s not that hard to go in and change a security setting in IE.

  • Pingback: Windows XP SP3 Update Breaks Windows Home Server Remote Access

  • http://www.dan-atkinson.com Dan Atkinson

    Jesus Christ monkey balls, Microsoft make it damned hard for me to like their products.

  • Pingback: » XP SP3 skaper problem mot Windows Home Server IKTAvisen

  • Pingback: Computerhilfen.de » Noch ein Problem mit SP3: Kein Zugriff mehr auf Windows Home Server

  • MitchSchaft

    SP3 installed fine for me on both my XP and MCE2005 box. Nothing was adversley affectly and everything is working fine!

    If you have an MCE2005 problem, check out this thread:
    http://thegreenbutton.com/forums/permalink/263563/263162/ShowThread.aspx#263162

  • Pingback: Windows XP SP3 Update Breaks Home Server Remote Access - zakeh blog

  • Pingback: Windows XP SP3 Update Breaks Home Server Remote Access - TechLookz

  • Pingback: yikfoong dot net : Windows XP SP3 Update Breaks Home Server Remote Access - YIKFOONG DOT NET

  • Mikael Gustafsson

    Had that problem. Trying the fix now. I used VPN and remote desktop instead for a while…

    /Mikael

  • Ken Warren

    I’ll point out that it’s not just Windows Home Server that’s affected by this. Anyone that uses SBS Remote Web Workplace is having the same issues.

  • jg007

    I have had the same issue connecting from a SP3 machine to my SBS 2003 server for remote assistance and remote workspace.

    I had to apply the fix to a slightly different registry key but after this it worked fine.

    the key I renamed was -

    HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Ext\Settings\{7584c670-2274-4efb-b00b-d6aaba6d3850}

  • Nick

    I had installed SP3 before I setup my WHS and it works just fine with remote access. (both via “Terminal Services” and browser-based)

  • http://comcast.net joyce pendleton

    after the service pack 3 installation, whenever I try to open Explorer to my COMCAST homepage, I get a block saying Comcast is a fraudulent site. I must cick continue or cancel but either one results in an error page going to Microsoft and then my screen closes. HELP

  • MitchSchaft

    This isn’t a support forum, sweetie pie.

  • http://www.AboutMeadows.com Larry

    Actually there is more to the Service Pack 3 Upgrade than this.

    This will fix it so that if you are currently using the 61 coding object model.

    If you are using the previous object model then you will still have an issue, if you like you can check out my blog that outlines the 2 different sets of object models

    http://aboutmeadows.com/archive/2008/07/12/rdp-rww-remote-desktop-remote-web-workplace-sp3-again.aspx

    Thanks
    Larry

  • John

    I have 5 different workstations that have been updated with XP SP3 and so far I have had no problems remote desktop from anywhere within my house. This is both using the remote function in WHS and also with RDP.

  • Martin

    This fix only works if you had previously accessed the site from the XP machine before you upgraded it. If you have a clean XP install, you appear to be screwed, because the add-on is not there for you to re-enable.

  • chengr

    I followed the procedure stated but still unable to remote access my MSS or any client computer. Initially, I couldn’t see the Terminal Services. So, I deleted the two HKCU’s. However, Terminal Services still didn’t show up in I.E. Tools -> Manage Add-Ons drop-downs. Did I screw-up the system by deleting those HKCU’s? If so, how do I get them back? Maybe the better question is: What should I do now, so that I can remote access computers?

  • Jimmy Vermeer

    I tried to follow the instructions here but could not find that registry entry. I also tried all the advice that was sent to me by Microsoft Support, but I cannot get the Remote Assistance feature to work in MSN Messenger.

  • http://blog.szuta.com Boggy

    For me SP3 wouldn’t install at all. I tried 3 times and got (apperently) very typical 1079 error. Thank GOD for the WHS backups – 1.5 hour restore got me back where I wanted (no pain, watched olympic games on my other machine). So, no SP3 for me, since it is piece of garbage, that buys me nothing, but trouble. Well, without SP3 I wouldn’t have a reason to use the restore functionality of WHS, so … I guess I should give it some credit for forcing me to finally verify my nightly backup procedure. Thanks Microsoft!

  • Marty

    @ Martin

    I did a fresh install of XP Pro w/ SP3 on my laptop and I have run into the issues described here. I have tried all the fixes, but am still unable to enable Terminal Services ActiveX control in IE7. Has a fix been put out for users who did a fresh install? I’ve scoured the web for a few hours now and have come up unsuccessful.

  • http://www.ipsupermarket.com IP

    Thanks for the info. Its really useful.

  • https://local.cfwnc.org/remote Sally Weldon

    I have two staff members (I’m one) who installed SP3 on home computers and no more access to remote desktop. I’m more of a database person than a desktop person. I’ve spend 3 hours at the other staff members house with nothing helping (registry, reinstall IE) and just decided to upgrade my home computer – stupid idea.

  • MitchSchaft

    To fix the remote desktop issue, there’s a registry entry you need to enter. Check it out:
    http://thegreenbutton.com/forums/permalink/287163/287163/ShowThread.aspx#287163

  • http://www.t4u.ne.jp Thaskell

    Hi,
    Does Windows Home Server comes with terminal services similar to Win Server 2003?
    Also, how many users/computers it can handle?

    Thanks,
    Tom

  • Pingback: http://www.wegotserved.co.uk/wp-content/uploads/2009/01/calendarbn.jpg | We Got Served

  • Chris

    Hi Guys,

    The fix for this is actually quite simple, no need to delete any reg keys… go to Tools > Internet Options > Advanced and click the Reset button at the bottom. This WILL remove all settings, trusted zones etc but will leave bookmarks in tact, once done restart IE, reconnect back to your WHS and re-add it to the trusted zone and try to RDP, all should be good again :)

    HTH.

    C.

  • Ad the Lad

    @Chris -
    I had the same problem and I have spent WEEKS trying to fix it. Eventually solved. It was caused by a faulty Windows Firewall (on the remote machine). XP SP3 appears to lockdown the faulty Firewall preventing any connection until this problem is fixed. The symptoms were that I was unable to Remote Desktop to the machine and also TELNET to port 3389 started failing after SP3 was applied.
    I verified that there was a Firewall problem as I was unable to start the Windows Firewall from Windows Control Panel – an error occurred. I fixed the Windows Firewall issue using the patch documented in http://support.microsoft.com/kb/892199. I then started the Windows Firewall service and checked that Remote desktop was setup as an exception. After that, I could Remote Desktop to the machine with no problems.

  • WilhelmII

    Originally Posted By ChrisHi Guys,

    The fix for this is actually quite simple, no need to delete any reg keys… go to Tools > Internet Options > Advanced and click the Reset button at the bottom. This WILL remove all settings, trusted zones etc but will leave bookmarks in tact, once done restart IE, reconnect back to your WHS and re-add it to the trusted zone and try to RDP, all should be good again :)

    HTH.

    C.

    Thank you. This is what finally got it to work! I have been pulling my hair out.

  • bob sagget

    HERE'S THE FIX:

    1. Go to Start, Run, and type this in: "%windir%system32regsvr32 mstscax.dll" (without the quotes)

    2. Hit "OK", then hit "OK" again at the next prompt.

    3. Close all open instances of Internet Explorer, reopen IE, and try to remote in again.

    It will work now!!

  • http://www.doxgame.com ps3 song

    Hi, I can't understand how to add your site in my rss reader. Can you help me please?