IPSec failure

Not using VPN. Changed the setting from automatic to manual. That seems to
have cleared the error message in the security log upon boot. I did not have
to change the setting to disable. No idea how the setting changed on 11/29th
or why an error message wasn't posted prior to that date.

I thought disabling the IPSec service would have stopped the message, but
wasn't sure if that was the action that I should have taken.

Thank you.
 >> Stay informed about: IPSec failure 

Hello

Hope this is related to the Q. I have a messege that says IPSec policy
changed :%1 PolicySource :%2 %3
Symbolic Name: SE_AUDITID_IPSEC_POLICY_CHANGED

Do i need to worry about this ?Hopefully,i'm not been hacked or spyed on !!

THANK YOU in advance for your time and effort.
"Steven L Umbach" wrote:

> It is highly unlikely you are using ipsec for anything unless you are using
> the l2tp VPN client [I am not even sure it is available in XP Home]. If that
> is not the case open services via services.msc and disable the ipsec service
> to see if that makes the error message go away. --- Steve
>
>
> "Rayfran" <Rayfran.TakeThisOut@discussions.microsoft.com> wrote in message
> news:B3710797-3AFB-49E4-B7E2-E404C21367EF@microsoft.com...
> > Looking in eventvwr.msc I have been getting a IPSec failure on boot notice
> > on
> > my client wirelessly networked machine. Event ID 615.
> >
> > "IPSec service failed to get the complete list of network interfaces on
> > the
> > machine. Please run IPSec monitor to further diagnose." I am running
> > WIN-XP
> > Home and believe the IPSec monitor is not available to me.
> >
> > Where do I look for the cause of this problem? How do I resolve this
> > problem?
> >
> > (Hoping this question is posted to the proper discussion group.)
>
>
>
 >> Stay informed about: IPSec failure 

Where did you see that message - in the security log?? If so it indicates
that there was a change in an ipsec policy which usually is done via Local
Security Policy unless the computer is in an Active Directory domain. In
both cases the computer would need to be XP Pro. If you are not in a
situation where you are using ipsec such as an XP Home computer I would not
worry about it.

Steve


"jordy" <jordy.DeleteThis@discussions.microsoft.com> wrote in message
news:0F4D7795-D1C4-49DE-A858-230FA3B87F3B@microsoft.com...
> Hello
>
> Hope this is related to the Q. I have a messege that says IPSec policy
> changed :%1 PolicySource :%2 %3
> Symbolic Name: SE_AUDITID_IPSEC_POLICY_CHANGED
>
> Do i need to worry about this ?Hopefully,i'm not been hacked or spyed on
> !!
>
> THANK YOU in advance for your time and effort.
> "Steven L Umbach" wrote:
>
>> It is highly unlikely you are using ipsec for anything unless you are
>> using
>> the l2tp VPN client [I am not even sure it is available in XP Home]. If
>> that
>> is not the case open services via services.msc and disable the ipsec
>> service
>> to see if that makes the error message go away. --- Steve
>>
>>
>> "Rayfran" <Rayfran.DeleteThis@discussions.microsoft.com> wrote in message
>> news:B3710797-3AFB-49E4-B7E2-E404C21367EF@microsoft.com...
>> > Looking in eventvwr.msc I have been getting a IPSec failure on boot
>> > notice
>> > on
>> > my client wirelessly networked machine. Event ID 615.
>> >
>> > "IPSec service failed to get the complete list of network interfaces on
>> > the
>> > machine. Please run IPSec monitor to further diagnose." I am running
>> > WIN-XP
>> > Home and believe the IPSec monitor is not available to me.
>> >
>> > Where do I look for the cause of this problem? How do I resolve this
>> > problem?
>> >
>> > (Hoping this question is posted to the proper discussion group.)
>>
>>
>>
 >> Stay informed about: IPSec failure 

First,thank you for your reply and yes,it's in the security log.Second,it's a
home computer and I'm running XPHome Edition .
Thanks,again,Steven if you need more info,let me know and do i worry about
it now,that you mentioned it's a XP Home Edition.????
"Steven L Umbach" wrote:

