images/contents.gifimages/index.gifimages/prev1.gifimages/next1.gif

Conceptual Overview

images/net00090000.gif Up to 30 active users are now allowed per server. (30 user profiles for ARES servers).

images/net00090000.gif All servers and workstations must run AspeNet software of the same version, respectively. Do not attempt to run workstations on one AspeNet version and servers on another. Ensuring AspeNet version compatibility is the best way to ensure correct AspeNet operation.

images/net00090000.gif A new version of IPX32SUP.COM must be loaded on all Servers and DOS workstations. (Windows 3.1, Windows 95, and Windows-NT workstations do not need this file.)

images/net00090000.gif All workstation feature-control passwords (non-ARES) must be re-issued.

images/net00090000.gif All server passwords must be re-issued.

images/net00090000.gif All user entitlement profiles on ARES systems will need to be re-transmitted by the data provider.

TCP/IP Support

images/net00090000.gif Aspen Servers and Workstations can now be configured to use the TCP/IP protocol.

images/net00090000.gif Servers and DOS-based or DOS/Windows 3.1 AspeNet Workstations no longer require IBM TCP/IP for DOS/Windows. Novell's TCP/IP stack has been adopted due to problems in the IBM product, and because IBM has no plans to support the product.

images/net00090000.gif Each Server requires Novell's TCP/IP Transport for DOS.

images/net00090000.gif Novell's TCP/IP Transport for DOS must be installed on each DOS-based or DOS/Windows 3.1 AspeNet Workstation.

images/net00090000.gif Aspen Servers can support both IPX-based and IP-based workstations simultaneously. Any authorized workstation may use either IPX or IP, whichever is more convenient for the workstation's configuration.

images/net00090000.gif Workstations running on Windows 95, Windows NT, or OS/2 Warp Connect do not require third-party software. These operating systems provide built-in support for TCP/IP.

images/net00090000.gif IBM TCP/IP software for DOS or DOS/Windows 3.1 is not supported.

Network Performance

images/net00090000.gif More than 90% of network traffic due to price updates has been eliminated.

images/net00090000.gif More than 90% of network traffic due to news index retrieval has been eliminated.

images/net00090000.gif Additional internal enhancements reduce overall traffic between Workstations and Servers.

images/net00090000.gif These enhancements also improve the overall quantity of data transmitted. Steady-state bandwidth usage has been reduced to about one-tenth of previous versions. (Initial page-loading traffic is only slightly reduced.)

images/net00090000.gif Response time of servers to workstation requests has been improved, especially under heavy-load conditions.

images/net00090000.gif Lag-time between data reception and workstation updates has been reduced to virtually zero under most load scenarios.

images/net00090000.gif Performance on IPX Servers supporting less than thirty users may be improved by placing the “MU=n” argument in the server's command line. This argument defines the ‘Maximum Users’ that can log into the server at any one time. Setting the maximum users to a number less than thirty (30 is the default) limits the amount of DOS memory pre-allocated for network data buffers. For example, on an IPX server supporting only ten users, loading the server with the “MU=10” argument releases about 150Kb of pre-allocated network data buffers. The server then uses this memory in the cache or expanded-queue.

Note: This option in no way affects the actual number of authorized users or user profiles on the system, but merely places an upper limit on how many IPX-based client sessions can be physically supported simultaneously.


Remote Workstations

images/net00090000.gif Network performance enhancements increase the live symbol capacity and response time of remote workstations. News index retrieval and display operations are also faster.

images/net00090000.gif Workstations, especially those requiring feature-control passwords, will now have a consistent system ID number, regardless of node-address fluctuations caused by unpredictable dial-up host connections, software-based address selection, or swapping of a workstation's network board. As mentioned above, a one-time re-issue of all workstation passwords is necessary when upgrading from v3.00.

Details and Clarifications

This section details issues that will assist your understanding of important AspeNet concepts.

Workstation System Ids

Server System Ids

IPX Isolated Networks