Error accessing an application through Terminal Server

María Eugenia · 04-20-2006, 08:55 AM

Hi there,

I access through Terminal Server (W98 and Wxp with Remote Desktop 5.1.2600.0) to a Windows 2003 Server machine. Once I am connected I run Internet Explorer in order to access an URL thorugh https. This page (see attachment) show a combo box that displays the list of certificates installed on the machine. As soon as the user selects the certificate and clicks on "Accept", he receives the error "fail to establish connection". If the user does the same directly from the Windows Server machine he receives no errors.

When you select the certificate and click on "Accept", the application executes an ActiveX control and open an explorer window in order to select some files to send.

It seems that something change when you execute the application directly on the W2K3 machine than through Terminal Server. Is it possible that this has to do with some security policies, access policies?.

I would appreciate any help on this.
Thank you very much in advance.
Best regards.
María Eugenia.

04-20-2006, 08:55 AM	#1 (permalink)
María Eugenia Registered User Join Date: Apr 2006 Location: Madrid (Spain) Posts: 1 OS: Windows 2003 Server	Error accessing an application through Terminal Server Hi there, I access through Terminal Server (W98 and Wxp with Remote Desktop 5.1.2600.0) to a Windows 2003 Server machine. Once I am connected I run Internet Explorer in order to access an URL thorugh https. This page (see attachment) show a combo box that displays the list of certificates installed on the machine. As soon as the user selects the certificate and clicks on "Accept", he receives the error "fail to establish connection". If the user does the same directly from the Windows Server machine he receives no errors. When you select the certificate and click on "Accept", the application executes an ActiveX control and open an explorer window in order to select some files to send. It seems that something change when you execute the application directly on the W2K3 machine than through Terminal Server. Is it possible that this has to do with some security policies, access policies?. I would appreciate any help on this. Thank you very much in advance. Best regards. María Eugenia.