Re: Logon/Logoff events
Tech-Archive recommends: Fix windows errors by optimizing your registry
- From: "Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]" <sbradcpa@xxxxxxxxxxx>
- Date: Tue, 14 Jun 2005 23:14:03 -0700
Actually this is normal. SBS 2003 will do success/failures on logins
Are they all successes?
Fred wrote:
I'm running SBS 2003 and in my security event file I'm getting well over 100
Logon/Logoff (event 538 and 540) and Account Logon (680) events every 5
minutes.
It seems to involve nearly all of the users and computers on the network.
I presume this is not normal. What can be the cause of this.
Thanks
Fred
--
An open letter to the Security Community::
http://msmvps.com/bradley/archive/2004/12/12/23540.aspx
.
Relevant Pages
- Re: Logon/Logoff events
... It seems to involve nearly all of the users and computers on the network. ... I presume this is not normal. ... Nearly all of these are logon/logoff events. ... (microsoft.public.windows.server.sbs) - Logon/Logoff events
... It seems to involve nearly all of the users and computers on the network. ... I presume this is not normal. ... Prev by Date: ... (microsoft.public.windows.server.sbs) - Re: The Hard Problem for Behaviorists
... correct low level abstractions to define the operation of the brain with - ... Do you not know how computers work? ... you can think of this type of network like you ... when you drop a marble in hole X1, ... (sci.cognitive) - Re: Networks : Workgroups and Domains. How Do I Use Them?
... I think the problem is from my lack of understanding whether these machines are together as a workgroup or domain. ... If I want to configure solely for a workgroup network, then I would think I do not need to provide a domain name, and vice versa for a domain network. ... It's not clear whether any of your computers is running Windows 2000 *Server.* If not, you don't have a "domain" and shouldn't be using domain names. ... Problems sharing files between computers on a network are generally caused by 1) a misconfigured firewall or overlooked firewall; or 2) inadvertently running two firewalls such as the built-in Windows Firewall and a third-party firewall; and/or 3) not having identical user accounts and passwords on all Workgroup machines; 4) trying to create shares where the operating system does not permit it. ... (microsoft.public.windowsxp.network_web) - Re: {workgroup}"...is not accessible" after removing NWLINK
... I generally reboot the machine whenever I make network ... >problem is a browse service that won?t run on the XP machine using the TCP/IP ... >?The browser has forced an election on network ... >> computer, and one, or preferably two, of the Windows 98 computers. ... (microsoft.public.windowsxp.network_web) |
|