| Q: |
What is Checkcode? |
| A: |
Ø Checkcode is one of the identification codes for IP-guard Server. Server based on the product code embedded in serial number and the Checkcode to identify the management right of agent. When installing IP-Guard Server at the first time, right click the Server icon, and select “ToolsàSet Checkcode”. Ø You may input the Checkcode manually, or it may be generated by the Server randomly. The default Checkcode is blank. After setting the Checkcode, Server will automatically send the updated Checkcode to agents. [We strongly recommend you record down your input Checkcode. Otherwise, if your server needs to be re-installed and you forget the previous Checkcode, the all corresponding agents may have to be re-installed too because the agent only records the last update Checkcode and the Checkcode is empty after the server re-installation]  Ø If the Server resets the Checkcode, the previous and the latest checkcodes will be saved in list. Ø If Agent’s current Checkcode matches with one of the Checkcodes recorded in Server, the Server would have right to manage that agent and then send the latest Checkcode to the agent. Ø Notice that the maximum no. of Checkcodes saved in Server is 99 and Agents only save the latest Checkcode locally. [Important] If the Agent computer is running normally but cannot be displayed inside the Console management windows, please go to “LogàSystem Log” and check whether it is the Checkcode verification problem. The error code for “Checkcode not matched” is 100. Consider the following cases would help you understand the purpose of Checkcode: n Scenario 1: Server A and Server B are installed in the same network 192.168.1.x, agent A is packed from Server A and agent B is packed from Server B. Server A and Server B have the same product code. - If no Checkcode are set in both servers, ideally Server A will manage agent A and Server B will manage agent B because they are packed from corresponding servers. - If Server B suddenly stopped and Server A applies Active Polling (see Figure 1), agent B will be managed by Server A  Figure 1 - However, when Server B starts up again, the agent B could not return back to Server Bautomatically as the Server A IP-address information is recorded in agent B. - If you want agent B back to Server B after Server B startup again, you can set the IP address of agent B in Server A’s exclude range (see Figure 2)  Figure 2 Conclusions for scenario 1: - If Checkcode is set in every server, agent B will not be managed by Server A because the Checkcode in agent B is not matched with Server A, so Server A cannot manage it. n Scenario 2: Server A and Server B are installed in two different subnets: 192.168.0.x and 192.168.1.x respectively. Agent A is packed from Server A and agent B is packed from Server B. These 2 servers have the same product code. - If both servers set the Checkcode, of course, agents in subnet 192.168.1.x will not be managed by Server A, or vice versa because the server must verify both the product code and Checkcode before connected with any agents u If Server A set with extend range 192.168.1.1 to 192.168.1.254, even the Server Bstopped by any uncertainties, the agents in subnet 192.168.1.x will not be managed by Server A as the Checkcode is not matched à you may check from the system log (LogàSystem Log). The error code is 100 if Checkcode is not matched - In our experience in IP-guard version 2, some clients may have 2 servers located in Hong Kong and China offices, they reported to us that some china agents appear in Hong Kong Server. Now, if you set the Checkcode in both servers, then the above situation would not happen anymore. |