Identifying "random" dialing source

[Kenneth L Salzman, PhD]

The knowledge base information did not quite get me what I am seeking. I am getting unexpected dialing, but had hoped to identify the source from the log files. Instead, I get:

========================================
12/28/03 00:15:29 Debug: Using WINVER-401 RAS support
12/28/03 00:15:33 Debug: Multilink dial mode == 1
12/28/03 00:15:33 Debug: Internet Express: Dialing: Internet Express
12/28/03 00:15:33 Internet Express: Dialing...(requested by )
12/28/03 00:15:33 Debug: Internet Express: Opening Port
12/28/03 00:15:33 Debug: Internet Express: Port Opened
12/28/03 00:15:33 Debug: Internet Express: Connecting to 56FW92
12/28/03 00:15:58 Debug: Internet Express: Connected
12/28/03 00:15:58 Debug: Internet Express: All devices connected
12/28/03 00:15:58 Debug: Internet Express: Verifying username and password
12/28/03 00:15:59 Debug: Internet Express: On line to Internet Express
12/28/03 00:15:59 Debug: Internet Express: Connected
12/28/03 00:15:59 Debug: Internet Express: Dial succeeded
12/28/03 00:15:59 Debug: Profile Internet Express managed connection
12/28/03 00:15:59 Debug: Profile Internet Express on line and grants access for
12/28/03 00:15:59 Debug: Profile Internet Express on line and grants access for
============================================

The "requested by" and "access for" have nothing after them. Is there a way to identify the source triggering the dialer event?

Ken

[Nev]

Hi Ken,

Found this issue was triggered by a public interface receiving ICMP traffic and more whilst the dial in was offline. Concluded [rightly or wrongly] that it was via the NAT/Firewall.

Solution was to at least make all users assumed [in Wingate's dialer profile policies] problem over.

Nev.