These are the steps you need to follow to correctly install the network dongle on the server, and to configure the client machines to use it:

1. Copy DDNET.exe and SetupDrv.exe from one of the client machines to the ‘dongle server’ (the server machine where the network dongle is plugged in). You can find these files in C:\Program files\ ATRIL\Deja Vu X\Dongle.
2. With the dongle unplugged, run SetupDrv.exe to install the dongle drivers on the server (the client machines don’t need to have them installed, since the dongle is not attached locally). Once the drivers are installed, please connect the dongle and let Windows recognize and configure the hardware.
3. Move the copy of DDNET.exe to a permanent folder (e.g. C:\Program Files\ATRIL\Dongle). We will be configuring DDNET to run as a service later, so it needs to be accessible.
4. On the server machine, you will need to create a network share (i.e. share a directory on the server) to which all the workstation machines have full access rights. You will need to set these rights not only in the Share Permission tab for the directory, but also in the Security tab for it. This share will be used by the server and the clients to communicate.
   You can test that this share is configured correctly by opening the shared folder with Windows Explorer from one of the client computers. If Windows Explorer cannot browse the folder over the network, Déjà Vu X won't be able to use it either.
5. Now that we have a path for the network dongle to use, we need to configure the DDNET service. To do this, you need to run DDNET.exe with the following command line parameters:
   

   DDNET /Ipath /s

   
   where is the local path of the shared folder; please note that there should be no space between the /I and the path (e.g. DDNET /IC:\MyDongleShare /S).
6. Now, we need to configure the clients. In the \Dongle sub-folder of the Déjà Vu X installation folder of the clients, you will find a file called DV2.INI. You need to edit this file and change the value of the DinkeyNetPath line to point to the network share you created in step 4.
7. Once you have changed DV2.INI, copy it to your C:\WINDOWS folder.
8. Repeat steps 6 and 7 on all the client machines (or just copy the DV2.INI file you modified on the first client to the C:\WINDOWS folder of all the other client machine).

If you are using Déjà Vu X2, you can read the Network Dongle Installation Guide here.

About Network Dongles

In order for the Network dongle to work correctly you need to install DinkeyServer on the computer that the dongle is connected to. On the client machines, Déjà Vu X3 will automatically search the network for DinkeyServer, so no configuration is required for the clients to communicate with the server.

Installing and Configuring DinkeyServer

The Déjà Vu X3 installer places a copy of the Dinkey Dongle Network Server in Déjà Vu X3’s installation directory, called dinkeyserver.exe.

To install DinkeyServer simply copy it to a directory on the machine that the Network dongle is attached to. This can be any machine on the network – it does not have to be the network server. Note that the installation and configuration of the server must be done by an Administrator, or a user with an Administrator’s privileges.

To configure DinkeyServer first run it and then select the appropriate options from the configuration dialog:

1. Choose to run DinkeyServer as an Application or as a Service.
   A Service starts automatically when Windows boots and does not require a user to be logged in for it to run. Starting DinkeyServer as a Service is the recommended setting for normal use.
   An application requires a user to be logged-on for it to run; this may not always be feasible on server machines. If you choose to run DinkeyServer as an application and want to have it start automatically when the user logs in, then you must create a shortcut to DinkeyServer in that user’s Startup folder and specify the appropriate command-line parameters to make DinkeyServer start automatically.
   Normally, the only time you may want to start DinkeyServer as an application is if you want to test it.
2. In the Advanced section, you will need to choose the IP Address which DinkeyServer will accept connections on. If your machine has only one IP Address then this will be pre-selected for you and cannot be changed. You will also need to choose a port number which the server will listen for connections on. Choose any one from the list and keep a note of it in case you need to configure your firewall later on. If that port is already being used then when DinkeyServer is started it will ask you to select another port.note

To start DinkeyServer click the Start button. It will then either run as an application and launch the viewer screen or install itself as a service and run in the background. You will need to have Administrator rights to setup a new service.

Using DinkeyServer

The DinkeyServer Viewer

When DinkeyServer is running as an Application, it will display the DinkeyServer Viewer. This utility displays the status of DinkeyServer, the Product Codes it is serving and the network users currently connected to it. A DinkeyServer icon will appear in the Windows System Tray.
You can also open the server’s log file using this utility. The log file records important events during the running of the server and may need to be viewed to diagnose problems.
When DinkeyServer is running as a Service, it will not display the viewer because Services cannot display Graphical User Interfaces (GUIs). However, you can still use the DinkeyServer Viewer by running DinkeyServer.exe with the /viewer command-line parameter.

Command-Line Parameters

DinkeyServer can accept several command-line parameters which control its behavior. These are as follows:

General Notes

Like any Service, DinkeyServer can be controlled through Windows Services Management (Control Panel > Administrative Tools > Services).

If you remove or add a dongle to the machine running DinkeyServer then you need to restart DinkeyServer in order for it to be detected.

If you have multiple network cards installed on your client machine then the protected program may fail to automatically detect DinkeyServer (this can also be caused by virtualization software, such as VMWare, installing "virtual" network adapters onto your system). In this case try disabling ones that don't connect to the LAN on which DinkeyServer runs.

Network

Firewalls

Failure to correctly configure your firewall(s) could result in DinkeyServer being inaccessible by client machines.

• Your firewall must allow both TCP and UDP traffic through to DinkeyServer.
• Your firewall must allow DinkeyServer to accept incoming connections on the IP Address and Port that you chose when setting up DinkeyServer.
• Clients (your protected software) auto-detect DinkeyServer by performing a multicast broadcast to 229.255.219.183 and whichever port you configured DinkeyServer to listen on. Your firewall must not block traffic destined for this address/port.

Like most server software, DinkeyServer accepts incoming connections by “listening” on a given IP Address and port. If the machine which runs DinkeyServer also runs firewall software (either the Windows one or a third party one) then the firewall software will need to be explicitly told to allow the incoming connections to get through to DinkeyServer. Likewise, if a firewall exists on a machine between the machine running DinkeyServer and the client machines then this will need to be configured too.note

Configuring Déjà Vu X3

Enabling support for the dongle

By default, Déjà Vu X3 does not support dongles as a method of activation. This means that Déjà Vu X3 will not be able to detect the network dongle even if everything else is configured correctly.

In order to enable support for the dongle in Déjà Vu X3 you must copy a specific DLL file to Déjà Vu X3’s installation folder.

If you need a copy of this DLL in order to enable support for the network dongle in your Déjà Vu X3 clients, contact Atril Support and request it.

Overriding DinkeyServer Auto-detection

If your network does not properly support UDP broadcast, Déjà Vu X3 will not be able to auto-detect DinkeyServer on the network. It is possible to override this behavior in the Déjà Vu X3 and instruct the program to look for the dongle in a specific place.

This is possible by creating a file called DVX2.ini. This file should be in Déjà Vu X3’s installation folder:

• In 32-bit versions of windows, this is usually the following: C:\Program Files\ATRIL\Deja Vu X3
• In 64-bit versions of windows, this is usually the following: C:\Program Files (x86)\ATRIL\Deja Vu X3

The folder names shown above may be different if your clients’ operating systems are in languages other than English.

This file will contain the IP address (or name) of the server that the Dinkey Server runs on as well as the port the server is configured to listen on. You specify this information by editing the file with a text editor and typing it yourself. The file uses the following syntax:

[ddpro]
server=<ip address>:<port> OR server=<machine name>:<port>
autodetect=FALSE

Where:

• the server key indicates either the ip address of the machine where DinkeyServer is located or the machine’s name. You should use one or the other, but not both.
• <port> indicates the value of the port you chose in DinkeyServer.
• The Autodetect key is used to tell Déjà Vu X3 if you want it to try to auto-detect the server if DinkeyServer was not found in the ip address and port you specified. The default value for this is FALSE.

An example of a correctly formated file is:

[ddpro]
server=192.168.1.4:32768
autodetect=FALSE

Configuring Déjà Vu X3

DinkeyServer maintains its own log file in which it records various important events during its execution. While the server is running, all events are recorded to this log file rather than being displayed on-screen. The most common reason for needing to view the log file is to begin diagnosing a problem.

You can view the logfile by running DinkeyServer with the /logfile command-line parameter. Alternatively, you can view it from the DinkeyServer Viewer.

The logfile is actually stored on disk in the “All Users” profile under the DinkeyServer/10016 directory.