Prev: 2003 TS Login Problem
Next: "You do not have access to logon to this session" on domain controller
From: Tony on 28 Jun 2005 11:39
Vera,
I have 3389 open to my TS from the outside and use SSL and certificates
to get to the TS web page that's on another 2003 server and am still
receiving the connection failed message that Marius mentioned. Can you think
of anything else that I might be missing? I've tried name as well as private
IP address.

"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 28 Jun 2005 16:39
I'm far from an expert on this, but maybe someone else joins the
discussion as well.

To minimize the level of complexity: if you forget the TSweb server
for a while, can you connect with the normal rdp client?
Alternatively, can you ping to port 3389 on the TS?

_________________________________________________________
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?VG9ueQ==?=" <Tony(a)discussions.microsoft.com> wrote on
28 jun 2005 in microsoft.public.windows.terminal_services:

> Vera,
> I have 3389 open to my TS from the outside and use SSL and
> certificates
> to get to the TS web page that's on another 2003 server and am
> still receiving the connection failed message that Marius
> mentioned. Can you think of anything else that I might be
> missing? I've tried name as well as private IP address.
>
> "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: Tony on 29 Jun 2005 09:15
Vera,
Could be a licensing issue with my TS box. I tried connecting to it
directly like you suggested and I got a message regarding insufficient
licensing. I should have additional licenses in a few days. I'll repost if
that's what it was.

Thanks for replying.

"Vera Noest [MVP]" wrote:

> I'm far from an expert on this, but maybe someone else joins the
> discussion as well.
>
> To minimize the level of complexity: if you forget the TSweb server
> for a while, can you connect with the normal rdp client?
> Alternatively, can you ping to port 3389 on the TS?
>
> _________________________________________________________
> 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?VG9ueQ==?=" <Tony(a)discussions.microsoft.com> wrote on
> 28 jun 2005 in microsoft.public.windows.terminal_services:
>
> > Vera,
> > I have 3389 open to my TS from the outside and use SSL and
> > certificates
> > to get to the TS web page that's on another 2003 server and am
> > still receiving the connection failed message that Marius
> > mentioned. Can you think of anything else that I might be
> > missing? I've tried name as well as private IP address.
> >
> > "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.
>
First  |  Prev  | 
Pages: 1 2
Prev: 2003 TS Login Problem
Next: "You do not have access to logon to this session" on domain controller