Release notes version 7.01 Danware introduces NetOp Remote Control in version 7.01 replacing version 7.0 as the shipping version. It s available as a free downloadable upgrade to existing version 7.0 customers from our Web Site. What s new in version 7.01? This is the news in headlines grouped by function. Further down in the document we have included detailed information about each new feature. Platform support Windows XP enabled Host with full functionality. Windows Pocket PC 2002 enabled Guest with remote-control functionality. Communication Gateway increased the number of concurrent incoming TCP sessions from 9 to 200. Re-initialize Host can now reload the communication profiles by a single click. Platform support Each new feature is introduced below in conceptual details. Windows XP Microsoft Windows XP Host This module includes the full functionality available in the 32-bit Windows Host. Windows XP Fast User switching is supported similarly to Windows 2000 Terminal Services. Specifically, a Host will be loaded for each user, and calling each such Host provides access to the screen, keyboard, files and other features of that user. When a user is not the active user being displayed by the desktop or remote desktop feature, screen and keyboard access for that user will be disabled in NetOp as well, but will resume when that user becomes active. A Guest user will be able to reconnect to the new active user after a Fast User Switch. Microsoft Windows Pocket PC 2002 Guest This module includes the remote-control feature with full screen, keyboard and mouse control. The interface has been adjusted to fit the small monitors available on these handheld devices. You can call and control almost any NetOp Host by its IP address, DNS name via TCP or UDP or NetOp Name Server entry via UDP. The Guest also supports inbound TCP connections via the NetOp Gateway. To be compliant with the Host s security settings, support for the security methods Default access privileges, Individual access privileges and Windows Security Management have been implemented. The program has been compiled to the following processor: Communications - ARM processor running Windows Pocket PC 2002 Each new feature is introduced below in conceptual details. Copenhagen, January 2002 Page 1 of 5
Gateway Among other routing features the NetOp Gateway can do many-to-many routing through one open port in a firewall. One of the advantages is that now up to 200 Guests can simultaneously access different hosts through the one open TCP port with this setup: Re-initialize Host Guest(s) ->TCP-> Firewall ->TCP-> Gateway ->UDP-> Host(s) If the firewall uses Network Address Translation (NAT), you must apply Port Address Translation (PAT) in the firewall configuration to map the incoming TCP Port to the NetOp Gateway and thereby route the NetOp traffic. This feature will do a Stop Host and a Wait for Call in one operation allowing a remote Guest user to change the Host s communication profiles and activate the changes. The Guest will be disconnected, but is now capable of reconnecting and take advantage of the changed settings. Minor enhancements Each enhancement is introduced below in conceptual details. Windows CE installation The interactive installation of the Guest will now allow the user to enter the serial number from the Windows computer before the auto-sync with the PDA takes place. Text Chat Chat is changed so it always is the top most window - even when not in full screen. Japanese keyboard Support has been added for the special modifier keys on Japanese keyboards. Both ends of the NetOp connection must be updated for this new feature to work. Terminal Services NetOp now supports terminal server sessions where the terminal session was configured to open a specific file upon logon. Previous versions only supported sessions that ran the full Windows desktop or specified a program with no file names on the command line. Security Server The Security Manager now allows you to assign rights against the NetOp Host ID group named "UNKNOWN HOSTS". All hosts that are not declared in the system are treated as members of the group of UNKNOWN HOSTS. A host that is registered in the database, but not assigned to be a Copenhagen, January 2002 Page 2 of 5
member of any host ID group is NOT treated a member of this group. It is only UNREGISTERED host IDs. The NetOp Security Manager now only searches for domains once. This search may take quite some time, so the results are cached. To rescan domains, exit and restart the Security Manager. Individual domains are not searched until one is selected. The text <Select a domain> has been moved to the combo box for domains in the role assignment wizard's pages. To become SQL92 compliant and support more databases, we have renamed to columns in the database. The renaming will happen automatically first time the database is accessed with 7.01. From this time on, NetOp 7.00 will NOT be able to successfully use the database, and so all security servers must be updated simultaneously. It is advised to run the NetOp Security Manager (NSM) as the first step after installing 7.01. NSM will echo what it does to the database and will report success or error. If an error occurs, you should manually rename "Lock" to "Lckm" in table DWROLE" mode" to "CBmode" in table DWUSERA Host ID Group named "Unregistered Host IDs" with ID=0 will automatically be added to the table named DWGRUH, the list of Host ID Groups. As a new feature in 7.01, one can add role assignments from Guest IDs or Guest ID Groups versus this new Host ID Group. Whenever the database is queried for the rights for the mentioned Guest ID or Guest ID Group against a Host that is not inserted in the table of Host ID's (named DWHOST), this role assignment will come in effect. This corresponds to what was called the default host group in the NetOp 6.x Access Server. In the original 7.00 design of NSM, the role named "Unknown Hosts' Role", was intended to handle this. The role is located in DWROLE, in the record with ID=4. This role is what you get when a query for rights cannot find any matching role assignment records. It would cover up for Host IDs not registered in the database, but it would grant everybody these same rights. With "Unregistered Host ID's", you can assign different rights to unknown Host IDs depending on the Guest ID. In 7.01, the name of the role number 4 is now "Unassigned Hosts' Role, because this seems more appropriate. If you continue on a database created with 7.00, the old name will persist. There have been requests to translate the names of the built-in roles and of the columns. We have not be enable to accomplish this. The columns must be in English as created by NetOp. However, you may freely change the names of the built-in roles if you can find a third-party database client able of doing it, and you may likewise change the name of the records with ID=0 in the DWGRUH table ("Unregistered Host IDs"). NetOp only recognizes these records by their ID field, the name is merely a cosmetic attribute. Web Download NetOp Remote Control version 7.01 updates available for download from www.netop.com are now digitally signed to protect users from damaged, modified or counterfeit software. The digital signature can be verified under Windows by right-clicking the download executable (e.g. UK.EXE), selecting properties and then the digital signatures tab. Genuine Danware Products should be signed by Danware Data A/S using a Verisign class 3 certificate. When the new-signed files are run directly or from Internet Explorer, a new wizard interface guides the user through the process of either installing NetOp directly or saving the setup files to disk for later use on the same or other computers. Corrected errors All the error descriptions listed below have been fixed in this version. Communication When using an outgoing Gateway, it would call out on two lines, if one of the modems were slow to hangup. Calling a Host from the ActiveX Guest using <address>:<port number> did not work. Copenhagen, January 2002 Page 3 of 5
Random TCP/IP station address can be disabled in NETOP.INI as old (6.0, 5,4) version of MAC/IP address check are unable to handle the extra random station ID: [TCPIP] ENH_IP_ADDR=1 Default value is 1 meaning that it s enabled. To be compatible with 6.0 and 5.4 set the value to 0. Call back didn't work when encryption was enabled. Security In the Security Manager permitted Guests for a Host ID did not show the Host ID Groups that this Host ID is member of. Only the Host ID was listed. In the Security Manager, NetOp Definitions, Hosts ID, Permitted Guests dialog did not display the permitted Guests ID or Guest ID groups. The Security Server queries with NetOp Guest versus NetOp Host took very long time if there were many Hosts and Guests. In the Security Manager sorting of domains, users and groups in combo boxes did not work correctly. The Host was unable to show local groups when using Windows Security Management. Graphics The Eudora mail client program may crash when being remote-controlled or demonstrated by NetOp in the default NetOp command mode. This has been observed on Windows 98 but may also affect Windows 95 and Windows ME. Windows XP / 2000 / NT are unaffected. This happens because Eudora makes an invalid graphics call that is processed by NetOp for transmission. The processing done by NetOp passes the invalid call from Eudora to an additional Windows function that tries to return an error to NetOp but crashes due to a bug in the Windows function itself. A bug in some older Matrox display drivers for Windows ME / 98 / 95 could cause NetOp to display horizontal black stripes across most of the display when trying to transfer the screen of a computer with an affected display driver. With Windows ME / 98 / 95 some combinations of display drivers and applications could fail in NDDHHST9.DLL. Installation Misc. The NetOp CD contains a rarely used utility to copy the setup files to a set of floppy disks for use on computers without CD-ROM drives. The diskette creation utility (MAKEDISK) would display an error message at startup and then only allow exit from the utility. The Name Server database was limited to a destination path no longer than 39 characters. NetOp installation didn t work without the 16 bit subsystem on Windows XP / 2000 / NT. Changed the error message appearing when the user tries to install NetOp on Windows XP / 2000 / NT without being member of the local administrators group. When the 7.0 Guest was updated from a Guest that was previously upgraded from a 5.x or 6.x the phonebook, Scripts, recordings and history was unconditionally updated from an original pre 7.0 Guest. Some valid serial numbers on the Linux Guest were rejected when entered. When you check or uncheck the "load host at windows startup "option in all types of a Host you may receive the following error message: Error accessing the NetOp Host service, try again. If the error persists check your configuration and security permissions and try logging on as an administrator. In Copenhagen, January 2002 Page 4 of 5
older NetOp versions you may receive a numeric error code. The message was harmless and could be ignored. On some Windows 2000 servers, the Host would refuse to load at boot displaying meaningless error messages regarding profile directories. Older NetOp versions are not affected. This would happen if the security on the registry keys \\MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion and \\MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders were too strict. NetOp needs read access to these keys in order to function properly. The Guest hot key did work correctly. NetOp on Terminal Servers now uses a single NETOP.INI and not user NETOP.INI. On Windows 2000 and later, terminal services automatically virtualizes INI files such as NETOP.INI. This causes confusion to NetOp users because NetOp is designed to need only a single shared NETOP.INI file. To avoid the issue, the NetOp executables have now been marked as "Terminal Services Aware". The executables have really been terminal services aware since some versions back, the bit in the program telling Windows this was the case just wasn't set. Remote print didn't work when encryption was enabled. The NetOp commands to reboot or shut down Windows XP / 2000 / NT sometimes failed. Write protected configuration files crashed the Guest program. Export or import of Wake on LAN MAC address from and to phonebook entries wasn t included. The address must have the following format:0x123456789012. The ActiveX Guest would display erroneous extra mouse movements when moving the Host mouse. The print redirector port monitor was using a record maximum of 10000 bytes, but the Windows XP spooler sends records of 65536 bytes. The limit for spooler record sizes has been removed. Copenhagen, January 2002 Page 5 of 5