HobLink JWT takes a cool approach to offering Web-based support for applications strictly through a Java-based connection. The same software can be installed locally to make it act as a local Java-based thin client or can run on a server and allow for connections through a Web browser. The local Java client is the same as the Web-based product but has been compiled for use by the local system.

This product fared slightly better than Microsoft TSAC because TSAC supports only Microsoft Internet Explorer. Additionally, Hob has built some load-balancing into the client, which the company says looks at the CPU load of each server and chooses the server with the lightest load. The load-balancing works by installing a module on any terminal server that will be included in the load-balancing.

We were impressed by HobLink's flexibility and installation. HobLink's administration and initial user interface, however, was less intuitive than those of the other products we tested. In addition, we were disappointed with HobLink's results in our screen-refresh performance testing. Like Citrix NFuse and Tarantella Enterprise, Hob HobLink supports specific application publishing but is limited to a single application for all users.

We tried both the local client and the Web features of HobLink. First, we installed the product as a Web-based package, which allows for Java terminal server connections from any Java-enabled Web browser. When you connect to a site where services are hosted, the Java applet is loaded, letting you connect with RDP to a Windows Terminal Server or with the Citrix ICA protocol. This client worked well. The only concern we have is that this product does not offer any administrative options to allow for application publishing. Rather, it lets the end user specify an application path for a program he or she wishes to run. This feature is available with some of the other products tested, such as Tarantella Enterprise and Citrix NFuse.

When testing HobLink, we found only one notable problem: The program trapped Alt-F4 (usually used to close programs) not only by closing the active application that was open, but by displaying a program shutdown dialog box that was very inconvenient.

In addition to the local and Web-based clients, HobLink offers HobLink Secure, which enables 128-bit encryption. Without HobLink Secure, the product relies on basic Terminal Server encryption. The cost of a base 15-user license is at the low end.

HobLink JWT, starts at $143 for a single user license, Hob, (800) 399-0990, (732) 650-2300; fax (732) 650-2323. www.hobsoft.com or info@hobsoft.com.

Microsoft Corp. Microsoft Windows 2000 Terminal Services Advanced Client

The heart of Microsoft TSAC is an ActiveX component, which interacts directly with Microsoft's Terminal Server. Although this client is a free turnkey solution, we noticed a drawback upon installation. Unlike Citrix NFuse and Tarantella Enterprise, TSAC does not provide single-application support to let certain users see only published applications. The end user is brought to the Windows desktop, rather than to a single application.

Another drawback is that TSAC does not have a Java component, nor does it support Navigator. The product supports only Internet Explorer. To make matters worse, when a user views one of the default TSAC pages with Navigator, he or she sees only a garbled screen as a result of the ActiveX control not loading; no message appears saying the page cannot be viewed with Navigator.

Web-Based Thin Client Features Chart Click here to enlarge

On the plus side, TSAC is free with the purchase of Windows Terminal Server. It performed well in the screen-redraw tests, and it was a snap to install.

TSAC comes with three components. In addition to the Web-based ActiveX client, it includes a Microsoft Management Console (MMC) plug-in that lets you maintain multiple Terminal Servers and connections, and a new 128-bit secure local Terminal Server client for Windows.

Installation of TSAC's Web component simply entails downloading the component and specifying the directory where public Web files should be placed. TSAC lets users who are enabled for terminal-server access connect to the terminal server through the use of a Web browser (provided that browser is Explorer). At this point, any client can connect to the configured server and then connect to any specified destination terminal server. The system's logon screen prompts the user to enter her or his user name, password, and domain and screen resolution/full screen. Once connected to the terminal server, Explorer asks to install Microsoft's signed Terminal Services ActiveX control. The ActiveX component functions much like the normal Windows-based Terminal Server client.

Because the ActiveX add-on is a free component for Terminal Server, Microsoft offers it as a download from the company's Web site (see www.microsoft.com/windows2000/news/bulletins/tsac.asp).

Microsoft Windows 2000 Terminal Services Advanced Client (TSAC), free download to Terminal Services clients, Microsoft Corp., (800) 426-9400, (425) 882-8080. www.microsoft.com.

Mark A. Seltzer is a freelance writer based in Syracuse, N.Y. Send your comments on this article to him at mark@seltzer.org.