Windows clients, it would be better to have the Windows clients on the same network as the Web server. You can run the Citrix client, and it does cache the graphics for faster access if the screens are repeated. But otherwise on a 56K connection it is going to be slow. The more graphics, the slower the load time. We tried to keep our ASP pages simple HTML tables with as little graphics as possible.

It depends on the settings and if the Citrix server was reset. Usually if the server was not reset, when the client reconnects, the applications are still in memory and waiting for a response. So if you had your browser open before Ma Bell cut you off, it will be open when you reconnect. At least it worked that way.

Gosh, I am trying to get all of this out of my mind. I've forgotten what versions we worked with, and I cannot connect to their servers anymore to check. They usually used the most recent one, unless the technical specialist who administrated it decided that they could not upgrade for some reason. They went from Citrix to Windows 2000 Terminal Server. As a result, I sometimes get the two confused. They still called Terminal Server the Citrix server, and the Terminal Server Client the Citrix client. Tomato, Tomoto, whatever.

I think you need 1 Server license, 1 Client license for both the NT/2000 Server and Windows Client, and the Citrix/Terminal Server and Clients. But don't quote me on that. Visit the [link|http://www.citrix.com|Citrix.com] and [link|www.microsoft.com/windows2000/technologies/terminal/default.asp|W2K terminal Server]web sites for more info.