Filter
Top Products
20.12 Sslvpn Log
295
a) Engine Startup:
[17/Dec/2004 12:11:33] Engine: Startup.
b) Engine Shutdown:
[17/Dec/2004 12:22:43] Engine: Shutdown.
20.12 Sslvpn Log
In this log, operations performed in the Clientless SSL-VPN interface are recorded. Each
log line provides information about an operation type, name of the user who performed
it and file associated with the operation.
Example:
[17/Mar/2005 08:01:51] Copy File: User: jsmith@company.com
File: ’\\server\data\www\index.html’
20.13 Warning Log
The Warning log displays warning messages about errors of little significance. Warnings
can display for example reports about invalid user login (invalid username or password),
error in communication of the server and Web administration interface, etc.
Events recalling warning messages in this log do not seriously affect WinRoute function-
ality. However, they can point at current or possible problems. The Warning log can
help if for example a user is complaining that certain services are not working.
Each warning message is identified by its numerical code (code xxx:). The following
warning categories are defined:
• 1000-1999 — system warnings (e.g. an application found that is known as conflicting)
• 2000-2999 — WinRoute configuration problems (e.g. HTTP rules require user authen-
tication, but the WWW interface is not enabled)
• 3000-3999 — warning from individual WinRoute modules (e.g. DHCP server, anti-
virus check, etc.)
• 4000-4999 — license warnings (subscription expiration, forthcoming expiration of
WinRoute’s license, ISS OrangeWeb Filter license, or the McAfee anti-virus license)
Note: License expiration is considered to be an error and it is logged into the Error
log.
Examples of Warning logs: