Re: Connection Problems

[Guest portlandjoe]

Re: Connection Problems

 

If that is the case, and port 3389 needs to be opened on the firewall

anyways, why use the web connection at all?

 

"TP" wrote:

> The tsweb page is just a delivery mechanism for the activex

> client. By default communication with the TS uses TCP port

> 3389, just like the regular Remote Desktop Client.

>

> -TP

>

> joanofarc wrote:

> > "Marius" wrote:

> >

> >> Hi,

> >>

> >> I am testing my terminal server via Web remote desktop, to avoid

> >> problems with the firewall. However, my connection attempts fail,

> >> and I get this error box:

> >>

> >> (Title:) VBScript : remote desktop disconnected

> >> The Client couldn't establish a connection to the remote computer.

> >> Maybe the remote connections are not activated, or the computer is

> >> overloaded, and can not establish any new connections. Eventually

> >> network problems prevent the connection of being established. Retry

> >> to connect at a later time. Consult your administrator, if the

> >> problem still occurs.

> >>

> >> (I have translated this message from my language, so please forgive

> >> me if it doesn't exactly fit the english original.)

> >>

> >> Now i wonder, what this problem might be. I have set the connection

> >> limit to a reasonable value. The connection isn't bad, since the

> >> tsweb start screen appears without any problems.

> >> I wonder: is there something used besides ActiveX, which I have to

> >> allow server side? Where does the VBScript Error come from, since I

> >> have no idea where VBScript might be in use at my server. And: is it

> >> possible, that the client is trying to establish a port different

> >> from port 80?

> >> Because my firewall is blocking any outbound traffic, and allows only

> >> inbound connections only with port 80 and 81.

>

[Guest TP]

Re: Connection Problems

 

Re: Connection Problems

 

There are several reasons.

 

Some people choose to use the web as a delivery mechanism

because they feel it is easier to ask end-users to browse to a

web page rather than give them instructions on downloading,

installing, clicking the shortcut on the start menu, typing in the

name, setting connection options, and finally clicking the connect

button.

 

Put another way, tsweb gives you the ability to not only deliver

the remote desktop software (if needed), but to also deliver the

proper settings required for the user to connect. With a small

bit of programming you can automate the process and provide

customization based upon user/group/location, startup program

to launch, etc.

 

Windows Server 2008 will provide much richer functionality in

this regard. Please download the beta and give it a try if you are

interested.

 

Thanks.

 

-TP

 

portlandjoe wrote:

> If that is the case, and port 3389 needs to be opened on the firewall

> anyways, why use the web connection at all?

>

> "TP" wrote:

>

>> The tsweb page is just a delivery mechanism for the activex

>> client. By default communication with the TS uses TCP port

>> 3389, just like the regular Remote Desktop Client.

>>

>> -TP