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
May 17th, 2008 at 9:13 am
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
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.
May 17th, 2008 at 10:17 pm
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.
May 17th, 2008 at 11:05 pm
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.
May 18th, 2008 at 3:20 am
“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.
May 18th, 2008 at 9:43 am
Jesus Christ monkey balls, Microsoft make it damned hard for me to like their products.
May 19th, 2008 at 1:08 am
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
May 22nd, 2008 at 11:11 am
Had that problem. Trying the fix now. I used VPN and remote desktop instead for a while…
/Mikael
May 22nd, 2008 at 9:18 pm
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.
May 23rd, 2008 at 7:50 pm
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}
June 4th, 2008 at 11:57 am
I had installed SP3 before I setup my WHS and it works just fine with remote access. (both via “Terminal Services” and browser-based)
July 11th, 2008 at 9:22 pm
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
July 11th, 2008 at 9:32 pm
This isn’t a support forum, sweetie pie.
July 13th, 2008 at 4:06 am
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
July 21st, 2008 at 5:53 pm
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.
July 30th, 2008 at 7:33 pm
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.
July 31st, 2008 at 9:59 pm
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?
August 3rd, 2008 at 7:42 pm
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.