Review the gateway configuration. Ensure the correct IP and port number has been entered.
Ensure all the gateway configuration files in the KNM\Gateway directory have been copied to the KNM folder of the host gateway machine.
If you have reinstalled the server on a new machine, the gateway configuration must be updated to update the public key file. After the gateway configuration is saved, move the gateway configuration files to the \Gateway root directory and restart the gateway.
If you changed the gateway configuration (IP number and port number) move the updated configuration files to the gateway and restart the gateway.
The server shuts down any gateway that does not match the server version number. Gateways can be updated directly from the Network Monitor management interface by choosing the Update gateway command on a selected gateway.
The gateway name is part of the server login session, if you change the gateway name you have to move the gateway configuration files to the gateway for it to be able to reconnect.
Logging debug information
To enable debug logging on the gateway, open the init.cfg file on the gateway and enter the following line: LOG_LEVEL=2. A debug file called debuglog.txt is written to the \logs directory.
Running the gateway in debug mode
Local gateway - To run the local gateway in debug mode you first need to stop the Kaseya Local Gateway (nmservicelg.exe) service on the system hosting the local gateway. When the service has been stopped start cmd.exe and navigate to the <KaseyaInstallDirectory>\knm\local_gateway directory. Start the gateway by entering the following line:
nmservicelg.exe -d
Remote gateway - To run a remote gateway in debug mode you first need to stop the Kaseya Network Monitor (nmservice.exe) service on the system hosting the remote gateway. When the service has been stopped start cmd.exe and navigate to the <KNMInstall> directory. Start the gateway by entering the following line:
