You cannot connect to Terminal Services from a Web page

You may receive a script error message or a blank page when you try to connect to a Terminal Services computer from a Web page after you install Windows XP Service Pack 1 (SP1), Internet Explorer 6 SP1, or the security patch discussed in the following Microsoft Knowledge Base article: Under these circumstances, your connection attempt is unsuccessful.

This behavior occurs because the Web site uses one of the following Terminal Services ActiveX controls that Internet Explorer blocks for security reasons:

• Terminal Services Advanced Client (TSAC) 1.0 ActiveX control - GUID: {1fb464c8-09bb-4017-a2f5-eb742f04392f}
• Microsoft Windows XP version of the TSAC - GUID: {791fa017-2de3-492e-acc5-53c67a2b94d0}
• Microsoft Windows .NET beta versions of the TSAC - GUID: {931a8c29-3ea9-494d-91e7-22e9a9247687}

The only GUID that will work in Internet Explorer after you install Windows XP SP1, Internet Explorer 6 SP1, or the security patch described in the "Symptoms" section of this article is the following:

To resolve this issue, contact the administrator of the Web server. If you are an administrator, you can obtain and install the new control immediately. To do so, visit the following Microsoft Web site: NOTE: This update must be performed on the Web Server hosting Active Server pages that reference these ActiveX controls.

Administrators of the Terminal server and Web developers may also have to modify existing Active Server Pages (ASP) code to load the updated control. To do so, open the ASP files in a text editor such as Notepad, and change any Object tags that refer to the Terminal Services ActiveX control so that the Clsid and Codebase attributes reference the following new values:

• CLASSID="CLSID:9059f30f-4eb1-4bd2-9fdc-36f43a218f4a"
  
  
• CODEBASE="msrdp.cab#version=5,1,2600,1095"

NOTE: The updated Terminal Services ActiveX control package automatically replaces the Clsid and Codebase attributes in the default Web page and changes the ID attribute to MsRdpClient. If you use custom code to script the Terminal Services ActiveX control, make sure that your code uses the same ID attribute in the OBJECT tag that you reference elsewhere in your custom code.

For additional information about this issue, click the following article number to view the article in the Microsoft Knowledge Base:

This behavior is by design.