Re: Connection Problems

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

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

Relevant Pages

  • Re: thin client com ports
    ... I'm glad that you got at least one more client working! ... MCSE, CCEA, Microsoft MVP - Terminal Server ... the COM port settings? ... I am testing several thin clients. ...
    (microsoft.public.windows.terminal_services)
  • Re: interfaces lo:1 lo:2 lo:3? (for remote ssh tunnels)
    ... That's the problem tunneling (port forwarding) solves. ... >>can't get past the client firewall. ... > I don't understand why the server would be making the ... server initiates another connection to the client -- in this ...
    (Debian-User)
  • Re: Using Remote Desktop From an SBS Domain
    ... when you tried to RDP while attached directly to a port on your router? ... So if 3389 needs forwarded on the client end too then that is what the ... Hopefully next week I can attempt a connection while my ISP watches the ...
    (microsoft.public.windows.server.sbs)
  • RE: Telnet/ftp problems SBS2000
    ... Please make sure your client computers are configured as both Firewall ... will find two options "Enable folder view for FTP sites" and "Use Passive ... that the control connection has been successfully established, ... (other than port 21) ...
    (microsoft.public.windows.server.sbs)
  • Re: One workstation cant access email from ISP - CROSSPOST
    ... Remove or disable the ISA Firewall client. ... Ethernet adapter Wireless Network Connection: ... Switch is nothing more than a patch panel; ... port - same result. ...
    (microsoft.public.exchange.admin)