the main › Tips › Aladdin monitor does not see hasp: aladdin monitor. Aladdin monitor does not see hasp: aladdin monitor Hasp does not work

Aladdin monitor does not see hasp: aladdin monitor. Aladdin monitor does not see hasp: aladdin monitor Hasp does not work

Faced such a problem the other day. Refused to work on one of the machines network version of 1C Enterprise... When connecting to the base, the following error was thrown out:

I want to draw your attention to the fact that the error appeared on a computer on which there were 2 network cards with 2 different networks. For some reason, I did not immediately attach importance to this moment. Apparently because HASP monitor found these keys perfectly, which is why I was looking for a problem in 1C. As a result, he killed half a day's work time. The problem really lay in two network cards, or more precisely, 2 different networks, the solution was in the file C: \ Program Files \ 1cv81 \ bin \ conf \ nethasp.ini

Disconnecting the network, in which there are no HASP keys, after restarting the machine - 1C started up .... I got into Google for a solution to this problem. The search was not long in coming, the solution is the following:

I'll start with a little educational program:

1C: Enterprise 8 using a security system using hardware keys HASP, you can download the driver, monitoring program and HASP Loader service on the website http://www.aladdin-rd.ru/, specifically in the support section http://www.aladdin-rd.ru/support/downloads/hasp/.

Protection keys for 1C are divided into:

1. Single-user (must be physically connected to the computer running 1C)

model HASP HL Basic (of blue color ), this key is marked H4 M1 ORGL8, does not have built-in memory and personal ID, does not store any parameters and settings. Supplied with products licensed for one seat.

HASP network key

2. Multiuser (the key is on the network, 1C can run on any computer in within the local network or domain)

Network client keys include the series ( Red ). They have an internal memory that stores the number of licenses and a unique ID. There are varieties for 5, 10, 20, 50 and 100 users. Has markings NETXX ORGL8 , where XX- number of licenses (for example NET5 ORGL8 ). There are also keys for 300 and 500 users that are marked NET250 + ORG8A and NET250 + ORG8B ... Supplied with products licensed for 5 seats, as well as separately, in the form of additional client licenses.

Key for Server 1C

3. Server (must be physically connected locally to the computer on which the 1C Enterprise agent server is installed and running)

Keys for 1C Enterprise server are only local. 32-bit version has a security key HASP HL Pro (purple ), which has internal memory and a unique ID. Has markings ENSR8 , comes with a license for the 1C Enterprise server.

For 64-bit server key used HASP HL Max (green color ) with internal memory and unique ID. Has markings EN8SA and also supports 32 bit server. Those. having a license for a 64-bit server, you can use the 32-bit version without changing the key, but not vice versa.

For the operation of the single-user and server key, it is enough install the dongle driver on the local machine and insert the dongle into the local USB port.

For a multi-user (network) security key, you must:
1. Install the dongle driver on one of the machines in the network, which will be the dongle server - HASP4_driver_setup.zip
2. Install the server (service) of the protection key on the same machine - HASP_LM_setup.zip
3. Insert the security key into the server into the USB port
4. Install 1C on client machines

In general, these actions are enough for 1C to work. During the launch and further operation of 1C: Enterprise 8 on local machines, the system will use a broadcast request on port 475 and look for a security key. In case of unsuccessful search, a message will be displayed "No program protection key found" and work 1C: Enterprise will be interrupted.

If you are faced with the message „ program protection key not found“It is necessary to check:
1.presence of a security key in the usb port of the key server
2. check if the key server is running on the server (process named "Hasp loader")
3.check with the telnet command the availability of the key server from the local machine on port 475 (for example: telnet 192.168.100.100 475)

If all checks were successful, but the error persists, proceed to more detailed settings. In the 1C: Enterprise 8 installation folder (as a rule, c: \ program files \ 1cv81 \ bin \ conf or c: \ program files \ 1cv8 \ bin \) has a file nethasp.ini ... This is the security key configuration file, it is divided into sections, we are interested in the section ... When installing 1C, by default, all parameters in this section are separated by double characters ";", which means ignoring these settings. In this case, the key driver behaves as follows:
1.a broadcast type packet is sent over the local network on port 475 in search of the security key server
2.if no response is received - error

Disadvantages of the default configuration:
1.the broadcast takes some time
2.not all servers respond to such packets
3. Broadcast some, but the load on the network

To solve this problem, you need to do the following:
1.specify the specific address where to look for the key server (for example: NH_SERVER_ADDR = 192.168.100.100)
2. disable broadcast search (NH_USE_BROADCAST = Disabled)
3.and restrict packet types to TCP only (NH_TCPIP_METHOD = TCP)

As practice shows, the launch speed of 1C: Enterprise 8 after this setting increases noticeably!

But there are also some disadvantages of this method:

make sure that the address of the dongle server does not change, otherwise you will have to reconfigure the nethasp.ini file on all local machines!

I would also like to clarify a few points about working with keys that I had to deal with when working:

1. Monitor HASP does not show the key

By itself, the monitor can only show the presence of a license manager at a particular address. He will be able to see the key only after the protected application has successfully opened at least one session with the key. In addition, it should be borne in mind that Aladdin Monitor works only over UDP, port 475. Thus, the absence of data about the key in the monitor does not mean that the key is not available to the application.

2. Two keys of protection 1C HASP on one computer

When installing two or more HASP software protection keys on one computer, keep in mind that:

Keys with different series will work fine. (in relation to 1C: 1 server and 1 network will work fine)
Keys of the same series will work if this feature was implemented by the developer of the protected software. If the developer did not implement this feature, then the keys belonging to the same series will not work together on the same computer, only one of them will be visible: either the one closest to the port (in the case of LPT keys), or located on the port with the lowest address (in the case of USB keys for protecting HASP programs). (in relation to 1C, - 2 local or 2 network keys on one computer will work correctly, most likely they will not)
it is not recommended to put the local and network keys together, this is due to the security feature of 1C Enterprise: when it finds a local key, the program will never look for a network key.

Possible solutions to this problem:

Replacing several protection keys for HASP programs with one, with a larger number of licenses (it is well written about this here: http://v8.1c.ru/predpriyatie/questions_licence.htm).
Installing protection keys on different computers with subsequent installation and configuration of license managers for each key.

3. Two or more License Managers on the network

If you have two or more network keys, it is not always enough to distribute them to different computers. The license managers must be configured. Each license manager must have a unique name that must be explicitly communicated to the protected program. It is recommended to perform the same configuration when using a terminal server, even with the same network key.

Find the file on the machine where the key is installed nhsrv.ini in the folder with the license manager. The NHS_SERVERNAMES parameter is responsible for the name of the license server; it can consist of Latin letters and numbers and contain no more than 7 characters.

NHS_SERVERNAMES = NAME1

After that, on the client machines, it is advisable to edit the nethasp.ini file, explicitly specifying the addresses and names of the license managers:

NH_TCPIP = Enabled NH_SERVER_ADDR = 192.168.0.10, 192.168.0.11 NH_SERVER_NAME = NAME1, NAME2

Well, like I described all the nuances, if I remember anything, I will definitely add it! Bye everyone!

Regards, Mc.Sim!

Aleksey1989

17.02.13 — 19:18

Good evening. Such a problem: there are 2 computers, each of which has network keys for 5 users. Hasp LM is installed on one of them as a service, and Alladin Monitor is also installed on this computer. Duck, this Alladin Monitor shows only the keys of the computer on which it is installed, it does not see the keys of another computer. Why?

P.S. computers, of course, are on the same local area network.

mrBlutig

1 — 17.02.13 — 19:20

hasp ini configured?

Aleksey1989

2 — 17.02.13 — 19:21

(1) Yes, it contains the ip-addresses of these 2 computers.

ansh15

3 — 17.02.13 — 20:25

And how is HASP LM installed on the second computer?

Armando

4 — 17.02.13 — 20:36

http://safenet-sentinel.ru/helpdesk/faq/

Aleksey1989

5 — 17.02.13 — 20:39

(4) “The monitor itself can only show the presence of a license manager at a given address. He will be able to see the key only after the protected application has successfully opened at least one session with the key. "

Those. it turns out that in order for this key to be displayed in the aladdin monitor, you must first use all the licenses of the local computer.

Aleksey1989

6 — 17.02.13 — 20:41

(3) the license manager is not installed on the second computer.

ansh15

7 — 17.02.13 — 20:46

(6) Well, put it on.

Aleksey1989

8 — 17.02.13 — 20:52

(7) Why is it needed at all on the 2nd computer? As far as I remember, one license manager is enough for one LAN, please correct if I'm wrong.

shuhard

9 — 17.02.13 — 20:55

(8) [one license manager is sufficient for one LAN]
aladdin doesn't think so

Aleksey1989

10 — 18.02.13 — 09:43

(7) Delivered, no changes.
By the way, this question: the manager set the license as a service, I go to the "Services" - I can not find it there. Why? What is it called?

ansh15

11 — 18.02.13 — 13:02

(10) Sentinel HASP License Manager.
In nethasp.ini, which is in the folder for the monitor, specify the addresses of these computers. Two license managers should appear on the monitor.

Aleksey1989

12 — 18.02.13 — 13:22

(11) Strange, this service (Sentinel HASP License Manager) is not in the list of Windows services.
I edited nethasp.ini in the folder for the monitor - it did not help.

Aleksey1989

13 — 18.02.13 — 13:57

That's it, I won: it turns out it was necessary to restart the computer where the license manager is located, after that everything worked.

ATTENTION! Ctrl-F5 or Ctrl-R

The topic has not been updated for a long time, and was marked as archived. It is not possible to add messages.
2000 Human.

Z_a_b_a_v_a

11.01.11 — 13:16

Tell me where you can download the driver for the Hasp key for 1c8.1 for Windows 7 (64x).

Aladdin's website only has:

HASP4. Utility for installing the HASP4 program protection key driver under Win32 / Win64 (Windows 95/98 / ME / NT4 / 2000 / XP / Vista / 2003, Windows XP / 2003 x64)
-Driver HASP4. Utility for installing the HASP4 program protection key driver under Win32 / Win64 (Windows 98 / ME / NT4 / 2000 / XP / Vista / 2003, Windows Server 2008, Windows XP / Vista / 2003/2008 x64).
-HASP key driver for Linux
And Win7 swears that this OS is not supported. (everything is in order with the rights in Windows)

Maxus43

1 — 11.01.11 — 13:23

http://www.aladdin-rd.ru/support/faq/634/#faq27952

Z_a_b_a_v_a

2 — 11.01.11 — 13:41

Cheers thanks!

HASP4 - cursed that OS is not supported
HASP HL and HASP SRM - earned

MaxS

3 — 14.01.11 — 22:00

(2) 1C 8.2 Windows 7 x64 Home Basic
The 1C network key for 5 licenses did not work over the network.
Aladdin's monitor shows that this computer has HASP License Manager version 8.320
What to do next? where to watch what versions?
The firewall turned off.

hhhh

4 — 15.01.11 — 00:59

where is the key inserted? There and put the HASP License Manager

Red fox

5 — 15.01.11 — 01:15

Locally, it works with the "Use hardware license (security key)" flag. If you uncheck the flag, it doesn't work.
And it shouldn't. This flag is responsible for obtaining a license through the server. Key search order: first the local key, then the network key, then on the server. Therefore, work with the network must be checked with another computer.

zak555

6 — 15.01.11 — 01:21

(0) why download?

MaxS

7 — 15.01.11 — 10:56

Windows 7 x64 won 😉 Probably reading the instruction HASP_License_Manager \ 135-Install_LM_Under_Windows_7.pdf from the file HASP_LM_setup.zip helped or in Russian there:
http://www.aladdin-rd.ru/support/faq/29188?print=Y&ID=29188

Drivers and software downloaded there:
http://www3.safenet-inc.com/support/hasp/enduser.aspx#latestDD
Sentinel_HASP_Run-time_ setup.zip
HASP_LM_setup.zip

(4) was frightened at first by the absence of the corresponding service in the usual place.

HASP License Manager - hardware license manager for 1C

it ended up under a different name "Sentinel HASP License Manager"
(5) if you connect to the computer on which the network key is connected via RDP, then 1C can access the local network key over the network, and this can be seen in the Aladdin Monitor.
If via Remote Admin or TeamViever, then using only one computer it was not possible to check the operation of the key over the network 😉

(6) Do key drivers supplied with the latest 1C 8.2 platform work everywhere? It seems to be installed on any Win OS. But if before that the drivers from Sentinel_HASP_Run-time_ setup.zip were installed, the system swears - "replace with an older one ...?"

Put things in order in your work using the configuration 1C "IT department management 8"

ATTENTION!

If you have lost the message input window, click Ctrl-F5 or Ctrl-R or the "Refresh" button in the browser.

The branch has been archived. It is not possible to add messages.
But you can create a new branch and they will answer you for sure!
Every hour on the Magic Forum there are more 2000 Human.

1С 8.3 Linux X64 Key Hasp Emulator Average ratng: 3,9 / 5 3687votes

Installation 1. From Enterprise 8. Cent. Os 6. 3. How to install 1.

Aladdin

Categories: Sega
Review prepared by: Liza
App rating: 3.08 points
Updated date: 23.04.2016

Aladdin- this is an opportunity to replay your favorite game, which practically does not differ from the original and received a quick save function.

Its plot is the plot of a cartoon released in 1992, the story of what deeds and battles Aladdin had to go to to prevent Jafar from taking his place on the throne. And, as in the cartoon, Ginny - a loyal friend and comrade of Gin - will become his assistant in this difficult matter. But he also has another goal - this is the heart of the beautiful Jasmine and the battle for him will not be much easier.

Each level of this game is a new location and new characters, based on scenes from the cartoon with numerous enemies and traps.

Why Aladdin Monitor Can't See the Key

Sometimes these are guards armed with curved sabers, which your hero can throw throwing apples or use the same sharp saber against them.

The game Aladdin was very popular on Sega and now all of its heroes have got a second life and will be able to fight with each other again. All of them are very lively and cheerful, they constantly take risks and are ready to do anything to cheer and please you. Everything that happens on the screen looks like a cartoon, and the main character is an exact copy of his cartoon prototype. That is why there are so many children among the players.

Download the game Aladdin for sega on android and you. Perhaps, with your help, its main character will be able to quickly achieve his goal: he will fall in love with Jasmine and defeat his worst enemy Jafar.

The article is a copy of the blog! In case of questions, the link at the end ..

Faced such a problem the other day. The network version of 1C Enterprise refused to work on one of the machines. When connecting to the base, the following error was thrown out:

I want to draw your attention to the fact that the error appeared on a computer that had 2 network cards with 2 different networks. For some reason, I did not immediately attach importance to this moment. Apparently, because the HASP monitor detected these keys perfectly, which is why I was looking for a problem in 1C. As a result, he killed half a day's work time. The problem really lay in two network cards, or more precisely, 2 different networks, the solution was in the file

C: \ Program Files \ 1cv81 \ bin \ conf \ nethasp.ini

Disconnecting the network, in which there are no HASP keys, after restarting the machine - 1C started up .... I went to Google for a solution to this problem. The search was not long in coming, the solution is the following:

I'll start with a little educational program:

1C: Enterprise 8 uses a protection system using hardware keys HASP, you can download the driver, monitoring program and the HASP Loader service on the website http://www.aladdin-rd.ru/, specifically in the support section http: //www.aladdin -rd.ru/support/downloads/hasp/. Protection keys for 1C are subdivided into: 1C1 single-user key. Single-user (must be physically connected to the computer running 1C)

model HASP HL Basic (blue), this key is marked H4 M1 ORGL8, has no built-in memory and personal ID, does not store any parameters and settings. Supplied with products licensed for one seat. Multiuser key 1C

HASP network key

Download Center

Multi-user (the key is on the network, 1C can run on any computer within the local network or domain)

Network client keys include the HASP HL Net series (red). They have an internal memory that stores the number of licenses and a unique ID. There are varieties for 5, 10, 20, 50 and 100 users. It is marked NETXX ORGL8, where ХX is the number of licenses (for example, NET5 ORGL8). There are also keys for 300 and 500 users which are marked NET250 + ORG8A and NET250 + ORG8B. Supplied with products licensed for 5 seats, as well as separately, in the form of additional client licenses. HASP servo key

Key for Server 1C

3. Server (must be physically connected locally to the computer on which the 1C Enterprise agent server is installed and running)

Keys for the 1C Enterprise server are only local. The 32-bit version has a HASP HL Pro security key (purple), which has an internal memory and a unique ID. It is marked ENSR8 and is supplied with a license for the 1C Enterprise server.

For a 64-bit server, a HASP HL Max key (green) with internal memory and a unique ID is used. It is marked EN8SA and also supports 32-bit server. Those. having a license for a 64-bit server, you can use the 32-bit version without changing the key, but not vice versa.

For the single-user and server dongle to work, it is enough to install the dongle driver on the local machine and insert the dongle into the local USB port.

For a multi-user (network) security key, you must: 1. Install the security key driver on one of the machines in the network that will act as the key server - HASP4_driver_setup.zip 2. Install the security key server (service) on the same machine - HASP_LM_setup.zip 3. Insert the security key into the server into USB port 4. Install 1C on client machines

In general, these actions are enough for 1C to work. During the launch and further operation of 1C: Enterprise 8 on local machines, the system will use a broadcast request on port 475 and look for a security key. If the search is unsuccessful, the message “the program protection key was not found” will be displayed and 1C: Enterprise will be terminated.

If you are faced with the message “the program protection key was not found”, you need to check: 1. the presence of the protection key in the usb port of the dongle server 2. check if the dongle server is running on the server (process named “Hasp loader”) 3. check the server availability with the telnet command key from the local machine on port 475 (for example: telnet 192.168.100.100 475)

If all checks were successful, but the error persists, go to more detailed settings. In the 1C: Enterprise 8 installation folder (as a rule, c: \ program files \ 1cv81 \ bin \ conf or c: \ program files \ 1cv8 \ bin \) has a nethasp.ini file. This is the security key configuration file, it is divided into sections, we are interested in the section. When installing 1C, by default, all parameters in this section are separated by double characters ";", which means ignoring these settings. In this case, the dongle driver behaves as follows: 1. a broadcast type packet is sent over the local network on port 475 in search of the security dongle server 2. if no response is received - an error

Disadvantages of the default configuration: 1. it takes some time for broadcast 2. not all servers respond to such packets 3. broadcast is not at all, but the load on the network

To solve this problem, you need to do the following: 1. specify the specific address where to look for the key server (for example: NH_SERVER_ADDR = 192.168.100.100) 2. disable broadcast search (NH_USE_BROADCAST = Disabled) 3. and restrict the packet types only to the TCP protocol (NH_TCPIP_METHOD = TCP )

As practice shows, the launch speed of 1C: Enterprise 8 after this setting increases noticeably!

But there are some disadvantages of this method:

make sure that the address of the dongle server does not change, otherwise you will have to reconfigure the nethasp.ini file on all local machines!

I would also like to clarify a few points about working with keys that I had to deal with during my work: 1. Monitor HASP does not show the key

When installing two or more HASP software protection keys on one computer, keep in mind that:

Keys with different series will work fine. (in relation to 1C: 1 server and 1 network will work normally) Keys of the same series will work if this feature was implemented by the developer of the protected software.

If the developer did not implement this feature, then the keys belonging to the same series will not work together on the same computer, only one of them will be visible: either the one closest to the port (in the case of LPT keys), or located on the port with the lowest address (in the case of USB keys for protecting HASP programs). (in relation to 1C, - 2 local or 2 network keys on one computer will most likely not work correctly) it is not recommended to put the local and network keys together, this is due to the security feature of 1C Enterprise: when finding a local key, the program will never look for a network ...

Possible solutions to this problem:

Replacing several protection keys for HASP programs with one, with a larger number of licenses (it is well written about this here: http://v8.1c.ru/predpriyatie/questions_licence.htm). Installing protection keys on different computers with subsequent installation and configuration of license managers for each key.

3. Two or more License Managers on the network

On the machine where the key is installed, we find the nhsrv.ini file in the folder with the license manager. The NHS_SERVERNAMES parameter is responsible for the license server name, it can consist of Latin letters and numbers and contain no more than 7 characters.

NHS_SERVERNAMES = NAME1

After that, on the client machines, it is advisable to edit the nethasp.ini file, explicitly specifying the addresses and names of the license managers:

NH_TCPIP = Enabled NH_SERVER_ADDR = 192.168.0.10, 192.168.0.11 NH_SERVER_NAME = NAME1, NAME2

Well, like I described all the nuances, if I remember anything, I will definitely add it! Bye everyone!

Protection of the 1C: Enterprise system can be built on the use of the HASP4 Net network protection system. In this case, users can be counted either by the server side of 1C: Enterprise, or by a special program - HASP License Manager. This article is dedicated to installing the HASP License Manager and setting up the 1C: Enterprise system to work with it.

Security keys and their labeling

HASP4 Net hardware dongles are connected to the USB ports of the computer. The total number of users who can work with the 1C: Enterprise system is equal to the sum of available licenses from all computers in the network to which the hardware keys are connected and the HASP License Manager is configured.

Dongles are like a USB flash drive and look something like this:

They can differ in color and markings. By marking, you can determine what kind of key it is: for which software products it is suitable and how many licenses it provides.

ORGL8- Local client key;
NET5 ORGL8- Multi-user client key for 5 users;
NET10 ORGL8- Multi-user client key for 10 users;
NET20 ORGL8- Multi-user client key for 20 users;
NET50 ORGL8- Multi-user client key for 50 users;
NET100 ORGL8- Multi-user client key for 100 users;
NET250 + ORG8A- Multi-user client key for 300 users;
NET250 + ORG8B- Multi-user client key for 500 users;
ENSR8- Local key of a 32-bit server;
EN8SA- 64-bit server local key.

For example, the photo above shows a multi-user client key for 5 users. It should be noted that only one key of each series (ORGL8, ORG8A and ORG8B) can work on one computer. If several keys of the same series are connected to one computer, then only one of them, chosen at random, will be used.

Installing the protection driver

HASP Device Driver must be installed on those computers to which hardware protection keys are directly connected. This driver is included in the 1C: Enterprise package and can be installed from the Start menu:

Installing the Protection Driver from the Start Menu

Or from the command line:

C: \> "Program Files \ 1cv8 \ common \ haspdinst.exe" -i

For Linux OS, you need to download the driver from the SafeNet website. The downloaded archive contains DEB package for Ubuntu / Debian, RPM package for RedHat / SuSE and script for automatic installation. Let's try the version with a script, for this we download and unpack the required archive. Next, let's make the dinst executable file and run it:

sudo chmod + x ./dinst

The result will look something like this:

It is recommended to install the driver in any operating system with a disconnected USB key.

The HASP License Manager distribution can be found on the SafeNet website. When installing on Windows OS, you will need to select the installation option - an application or a service, usually a service is selected:

On Linux, installing HASP LM looks a little more complicated. The archive from the SafeNet site contains two RPM packages for RedHat and SuSE (probably for these systems HASP LM installation is quite simple) and a compressed hasplm file for everything else. Following the instructions from the ITS website, I was unable to run the hasplm file on Ubuntu 16.04.

Therefore, I had to use a solution from Etersoft. Go to the company's FTP and find the version you want. For my 64 bit Ubuntu 16.04 I chose this version: http://ftp.etersoft.ru/pub/Etersoft/HASP/stable/x86_64/Ubuntu/16.04/. We download the files and first install the necessary packages, in my case I needed to install the make package:

sudo apt-get install make

and the libc6-i386 package (although I downloaded the 64-bit version of HASP LM, it is essentially still a 32-bit application and requires 32-bit libraries):

sudo apt-get install libc6-i386

after that, install the HASP LM packages:

sudo dpkg -i haspd_7.60-eter1ubuntu_amd64.deb

sudo dpkg -i haspd-modules_7.60-eter1ubuntu_amd64.deb

We restart the service:

sudo service haspd restart

As you can see from the screenshot, the settings file is located here: /etc/haspd/hasplm.conf.

Customization

nhsrv.ini

On Windows, the nhsrv.ini file can be located in various locations:

directory with installed HASP LM (for example, C: \ Program Files (x86) \ Aladdin \ HASP LM);
Windows directory (C: \ Windows);
Windows system directory (C: \ Windows \ system32 or C: \ Windows \ system).

For Linux OS, the configuration file is specified using the "-c" parameter and its name and location are not defined by default.

HASP LM settings are set by the values of the parameters of the section of the nhsrv.ini file:

NHS_IP_LIMIT- defines the range of IP addresses served by the HASP LM. For example: 192.168. *. *, 192.168.1.1/24.
NHS_ADAPTER- defines the IP address of one or more network cards that will serve the HASP LM. Applies when using HASP LM with Win32. For example: 10.1.1.111, 255.255.0.0.
NHS_USERLIST- defines the maximum number of users simultaneously connected to HASP LM Default value: 250 (important for keys for 300 and 500 users).

nethasp.ini

To configure the interaction of the 1C: Enterprise system with HASP LM, the nethasp.ini configuration file is used. Despite the fact that in most cases no additional configuration is required, it is useful to be aware of the possibilities offered by this file.

The nethasp.ini file, in Windows OS, is usually located in the 1C directory (for example, C: \ Program Files \ 1cv8 \ conf), and in Linux OS, it can be located in the user's home directory or in the / etc directory.

The example below specifies that the security server is located at 192.168.0.12 and the TCP / IP broadcast mechanism is disabled.

NH_TCPIP = Enabled
NH_SERVER_ADDR = 192.168.0.12
NH_USE_BROADCAST = Disabled

Section

NH_IPX- to use or not to use the IPX protocol for communication with HASP LM, options: Enabled, Disabled (Enabled by default);
NH_NETBIOS- to use or not to use the NetBIOS protocol for communication with HASP LM, options: Enabled, Disabled (by default Enabled);
NH_TCPIP- to use or not to use the TCP / IP protocol for communication with HASP LM, options: Enabled, Disabled (by default Enabled);
NH_SESSION- sets the interval in seconds during which the program tries to establish a connection with HASP LM (2 seconds by default);
NH_SEND_RCV- sets the maximum time for receiving or sending a packet for HASP LM (by default 1 second).

The last two parameters can be used in all sections.

Section

NH_USE_SAP- use or not use the SAP service to search the HASP LM network, options: Enabled, Disabled (Enabled by default);
NH_USE_BROADCAST- use only the Broadcast mechanism to search the HASP LM network, options: Enabled, Disabled (Enabled by default);
NH_BC_SOCKET_NUM- defines the socket number (number in hexadecimal) for the broadcast mechanism (default: 7483H);
NH_SERVER_NAME- determines whether the application will exchange data only with the HASP LM located in the local network, or with any other HASP LM, options: localnet, Internet (Internet by default);
NH_DATFILE_PATH- the path to search for the haspaddr.dat and newhaddr.dat files containing the HASP LM network address.

Section

NH_NBNAME- sets the name of HASP LM (no more than 8 characters);
NH_USELANANUM- sets the number of the communication channel.

Section

NH_SERVER_ADDR- sets the IP addresses of the HASP LM servers (the number of addresses is not limited);
NH_SERVER_NAME- exchanges data with HASP LM with a specific name (maximum 6 names, each no more than 7 characters);
NH_PORT_NUMBER- sets the network port number (475 by default);
NH_TCPIP_METHOD- sends a TCP or UDP packet, access to HASP LM is always performed via UDP, regardless of the value of this parameter;
NH_USE_BROADCAST- use the UDP broadcast mechanism, options: Enabled, Disabled (Enabled by default).

That's all, I hope this article was useful to you.

Software products "1C: Enterprise" version 8 in addition can be protected from copying by hardware LPT or USB keys such as HASP4 Net from Aladdin. This article provides information on the type, marking and purpose of various HASP4 Net keys from 1C: Enterprise. And also an overview of software products from Aladdin, which are used to install, configure and administer these keys (for Windows operating systems).

1. Marking and assignment of keys

All HASP4 Net keys can be conditionally divided into 2 types "Client" and "Server":

The purpose of a specific key can be determined by its color and labeling... In the figures below, the key marking is highlighted with a frame. The rest of the symbols on the key have no special meaning for program users. The type and purpose of the key by marking can be determined from the table below:

Table of key types HASP 1C: Enterprise 8

Type / color	Marking / series	Appointment
SINGLE USER VERSIONS OF BASIC SUPPLIES AND CLIENT KEYS
	H4 M1 ORGL8	1C: Accounting 8 PROF 1C: Accounting 8 PROF. Supply for retail distribution 1C: Accounting 8 CORP 1C: Accounting of a budgetary institution 8 1C: Accounting of an autonomous institution 8 PROF 1C: Accounting of an autonomous institution 8 CORP 1C: Trade Management 8 1C: Salary and Personnel Management 8 1C: Salary and personnel of a budgetary institution 8 1C: Management of a small company 8 1C: Integrated Automation 8 1C: Enterprise 8. Manufacturing Enterprise Management 1C: Document flow 8 1C: Enterprise 8. Client license for 1 workplace
NETWORK VERSIONS OF BASIC SUPPLIES AND MULTIPLAYER KEYS
	H4 NET5 ORGL8	1C: Accounting 8. Set for 5 users 1C: Accounting 8 PROF for 5 users. Supply for retail distribution 1C: Enterprise 8. A set of applied solutions for 5 users
	H4 NET5 ORGL8	1C: Enterprise 8. Client license for 5 workplaces
	H4 NET10 ORGL8	1C: Enterprise 8. Client license for 10 workplaces
	H4 NET20 ORGL8	1C: Enterprise 8. Client license for 20 workplaces
	H4 NET50 ORGL8	1C: Enterprise 8. Client license for 50 workplaces
	H4 NET100 ORGL8	1C: Enterprise 8. Client license for 100 workplaces
	NET250 + ORG8A	1C: Enterprise 8. Client license for 300 workplaces
	NET250 + ORG8B	1C: Enterprise 8. Client license for 500 workplaces
KEYS FOR SERVER 1C: ENTERPRISE 8. *
	H4 M1 ENSR8	1C: Enterprise 8. Server license (x32).
	Max EN8SA	1C: Enterprise 8. Server license (x86-64).
KITS
		1C: Enterprise 8. Manufacturing enterprise management for 10 users + client-server. The delivery set includes two keys: Multiuser for 10 workplaces and for 1C: Enterprise 8. * (x32)
		1C: Comprehensive automation 8 for 10 users + client-server. The delivery set includes two keys: Multiuser for 10 workplaces and for 1C: Enterprise 8. * (x32)
		1C: Enterprise 8. Kit for training in higher and secondary educational institutions. The delivery set includes two keys: Multiuser for 20 workplaces and for 1C: Enterprise 8. * (x32)

The size of the USB keys may differ from the size of the keys shown in the pictures. The software products of the 1C: Enterprise system, produced before 2009, were completed with USB keys in a longer form factor - 52 mm. The color scheme and marking of the keys remained unchanged.

2. What you need to know when installing keys

There are several things to consider before installing HASP keys, namely:

The total number of users who can work with the 1C: Enterprise system is equal to the sum of licenses available in each of the client keys.
2 or more keys of one cannot work on one physical computer Series, since these keys are indistinguishable and in fact only one of them will be used (chosen arbitrarily). The key series can be identified by the last 5 characters in the marking (ORGL8, ORGL8A, ENSR8, etc.). Keys of different series can be installed on one computer without any problems.
Client keys can be installed on any computer in the network (if HASP License Manager is running).
If there are several keys, licenses are issued in the following order:
- in the key of the ORGL8 series
- in the key of the ORGL8A series
- in the key of the ORGL8B series
Also valid “Remembering the key”, that is, upon repeated access, an attempt will be made to obtain a license from the key, whose license was obtained by the user during the last connection.
The server key must be installed directly on the same computer that is used as the cluster server "1C: Enterprise"... It will not work over the network.
Server 64-bit keys can also be used on 32-bit systems.
There are certain problems with forwarding the server key from the physical to the virtual environment on some hypervisors. For example, I was not able to forward the server key to the virtual machine using standard tools.
COM connection also requires a license.
No CALs are required to run Web services.
Full algorithm for searching a license at the start of "1C: Enterprise" for the version 8.3 described, for version 8.2 — .

3. Features of accounting of client licenses

At startup, the 1C: Enterprise client can use the following to obtain licenses:

Local key- a key installed on a physical computer from which 1C: Enterprise is launched. Gives the right to launch an arbitrary number of system instances in 1C: Enterprise or Configurator mode on a computer with a key from under one Windows session. When working in terminal mode, it allows only one user to work, who connected to the terminal session with the identifier 0.
Multi-user key available over the network via HASP License Manager- Ensures the simultaneous operation of as many computers for how many users there is a key. Similarly to a local key on one computer in one Windows session, it is possible to launch an arbitrary number of system instances in any mode under one license. When working in terminal mode, the installation of the HASP License Manager is also required.
1C: Enterprise server or web server extension module- In addition to the HASP License Manager program, licenses can also be issued by the 1C: Enterprise server or by a web server extension module (only in the case of working with the file database via a web client). At the same time, the 1C: Enterprise server or a web server extension module is responsible for calculating licenses. In this case, in contrast to the two previous options, licenses are consumed on the basis of "one session - one license". Thus, if two copies of "1C: Enterprise" are running on one computer, then two licenses will be spent.

Besides it is very important to know and take into account the following feature: if several ORGL8 series multi-user client keys are found on the network, the server will select one arbitrary key. After exhausting the licenses of this key, it is possible to use one multi-user key ORG8A, and then it is possible to use one multi-user key ORG8B.

4. Programs for the administration of HASP keys

4.1 HASP Device Driver

At the time of this writing, version 6.62.1 was relevant. You can download it from the official website or from.

This is nothing more than a regular device driver. It is needed in order for the HASP4 Net key to be identified in the system. Install following the instructions of the installer.

4.2 HASP HL License Manager

from the official website or from.

The license manager is a utility that serves as a link between the network key and "1C" launched on a remote machine. HASP License Manager automatically creates a. However, for the protected application to work on a remote workstation, it is necessary to check that UDP and TCP packets pass freely through port 475 in both directions. It is desirable to install the manager as a service by selecting “ Service (nhsrvice.exe)"During installation.

Well, after installation, the corresponding service should appear.

When installing two or more license managers on the network, they must be configured for correct operation. Otherwise, there may be a collision on the network between license managers by names - at startup they accept the same name by default, and as a result, there are several resources on the network with the same names. It is worth noting that managers often work fine without customization. However, keep in mind that a problem may occur. In addition, configuration may be required, for example, to separate clients into different license managers. Read more about this.

4.3 Aladdin HASP Monitor

At the time of this writing, version 8.32.5 was relevant. You can download it from the official website or from.

This utility is used to monitor access to the key and occupied licenses. After installation and launch, the program scans the network in search of a license manager and shows active connections of client applications with these services. The monitor allows you to see the names of the hosts on which the service and HASP keys are installed, the maximum number of licenses in the key, the number of occupied licenses and the imine of clients who have received a license.

It should be understood that the monitor itself can only show the presence of a license manager at a particular address. He will be able to see the key only after the protected application has successfully opened at least one session with the key. In addition, it should be borne in mind that Aladdin Monitor works only over UDP, port 475, so for the program to work it is necessary. Thus, the absence of information about the key in the monitor does not mean that the key is not available to the application.

5. Viewing the received license in 1C

The list of all visible keys, as well as the place where the current license was obtained, can be viewed directly from 1C: Enterprise. It is enough to start 1C in 1C: Enterprise mode, select " reference» — « About the program…»Or click the exclamation mark icon on the panel.

In the window that opens, information about licenses can be viewed in the item " License».

Here we will see the key that issued the license to this user, as well as all the visible network keys. Information about issued licenses is also present in the 1C: Enterprise Server Administration Console in the list of infobase sessions (starting from platform version 8.2.15).

Did this article help you?

In the organization where I work, all software is licensed, incl. and 1C. Therefore, every time you install 1C, you need to install a protection driver in order for the program to start.

Somehow they asked me to install the platform on a laptop. I took the distribution kit and went to install the program. The installation went as quickly as usual, after which I clicked the "Install protection driver" menu item. An information window of the installer with the status of the installation progress appears on the screen. After a couple of seconds of waiting, the installer displays a message that the driver could not be installed:

Failed start the Aladdin Device Driver.

Failed to start a service in the Service Control Manager Database 0x2008007 0x0.

I forgot to say that the laptop is running Windows XP SP2. My further installation attempts

the drivers produced the same result. I tried to reboot the laptop, and log in as an administrator, and directly copy the driver files to the disk - everything is useless.

I decided to download the Hasp driver from his home site, that is, from www.aladdin.com (there is also a Russian site www.aladdin.ru). I downloaded it, started the installation ... I'm waiting ... Hurray! Installed! I'm launching 1C ... I'm waiting ... We've arrived! "Security key not found!"

What to do? After all, everything should work. Maybe a network? I check the connection with the server where the license manager is located - everything is fine. Strange ... I return to the Aladdins website, download diagnostic utilities that scan the network for Hasp "s, check - the key is visible on the network. I try to change the settings of the Nethasp.ini driver initialization file, where I specify the ip-address, port and sending method packages - did not help either. ”There was only one way out - yandex, rambler, google.

After a short search, I open another link and see a description of my situation. Fortunately, in addition to describing the problem, there was also a hint on how to solve it. So, it turns out that this situation can occur on some computers with Windows XP Service Pack 2.

Let's just say that the problem is solved in two moves. We find the boot.ini file in the boot disk (usually drive C, we MUST make a backup copy of it. Replace the "read-only" and "hidden" attributes, open it and find a line that looks something like this:

multi (0) disk (0) rdisk (0) partition (1) \ WINXP = "Windows XP RU" / fastdetect / NoExecute = OptIn

In this line, replace the parameters / fastdetect / NoExecute = OptIn with / fastdetect / Execute = OptIn

/ noguiboot / NOPAE, which will make the line look something like this:

multi (0) disk (0) rdisk (0) partition (1) \ WINXP = "Windows XP RU" / fastdetect / Execute = OptIn

/ noguiboot / NOPAE

This means that the system will boot without the driver signature verification service.

I reboot the system with the changed parameters, install the driver again - everything is fine, installed! RESTORED the boot.ini file to its original state, rebooted the laptop, start 1C - again "Security key not found!"

Back to yandex, rambler, google. I find something similar again. There it is advised to change some parameters of the Nethasp.ini file. Namely NH_USE_BROADCAST is set to Disabled, which means to disable broadcast messages. I did it as recommended, I run 1C ... THIS IS IT! FINALLY! WORKING!

In this way, a whole day (!) Was spent on installing 1C, which usually takes

maximum 20 minutes.

Popular in the heading: