Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
Hi,
I just recently had to reinstall windows on my work computer for reasons I won't get into now. It is Windows NT 4.0 service pack 6a, at home I have windows XP Pro, and I have IIS and tsweb working for remote desktop, I used to have no problem connecting from my computer at work until now. It still works from other computers, but when I try it on mine, I get this error message "Object doesn't support this property or method: 'MsTsc.Server' "
I'm sure if I reinstalled everything again it would work but this is very time consuming. If anyone has any suggestions on how to fix this, I was thinking of reinstalling IE6 but I don't know if that will work. I would like to uninstalled IE and reinstall it but I don't think it's possible to remove IE.
Just to be clear I have installed IE6, the most recent version, service pack 6a, and a bunch of other security fixes from the windows site. I am almost 100% certain it is not a driver issue, I set up computers all the time and always get the most recent drivers for everything.
Thanks to anyone who can help
Matt

Ditto, Have the same problem all the sudden. The computer I connect with started having this problem today. I can connect from a third computer just fine. I installed the Microsoft Virtual Machine and after restarting I couldn't remote desktop anymore.

Same problem here as of today. I just installed the latest updates from windowsupdate recently and have confirmed the same situation with others as well.
Anyone know a quick fix without "restoring" your system.

Hopefully you have the uninstall for SP3... Uninstall and reinstall the Service Pack worked for me...

The problem isn't in the service pack though I don't believe. I've had the service pack (SP3) installed for some time now and it didn't cause any problems..
The problem started occuring after installed the critical fix yesterday with the cumulative IE6 patches, etc...
Rolling back the system works fine, which is basically the same as uninstalling SP3 and re-installing it, but I was hoping to find a better solution, perhaps a hot-fix released by MS sometime soon.
I sent some information to MS regarding the problem and I'll post any information I get back on the problem.
Thanks
Matt

Right... it was from the patch yesterday, but if you roll that one back it still does not work... only way we eventually got it fixed was rolling all post SP3 patches back to SP3, then roll back SP3 and reapply it... There might be a quicker/easier, but this worked for us..

Nunya, by the way, I imaging the SP3 issue was strictly a Windows 2000 issue correct? I believe most of the people are recently having problems who use XP, because of some IE6 pathces released in the last couple of days.
Matt

I believe this is the patch in question right?
Q323759: August, 2002 Cumulative Patch for Internet Explorer
The "August, 2002 Cumulative Patch for Internet Explorer" eliminates all previously addressed security vulnerabilities affecting Internet Explorer, as well as additional newly discovered vulnerabilities. This update includes the functionality of all previously released patches. Download now to continue keeping your computer secure.
For more information about the vulnerabilities this update addresses, read the associated Microsoft Security Bulletin. (This site may be in English.)
System Requirements
This update applies to Internet Explorer 6 with Windows XP.
How to use
Restart your computer to complete the installation.
How to uninstallUninstall is not available.
Doesn't look like undoing this one is an option...
I'll keep researching it.

I installed Client Connection Manager. Unfortunately I won't be able to do it from the browser, but this is a quick fix.

Same thing happened to me. I updated both of my 2000 boxes and IE can no longer connect to ANY terminal server session (2000 or XP).
If anyone hears anything from MS regarding a patch, please let us know.

I found a fix:
I went to: http://www.microsoft.com/windowsxp/remotedesktop/rdwebconn.asp
and installed the new TS web control on my 2000 server machine. It's an updated version of the old one and works fine.

So, did you install that control on your client, or the actual server running Terminal Services?

Thanks, Matias! That worked for me.
I am running Windows 2000, and depend on a Terminal Services connection to my work computer to do my work.
Last night, I stupidly downloaded the cumulative IE6 patches, without making a complete backup right down to the bare metal. This morning, I turned on my machine, connected to work, and got the "Object doesn't support this property or method: 'MsTsc.Server'" message.
So I installed the new control on my PC, and turned on IIS. I pointed my browser at http://localhost/tsweb , and I was back in business.
May God damn and blast the IIS engineers to hell for not testing this before deploying it.

Ok, quick question. I have the tswebsetup.exe file downloaded from the link posted above, but how can i go about remotely logging into a server that I can install that on if I can't do so via Terminal Services (web).
Thanks

Ok, just an update for anyone who hasn't got this working yet, the solution posted previously to load the new TS Web Control works just fine, and also works for those using XP on their client.
Thanks to John I was able to get the Terminal Service Client software installed and then I remotely logged in to my terminal server (Win2k Adv Server) and I loaded the new TS Web Control found at http://www.microsoft.com/windowsxp/remotedesktop/rdwebconn.asp
Then after doing so I was able to go to back to the TS Web page on the server to connect remotely and it asked me to install the new web control, which I let it do, and then I was able to connect perfectly.
Anyways, hope that clears up any confusion and gets everybody squared away.
Thanks for all the help.
Matt

Also, I thought it was strange that all along we were thinking the problem was not on the server and rather the client because after installing updates on my client (XP) is when things stopped working.
So all along I thought the problem was on the client also, which technically I guess it might have been, but I do know that installing the new web control on the actual server, allowed me to fix the problem on the client by forcing it to start using the new web control.
Anyways, hope that helps and get everything taken care of.
But if anyone finds out anymore information about the actual reason for the error to start occurring or if MS posts anything about it, please do follow up.
Thanks
Matt

Has anyone written/called Micro$oft on this one? I find it incredibly stupid that after installing their latest IE patch (I use win XP), I cant connect to my employers computer using Explorer anymore. I have to run "Remote Desktop Connection", and it is very inconvienent.
Thanks!
tom_alford@hotmail.com

I actually notified them and received a rather unhelpful response so far. Mainly because they needed more information from me to verify my copy of XP, etc..
So I sent them all the information to verify my software, etc.. and they are supposed to be getting back with me.
However, from what I can tell they are probably just going to recommend that anyone who experiences this problem to just rollback their system to a previous state, but in my case, that wasn't really an option. Luckily installing the new TS web control on the server fixed my problem on the client by forcing it to use the newest control.
Hope that helps.
By the way, I'll post any feedback I get from MS.
Matt

Actually, you don’t even need to install that TSClient software if you are using XP on the client.
Check this out:
Note: The Remote Desktop Connection software is pre-installed with Windows XP. To run it, click Start, click All Programs, click Accessories, click Communications, and then click Remote Desktop Connection. This software package can also be found on the Windows XP Professional and Windows XP Home Edition product CDs and can be installed on any supported Windows platform. To install from the CD, insert the disc into the target machine's CD-ROM drive, select Perform Additional Tasks, and then click Install Remote Desktop Connection.
I was able to just use that remote desktop connection software to connect just fine. And after I installed the new TS web control, I could use TS from the web (IE) again just fine.
So if you can’t use TS from the web after installing some windows updates, just try this remote desktop connection software (which is just an XP version of the TS Client software) and connect. Just use the IP as the computer name when trying to connect.
By the way, the TS Client software for non-XP users can be found here:http://www.microsoft.com/windowsxp/pro/downloads/rdclientdl.asp
Hope that helps.
Thanks
Matt

Matt,
I can use TS fine from XP's remote desktop-connection icon, by entering the IP, etc. However, I used to be able to do this from IE and now I can't, even after downloading the TS Web Control.
I used that link in an earlier post, http://www.microsoft.com/windowsxp/remotedesktop/rdwebconn.asp, to get it.
Is that the correct link for XP? I noticed it said Windows 2000 all over the page. Is there something else I can d/l for XP to try and make it work, without having to use Remote Desktop Connections?
Tom
tom_alford@hotmail.com

Yes, http://www.microsoft.com/windowsxp/remotedesktop/rdwebconn.asp, was the correct link.
I downloaded that version, 6.0.2600.0, and loaded it on the server I was connecting to (Win2k Adv Server), and then when trying to connect from my client machine (XP) it asked me to load the new control and then worked fine.
Hope that helps. If not, I'll see if I can find any more information regarding the situation.

I can't get this solution to fix my problem. I have a Win2K server and I'm trying to connect from my Win2K workstation via the TSAC (web-based). I've installed the update to the server, but wasn't prompted to update my workstation. I manually updated my workstation, and I'm still getting the same error. Can anyone see what I'm missing?
Best Regards,
Alan

Matt, I see now. I am not able to install that TCS thing the computer I am trying to connect to, just my own. IN that case I probably wont ever be able to do it from IE, unless Micro$oft fixes that last patch they put out.Tom

I've got the fix working, but MS decided to change the way they aprouch this. Instead of using a html file wich calls a .asp file, they implementend the functionality in a html file. This seem preferable from a security point of view (you can disable scripting for this folder), however this has a rather annoying side-effect; it's now impossible to create bookmarks/favorites to servers. Anyone found a way to get the old way (with connect.asp) working with this silly IE patch?