> Where did you see that message - in the security log?? If so it indicates
> that there was a change in an ipsec policy which usually is done via Local
> Security Policy unless the computer is in an Active Directory domain. In
> both cases the computer would need to be XP Pro. If you are not in a
> situation where you are using ipsec such as an XP Home computer I would not
> worry about it.
>
> Steve
>
>
> "jordy" <jordy DeleteThis @discussions.microsoft.com> wrote in message
> news:0F4D7795-D1C4-49DE-A858-230FA3B87F3B@microsoft.com...
> > Hello
> >
> > Hope this is related to the Q. I have a messege that says IPSec policy
> > changed :%1 PolicySource :%2 %3
> > Symbolic Name: SE_AUDITID_IPSEC_POLICY_CHANGED
> >
> > Do i need to worry about this ?Hopefully,i'm not been hacked or spyed on
> > !!
> >
> > THANK YOU in advance for your time and effort.
> > "Steven L Umbach" wrote:
> >
> >> It is highly unlikely you are using ipsec for anything unless you are
> >> using
> >> the l2tp VPN client [I am not even sure it is available in XP Home]. If
> >> that
> >> is not the case open services via services.msc and disable the ipsec
> >> service
> >> to see if that makes the error message go away. --- Steve
> >>
> >>
> >> "Rayfran" <Rayfran DeleteThis @discussions.microsoft.com> wrote in message
> >> news:B3710797-3AFB-49E4-B7E2-E404C21367EF@microsoft.com...
> >> > Looking in eventvwr.msc I have been getting a IPSec failure on boot
> >> > notice
> >> > on
> >> > my client wirelessly networked machine. Event ID 615.
> >> >
> >> > "IPSec service failed to get the complete list of network interfaces on
> >> > the
> >> > machine. Please run IPSec monitor to further diagnose." I am running
> >> > WIN-XP
> >> > Home and believe the IPSec monitor is not available to me.
> >> >
> >> > Where do I look for the cause of this problem? How do I resolve this
> >> > problem?
> >> >
> >> > (Hoping this question is posted to the proper discussion group.)
> >>
> >>
> >>
>
>
>
 >> Stay informed about: IPSec failure 

If you are using XP Home I would not worry about it. Ipsec can be used in
networks to secure communications between two ipsec aware computers and each
computer would need to have a compatible ipsec policy. This typically
happens in larger networks using an Active Directory domain. I am about 99.9
percent sure in your case that the event you seen was generated by the
operating system and not relevant to any security issue affecting your
computer.

Steve


"jordy" <jordy.TakeThisOut@discussions.microsoft.com> wrote in message
news:7CA644E1-1872-4121-BC48-579234ECC113@microsoft.com...
> First,thank you for your reply and yes,it's in the security
> log.Second,it's a
> home computer and I'm running XPHome Edition .
> Thanks,again,Steven if you need more info,let me know and do i worry about
> it now,that you mentioned it's a XP Home Edition.????
> "Steven L Umbach" wrote:
>
>> Where did you see that message - in the security log?? If so it indicates
>> that there was a change in an ipsec policy which usually is done via
>> Local
>> Security Policy unless the computer is in an Active Directory domain. In
>> both cases the computer would need to be XP Pro. If you are not in a
>> situation where you are using ipsec such as an XP Home computer I would
>> not
>> worry about it.
>>
>> Steve
>>
>>
>> "jordy" <jordy.TakeThisOut@discussions.microsoft.com> wrote in message
>> news:0F4D7795-D1C4-49DE-A858-230FA3B87F3B@microsoft.com...
>> > Hello
>> >
>> > Hope this is related to the Q. I have a messege that says IPSec policy
>> > changed :%1 PolicySource :%2 %3
>> > Symbolic Name: SE_AUDITID_IPSEC_POLICY_CHANGED
>> >
>> > Do i need to worry about this ?Hopefully,i'm not been hacked or spyed
>> > on
>> > !!
>> >
>> > THANK YOU in advance for your time and effort.
>> > "Steven L Umbach" wrote:
>> >
>> >> It is highly unlikely you are using ipsec for anything unless you are
>> >> using
>> >> the l2tp VPN client [I am not even sure it is available in XP Home].
>> >> If
>> >> that
>> >> is not the case open services via services.msc and disable the ipsec
>> >> service
>> >> to see if that makes the error message go away. --- Steve
>> >>
>> >>
>> >> "Rayfran" <Rayfran.TakeThisOut@discussions.microsoft.com> wrote in message
>> >> news:B3710797-3AFB-49E4-B7E2-E404C21367EF@microsoft.com...
>> >> > Looking in eventvwr.msc I have been getting a IPSec failure on boot
>> >> > notice
>> >> > on
>> >> > my client wirelessly networked machine. Event ID 615.
>> >> >
>> >> > "IPSec service failed to get the complete list of network interfaces
>> >> > on
>> >> > the
>> >> > machine. Please run IPSec monitor to further diagnose." I am
>> >> > running
>> >> > WIN-XP
>> >> > Home and believe the IPSec monitor is not available to me.
>> >> >
>> >> > Where do I look for the cause of this problem? How do I resolve this
>> >> > problem?
>> >> >
>> >> > (Hoping this question is posted to the proper discussion group.)
>> >>
>> >>
>> >>
>>
>>
>>
 >> Stay informed about: IPSec failure 

