Welcome to ISAserver.org

Account Lockout Issues with ISA 2006 and OWA

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA 2006 General] >> General >> Account Lockout Issues with ISA 2006 and OWA

Page: [1]

Message

<< Older Topic Newer Topic >>

Account Lockout Issues with ISA 2006 and OWA - 8.Mar.2012 12:46:03 PM

jvansym

Posts: 1
Joined: 8.Mar.2012
Status: offline

Hi Everyone,
We are having a bit of a problem with one of our users. It appears that his account is getting locked out on a regular basis and the server that the authentication request is coming from is our ISA 2006 server that we use for OWA/Active sync for our Exchange 2007 environment.

The issue here is that when looking at the ISA server logs as far as i can tell I'm not seeing any entries when a user makes a failed authentication attempt on our OWA site or through active sync. I tested this by setting up a test user and typing in the incorrect password until my account was locked out while watching the live log on the ISA server and filtering by that users account. If i make a successful attempt i see the connection details in the log but failed attempts do not show anything.

My question is, is there any way to get the ISA logs to show the IP addresses of the connecting system for the failed authentication attempt on our OWA site ? The intention would be to evaluate where the request is coming from and if it is external (someone trying to brute force his account) to block that IP address at our firewall.

Post #: 1

Featured Links*

RE: Account Lockout Issues with ISA 2006 and OWA - 9.Mar.2012 1:39:47 AM

hadideveloper

Posts: 156
Joined: 20.Jun.2011
Status: offline

Hi,
yes there is. it is one of the isa's duty.
but if there is no log in the isa for specific client then you should reconfigure your log setting
or there is a problem on the client (e.g. certificate problem) or routing table.
some times ip filtering or client ip cause a packet drop and in that situation there is no log

(in reply to jvansym)

Post #: 2