12.07.2015 Views

NetSupport Manager Gateway - NetSupport Limited

NetSupport Manager Gateway - NetSupport Limited

NetSupport Manager Gateway - NetSupport Limited

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

The <strong>NetSupport</strong> Connectivity Server creates a log file that records activity through the<strong>NetSupport</strong> Connectivity Server. The log file name is gw001.log and is stored in thelocations specified in the <strong>NetSupport</strong> Connectivity Server configuration dialog.Gw001.log Example02-Oct-13, 09:01:20, <strong>NetSupport</strong> V12.00, running on Windows NT 5.1 Service Pack 3(build 2600), platform 202-Oct-13, 09:01:22, Activating Connectivity Server (code: 0)02-Oct-13, 09:01:22, Connectivity Server started, Max. licensed clients: 10 (web: 0) andagents: 002-Oct-13, 09:01:22, Using transport protocol version 1.1The following is a list of events that are logged to the <strong>NetSupport</strong> <strong>Gateway</strong> Log File , running on (build), platform This event is logged when the <strong>Gateway</strong> is first started. A typical example would be asfollows:<strong>NetSupport</strong> V12.00D, running on Windows NT 5.1 Service Pack 3 (build 2600), platform 2<strong>Gateway</strong> started. Mac licensed connections: This event is logged when the <strong>Gateway</strong> is first started.Failed to start gatewayThis event is logged when the <strong>Gateway</strong> fails to start.<strong>Gateway</strong> stoppedThis event is logged when the <strong>Gateway</strong> is stopped.Listening on port This event is logged when the <strong>Gateway</strong> starts listening on the specified port. This occursduring start-up and when a change in the <strong>Gateway</strong> port is applied in the <strong>Gateway</strong>configurator.Listening on port This event is logged when the <strong>Gateway</strong> starts listening on the specified port. This occursduring start-up and when a change in the <strong>Gateway</strong> port is applied in the <strong>Gateway</strong>Configurator.Failed to bind to listening port This event is logged when the <strong>Gateway</strong> fails to assign the specified port to listen forincoming connections. The port is probably being used by another application.Reloading configurationThis event is logged by the <strong>Gateway</strong> when the administrator has used the <strong>Gateway</strong>configurator to apply configuration changes.Listen port has changed. All current connections and sessions will be terminated.This event is logged by the <strong>Gateway</strong> when the administrator modifies the listening port inthe <strong>Gateway</strong> configurator and then applies the change whilst the gateway is running.13

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!