Warning reports are displayed in the Warning log. Reports included in this section represent serious errors and bugs. 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 functionality. However, they can point at current or possible problems. The Warning log can be used for example when a user has problems with functioning of some services.
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 reqire user authentication, 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, Cobion 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:
[15/Apr/2003 15:00:51] (3004) Authentication subsystem warning: Kerberos 5 auth:
user james@company.com not authenticated
[15/Apr/2003 15:00:51] (3004) Authentication subsystem warning: Invalid password for user admin
[16/Apr/2003 10:53:20] (3004) Authentication subsystem warning: User johnblue doesn't exist
The first log informs that authentication of user jsmith by the Kerberos system in the company.com domain failed
The second log informs on a failed authentication attempt by user admin (invalid password)
The third log informs on an authentication attempt by a user which does not exist (johnblue)
Note: With the above three examples, the relevant records will also appear in the Security log.