Getting of user name for failed authentication

From: Antonio (antoniopassado_at_hotmail.com)
Date: 06/25/04


Date: Fri, 25 Jun 2004 12:51:09 +0200

Hi everybody,

We are using NTLM for authenticating clients that connect over network to
our server. In case of failed authentication we would like to log a message
into event log with the name under which user tried to login. Is it possible
somehow to obtain this name during authentication process?

Thanks in advance,
Antonio



Relevant Pages

  • RE: [fw-wiz] IPv6 comes in the game
    ... Microsoft Windows 2000/2003 server does 802.1x auth fine. ... wireless access as well as port access on certain switches in the network. ... then you're able to log the authentication at the RADIUS ...
    (Firewall-Wizards)
  • Re: ipfw plus authentication (authpf is cool but....)
    ... authentication happening in the process of dhcp. ... router first before being allowed to access any server. ... script will happily change the router's firewall ruleset to allow the ... user does not want to access any network server anymore. ...
    (freebsd-questions)
  • Re: SQLCEReplication over GPRS
    ... Internet side, just not over GPRS: ... network that was causing the issue. ... as that's the server sync DLL version that you're using. ... connecting via GPRS via vodafone the authentication part is missing. ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: Access Denied to share with anonymous access disabled
    ... > Integrated Windows authentication, then you are looking at the classic ... > server, why should the server automatically be able to use your ... > to access some other network resource? ... > ASPNet local user account full access to the share. ...
    (microsoft.public.inetserver.iis.security)
  • Re: Kerberos machine authentication - apparent authentication fail
    ... > until logon), the wireless connection can kick off when it is ready. ... > was confirmed in the server event logs with IAS (i set that up as the radius ... > as an ordinary user kicks in and takes over from the machine authentication. ... > while the network sorts itself out and a double click on a network link of ...
    (microsoft.public.windows.server.security)