UniKey Network Monitor Tool: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
[[category:UniKey Network Monitor Tool]] | [[category:UniKey Network Monitor Tool]] | ||
[[category:UniKey_Tools]] | |||
Revision as of 17:25, 2 May 2012
Getting Started
Install Unikey Network Service
The NetUniKey service is an application that runs in the background, which enables the network connections for UniKey dongles to operate over a network.
To install the service, please navigate to the network folder:
UniKey SDK->Network->Server->Network.Server.ia32.
File:UniKey Network Monitor Pic01.jpg
Open the Server folder and right click on the “Install.exe” icon.
File:UniKey Network Monitor Pic02.jpg
Click on “Run as administrator”
A command-line installation window will pop up
There are two options:
[A] Install the NetUniKey service and Run it now
[B] Uninstall the NetUniKey service
Enter A and press enter to install
Uninstall Unikey Network Service
To Uninstall UniKey Network Service please repeat the same operation as installation of the UniKey Network Service, when the command-line window appears, please input b and press enter. The service will uninstall automatically. After uninstalling successfully, the command-line window will close.
Network Server Console
UniKey Network Server Console is a tool that helps users to monitor client connections, set up servers, and manage black and white IP Lists.
Please double Click on the “NetUniKeyServer” icon in the Server folder.
The UniKey Network Server Console will appear.
In the Monitor section, it shows the connected clients in detail, including:
• Client IP Address
• computer name
• Client working Mode – how the Client find UniKey
• HID – UniKey HID which the client connect to
• GUID – each connection will be assigned with a unique ID
Users can click [Refresh] button to update the server status
Disconnect an IP
To disconnect a connection with the corresponding client, you can select that item, then click [Kill] or click [Kill All] to disconnect all connection.
Service Manager
By clicking the Service Manage tag, you can check the server’s status and configure the server.
You can start or stop Service and Network just by clicking the [start] or [Stop] button respectively.
The green dot next to Service and Network indicate both of them are working properly. If the dot turns red, it indicates that the corresponding function has been stopped.
Configuration of the server
When the server has more than one IP Address, click the Server IP address drop down menu, you can select different IP Address as the server’s address. And define the connect port value.
Times limit(s) – defines an interval that the server will check client connection. If the client has no response in that period, the server will close the connection.
By Picking the Auto Start option, you can let the service run automatically when the server starts.
Click [Refresh], you can update the server status, and click [OK] to confirm all settings.
Black IP list
IP Addresses which are listed in black IP list cannot connect to the server.
To enable this function just pick the “Enable Black List” option on top of the panel.
Add an IP address to the black list
Click [Add]. A Server window will pop up, and input Start IP Address and End IP Address.
Click [OK] to confirm
The segment of IP Addresses will be added into the black IP list, and is shown in the message box.
To delete an item from the list, just select the item and click [delete]
Click [Refresh] to update Black IP List
White IP list
Only IP Addresses listed in this White IP List can connect to the server.
The configuration of White IP List is same as the configuration of Black IP List
Client Configuration
In this part, we will describe how to configure the client computer, including working mode, access mode and Server information. To set up the working mode and access mode there are two ways, by modifying the NetUniKey.ini file or by using API. We will introduce NetUniKey.ini file modification first.
Open the Client Folder in the SDK, located in:
SDK->Network->Client
There are two sub-folders:
Libraries
Includes all the libraries for various programming languages for clients
Samples
Includes all the samples for various programming languages for clients
Configuration file
Open the Libraries Folder and double click NetUniKey.ini file, and The file will be opened by Notepad.
In this file you can configure your client computer.
WorkingMode defines how the client find Unikey hardware, and there are 4 options:
1. Client will only try to find Unikey from local computer.
2. Client will only find UniKey from network
3. The default setting, client will firstly find UniKey from local computer, if not find, it will find Unikey from network.
4. Client will firstly try to find UniKey from network, and if not find, it will find UniKey from local computer.
AccessMode defines how the client find UniKey from network, and there are 3 options:
0. Per IP address mode, which indicating you can do logon UniKey(logon UniKey as a Client User) once for one computer.
1. Per process mode, indicating you can do logon UniKey for one application once, and you can run many applications to logon UniKey on one computer.
2. Per thread mode, indicating you can do logon UniKey many times for one application and you can run many applications to logon UniKey on one computer.
ServerIP: Refers to the server’s IP address
Port: The connection port number
TimeOut: Send/receive out value in second
Alternative methods of configuration
The other way is to use API in the libraries, the steps are shows as below:
For the UniKey_Find function, you need to assign a value to lp1 and lp2 parameters.
retcode = UniKey_Find(&handle[0], &lp1, &lp2);
lp1 and lp2 are WorkingMode and AcessMode respectively.
If you want to modify the WorkingMode and the AccessMode directly from the NetUniKey.ini file, please assign lp1’s value and lp2’s value greater than 5.
The ServerIP in NetUniKey.ini file should be the same as the server's IP address. Please modify the ServerIP according to the server's IP address.
The 105 error code is caused by firewall. It is NECESSARY to close the firewall at both the server side and the client side.











