Problems with tsweb/tsac

[Craig Householder]

We have a couple of terminal servers that users access
through the web (our portal product also locks down our
desktop so the client isn't an option) All users are on
Windows 2000 desktops. Typically they go to
http://servername.domainname.org and away they go.
Recently we have started hearing that some users have to
http://servername.domainname.org/tsweb in order to get
connected. Our desktop support people can't seem to find
a common link (patch version, ie version, activex version
etc) Is there a windows 2000 or ie patch that changed it
so that you had to use tsweb or is it something else?

 

[Matthew Harris [MVP]]

Are these people using the latest version of the RDP
client and is the server running the latest version of the
RDP ActiveX component? IE 6 has a patch in it that
doesn't allow the older TS Active X component to run since
it had a security vulnerability.

-M

 

[John Smith]

No, they are hitting it via http://severname or http://servername/tsweb.

We have a browser based portal product and that prohibits us from using the
actual client.

tia

 

[Matthew Harris [MVP]]

Right, I understand that, it is just that is you are using
an older version of the the remote desktop web connection
(TSAC), then people with the latest version of IE will get
an error. When you upgrade the server's software, then
the users will have to download a new ActiveX component if
they don't have it already installed.

-M