Re: [Thinstation-general] rdesktop issue

[<l.k...@ch...>]

Hi,

First of all, thanks for the great reply. I thought about switching
back to pxes again after reading this, but i decided to stick with
Thinstation. I have to set everything up in such a way that everyone
can maintain it. Something that is not so easy to do with pxes, as you
would agree.

So i've played with TS some more, started rdesktop from an xterm in a
blackbox session and found the error was 'recv: connection reset by
peer'. I google'd a big part of the day searching for people who had a
similar problem and it could be a problem on rdesktop's side. Maybe if
the 128bit encryption on the terminal server is causing the client to
(sometimes) fail.

I know it's definately not the RR, since i have similar problems
connecting to a server directly.

Right now i've made a new package (depends on rdesktop) that contains
a small shell script that keeps restarting rdesktop as long as the
(created) error-logfile is empty. Works nicely if its the only session
and set to autostart, but fails if it's called from the menu. I wish i
could paste the shellscript now, but i forgot to enable sshd at work,
so i can't access it now ;)   Anyways, it works great now. At boot you
(might) see X start a couple of times and then display a nice Terminal
Server login prompt.

Maybe you have an idea on how to get this thing working from within
the menu, lemme know. Might also be that more people have this
problem (and no solution), in which case i'll post the script.

On a sidenote: the bootsplash? Not working for me. But i hear that's a
known issue :)


Thanks again,

Leon

PS: duncan, sorry for sending this mail directly to you in the first
place. My client takes the wrong reply address :|




On 6-7-2004 22:21, duncan wrote:

dc> Leon
dc> I was more successful with the PXES version but I do agree that the
dc> ThinStation version is a lot easier to use thanks largely to the better
dc> documentation. (and the great work of the developers!)
 
dc> I installed and support a site with over 100 PXES thin client
dc> workstations successfully connecting to two Windows 2000 Terminal
dc> Servers.
dc> The simple method of DNS round robin is used to provide a primitive load
dc> balancing across the two terminal servers. This works really well and
dc> gives sufficient load balancing for the customer’s needs.
 
dc> I plan to use the same method with my next rollout of 70 ThinStation
dc> clients across two Windows 2003 Terminal Servers.
 
dc> If you haven’t used it before DNS round robin is easy to implement on
dc> the Microsoft platform. I have configured the PXES clients to connect to
dc> ‘Tserver’ (DNS name)and then made two entries in the DNS for ‘Tserver’
dc> pointing to the two IP addresses of the Terminal Servers. The DNS server
dc> issues both IP addresses to the client in a rotating order. If one of
dc> the servers is off-line the PXES client times out on the first IP
dc> address and tries the second IP address. Hitting the ‘esc’ key at the
dc> client during the time out wait will force and immediate connection to
dc> the other IP address.
 
dc> Hope this helps.
 
dc> Duncan