You will see logon success and failure events in the security log on your domain controller, since the OWA server refers authentication queries to the DC. Usually the events give the username that was attempted and the system on which the authentication was attempted.
Look for a 529 failure event. It will be generated by the system account on the server and will include the source IP address that was attempting to log on to the OWA server.
If you your Exchange server is also a DC (like on SBS), the same thing applies.
Have you tried logging on to OWA or putting a bad password in on an OWA logon and then checking the security log for the events that I mentioned?
The events I mentioned don't require special logging options to be turned on; they are recorded by default.
If you do want to get more logging for OWA, you could probably monitor logons by changing the logging settings for MSExchangeIS->Mailbox->Logons to Maximum. You find that setting in the Exchange System Manager when you get properties on the server name and choose the Diagnostic Logging tab. Any change you make here will cause changes in what gets logged to the Application log. Personally, I think that if you just filter the Security log for the event numbers I mentioned earlier, you should get a pretty good idea of who logged on, and when.
MS technote 246248
talks about ones to turn on,but
i dont see any of those,
is that only for exch 5.5 ??
its option 4 talks about turning on MSExchangeDS
set security, ExDS Interface and Mapi interface, Directory access, LDAP interface and Name resolution
That article is for 5.5. In 2003, the one you want to log connections is the one that I mentioned above: MSExchangeIS->Mailbox->Logons.
That's the same as option 6 in the article you read, and that's the option that actually logged who used OWA in the events listed below that. The last event in that article shows someone logging on to OWA.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.