This is caused because of typelib corruption in the registry.
Look in the .htm file for the tag. Search and delete from the registry, all occurances of the CLSID. Also search and delete from the registry, all occurances of the .cab file (again, the one mentioned in the tag)
Now, when you browse to the /tsweb directory, you will be prompted again to install the ActiveX control. After you do this, the typelib info will be refreshed and things should work.

Well, I was fortunate enough to get things up and running again by just installing the newer web control from MS, but for everyone else, Ryan's approach seems like a sure shot to get things up and running again.
Thanks for all the help.
Matt

Yea, I went ahead and corrupted another machine just for testing purposes, and Ryan's method worked perfectly for fixing the problem. At first I didn't think it worked, but once I closed the browser and re-opened it and tried accessing that page, it prompted me just like I expected and loaded the new RC2 control.
Good luck,
Matt

Can anyone confirm exactlly which Patch (For Win XP PRO) or critical update is causing this? I just reinstalled windows XP, and I installed all the critical patches execept for the "August IE security Update", because I thought that was the bad patch. However, I still cant access the remote computer from IE.
Thanks

I can't confirm this, but mine seemed to mess up after installing this patch:
Q323759: August, 2002 Cumulative Patch for Internet Explorer 6 (Windows XP)
But, I do recall loading this patch around the same time:
Q326830: Security Update (Windows XP)
Hope that helps.
Matt

Note to self: Always check computing.net before microsoft.com...you guys are AWESOME.
The above fixes solved my problem, but I'm with Milo above...the html vice asp hosed all my links (e.g., click HERE for an 800x600 resolution terminal services connection to server 1). Is there any way to retain at least the choice of server in my web page links so my users don't have to type in the server name?
Thanks again...anxious to hear any ideas.
rob

Actually, some of us at MS do read these boards and we do create solution objects based on the information. This one is a beaut, guys. I'll be sure and let someone know about it.

Hi I see now that you guys found the solution too. Honestly I dont understand the below solution. I could remove the CLSID fine, but dont know how to get the package with the new CLSID other than installing the new client. (Which I did, so it works now)
Hi Kenneth!
Regarding above referenced case: "TS clients cannot log in via website"
This is indeed a bug, and will therefore be free for you.
Please see below for information:
SYMPTOMS
========
After installing the fix for the following article:
Q323759 MS02-0xx: August 14, 2002, Cumulative Patch for Internet Explorer
The Terminal Services web client may not function as expected.
Upon connecting to a web server that hosts the Terminal Services client control, attempting to connect to a Terminal Services based system may result in the
following error:
Internet Explorer
Problems with this Web page might prevent it from being displayed properly or functioning properly. In the future, you can display this message by double-clicking the warning icon displayed in the status bar.
[ ] Always display this message when a page contains errors.
[okay] [show details]
show details displays:
Line: 67
Char: 7
Error: Object doesn't support this property or method: 'MsTsc.Server"
Code: 0
URL: http://server/tsweb/connect.asp?Server=Servername&UserName=user@Domain=domainname&rW=800&rH=
CAUSE
=====
In order to prevent potential exploits in older versions of the Terminal Services web client, Internet Explorer blocks certain OCX controls.
You may be able to verify the version of the Terminal Services web control by performing the following steps:
In Internet Explorer choose Internet Options from the tools menu
On the General tab under Temporary Internet Files choose Settings
Click View Objects
look for the a control named
Microsoft Terminal Services Client Control
or
Microsoft RDP Client Control
right click on that file and choose properties
on the general tab you will be able to see the GUID in the ID field.
The following GUIDs have been blocked
{1fb464c8-09bb-4017-a2f5-eb742f04392f}
{791fa017-2de3-492e-acc5-53c67a2b94d0}
{931a8c29-3ea9-494d-91e7-22e9a9247687}
RESOLUTION
==========
Ensure that the control included in Q323759 or newer is installed. The GUID for this control is listed below:
9059f30f-4eb1-4bd2-9fdc-36f43a218f4a
STATUS
======
Microsoft has confirmed that this is a problem.
MORE INFORMATION
================
Web developers and administrators hosting the Terminal Services client may need to modify existing code to include the newer controls GUID.
The following is an HTML snippet that illustrates the new GUID being used:

![]() |
![]() |
![]() |

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |