RE: Windows client in Terminal server/Citrix

Unfortunately I am running the latest version.  I did see in the OpenAFS
road map that there are a couple of things that might directly address
this.  
	- RX connection pools
	- UNICODE character set support.  

I see that the RX is not currently funded. Though the native client
would be the best solution.

Unfortunately on a server farm that his hosting 5000+ users I cannot
just restart the service that drops everyone's connections that are
established and working.  

Robin Manke-Cassidy
Arizona State University
University Technology Office
(p) 480-965-5683
[email protected]


-----Original Message-----
From: Christopher D. Clausen [mailto:[email protected]] 
Sent: Thursday, March 06, 2008 3:33 PM
To: Robin Manke-Cassidy
Cc: [email protected]
Subject: Re: [OpenAFS-win32-devel] Windows client in Terminal
server/Citrix

Robin Manke-Cassidy <[email protected]> wrote:
> Jeff, I have been a users and configuration support for AFS @ ASU for
> many years.
>
> What I mean by client quitting is the service seems to just stop
> functioning or I guess could be locked up.  We have to restart the
> AFS client service to get it back on line.  But there does not seem
> to be any rhythm or reason to it.

I too have had this problem on Windows Terminal Servers, but have not 
been able to track it down and it is almost always more important to get

the service working again than to find the problem.  And I have been 
unable to reproduce the problem on my test systems.

I/O will just stop working into or out of AFS during file transfers and 
there is little or no network traffic leaving the computer.  Only 
restarting the afs client service seems to fix the problem.

What AFS version are you running?  I'm sure that trying the newest 
version will likely be an improvement.

<<CDC