This article applies to:
Question:
- What does the mobile log show?
Information:
By default the filter will look for an internal ip first, no need to add one if you are only using mobile for inside and outside network. the filter uses port 443 to connect then the public ip can be natted to an internal ip if your mobile filter is not in the DMZ.
The log file shows:
what version the mobile client your using.
Time stamp
The public ip it is trying to connect to
success or fail and reason
This case was port 443 was not allowed though firewall so no hand shake ( Auth::Sock failed with error 2)
12/07/11 13:22:05 - ~0300,3 MC loadRegistry() -> full command line = c:\windows\system32\inetcntrl\inetcntrl.exe
12/07/11 13:22:05 - ~0300,3 Version info: vN(M86 Security Technologies, Inc.),vP(M86 Security Mobile Client for Windows),vV(3.0.7.0)
12/07/11 13:22:05 - ~0300,3 M86 Security Mobile Client LSP DLL version is 3.0.7.0
12/07/11 13:22:05 - ~0000,3 M86 Mobile Client filter initializing (v3.0.7.0, Built: Jul 27 2010 13:49:02)
12/07/11 13:22:05 - ~0100,4 DeviceIoControl returned an error = 87
12/07/11 13:22:10 - ~0100,4 DeviceIoControl returned an error = 87
12/07/11 13:22:13 - ~0100,3 Attempting connection to R3000 external server 65.208.43.234<---public ip (this is a sample only)
12/07/11 13:22:13 - ~0100,3 Connection to R3K failed
12/07/11 13:22:13 - ~0100,3 Auth::Sock failed with error 2
=================location for mobile log====================
For version 3.x mobile client log file name is “M86Security-mobile.log”.
Waco can guide the customer to locate the log file at following location.
Windows XP: C:/Documents and Setting/USERNAME/ M86Security-mobile.log
Windows Vista/7: C:/Users/USERNAME/ M86Security-mobile.log
• USERNAME: use the name of the user not working.
Mac: /private/var/log/M86Security-mobile.log
Just keep in mind, for mobile client version 2.x, the log file name is still 8e6-mobile.log
Notes:
Tech support will need this log file to verify the problem, so your log may look very different then the one above.
