NetOp 7.0 also includes file transfer, text chat (keystroke-by-keystroke as opposed to line-by-line), audio chat (works quite well), remote printing (a Guest can print on a Host machine's printer and vice versa, provided the correct printer drivers are installed locally), transferring the clipboard contents, and a marker function (triggered by the Guest on the Host to draw lines around points of interest on the Host display); and Guest machines can execute scripts for automated or repetitive command sequences. The Guest can also make a video recording of the Host display which is saved compressed and encrypted, viewable only by the Guest console.

Remote control programs have existed in one form or another for a long time. But as methods of computers communicating with each other have diversified, these programs have also incorporated those methods, most of them careful to maintain enhanced levels of security.

Granted, Microsoft has placed within Windows XP a utility called Remote Assistance. XP is great for enterprise environments where not having separate licensing, installation, and maintenance issues save significant costs. On the other hand, systems using Internet Connection Sharing can't use RA. The Expert's machine cannot sit behind a router without some editing of the "invite," token but UPnP devices may alleviate this difficulty.

Remote Assistance's features and capabilities resemble that of NetOp to a limited degree. So, why would anyone with XP actually buy NetOp (or PCAnywhere, Carbon Copy, etc)? It's been mentioned (and I haven't confirmed it though I did attempt the research), the RA feature uses the same code as Microsoft's terminal server, for which there are 251 vulnerability and patch postings on the CERT Coordination Center Web site. Remote control capability will be shoved onto a much broader user base, whether the unwashed public is ready for it or not, and whether the protocols have been thoroughly tested or not.

Versions prior to NetOp 7.0 did have some security concerns: most were related to negligent administration of the Host program— un-enabled password protection, for example. Installing the Host on an operating system designed for multiple account users (NT, 2000, XP), there may be times when the system is logged in under an "everybody" status. Unless the NTFS file permissions are administered against "everyone," the Guest can have access to the whole system. Version 7 has enhanced encryption capabilities.

I had installed the Host half of the NetOp system on my wife's machine. The Guest half was installed on the system in the Sacramento PC Users Group research lab. On a third machine, I installed another Host component. The first Host was configured for "Internet" settings and the second Host was set for TCP/IP. Sending data through a 28-K connection quickly became ponderous but I still managed to complete the task setup for the evaluation. The TCP/IP connection was smooth and snappy.

It is the Guest half that initiates the connection. The Host sits there with "Waiting for call" and the Guest "Places the call." The lab's computer is behind a NAT-enabled router and required no port redirection for an outgoing connection. Port redirection would be required if the roles were reversed.

There is a Help Request section in the Host program options. One can also click a "Request Help" button on the toolbar. The Host will then poll for "Help Providers" visible on the LAN. Having enabled the Guest component to accept help requests, the Host will be given a list of possible Guests identified by a description of the type of help provided. The Host can enter a short description of the problem to be sent to the chosen Guest's Help Request screen. This screen collects all help requests sent to it by all other Hosts that chose it from the list of eligible Help Guests.

The Guest then starts a standard Remote Session. In Microsoft's RA, the Novice must ask for help via MSN or e-mail— a "help ticket" is sent.

The two halves of NetOp can be started independently without requiring any token passing. Using any method available, all that needs to be sent to the "Guest" ("Expert" in MS parlance) is the computer name if on a local network, or current IP address if on an extended network or Internet (and hope it doesn't change before the connection is made).

The Host part is set to configure itself to "Wait for Call" at the program's startup. It's also set to load the program at Windows startup. This isn't mentioned anywhere in the documentation I had read and freaked my wife when something was trying to connect to the Internet when she next booted her machine. There's a security consideration as to why the program does this. I haven't studied this but it may involve having NetOp establish its security protocols before any virus or back-door trojan starts during bootup.

So, what do you actually see relative to the Host you've connected to? Exactly what the user at the Host machine sees (as far as I could tell). My wife uses a software-based screen enlargement utility. The guest also sees the screen enlarged. Many years ago, she used a secondary video card that grabbed the signal from the primary video card. I have no way to tell what sort of image would be displayed in this scenario, nor have I tried using a Host system with multiple monitors.

According to Microsoft, RA works great with multiple monitors and there can be multiple instances (of which half, I'm not sure). The Host cannot be connected to more than one Guest, but the Guest's control panel handles multiple Host connections. (In fact, the NetOp School version presumably has the Guest system operated by the instructor, controlling several Host machines operated by the students.) Both the Guest and Host can control the Host's mouse cursor, making for some interesting battles of will. Settings on both the Host and Guest can determine who has the better control of the Host computer.

NetOp 7.0 has several additional components. For elaborate security considerations, a Security Server role can be installed on one of the machines for centrally-controlled NetOp security management. The Security Server interrogates a database to provide permissions to a query sent by a Host about an attempted connection from a Guest.

Various levels of encryption are available, machine-specific permissions can disable key activities, and password protection can be enforced against changes to the Host security settings.

For extended reach, a Gateway role can be installed. This permits one machine to bridge two dissimilar networking protocols or a LAN to a serial connection (direct to COM, modem, and IrDA). The Gateway can also bridge two distinct LANs through a firewall. The system playing the role of Gateway must sit in the firewall's DMZ and have two IP addresses assigned to it.

For extended naming capabilities, a Name Server role can be installed. The Name Server can assist in connecting a Host and a Guest across two disparate networks, even behind routers and firewalls if that equipment is properly configured.

The hardcopy manual (500 pages), much of it brainless descriptions of command menu selections ("The phonebook entry window displays the phonebook entries…"), still has a decent number of examples.

The index at the back of the book is nothing more than an alphabetical listing of command names, not topical keywords— "port redirection," for example. I feel the NetOp package is prime for a third-party book— NetOp for Dummies. The installed on-line help system for NetOp contains the same information as the manual. The Danware Web site has a few dozen knowledge-base articles and white papers, but I'm not impressed with the level of detail.

Some additional comments: The Host component of NetOp doesn't show up in the Task Manager list. The Host's mouse cursor position can be seen on the Guest's display but won't wake up the Guest computer if it went to sleep. If a Wake-on-LAN network card can boot the computer, a Guest can remotely start a Host if the MAC address is known.

NetOp has Guest and Host components for Windows 95+ including terminal servers, DOS, and OS/2. In DOS, the Guest must have higher video resolution than the Host (VGA vs. EGA, for example). Other limited-functionality Guest components are available for Windows CE and Linux, and there exists an ActiveX component for a Guest component in a browser window or custom application.

Here's a thought, though: If I need to run an application on the Host machine, will I need to buy a license for that application? Check the license agreement— if it says it cannot be used by more than one person at a time, what are ya gonna do?

NetOp Remote Control 7.01
Danware Data A/S
$179 for one Guest and one Host
(Prices vary according to component quantity)
NetOp (USA reseller: CrossTecCorp)