OK, Steven
Thank You for taking so much time and answering my question so thoroughly .
I really appreciate it.Have a great weekend !!!

"Steven L Umbach" wrote:

> If you are using XP Home I would not worry about it. Ipsec can be used in
> networks to secure communications between two ipsec aware computers and each
> computer would need to have a compatible ipsec policy. This typically
> happens in larger networks using an Active Directory domain. I am about 99.9
> percent sure in your case that the event you seen was generated by the
> operating system and not relevant to any security issue affecting your
> computer.
>
> Steve
>
>
> "jordy" <jordy RemoveThis @discussions.microsoft.com> wrote in message
> news:7CA644E1-1872-4121-BC48-579234ECC113@microsoft.com...
> > First,thank you for your reply and yes,it's in the security
> > log.Second,it's a
> > home computer and I'm running XPHome Edition .
> > Thanks,again,Steven if you need more info,let me know and do i worry about
> > it now,that you mentioned it's a XP Home Edition.????
> > "Steven L Umbach" wrote:
> >
> >> Where did you see that message - in the security log?? If so it indicates
> >> that there was a change in an ipsec policy which usually is done via
> >> Local
> >> Security Policy unless the computer is in an Active Directory domain. In
> >> both cases the computer would need to be XP Pro. If you are not in a
> >> situation where you are using ipsec such as an XP Home computer I would
> >> not
> >> worry about it.
> >>
> >> Steve
> >>
> >>
> >> "jordy" <jordy RemoveThis @discussions.microsoft.com> wrote in message
> >> news:0F4D7795-D1C4-49DE-A858-230FA3B87F3B@microsoft.com...
> >> > Hello
> >> >
> >> > Hope this is related to the Q. I have a messege that says IPSec policy
> >> > changed :%1 PolicySource :%2 %3
> >> > Symbolic Name: SE_AUDITID_IPSEC_POLICY_CHANGED
> >> >
> >> > Do i need to worry about this ?Hopefully,i'm not been hacked or spyed
> >> > on
> >> > !!
> >> >
> >> > THANK YOU in advance for your time and effort.
> >> > "Steven L Umbach" wrote:
> >> >
> >> >> It is highly unlikely you are using ipsec for anything unless you are
> >> >> using
> >> >> the l2tp VPN client [I am not even sure it is available in XP Home].
> >> >> If
> >> >> that
> >> >> is not the case open services via services.msc and disable the ipsec
> >> >> service
> >> >> to see if that makes the error message go away. --- Steve
> >> >>
> >> >>
> >> >> "Rayfran" <Rayfran RemoveThis @discussions.microsoft.com> wrote in message
> >> >> news:B3710797-3AFB-49E4-B7E2-E404C21367EF@microsoft.com...
> >> >> > Looking in eventvwr.msc I have been getting a IPSec failure on boot
> >> >> > notice
> >> >> > on
> >> >> > my client wirelessly networked machine. Event ID 615.
> >> >> >
> >> >> > "IPSec service failed to get the complete list of network interfaces
> >> >> > on
> >> >> > the
> >> >> > machine. Please run IPSec monitor to further diagnose." I am
> >> >> > running
> >> >> > WIN-XP
> >> >> > Home and believe the IPSec monitor is not available to me.
> >> >> >
> >> >> > Where do I look for the cause of this problem? How do I resolve this
> >> >> > problem?
> >> >> >
> >> >> > (Hoping this question is posted to the proper discussion group.)
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
>
 >> Stay informed about: IPSec failure