Logging Configuration Changes

[labull]

In Extended Networking - Logging

I have Configuration Changes checked.

I can't find the changes logged in either the WinGate NAT or System log files.

Thanks!

Larry

[tim]

In Extended Networking - Logging
I have Configuration Changes checked.
I can't find the changes logged in either the WinGate NAT or System log files.

Its possible that these services have not got logging events for this kind of action. I will get it reproduced in QA and schedule a fix for this is that is the case.

Thanks

Tim

[labull]

Thanks Tim!

You're a wonderful human being.

[tim]

Thanks Tim!

You're a wonderful human being.

I am but a servant.

[ChrisH]

I agree with Larry, something is up with logging in 5.0.10 . Stopping WG engine then restarting would show up in System log in 5.0.7-doesn't now and I am seeing the following "garbage?" in System log file. I have seen it every day since 5.0.10 install (clean). XP WG server, Win98 clients. Here is exerpt from latest System log. Does it mean anything?
10/14/03 18:38:02 Cu1M3QrtWOgAAAAAAQAAAAEAoMw5wyQAUPzEtEwIAEUAAFxbbAAAgAEjlgrtTN0K7VjoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAIAjliqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqo=
10/14/03 19:11:15 Cu1OzArtWOgAAAAAAQAAAAEAoMw5wyQAQPR/QS4IAEUAAFxdZwAAgAEfrArtTswK7VjoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAIAjliqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqo=
10/14/03 19:11:15 Cu1OzArtWOgAAAAAAQAAAAEAoMw5wyQADEFIgk8IAEUAAFxdZwAAfwEgrArtTswK7VjoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAIAjliqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqo=
10/14/03 19:13:27 Cu1T2ArtWOgAAAAAAQAAAAEAoMw5wyQAMPEV8CAIAEUAAFzhwwAAgAGWQwrtU9gK7VjoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAMAqKqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqo=
10/14/03 19:42:49 Cu1U7grtWOgAAAAAAQAAAAEAoMw5wyQAUL9zeMwIAEUAAFwNgAAAgAFpcQrtVO4K7VjoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAkP2qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqo=
10/14/03 19:47:04 Cu1M3QrtWOgAAAAAAQAAAAEAoMw5wyQAUPzEtEwIAEUAAFxQLgAAgAEu1ArtTN0K7VjoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAIAEUqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqo=
10/14/03 20:11:43 Cu1T2ArtWOgAAAAAAQAAAAEAoMw5wyQAMPEV8CAIAEUAAFzbjwAAgAGcdwrtU9gK7VjoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAMAzZuqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqo=
10/14/03 20:11:43 Cu1T2ArtWOgAAAAAAQAAAAEAoMw5wyQADEFIgk8IAEUAAFzbjwAAfwGddwrtU9gK7VjoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAMAzZuqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqo=
10/14/03 20:57:32 Cu1OzArtWOgAAAAAAQAAAAEAoMw5wyQAQPR/QS4IAEUAAFxgeAAAgAEcmwrtTswK7VjoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAIArUmqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqo=
10/14/03 21:09:54 Cu1T2ArtWOgAAAAAAQAAAAEAoMw5wyQAMPEV8CAIAEUAAFzQ9gAAgAGnEArtU9gK7VjoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAMAUI2qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqo=
10/14/03 21:09:55 Cu1T2ArtWOgAAAAAAQAAAAEAoMw5wyQADEFIgk8IAEUAAFzQ9gAAfwGoEArtU9gK7VjoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAMAUI2qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqo=
10/14/03 21:47:22 Authentication Authentication failed - user Guest on 192.168.0.4 requested
10/14/03 21:47:23 Authentication Authentication failed - user Guest on 192.168.0.4 requested
10/14/03 21:47:26 Authentication Authentication failed - user Guest on 192.168.0.4 requested
10/14/03 21:47:30 Authentication Authentication failed - user Guest on 192.168.0.4 requested
10/14/03 21:47:39 Authentication Authentication failed - user Guest on 192.168.0.4 requested
10/14/03 21:47:41 Authentication Authentication failed - user Guest on 192.168.0.4 requested
10/14/03 21:47:43 Authentication Authentication failed - user Guest on 192.168.0.4 requested
10/14/03 21:47:48 Authentication Authentication failed - user Guest on 192.168.0.4 requested
10/14/03 21:48:36 Authentication Authentication failed - user Guest on 192.168.0.4 requested
10/14/03 21:48:38 Authentication Authentication failed - user Guest on 192.168.0.4 requested
10/14/03 21:48:40 Authentication Authentication failed - user Guest on 192.168.0.4 requested
10/14/03 21:48:45 Authentication Authentication failed - user Guest on 192.168.0.4 requested
10/14/03 21:48:53 Authentication Authentication failed - user Guest on 192.168.0.4 requested
10/14/03 21:48:55 Authentication Authentication failed - user Guest on 192.168.0.4 requested
10/14/03 21:48:57 Authentication Authentication failed - user Guest on 192.168.0.4 requested
10/14/03 21:49:02 Authentication Authentication failed - user Guest on 192.168.0.4 requested
10/14/03 21:49:41 Authentication Authentication failed - user Guest on 192.168.0.4 requested
10/14/03 21:49:42 Authentication Authentication failed - user Guest on 192.168.0.4 requested
10/14/03 21:49:45 Authentication Authentication failed - user Guest on 192.168.0.4 requested
10/14/03 21:49:49 Authentication Authentication failed - user Guest on 192.168.0.4 requested
10/14/03 21:49:58 Authentication Authentication failed - user Guest on 192.168.0.4 requested
10/14/03 21:50:00 Authentication Authentication failed - user Guest on 192.168.0.4 requested
10/14/03 21:50:02 Authentication Authentication failed - user Guest on 192.168.0.4 requested
10/14/03 21:50:07 Authentication Authentication failed - user Guest on 192.168.0.4 requested
10/14/03 21:50:09 Cu1M3QrtWOgAAAAAAQAAAAEAoMw5wyQAUPzEtEwIAEUAAFxbaAAAgAEjmgrtTN0K7VjoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAIAjliqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqo

[labull]

Chris,

The unintelligable info in the System log is there to allow storage of blocked packet info.

Adrien explained that in a post here in the WinGate Beta forum under the topic "5.0.8".


Larry

[ChrisH]

Larry,

Thanks. I must have missed that section in the thread. Does that code have to show up in log? IMHO it is unecessary because it is unreadable by humans (me anyway). But I still think that the logging is behaving differently from 5.0.7 as in your example and I know that stopping and starting any service used to show up in the appropriate service log especially if WG is configured to log those events. The only one that I see logging start/stop now, is DHCP log file.