How we did it

We connected the fully self-contained IPNexus tower server and assigned it an internal IP address via Ethernet network to a BayStack 350 T Switch. Configuration of FTP and Web services was performed on the local server for testing purposes; however, we separately registered clients via T-1 (through a network address translation device in one case and a VPN client in another) with two Internet-based IPNexus demonstration servers to test WebsShare features and compare feature performance on servers located across the country (23 hops between California to Atlanta during business hours) and on a server with more than 50 simultaneous users.

IPNexus client software was installed, and tests were conducted with Windows 98 SE, Windows 2000 Professional, Windows XP Home Edition and Windows XP Professional operating systems.

To continue reading, register here and become an Insider. You'll get free access to premium content from CIO, Computerworld, CSO, InfoWorld, and Network World. See more Insider content or sign in.

We connected the fully self-contained IPNexus tower server and assigned it an internal IP address via Ethernet network to a BayStack 350 T Switch. Configuration of FTP and Web services was performed on the local server for testing purposes; however, we separately registered clients via T-1 (through a network address translation device in one case and a VPN client in another) with two Internet-based IPNexus demonstration servers to test WebsShare features and compare feature performance on servers located across the country (23 hops between California to Atlanta during business hours) and on a server with more than 50 simultaneous users.

IPNexus client software was installed, and tests were conducted with Windows 98 SE, Windows 2000 Professional, Windows XP Home Edition and Windows XP Professional operating systems.

Read more about software in Network World's Software section.