|S N E A K P R E V I E W|
RemotelyAnywhere Simplifies Administration From Afar
August 23, 1999
By E. Shane Turner
Maintaining a room full of Windows NT servers can be a challenge. For some reason, mission-critical applications that run flawlessly during normal workdays have a nasty tendency to fail in the middle of the night, on weekends and/or when the system administrator is halfway across the country on vacation.
Remote-control software, such as Binary Research International's RemotelyAnywhere, can make the lives of administrators and system support personnel a little easier.
I tested a beta version of RemotelyAnywhere, which runs on Windows NT 3.51 or 4.0. RemotelyAnywhere incorporates a design that is different from most remote- control tools--it does not include a proprietary client module that must be installed on remote workstations. Instead, it employs a Web-server architecture with a Java-based client module designed to run within a standard Web browser. As a result, system administrators and support specialists can connect with their Windows NT servers from any Java-enabled Web browser. This capability by itself could make RemotelyAnywhere the remote-control utility of choice for some companies.
When I installed RemotelyAnywhere on my NT workstation, the setup process was so quick and easy that I had to wonder if I'd done something wrong. But when I tested the software, it operated just fine. I invoked the client applet initially on the local NT host by typing in the special "localhost" IP address (http://127.0.0.1:2000). I next tried to access my workstation from another PC on the same LAN, and found that this operation worked correctly also.
To connect from a remote workstation, you simply type the IP address of the NT host (or its domain name if it has one) along with the communication port number into the address field
of the Web browser on the remote machine (http://
MyServer:2000, for example). The RemotelyAnywhere software is set up to communicate via Port 2000 by default (you can change this). This means that the RA service can reside on the same NT host as a standard Web server because the HTTP protocol typically uses Port 80.
A Wealth of Options
|PAGE: 1 I 2 I NEXT PAGE|