client could not connnect across WAN

From: cody (fcody_at_net-xperts.com)
Date: 04/21/04 

Date: Wed, 21 Apr 2004 02:31:21 -0700

When Compaq thin clients connect to a Win2003 Terminal
server, they sometimes get the "client could not connect
to the remote computer. Remote connections might not be
enabled......" error. After clicking okay 5 to 10 times
the thin clients connect and perform 100%. Issue only
happens when logging in. Error started when server was
moved to remote location. Using same Compaq thin client
locally tests good. 4 thin clients connect via 384K DSL
through a VPN to the main site, which has T1 connection
to internet. Do I have a latency issue or what?

Relevant Pages

  • RE: More on Shatter
    ... > or with any countless number of other "remote ... In thin clients such as the Wyse WinTerm, ... applications indeed run on the server, ... Do You Yahoo!? ...
    (Vuln-Dev)
  • setup
    ... Looking at implementing some thin clients and was wandering if the following ... Have 3 remote offices where each remote has a server that will be used as a ... terminal service server. ...
    (microsoft.public.windows.terminal_services)
  • Re: MIDI
    ... have to purchase the big iron fat server for the thin clients. ... A nice side effect of setting up a server with k12ltsp is ... that it is automatically also prepared to handle remote X ... it is also very nice for remote or cross platform work so ...
    (Fedora)
  • Re: The Desktop Strikes Back [was Re: Newbie FAQ #2: Wheres the GUI?]
    ... Hence, if we really want thin clients, than we really should ... while programs executed on a remote server. ... remote desktop client/web browser/whatever!" ...
    (comp.lang.lisp)
  • Connection ended on "thin clients"
    ... I have a remote office that connects to our corp office via Remote Desktop. ... The "regular computers" seem to login fine to the Terminal Server, however, ... the 3 HP thin clients appear to have trouble connecting. ...
    (microsoft.public.win2000.termserv.clients)