To view the Report card.
For this review, we stayed with the NetWare services, enabling NetWare connections and defining the v
isible volumes. Accounts already were active, as we decided to let TAS authenticate against the local Unix machine. Licensing is based on concurrent connections regardless of the file service being used.
We were disappointed to find that Syntax doesn't make use of existing NetWare utilities, though we had no problem connecting to the server from Windows NT 3.51, 4.0 or Windows95. Using the DOS Virtual Loadable Module (VLM) client, we found that the login directory contains a number of executables that resemble their NetWare counterparts, such as CAPTURE.EXE, MAP.EXE and LOGIN.EXE. Those posed no problem logging into the TAS server or into true NetWare servers.
Syntax even supports case sensitivity through the NetWare login, though, you must type the "~" character before each uppercase letter so it knows which case to pass to the Unix authentication side.
Its support for a multitude of NOS emulatio
ns (called Realms), including SMB (LAN manager), NetWare and AppleShare, makes TAS an ideal choice fo
r integrating your desktop operating systems' resources. But we were a bit disappointed to find that long file names are not yet supported in the NetWare realm. However, they are supported under SMB. Syntax promises long file name support in its next revision, version 4.2.
NetCon Corp. NetCon 6.0
NetCon offers a solid solution, but suffers with respect to its management and integration with Novell NetWare. NetCon's scalability is good, since it supports routing and can talk to numerous network cards. However, the product needs to be integrated better with either the Unix or NetWare environment. Specifically, it has to make use of either network operating systems native administrative tools.
Like TAS, NetCon uses a simple pkgadd to add the software to the system. During installation, we were prompted by several questions regarding network interfaces, though the version we tested was unable to function using our Ethernet 802.3 frame type. NetCon quickly issued a patch when we
told them of this, and we were up and running without a problem.
We found the NetCon add user and group utility to be cumbersome. The menu-driven utility is poorly laid out and we often had to guess at the proper syntax to add users. Of course, our troubles could have been avoided had NetCon made better use of SYSCON.EXE or had been integrated with the Unix password file. Though accounts are created only once, organizations add and delete users quite often.
Once up and running, NetCon operates well. We were able to login from any Windows or DOS platform and run executables. Since account entries are kept in NetCon's private bindery, case sensitivity is not an issue. In addition, we had no problems connecting from an NT 4.0 client. Like Syntax, NetCon does not support long file names.
Robert J. Kohlhepp can be reached at rkohlhepp@nwc.com.
|