Re: asp.net

From: Roger Abell (mvpNOSpam_at_asu.edu)
Date: 12/17/03 

Date: Wed, 17 Dec 2003 01:44:40 -0700

The snap-in that is referred to is accessed by entering
mmc at the Start / Run area, and then using the Add/Remove
Snap-in selection in the drop menu, and adding the snap-in
after selecting it from the add list.

Are these events corresponding in time to when you get
pop-up messages from network sense telling you that the
network is unavailable and then again available ? 

-- 
Roger
"jane" <anonymous@discussions.microsoft.com> wrote in message
news:00a001c3c45d$7e624d40$a001280a@phx.gbl...
> my computer is the only one here in house so, there
> shouldn't be any network interface i understand that, but
> i thought it might have something to do with the asp.net
> because they both have "net" in them (shows how much i
> know) still, it DOES succeed (sometimes)!!! go figure....
>
> is this directly related to the "stand by" power settings
> and re-entering my password to access my machine?
>
> i probably wouldn't worry about it too much but it sure
> seems to be clogging up my log because....  YES. this is
> something that's going on continually...i've
> was kind of looking for a pattern but it just confuses me
> all the more.
> for instance today 12-16 i've had 1 fail at 1:37am.
> yesterday there were 5 fails and 2 successes. they
> occurred like this fail 4:28am success 4:28am, fail 7:40am
> fail 7:57am, success 7:57am, fail 8:20am, fail 9:22am...
> fyi, the success (if there is one) always come right
> after the fails & with the same time on them as the
> fails.
> on 12-14 i had 3 fails 0 successes / 12-13 5 fails 1
> success / none on 12-12 / 12-11 1 fail 1 success / 12-10
> 15 fails 6 successes....etc, etc as far back as my log
> goes which is till nov 13.
> fyi, (not that it means anything) every time there is a
> succeed, there is an event id 612 policy change a few
> minutes or entries before the fail/succeed entry. they
> (the612's) all look the same too --
>   Success Failure
> +     + Logon/Logoff
> -     - Object Access
> -     - Privilege Use
> +     + Account Management
> +     + Policy Change
> +     + System
> -     - Detailed Tracking
> -     - Directory Service Access
> +     + Account Logon
> Changed By:
>     User Name: THEHOOD$
>     Domain Name: WORKGROUP
>
> thanks for your patience and help...jane
>
> >-----Original Message-----
> >The two issues you mention are totally unrelated.
> >Your deleting ASPNET account in XP Home, AFAIK
> >will cause no issues whatsoever.
> >
> >One normally sees the IPsec message that you mention
> >when one network capable interface has not finished its
> >initialization during boot before IPsec tries to
> initialize.
> >It is telling you that an interface is not protected,
> but it is
> >because the interface is not functioning.
> >I really would not be too concerned about it if it was
> >only something that happened for a while on that day.
> >Is this being recorded continuously?
> >
> >-- 
> >Roger Abell
> >Microsoft MVP (Windows Server System: Security)
> >MCSE (W2k3,W2k,Nt4)  MCDBA
> >"jane" <anonymous@discussions.microsoft.com> wrote in
> message
> >news:07cc01c3c39d$2d370c50$a301280a@phx.gbl...
> >> i have xp home edition. in a moment of stupidity, i
> >> deleted asp.net from my user group a couple of weeks
> ago.
> >> i haven't had any real ill effects from it (that i know
> >> of) BUTTT.....i have noticed that very day -- multiple
> >> times, i'm logging a security error 615 IPSEC security
> >> error. "IPSEC failed to get the complete list of
> network
> >> interfaces on the machine. This can be a potential
> >> security hazard to the machine since some of the
> network
> >> interfaces may not get the protection as desired by the
> >> IPSEC filters. Please run IPSEC monitor snapin to
> further
> >> dianose the problem." The user shown is NT AUTORITY\
> >> NETWORK SERVICE... i can't find this snapin. don't
> really
> >> want to mess things up further...anyone out there who
> can
> >> help me fix this?? (oh and no, i won't be messing
> where i
> >> shouldn't again)
> >
> >
> >.
> >