Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
A packet from <source ip address> destined to <destination ip address> over protocol <protocol number> caused interface <interface type> to be brought up. The first <number of bytes> bytes of the packet are in the data.
0000: 5a 42 01 85 98 e3 aa 68 ZB.??ãªh
0008: 00 00 00 00 70 02 22 38 ....p."8
0010: ff 49 00 00 02 04 05 b4 ÿI.....´
|English: Request a translation of the event description in plain English.|
In my case I fixed the problem by uninstalling and reinstalling RRAS.
The <protocol number> field indicates the type of protocol that caused the event:
0x01 (decimal 1) = ICMP
0x06 (decimal 6) = TCP
0x11 (decimal 17) = UDP
This event in itself is not an indication of a problem. It simply records the fact that a Dial on Demand (DoD) interface has been brought up as there was traffic from the local to the remote network (for which the DoD has been configured). Some users reported this event as occuring when there were problems with the RRAS server. This could be because the DoD would keep trying to reconnect (but failing for whatever reason).
If you need to investigate what is causing the DoD see this comment (from a newsgroup):
"Under IP Routing\General\Properties\Logging set logging to Maximum. In the
Event log you will see the entries that correspond to the traffic that
triggered the event. Use this and netmon to help pin point the traffic. Then
use IP Filters and Demand Dial Filters to solve the problem."
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated