Installing with Windows installer


Currently the nds2-client Windows installer is only available for 64-bit Windows.

The nds2 client (version 0.14.2) installer for Windows 7 available at the moment is only 64 bits. You can download it from

Run the installer. The default options are reasonable if you don't know of a reason to change them.

An important dependency of the nds2 client is the authentification libraries. If you do not have them installed then the client will complain of missing gssapi64.dll. The recomended authentification package for Windows is MIT Kerberos. It is important that you get the 64 bit version. MIT does not have an installer for 64 bit Windows so it is advised to use the one provided by Secure Endpoints through their Heimdal release. Notice that they recomend installing first the 64 bit installer and then install the 32 bit installer on top of the previous one. I can confirm that the 2nd step was not needed, just installing the 64 bit installer was enough.

In order to test the nds2 client you would need to use the previously installed Kerberos (from the Start menu the executable is called "Network Identity Manager". Notice that you can set it up to start authomatically when you log in) to authenticate to LIGO.ORG, using the albert.einstein naming convention. From the menu 'Credential' choose 'Obtain new Credentials'. In the field 'Realm' insert: LIGO.ORG, in Username insert: your equivalent albert.einstein, then fill the Password field and you are ready to press OK.

Notice that you should only have this Credential active, if you have any other credential active at the same time causes issues with 'daq_connect' of the nds2 client. This error is obtained: error in gss_init_sec_contextError in daq_connect: Request SASL authentication protocol

Other reason to obtain a similar error message is by having the date and time on your computer considerably different to that of the nds2 server.

At this point we can confirm that the nds2 client is properly installed and communicating with the Ticket Manager by opening a command window and entering: cd C:\Program Files (x86)\nds2-client 0.14.2\bin nds2_query -l -n Check if you see the above error messages. If everything is working you will get a (long) list of available channels. If you see the dialog box complaining of a missing MSVCR100.dll library then you will need to install the Visual C redistribution libraries which can be downloaded for free from Microsoft. They come as an installer, and need to be run from an account with administrator privileges.

You may also want to add the nds2 client bin folder to the system variable PATH. In order to do this right click in 'Computer' and select 'Properties'. There click in 'Advanced system settings' for which you will need administrator privileges. On the tab 'Advanced' click on the button 'Environment Variables' and under 'System variables' choose the variable 'Path' then click 'Edit...' and in the 'Variable value' field ADD the folder: C:\Program Files (x86)\nds2-client 0.14.2\bin.