Prev: 2003 TS Login Problem
Next: "You do not have access to logon to this session" on domain controller
From: Marius on 27 Jun 2005 08:09
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.

From: Vera Noest [MVP] on 27 Jun 2005 10:18
You have to open port 3389 on the firewall as well. The client
makes the initial contact with the webserver through port 80, but
after authentication, all other rdp traffic is directly between
the client and the terminal server, through port 3389.

--
Vera Noest
MCSE,CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
*----------- Please reply in newsgroup -------------*

=?Utf-8?B?TWFyaXVz?= <Marius(a)discussions.microsoft.com> wrote on
27 jun 2005:

> 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.

From: Marius on 27 Jun 2005 11:50
I know this would be problematic, but is it possible to reconfigure the
client to use another port?

Or, as an alternative, is it possible to run remote desktop on some
encapsulating protocol, for example, like VPN? Would this hit hard on
performance/latency?

"Vera Noest [MVP]" wrote:

> You have to open port 3389 on the firewall as well. The client
> makes the initial contact with the webserver through port 80, but
> after authentication, all other rdp traffic is directly between
> the client and the terminal server, through port 3389.
>
> --
> Vera Noest
> MCSE,CCEA, Microsoft MVP - Terminal Server
> http://hem.fyristorg.com/vera/IT
> *----------- Please reply in newsgroup -------------*
>
> =?Utf-8?B?TWFyaXVz?= <Marius(a)discussions.microsoft.com> wrote on
> 27 jun 2005:
>
> > 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.
>
>
From: Vera Noest [MVP] on 27 Jun 2005 17:33
Yes, you can configure the TS and the client to use another port,
but not port 80, so there's really no point. You have to open
*some* port on the firewall to let rdp traffic through.

Yes, you can run rdp inside VPN, but again: there's no need. rdp
uses 128-bit encryption, and VPN is actually lessening your
security if you don't have full control over the client at the
other end of the VPN tunnel (i.e. a home PC).

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?TWFyaXVz?= <Marius(a)discussions.microsoft.com> wrote on
27 jun 2005 in microsoft.public.windows.terminal_services:

> I know this would be problematic, but is it possible to
> reconfigure the client to use another port?
>
> Or, as an alternative, is it possible to run remote desktop on
> some encapsulating protocol, for example, like VPN? Would this
> hit hard on performance/latency?
>
> "Vera Noest [MVP]" wrote:
>
>> You have to open port 3389 on the firewall as well. The client
>> makes the initial contact with the webserver through port 80,
>> but after authentication, all other rdp traffic is directly
>> between the client and the terminal server, through port 3389.
>>
>> --
>> Vera Noest
>> MCSE,CCEA, Microsoft MVP - Terminal Server
>> http://hem.fyristorg.com/vera/IT
>> *----------- Please reply in newsgroup -------------*
>>
>> =?Utf-8?B?TWFyaXVz?= <Marius(a)discussions.microsoft.com> wrote
>> on 27 jun 2005:
>>
>> > 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.
From: Marius on 28 Jun 2005 03:37
Thank you very much. I think you have brought me on a trail which might work
most probably...


"Vera Noest [MVP]" wrote:

> Yes, you can configure the TS and the client to use another port,
> but not port 80, so there's really no point. You have to open
> *some* port on the firewall to let rdp traffic through.
>
> Yes, you can run rdp inside VPN, but again: there's no need. rdp
> uses 128-bit encryption, and VPN is actually lessening your
> security if you don't have full control over the client at the
> other end of the VPN tunnel (i.e. a home PC).
>
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> http://hem.fyristorg.com/vera/IT
> ___ please respond in newsgroup, NOT by private email ___
>
> =?Utf-8?B?TWFyaXVz?= <Marius(a)discussions.microsoft.com> wrote on
> 27 jun 2005 in microsoft.public.windows.terminal_services:
>
> > I know this would be problematic, but is it possible to
> > reconfigure the client to use another port?
> >
> > Or, as an alternative, is it possible to run remote desktop on
> > some encapsulating protocol, for example, like VPN? Would this
> > hit hard on performance/latency?
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> You have to open port 3389 on the firewall as well. The client
> >> makes the initial contact with the webserver through port 80,
> >> but after authentication, all other rdp traffic is directly
> >> between the client and the terminal server, through port 3389.
> >>
> >> --
> >> Vera Noest
> >> MCSE,CCEA, Microsoft MVP - Terminal Server
> >> http://hem.fyristorg.com/vera/IT
> >> *----------- Please reply in newsgroup -------------*
> >>
> >> =?Utf-8?B?TWFyaXVz?= <Marius(a)discussions.microsoft.com> wrote
> >> on 27 jun 2005:
> >>
> >> > 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.
>
 |  Next  |  Last
Pages: 1 2
Prev: 2003 TS Login Problem
Next: "You do not have access to logon to this session" on domain controller