Re: This is up my alley.

I should point out that the license for the server and clients is prety steep. You may want to consider Win4Lin and then running clients off of that to avoid the big licensing fees of MS and Citrix.

Again, these guys are strictly a Microsoft shop. If Netscape is too big a leap, Linux just ain't gonna happen. :-)

2. No need to install anything but the Citrix Client on the client machine. There exists the Windows 9X, NT/2000/XP, MacOS, Linux, OS/2, DOS, and Java clients. The Citrix ICA client can be used with MS Terminal Server if set up properly.

Are there license charges no matter the platform, though?

1. Performance is slow, graphic data has to be sent to the client to update it. This would be faster if used natively.

Just to make sure I'm reading you correctly: are you saying the Windows clients perform better with graphics?

3. If the connection to the server is gone, or the client gets messed up, they will not have access until it is fixed. If someone installs software like the AOL client, it can mess up the VPN software.

If the connection is lost, the app goes down? This is not like VNC then where you can reconnect later?

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.

Welcome to IWETHEY!