My problem is my account locks out every 10 minutes. (W2K domain) No other account has a problem. Over the past 3 days I have narrowed it down to the exchange server. Shut each DC down one at a time acct still locks. Shut don exchange server account doesnt lock Shut down exchange service acct still locks I have also shut down all non MS services and the acct still locks I am confident the problem exists on the exchange server seperate from the exchange services. The MS services that are running on the Exchange 2000 server are: alerter computer browser dist file system dhcp cllient logical disk mgr dns client event log com+ event system IIS admin server workstation license logging service tcp/ip netbios helper messenger distributed transaction coordinator MS Exch information store MS Exch system attendant net logon network connections network news transport protocol NT LM security support prov plug n play IPSEC policy agent protected storage remote registry MS Exch routing engine RPC locator RPC SAM task scheduler run as system event smtp print spooler term services dist link tracking client windows time WWW publihing windows mgt instrumentaion windows mgt instrumentaion driver automatic updates Of these which ones can I safely shut down w/o affecting exchange during production. I can then shut the others down after hours. Any suggestions would greatly appreciated as my next step may require gasoline a match and a pack of hotdogs. Thanks in advance. Cody
On Fri, 21 Jul 2006 09:46:02 -0700, Cody Lewis <CodyLewis@discussions.microsoft.com> wrote: >My problem is my account locks out every 10 minutes. (W2K domain) No other >account has a problem. Over the past 3 days I have narrowed it down to the >exchange server. What do you mean you narrowed it down to the Exch Server? What do the security event logs say? > >Shut each DC down one at a time acct still locks. >Shut don exchange server account doesnt lock >Shut down exchange service acct still locks >I have also shut down all non MS services and the acct still locks > >I am confident the problem exists on the exchange server seperate from the >exchange services. The MS services that are running on the Exchange 2000 >server are: > >alerter >computer browser >dist file system >dhcp cllient >logical disk mgr >dns client >event log >com+ event system >IIS admin >server >workstation >license logging service >tcp/ip netbios helper >messenger >distributed transaction coordinator >MS Exch information store >MS Exch system attendant >net logon >network connections >network news transport protocol >NT LM security support prov >plug n play >IPSEC policy agent >protected storage >remote registry >MS Exch routing engine >RPC locator >RPC >SAM >task scheduler >run as >system event >smtp >print spooler >term services >dist link tracking client >windows time >WWW publihing >windows mgt instrumentaion >windows mgt instrumentaion driver >automatic updates > >Of these which ones can I safely shut down w/o affecting exchange during >production. I can then shut the others down after hours. > >Any suggestions would greatly appreciated as my next step may require >gasoline a match and a pack of hotdogs. > >Thanks in advance. >Cody
Instead of trying to shut down services, why don't you look at the services that are started from the Services Applet, and see if any of them are configured to run as your account? If so, which ones? -- Ben Winzenz Exchange MVP MessageOne Read my blog! http://winzenz.blogspot.com http://feeds.feedburner.com/winzenz (RSS Feed) "Cody Lewis" <CodyLewis@discussions.microsoft.com> wrote in message news:FC23EF79-76B6-4F0D-B40D-3678360B083F@microsoft.com... > My problem is my account locks out every 10 minutes. (W2K domain) No > other > account has a problem. Over the past 3 days I have narrowed it down to > the > exchange server. > > Shut each DC down one at a time acct still locks. > Shut don exchange server account doesnt lock > Shut down exchange service acct still locks > I have also shut down all non MS services and the acct still locks > > I am confident the problem exists on the exchange server seperate from the > exchange services. The MS services that are running on the Exchange 2000 > server are: > > alerter > computer browser > dist file system > dhcp cllient > logical disk mgr > dns client > event log > com+ event system > IIS admin > server > workstation > license logging service > tcp/ip netbios helper > messenger > distributed transaction coordinator > MS Exch information store > MS Exch system attendant > net logon > network connections > network news transport protocol > NT LM security support prov > plug n play > IPSEC policy agent > protected storage > remote registry > MS Exch routing engine > RPC locator > RPC > SAM > task scheduler > run as > system event > smtp > print spooler > term services > dist link tracking client > windows time > WWW publihing > windows mgt instrumentaion > windows mgt instrumentaion driver > automatic updates > > Of these which ones can I safely shut down w/o affecting exchange during > production. I can then shut the others down after hours. > > Any suggestions would greatly appreciated as my next step may require > gasoline a match and a pack of hotdogs. > > Thanks in advance. > Cody
![]() |
0 |
![]() |
"Andy David - MVP" wrote: > On Fri, 21 Jul 2006 09:46:02 -0700, Cody Lewis > <CodyLewis@discussions.microsoft.com> wrote: > > >My problem is my account locks out every 10 minutes. (W2K domain) No other > >account has a problem. Over the past 3 days I have narrowed it down to the > >exchange server. > > What do you mean you narrowed it down to the Exch Server? Do these steps listed not direct the problem to the exchange server? Shut each DC down one at a time acct still locks. Shut don exchange server account doesnt lock Shut down exchange service acct still locks I have also shut down all non MS services and the acct still locks What do the security event logs say? Sorry should have included that I get Event 539 Logon process ADVAPI logon type 3 followed by Event 681 Error code was 321225572, these errors repeat until acct is locked. I have the policy set at 10 bad attempts until lockout. > > > > >Shut each DC down one at a time acct still locks. > >Shut don exchange server account doesnt lock > >Shut down exchange service acct still locks > >I have also shut down all non MS services and the acct still locks > > > >I am confident the problem exists on the exchange server seperate from the > >exchange services. The MS services that are running on the Exchange 2000 > >server are: > > > >alerter > >computer browser > >dist file system > >dhcp cllient > >logical disk mgr > >dns client > >event log > >com+ event system > >IIS admin > >server > >workstation > >license logging service > >tcp/ip netbios helper > >messenger > >distributed transaction coordinator > >MS Exch information store > >MS Exch system attendant > >net logon > >network connections > >network news transport protocol > >NT LM security support prov > >plug n play > >IPSEC policy agent > >protected storage > >remote registry > >MS Exch routing engine > >RPC locator > >RPC > >SAM > >task scheduler > >run as > >system event > >smtp > >print spooler > >term services > >dist link tracking client > >windows time > >WWW publihing > >windows mgt instrumentaion > >windows mgt instrumentaion driver > >automatic updates > > > >Of these which ones can I safely shut down w/o affecting exchange during > >production. I can then shut the others down after hours. > > > >Any suggestions would greatly appreciated as my next step may require > >gasoline a match and a pack of hotdogs. > > > >Thanks in advance. > >Cody >
On Fri, 21 Jul 2006 10:57:02 -0700, Cody Lewis <CodyLewis@discussions.microsoft.com> wrote: > > >"Andy David - MVP" wrote: > >> On Fri, 21 Jul 2006 09:46:02 -0700, Cody Lewis >> <CodyLewis@discussions.microsoft.com> wrote: >> >> >My problem is my account locks out every 10 minutes. (W2K domain) No other >> >account has a problem. Over the past 3 days I have narrowed it down to the >> >exchange server. >> >> What do you mean you narrowed it down to the Exch Server? > >Do these steps listed not direct the problem to the exchange server? >Shut each DC down one at a time acct still locks. >Shut don exchange server account doesnt lock >Shut down exchange service acct still locks >I have also shut down all non MS services and the acct still locks > What do the security event logs say? > >Sorry should have included that >I get Event 539 Logon process ADVAPI logon type 3 followed by Event 681 >Error code was 321225572, these errors repeat until acct is locked. I have >the policy set at 10 bad attempts until lockout. Right, but the security logs typically show the calling server (either one the server in question or on the DC the account gets locked on), so I am wondering why you went through all those steps. Logon type 3 is a network logon, so it could be logon to IIS, or a shared printer or mapped drive, etc/// > >> >> > >> >Shut each DC down one at a time acct still locks. >> >Shut don exchange server account doesnt lock >> >Shut down exchange service acct still locks >> >I have also shut down all non MS services and the acct still locks >> > >> >I am confident the problem exists on the exchange server seperate from the >> >exchange services. The MS services that are running on the Exchange 2000 >> >server are: >> > >> >alerter >> >computer browser >> >dist file system >> >dhcp cllient >> >logical disk mgr >> >dns client >> >event log >> >com+ event system >> >IIS admin >> >server >> >workstation >> >license logging service >> >tcp/ip netbios helper >> >messenger >> >distributed transaction coordinator >> >MS Exch information store >> >MS Exch system attendant >> >net logon >> >network connections >> >network news transport protocol >> >NT LM security support prov >> >plug n play >> >IPSEC policy agent >> >protected storage >> >remote registry >> >MS Exch routing engine >> >RPC locator >> >RPC >> >SAM >> >task scheduler >> >run as >> >system event >> >smtp >> >print spooler >> >term services >> >dist link tracking client >> >windows time >> >WWW publihing >> >windows mgt instrumentaion >> >windows mgt instrumentaion driver >> >automatic updates >> > >> >Of these which ones can I safely shut down w/o affecting exchange during >> >production. I can then shut the others down after hours. >> > >> >Any suggestions would greatly appreciated as my next step may require >> >gasoline a match and a pack of hotdogs. >> > >> >Thanks in advance. >> >Cody >>
I have dont that as well. All services run as the administrator acct. "Ben Winzenz [Exchange MVP]" wrote: > Instead of trying to shut down services, why don't you look at the services > that are started from the Services Applet, and see if any of them are > configured to run as your account? If so, which ones? > > -- > Ben Winzenz > Exchange MVP > MessageOne > Read my blog! > http://winzenz.blogspot.com > http://feeds.feedburner.com/winzenz (RSS Feed) > > > "Cody Lewis" <CodyLewis@discussions.microsoft.com> wrote in message > news:FC23EF79-76B6-4F0D-B40D-3678360B083F@microsoft.com... > > My problem is my account locks out every 10 minutes. (W2K domain) No > > other > > account has a problem. Over the past 3 days I have narrowed it down to > > the > > exchange server. > > > > Shut each DC down one at a time acct still locks. > > Shut don exchange server account doesnt lock > > Shut down exchange service acct still locks > > I have also shut down all non MS services and the acct still locks > > > > I am confident the problem exists on the exchange server seperate from the > > exchange services. The MS services that are running on the Exchange 2000 > > server are: > > > > alerter > > computer browser > > dist file system > > dhcp cllient > > logical disk mgr > > dns client > > event log > > com+ event system > > IIS admin > > server > > workstation > > license logging service > > tcp/ip netbios helper > > messenger > > distributed transaction coordinator > > MS Exch information store > > MS Exch system attendant > > net logon > > network connections > > network news transport protocol > > NT LM security support prov > > plug n play > > IPSEC policy agent > > protected storage > > remote registry > > MS Exch routing engine > > RPC locator > > RPC > > SAM > > task scheduler > > run as > > system event > > smtp > > print spooler > > term services > > dist link tracking client > > windows time > > WWW publihing > > windows mgt instrumentaion > > windows mgt instrumentaion driver > > automatic updates > > > > Of these which ones can I safely shut down w/o affecting exchange during > > production. I can then shut the others down after hours. > > > > Any suggestions would greatly appreciated as my next step may require > > gasoline a match and a pack of hotdogs. > > > > Thanks in advance. > > Cody > > >
right...and have you changed your password lately? if you have a persistent connection to anything like Andy mentioned, and you recently changed your pw and have not disconnected and re-connected, that could be the problem... -- Susan Conkey [MVP] "Andy David - MVP" <adavid@pleasekeepinngcheesebucket.com> wrote in message news:uk52c2924a1i5agbpi6d3ekphqireegnv7@4ax.com... > On Fri, 21 Jul 2006 10:57:02 -0700, Cody Lewis > <CodyLewis@discussions.microsoft.com> wrote: > > > > > > >"Andy David - MVP" wrote: > > > >> On Fri, 21 Jul 2006 09:46:02 -0700, Cody Lewis > >> <CodyLewis@discussions.microsoft.com> wrote: > >> > >> >My problem is my account locks out every 10 minutes. (W2K domain) No other > >> >account has a problem. Over the past 3 days I have narrowed it down to the > >> >exchange server. > >> > >> What do you mean you narrowed it down to the Exch Server? > > > >Do these steps listed not direct the problem to the exchange server? > >Shut each DC down one at a time acct still locks. > >Shut don exchange server account doesnt lock > >Shut down exchange service acct still locks > >I have also shut down all non MS services and the acct still locks > > What do the security event logs say? > > > >Sorry should have included that > >I get Event 539 Logon process ADVAPI logon type 3 followed by Event 681 > >Error code was 321225572, these errors repeat until acct is locked. I have > >the policy set at 10 bad attempts until lockout. > > Right, but the security logs typically show the calling server (either > one the server in question or on the DC the account gets locked on), > so I am wondering why you went through all those steps. > Logon type 3 is a network logon, so it could be logon to IIS, or a > shared printer or mapped drive, etc/// > > > > >> > >> > > >> >Shut each DC down one at a time acct still locks. > >> >Shut don exchange server account doesnt lock > >> >Shut down exchange service acct still locks > >> >I have also shut down all non MS services and the acct still locks > >> > > >> >I am confident the problem exists on the exchange server seperate from the > >> >exchange services. The MS services that are running on the Exchange 2000 > >> >server are: > >> > > >> >alerter > >> >computer browser > >> >dist file system > >> >dhcp cllient > >> >logical disk mgr > >> >dns client > >> >event log > >> >com+ event system > >> >IIS admin > >> >server > >> >workstation > >> >license logging service > >> >tcp/ip netbios helper > >> >messenger > >> >distributed transaction coordinator > >> >MS Exch information store > >> >MS Exch system attendant > >> >net logon > >> >network connections > >> >network news transport protocol > >> >NT LM security support prov > >> >plug n play > >> >IPSEC policy agent > >> >protected storage > >> >remote registry > >> >MS Exch routing engine > >> >RPC locator > >> >RPC > >> >SAM > >> >task scheduler > >> >run as > >> >system event > >> >smtp > >> >print spooler > >> >term services > >> >dist link tracking client > >> >windows time > >> >WWW publihing > >> >windows mgt instrumentaion > >> >windows mgt instrumentaion driver > >> >automatic updates > >> > > >> >Of these which ones can I safely shut down w/o affecting exchange during > >> >production. I can then shut the others down after hours. > >> > > >> >Any suggestions would greatly appreciated as my next step may require > >> >gasoline a match and a pack of hotdogs. > >> > > >> >Thanks in advance. > >> >Cody > >>
It seemed like a logical progression of steps to go through. I am up for suggestion at this point. I diconnected all Mapped Drives, I dont have disconnected term serv sessions, I ddint look at shared printers I will look at that. Do you think that the problem could exist on a different machine? Thanks Cody " > > Right, but the security logs typically show the calling server (either > one the server in question or on the DC the account gets locked on), > so I am wondering why you went through all those steps. > Logon type 3 is a network logon, so it could be logon to IIS, or a > shared printer or mapped drive, etc/// >
I did change my password and that is the start of this issue. How can I track down a persistant connection? "Susan" wrote: > right...and have you changed your password lately? if you have a persistent > connection to anything like Andy mentioned, and you recently changed your pw > and have not disconnected and re-connected, that could be the problem... > > -- > Susan Conkey [MVP] > > > > "Andy David - MVP" <adavid@pleasekeepinngcheesebucket.com> wrote in message > news:uk52c2924a1i5agbpi6d3ekphqireegnv7@4ax.com... > > On Fri, 21 Jul 2006 10:57:02 -0700, Cody Lewis > > <CodyLewis@discussions.microsoft.com> wrote: > > > > > > > > > > >"Andy David - MVP" wrote: > > > > > >> On Fri, 21 Jul 2006 09:46:02 -0700, Cody Lewis > > >> <CodyLewis@discussions.microsoft.com> wrote: > > >> > > >> >My problem is my account locks out every 10 minutes. (W2K domain) No > other > > >> >account has a problem. Over the past 3 days I have narrowed it down > to the > > >> >exchange server. > > >> > > >> What do you mean you narrowed it down to the Exch Server? > > > > > >Do these steps listed not direct the problem to the exchange server? > > >Shut each DC down one at a time acct still locks. > > >Shut don exchange server account doesnt lock > > >Shut down exchange service acct still locks > > >I have also shut down all non MS services and the acct still locks > > > What do the security event logs say? > > > > > >Sorry should have included that > > >I get Event 539 Logon process ADVAPI logon type 3 followed by Event 681 > > >Error code was 321225572, these errors repeat until acct is locked. I > have > > >the policy set at 10 bad attempts until lockout. > > > > Right, but the security logs typically show the calling server (either > > one the server in question or on the DC the account gets locked on), > > so I am wondering why you went through all those steps. > > Logon type 3 is a network logon, so it could be logon to IIS, or a > > shared printer or mapped drive, etc/// > > > > > > > >> > > >> > > > >> >Shut each DC down one at a time acct still locks. > > >> >Shut don exchange server account doesnt lock > > >> >Shut down exchange service acct still locks > > >> >I have also shut down all non MS services and the acct still locks > > >> > > > >> >I am confident the problem exists on the exchange server seperate from > the > > >> >exchange services. The MS services that are running on the Exchange > 2000 > > >> >server are: > > >> > > > >> >alerter > > >> >computer browser > > >> >dist file system > > >> >dhcp cllient > > >> >logical disk mgr > > >> >dns client > > >> >event log > > >> >com+ event system > > >> >IIS admin > > >> >server > > >> >workstation > > >> >license logging service > > >> >tcp/ip netbios helper > > >> >messenger > > >> >distributed transaction coordinator > > >> >MS Exch information store > > >> >MS Exch system attendant > > >> >net logon > > >> >network connections > > >> >network news transport protocol > > >> >NT LM security support prov > > >> >plug n play > > >> >IPSEC policy agent > > >> >protected storage > > >> >remote registry > > >> >MS Exch routing engine > > >> >RPC locator > > >> >RPC > > >> >SAM > > >> >task scheduler > > >> >run as > > >> >system event > > >> >smtp > > >> >print spooler > > >> >term services > > >> >dist link tracking client > > >> >windows time > > >> >WWW publihing > > >> >windows mgt instrumentaion > > >> >windows mgt instrumentaion driver > > >> >automatic updates > > >> > > > >> >Of these which ones can I safely shut down w/o affecting exchange > during > > >> >production. I can then shut the others down after hours. > > >> > > > >> >Any suggestions would greatly appreciated as my next step may require > > >> >gasoline a match and a pack of hotdogs. > > >> > > > >> >Thanks in advance. > > >> >Cody > > >> > > >
if you're connected to anything from a different machine, yes... -- Susan Conkey [MVP] "Cody Lewis" <CodyLewis@discussions.microsoft.com> wrote in message news:7C2B7781-515E-4FCA-9764-44B3E2AEA3CC@microsoft.com... > It seemed like a logical progression of steps to go through. I am up for > suggestion at this point. I diconnected all Mapped Drives, I dont have > disconnected term serv sessions, I ddint look at shared printers I will look > at that. Do you think that the problem could exist on a different machine? > > Thanks > Cody > > " > > > > Right, but the security logs typically show the calling server (either > > one the server in question or on the DC the account gets locked on), > > so I am wondering why you went through all those steps. > > Logon type 3 is a network logon, so it could be logon to IIS, or a > > shared printer or mapped drive, etc/// > > >
it's not easy...in the meantime, you might want to change your password back to what it was, if your policies allow that, until you can track it down...somewhere, your account is trying to access a network resource with the old password...could be a connection to something, or some service running somewhere trying to run under your account...are there any services or functions failing somewhere? -- Susan Conkey [MVP] "Cody Lewis" <CodyLewis@discussions.microsoft.com> wrote in message news:0209DFE7-3D6F-4213-B2D8-364487ED9E5A@microsoft.com... > I did change my password and that is the start of this issue. How can I > track down a persistant connection? > > "Susan" wrote: > > > right...and have you changed your password lately? if you have a persistent > > connection to anything like Andy mentioned, and you recently changed your pw > > and have not disconnected and re-connected, that could be the problem... > > > > -- > > Susan Conkey [MVP] > > > > > > > > "Andy David - MVP" <adavid@pleasekeepinngcheesebucket.com> wrote in message > > news:uk52c2924a1i5agbpi6d3ekphqireegnv7@4ax.com... > > > On Fri, 21 Jul 2006 10:57:02 -0700, Cody Lewis > > > <CodyLewis@discussions.microsoft.com> wrote: > > > > > > > > > > > > > > >"Andy David - MVP" wrote: > > > > > > > >> On Fri, 21 Jul 2006 09:46:02 -0700, Cody Lewis > > > >> <CodyLewis@discussions.microsoft.com> wrote: > > > >> > > > >> >My problem is my account locks out every 10 minutes. (W2K domain) No > > other > > > >> >account has a problem. Over the past 3 days I have narrowed it down > > to the > > > >> >exchange server. > > > >> > > > >> What do you mean you narrowed it down to the Exch Server? > > > > > > > >Do these steps listed not direct the problem to the exchange server? > > > >Shut each DC down one at a time acct still locks. > > > >Shut don exchange server account doesnt lock > > > >Shut down exchange service acct still locks > > > >I have also shut down all non MS services and the acct still locks > > > > What do the security event logs say? > > > > > > > >Sorry should have included that > > > >I get Event 539 Logon process ADVAPI logon type 3 followed by Event 681 > > > >Error code was 321225572, these errors repeat until acct is locked. I > > have > > > >the policy set at 10 bad attempts until lockout. > > > > > > Right, but the security logs typically show the calling server (either > > > one the server in question or on the DC the account gets locked on), > > > so I am wondering why you went through all those steps. > > > Logon type 3 is a network logon, so it could be logon to IIS, or a > > > shared printer or mapped drive, etc/// > > > > > > > > > > >> > > > >> > > > > >> >Shut each DC down one at a time acct still locks. > > > >> >Shut don exchange server account doesnt lock > > > >> >Shut down exchange service acct still locks > > > >> >I have also shut down all non MS services and the acct still locks > > > >> > > > > >> >I am confident the problem exists on the exchange server seperate from > > the > > > >> >exchange services. The MS services that are running on the Exchange > > 2000 > > > >> >server are: > > > >> > > > > >> >alerter > > > >> >computer browser > > > >> >dist file system > > > >> >dhcp cllient > > > >> >logical disk mgr > > > >> >dns client > > > >> >event log > > > >> >com+ event system > > > >> >IIS admin > > > >> >server > > > >> >workstation > > > >> >license logging service > > > >> >tcp/ip netbios helper > > > >> >messenger > > > >> >distributed transaction coordinator > > > >> >MS Exch information store > > > >> >MS Exch system attendant > > > >> >net logon > > > >> >network connections > > > >> >network news transport protocol > > > >> >NT LM security support prov > > > >> >plug n play > > > >> >IPSEC policy agent > > > >> >protected storage > > > >> >remote registry > > > >> >MS Exch routing engine > > > >> >RPC locator > > > >> >RPC > > > >> >SAM > > > >> >task scheduler > > > >> >run as > > > >> >system event > > > >> >smtp > > > >> >print spooler > > > >> >term services > > > >> >dist link tracking client > > > >> >windows time > > > >> >WWW publihing > > > >> >windows mgt instrumentaion > > > >> >windows mgt instrumentaion driver > > > >> >automatic updates > > > >> > > > > >> >Of these which ones can I safely shut down w/o affecting exchange > > during > > > >> >production. I can then shut the others down after hours. > > > >> > > > > >> >Any suggestions would greatly appreciated as my next step may require > > > >> >gasoline a match and a pack of hotdogs. > > > >> > > > > >> >Thanks in advance. > > > >> >Cody > > > >> > > > > > >
Susan that is an good idea, I just reset the password back the original, I will post back if it locks again. As far as I can tell nothing is failing. The morning after I changed the password, I started modifying rights on a public folder, then i noticed the problem I dont know if it is connected at all. Thanks for your help Cody "Susan" wrote: > it's not easy...in the meantime, you might want to change your password back > to what it was, if your policies allow that, until you can track it > down...somewhere, your account is trying to access a network resource with > the old password...could be a connection to something, or some service > running somewhere trying to run under your account...are there any services > or functions failing somewhere? > > -- > Susan Conkey [MVP] > > > > "Cody Lewis" <CodyLewis@discussions.microsoft.com> wrote in message > news:0209DFE7-3D6F-4213-B2D8-364487ED9E5A@microsoft.com... > > I did change my password and that is the start of this issue. How can I > > track down a persistant connection? > > > > "Susan" wrote: > > > > > right...and have you changed your password lately? if you have a > persistent > > > connection to anything like Andy mentioned, and you recently changed > your pw > > > and have not disconnected and re-connected, that could be the problem... > > > > > > -- > > > Susan Conkey [MVP] > > > > > > > > > > > > "Andy David - MVP" <adavid@pleasekeepinngcheesebucket.com> wrote in > message > > > news:uk52c2924a1i5agbpi6d3ekphqireegnv7@4ax.com... > > > > On Fri, 21 Jul 2006 10:57:02 -0700, Cody Lewis > > > > <CodyLewis@discussions.microsoft.com> wrote: > > > > > > > > > > > > > > > > > > >"Andy David - MVP" wrote: > > > > > > > > > >> On Fri, 21 Jul 2006 09:46:02 -0700, Cody Lewis > > > > >> <CodyLewis@discussions.microsoft.com> wrote: > > > > >> > > > > >> >My problem is my account locks out every 10 minutes. (W2K domain) > No > > > other > > > > >> >account has a problem. Over the past 3 days I have narrowed it > down > > > to the > > > > >> >exchange server. > > > > >> > > > > >> What do you mean you narrowed it down to the Exch Server? > > > > > > > > > >Do these steps listed not direct the problem to the exchange server? > > > > >Shut each DC down one at a time acct still locks. > > > > >Shut don exchange server account doesnt lock > > > > >Shut down exchange service acct still locks > > > > >I have also shut down all non MS services and the acct still locks > > > > > What do the security event logs say? > > > > > > > > > >Sorry should have included that > > > > >I get Event 539 Logon process ADVAPI logon type 3 followed by Event > 681 > > > > >Error code was 321225572, these errors repeat until acct is locked. > I > > > have > > > > >the policy set at 10 bad attempts until lockout. > > > > > > > > Right, but the security logs typically show the calling server (either > > > > one the server in question or on the DC the account gets locked on), > > > > so I am wondering why you went through all those steps. > > > > Logon type 3 is a network logon, so it could be logon to IIS, or a > > > > shared printer or mapped drive, etc/// > > > > > > > > > > > > > >> > > > > >> > > > > > >> >Shut each DC down one at a time acct still locks. > > > > >> >Shut don exchange server account doesnt lock > > > > >> >Shut down exchange service acct still locks > > > > >> >I have also shut down all non MS services and the acct still locks > > > > >> > > > > > >> >I am confident the problem exists on the exchange server seperate > from > > > the > > > > >> >exchange services. The MS services that are running on the > Exchange > > > 2000 > > > > >> >server are: > > > > >> > > > > > >> >alerter > > > > >> >computer browser > > > > >> >dist file system > > > > >> >dhcp cllient > > > > >> >logical disk mgr > > > > >> >dns client > > > > >> >event log > > > > >> >com+ event system > > > > >> >IIS admin > > > > >> >server > > > > >> >workstation > > > > >> >license logging service > > > > >> >tcp/ip netbios helper > > > > >> >messenger > > > > >> >distributed transaction coordinator > > > > >> >MS Exch information store > > > > >> >MS Exch system attendant > > > > >> >net logon > > > > >> >network connections > > > > >> >network news transport protocol > > > > >> >NT LM security support prov > > > > >> >plug n play > > > > >> >IPSEC policy agent > > > > >> >protected storage > > > > >> >remote registry > > > > >> >MS Exch routing engine > > > > >> >RPC locator > > > > >> >RPC > > > > >> >SAM > > > > >> >task scheduler > > > > >> >run as > > > > >> >system event > > > > >> >smtp > > > > >> >print spooler > > > > >> >term services > > > > >> >dist link tracking client > > > > >> >windows time > > > > >> >WWW publihing > > > > >> >windows mgt instrumentaion > > > > >> >windows mgt instrumentaion driver > > > > >> >automatic updates > > > > >> > > > > > >> >Of these which ones can I safely shut down w/o affecting exchange > > > during > > > > >> >production. I can then shut the others down after hours. > > > > >> > > > > > >> >Any suggestions would greatly appreciated as my next step may > require > > > > >> >gasoline a match and a pack of hotdogs. > > > > >> > > > > > >> >Thanks in advance. > > > > >> >Cody > > > > >> > > > > > > > > > > > >
Don't forget to check things like scheduled tasks. You might also check into downloading and running Process Explorer from Sysinternals - you can add a column to see which processes are running as which user. -- Ben Winzenz Exchange MVP MessageOne Read my blog! http://winzenz.blogspot.com http://feeds.feedburner.com/winzenz (RSS Feed) "Cody Lewis" <CodyLewis@discussions.microsoft.com> wrote in message news:A0E31A87-9A5C-4CF0-8E50-302F0081D4BA@microsoft.com... > Susan that is an good idea, I just reset the password back the original, I > will post back if it locks again. As far as I can tell nothing is > failing. > > The morning after I changed the password, I started modifying rights on a > public folder, then i noticed the problem I dont know if it is connected > at > all. > > Thanks for your help > Cody > > "Susan" wrote: > >> it's not easy...in the meantime, you might want to change your password >> back >> to what it was, if your policies allow that, until you can track it >> down...somewhere, your account is trying to access a network resource >> with >> the old password...could be a connection to something, or some service >> running somewhere trying to run under your account...are there any >> services >> or functions failing somewhere? >> >> -- >> Susan Conkey [MVP] >> >> >> >> "Cody Lewis" <CodyLewis@discussions.microsoft.com> wrote in message >> news:0209DFE7-3D6F-4213-B2D8-364487ED9E5A@microsoft.com... >> > I did change my password and that is the start of this issue. How can >> > I >> > track down a persistant connection? >> > >> > "Susan" wrote: >> > >> > > right...and have you changed your password lately? if you have a >> persistent >> > > connection to anything like Andy mentioned, and you recently changed >> your pw >> > > and have not disconnected and re-connected, that could be the >> > > problem... >> > > >> > > -- >> > > Susan Conkey [MVP] >> > > >> > > >> > > >> > > "Andy David - MVP" <adavid@pleasekeepinngcheesebucket.com> wrote in >> message >> > > news:uk52c2924a1i5agbpi6d3ekphqireegnv7@4ax.com... >> > > > On Fri, 21 Jul 2006 10:57:02 -0700, Cody Lewis >> > > > <CodyLewis@discussions.microsoft.com> wrote: >> > > > >> > > > > >> > > > > >> > > > >"Andy David - MVP" wrote: >> > > > > >> > > > >> On Fri, 21 Jul 2006 09:46:02 -0700, Cody Lewis >> > > > >> <CodyLewis@discussions.microsoft.com> wrote: >> > > > >> >> > > > >> >My problem is my account locks out every 10 minutes. (W2K >> > > > >> >domain) >> No >> > > other >> > > > >> >account has a problem. Over the past 3 days I have narrowed it >> down >> > > to the >> > > > >> >exchange server. >> > > > >> >> > > > >> What do you mean you narrowed it down to the Exch Server? >> > > > > >> > > > >Do these steps listed not direct the problem to the exchange >> > > > >server? >> > > > >Shut each DC down one at a time acct still locks. >> > > > >Shut don exchange server account doesnt lock >> > > > >Shut down exchange service acct still locks >> > > > >I have also shut down all non MS services and the acct still locks >> > > > > What do the security event logs say? >> > > > > >> > > > >Sorry should have included that >> > > > >I get Event 539 Logon process ADVAPI logon type 3 followed by >> > > > >Event >> 681 >> > > > >Error code was 321225572, these errors repeat until acct is >> > > > >locked. >> I >> > > have >> > > > >the policy set at 10 bad attempts until lockout. >> > > > >> > > > Right, but the security logs typically show the calling server >> > > > (either >> > > > one the server in question or on the DC the account gets locked >> > > > on), >> > > > so I am wondering why you went through all those steps. >> > > > Logon type 3 is a network logon, so it could be logon to IIS, or a >> > > > shared printer or mapped drive, etc/// >> > > > >> > > > > >> > > > >> >> > > > >> > >> > > > >> >Shut each DC down one at a time acct still locks. >> > > > >> >Shut don exchange server account doesnt lock >> > > > >> >Shut down exchange service acct still locks >> > > > >> >I have also shut down all non MS services and the acct still >> > > > >> >locks >> > > > >> > >> > > > >> >I am confident the problem exists on the exchange server >> > > > >> >seperate >> from >> > > the >> > > > >> >exchange services. The MS services that are running on the >> Exchange >> > > 2000 >> > > > >> >server are: >> > > > >> > >> > > > >> >alerter >> > > > >> >computer browser >> > > > >> >dist file system >> > > > >> >dhcp cllient >> > > > >> >logical disk mgr >> > > > >> >dns client >> > > > >> >event log >> > > > >> >com+ event system >> > > > >> >IIS admin >> > > > >> >server >> > > > >> >workstation >> > > > >> >license logging service >> > > > >> >tcp/ip netbios helper >> > > > >> >messenger >> > > > >> >distributed transaction coordinator >> > > > >> >MS Exch information store >> > > > >> >MS Exch system attendant >> > > > >> >net logon >> > > > >> >network connections >> > > > >> >network news transport protocol >> > > > >> >NT LM security support prov >> > > > >> >plug n play >> > > > >> >IPSEC policy agent >> > > > >> >protected storage >> > > > >> >remote registry >> > > > >> >MS Exch routing engine >> > > > >> >RPC locator >> > > > >> >RPC >> > > > >> >SAM >> > > > >> >task scheduler >> > > > >> >run as >> > > > >> >system event >> > > > >> >smtp >> > > > >> >print spooler >> > > > >> >term services >> > > > >> >dist link tracking client >> > > > >> >windows time >> > > > >> >WWW publihing >> > > > >> >windows mgt instrumentaion >> > > > >> >windows mgt instrumentaion driver >> > > > >> >automatic updates >> > > > >> > >> > > > >> >Of these which ones can I safely shut down w/o affecting >> > > > >> >exchange >> > > during >> > > > >> >production. I can then shut the others down after hours. >> > > > >> > >> > > > >> >Any suggestions would greatly appreciated as my next step may >> require >> > > > >> >gasoline a match and a pack of hotdogs. >> > > > >> > >> > > > >> >Thanks in advance. >> > > > >> >Cody >> > > > >> >> > > >> > > >> > > >> >> >>
![]() |
0 |
![]() |
Thanks Ben I will try that Cody "Ben Winzenz [Exchange MVP]" wrote: > Don't forget to check things like scheduled tasks. > > You might also check into downloading and running Process Explorer from > Sysinternals - you can add a column to see which processes are running as > which user. > > -- > Ben Winzenz > Exchange MVP > MessageOne > Read my blog! > http://winzenz.blogspot.com > http://feeds.feedburner.com/winzenz (RSS Feed) > > > "Cody Lewis" <CodyLewis@discussions.microsoft.com> wrote in message > news:A0E31A87-9A5C-4CF0-8E50-302F0081D4BA@microsoft.com... > > Susan that is an good idea, I just reset the password back the original, I > > will post back if it locks again. As far as I can tell nothing is > > failing. > > > > The morning after I changed the password, I started modifying rights on a > > public folder, then i noticed the problem I dont know if it is connected > > at > > all. > > > > Thanks for your help > > Cody > > > > "Susan" wrote: > > > >> it's not easy...in the meantime, you might want to change your password > >> back > >> to what it was, if your policies allow that, until you can track it > >> down...somewhere, your account is trying to access a network resource > >> with > >> the old password...could be a connection to something, or some service > >> running somewhere trying to run under your account...are there any > >> services > >> or functions failing somewhere? > >> > >> -- > >> Susan Conkey [MVP] > >> > >> > >> > >> "Cody Lewis" <CodyLewis@discussions.microsoft.com> wrote in message > >> news:0209DFE7-3D6F-4213-B2D8-364487ED9E5A@microsoft.com... > >> > I did change my password and that is the start of this issue. How can > >> > I > >> > track down a persistant connection? > >> > > >> > "Susan" wrote: > >> > > >> > > right...and have you changed your password lately? if you have a > >> persistent > >> > > connection to anything like Andy mentioned, and you recently changed > >> your pw > >> > > and have not disconnected and re-connected, that could be the > >> > > problem... > >> > > > >> > > -- > >> > > Susan Conkey [MVP] > >> > > > >> > > > >> > > > >> > > "Andy David - MVP" <adavid@pleasekeepinngcheesebucket.com> wrote in > >> message > >> > > news:uk52c2924a1i5agbpi6d3ekphqireegnv7@4ax.com... > >> > > > On Fri, 21 Jul 2006 10:57:02 -0700, Cody Lewis > >> > > > <CodyLewis@discussions.microsoft.com> wrote: > >> > > > > >> > > > > > >> > > > > > >> > > > >"Andy David - MVP" wrote: > >> > > > > > >> > > > >> On Fri, 21 Jul 2006 09:46:02 -0700, Cody Lewis > >> > > > >> <CodyLewis@discussions.microsoft.com> wrote: > >> > > > >> > >> > > > >> >My problem is my account locks out every 10 minutes. (W2K > >> > > > >> >domain) > >> No > >> > > other > >> > > > >> >account has a problem. Over the past 3 days I have narrowed it > >> down > >> > > to the > >> > > > >> >exchange server. > >> > > > >> > >> > > > >> What do you mean you narrowed it down to the Exch Server? > >> > > > > > >> > > > >Do these steps listed not direct the problem to the exchange > >> > > > >server? > >> > > > >Shut each DC down one at a time acct still locks. > >> > > > >Shut don exchange server account doesnt lock > >> > > > >Shut down exchange service acct still locks > >> > > > >I have also shut down all non MS services and the acct still locks > >> > > > > What do the security event logs say? > >> > > > > > >> > > > >Sorry should have included that > >> > > > >I get Event 539 Logon process ADVAPI logon type 3 followed by > >> > > > >Event > >> 681 > >> > > > >Error code was 321225572, these errors repeat until acct is > >> > > > >locked. > >> I > >> > > have > >> > > > >the policy set at 10 bad attempts until lockout. > >> > > > > >> > > > Right, but the security logs typically show the calling server > >> > > > (either > >> > > > one the server in question or on the DC the account gets locked > >> > > > on), > >> > > > so I am wondering why you went through all those steps. > >> > > > Logon type 3 is a network logon, so it could be logon to IIS, or a > >> > > > shared printer or mapped drive, etc/// > >> > > > > >> > > > > > >> > > > >> > >> > > > >> > > >> > > > >> >Shut each DC down one at a time acct still locks. > >> > > > >> >Shut don exchange server account doesnt lock > >> > > > >> >Shut down exchange service acct still locks > >> > > > >> >I have also shut down all non MS services and the acct still > >> > > > >> >locks > >> > > > >> > > >> > > > >> >I am confident the problem exists on the exchange server > >> > > > >> >seperate > >> from > >> > > the > >> > > > >> >exchange services. The MS services that are running on the > >> Exchange > >> > > 2000 > >> > > > >> >server are: > >> > > > >> > > >> > > > >> >alerter > >> > > > >> >computer browser > >> > > > >> >dist file system > >> > > > >> >dhcp cllient > >> > > > >> >logical disk mgr > >> > > > >> >dns client > >> > > > >> >event log > >> > > > >> >com+ event system > >> > > > >> >IIS admin > >> > > > >> >server > >> > > > >> >workstation > >> > > > >> >license logging service > >> > > > >> >tcp/ip netbios helper > >> > > > >> >messenger > >> > > > >> >distributed transaction coordinator > >> > > > >> >MS Exch information store > >> > > > >> >MS Exch system attendant > >> > > > >> >net logon > >> > > > >> >network connections > >> > > > >> >network news transport protocol > >> > > > >> >NT LM security support prov > >> > > > >> >plug n play > >> > > > >> >IPSEC policy agent > >> > > > >> >protected storage > >> > > > >> >remote registry > >> > > > >> >MS Exch routing engine > >> > > > >> >RPC locator > >> > > > >> >RPC > >> > > > >> >SAM > >> > > > >> >task scheduler > >> > > > >> >run as > >> > > > >> >system event > >> > > > >> >smtp > >> > > > >> >print spooler > >> > > > >> >term services > >> > > > >> >dist link tracking client > >> > > > >> >windows time > >> > > > >> >WWW publihing > >> > > > >> >windows mgt instrumentaion > >> > > > >> >windows mgt instrumentaion driver > >> > > > >> >automatic updates > >> > > > >> > > >> > > > >> >Of these which ones can I safely shut down w/o affecting > >> > > > >> >exchange > >> > > during > >> > > > >> >production. I can then shut the others down after hours. > >> > > > >> > > >> > > > >> >Any suggestions would greatly appreciated as my next step may > >> require > >> > > > >> >gasoline a match and a pack of hotdogs. > >> > > > >> > > >> > > > >> >Thanks in advance. > >> > > > >> >Cody > >> > > > >> > >> > > > >> > > > >> > > > >> > >> > >> > > >
Hi Susan, The acct locked again. I went back two passwords no luck. Thanks "Susan" wrote: > it's not easy...in the meantime, you might want to change your password back > to what it was, if your policies allow that, until you can track it > down...somewhere, your account is trying to access a network resource with > the old password...could be a connection to something, or some service > running somewhere trying to run under your account...are there any services > or functions failing somewhere? > > -- > Susan Conkey [MVP] > > > > "Cody Lewis" <CodyLewis@discussions.microsoft.com> wrote in message > news:0209DFE7-3D6F-4213-B2D8-364487ED9E5A@microsoft.com... > > I did change my password and that is the start of this issue. How can I > > track down a persistant connection? > > > > "Susan" wrote: > > > > > right...and have you changed your password lately? if you have a > persistent > > > connection to anything like Andy mentioned, and you recently changed > your pw > > > and have not disconnected and re-connected, that could be the problem... > > > > > > -- > > > Susan Conkey [MVP] > > > > > > > > > > > > "Andy David - MVP" <adavid@pleasekeepinngcheesebucket.com> wrote in > message > > > news:uk52c2924a1i5agbpi6d3ekphqireegnv7@4ax.com... > > > > On Fri, 21 Jul 2006 10:57:02 -0700, Cody Lewis > > > > <CodyLewis@discussions.microsoft.com> wrote: > > > > > > > > > > > > > > > > > > >"Andy David - MVP" wrote: > > > > > > > > > >> On Fri, 21 Jul 2006 09:46:02 -0700, Cody Lewis > > > > >> <CodyLewis@discussions.microsoft.com> wrote: > > > > >> > > > > >> >My problem is my account locks out every 10 minutes. (W2K domain) > No > > > other > > > > >> >account has a problem. Over the past 3 days I have narrowed it > down > > > to the > > > > >> >exchange server. > > > > >> > > > > >> What do you mean you narrowed it down to the Exch Server? > > > > > > > > > >Do these steps listed not direct the problem to the exchange server? > > > > >Shut each DC down one at a time acct still locks. > > > > >Shut don exchange server account doesnt lock > > > > >Shut down exchange service acct still locks > > > > >I have also shut down all non MS services and the acct still locks > > > > > What do the security event logs say? > > > > > > > > > >Sorry should have included that > > > > >I get Event 539 Logon process ADVAPI logon type 3 followed by Event > 681 > > > > >Error code was 321225572, these errors repeat until acct is locked. > I > > > have > > > > >the policy set at 10 bad attempts until lockout. > > > > > > > > Right, but the security logs typically show the calling server (either > > > > one the server in question or on the DC the account gets locked on), > > > > so I am wondering why you went through all those steps. > > > > Logon type 3 is a network logon, so it could be logon to IIS, or a > > > > shared printer or mapped drive, etc/// > > > > > > > > > > > > > >> > > > > >> > > > > > >> >Shut each DC down one at a time acct still locks. > > > > >> >Shut don exchange server account doesnt lock > > > > >> >Shut down exchange service acct still locks > > > > >> >I have also shut down all non MS services and the acct still locks > > > > >> > > > > > >> >I am confident the problem exists on the exchange server seperate > from > > > the > > > > >> >exchange services. The MS services that are running on the > Exchange > > > 2000 > > > > >> >server are: > > > > >> > > > > > >> >alerter > > > > >> >computer browser > > > > >> >dist file system > > > > >> >dhcp cllient > > > > >> >logical disk mgr > > > > >> >dns client > > > > >> >event log > > > > >> >com+ event system > > > > >> >IIS admin > > > > >> >server > > > > >> >workstation > > > > >> >license logging service > > > > >> >tcp/ip netbios helper > > > > >> >messenger > > > > >> >distributed transaction coordinator > > > > >> >MS Exch information store > > > > >> >MS Exch system attendant > > > > >> >net logon > > > > >> >network connections > > > > >> >network news transport protocol > > > > >> >NT LM security support prov > > > > >> >plug n play > > > > >> >IPSEC policy agent > > > > >> >protected storage > > > > >> >remote registry > > > > >> >MS Exch routing engine > > > > >> >RPC locator > > > > >> >RPC > > > > >> >SAM > > > > >> >task scheduler > > > > >> >run as > > > > >> >system event > > > > >> >smtp > > > > >> >print spooler > > > > >> >term services > > > > >> >dist link tracking client > > > > >> >windows time > > > > >> >WWW publihing > > > > >> >windows mgt instrumentaion > > > > >> >windows mgt instrumentaion driver > > > > >> >automatic updates > > > > >> > > > > > >> >Of these which ones can I safely shut down w/o affecting exchange > > > during > > > > >> >production. I can then shut the others down after hours. > > > > >> > > > > > >> >Any suggestions would greatly appreciated as my next step may > require > > > > >> >gasoline a match and a pack of hotdogs. > > > > >> > > > > > >> >Thanks in advance. > > > > >> >Cody > > > > >> > > > > > > > > > > > >
The services all ran under the domain admin acct. Thanks "Ben Winzenz [Exchange MVP]" wrote: > Don't forget to check things like scheduled tasks. > > You might also check into downloading and running Process Explorer from > Sysinternals - you can add a column to see which processes are running as > which user. > > -- > Ben Winzenz > Exchange MVP > MessageOne > Read my blog! > http://winzenz.blogspot.com > http://feeds.feedburner.com/winzenz (RSS Feed) > > > "Cody Lewis" <CodyLewis@discussions.microsoft.com> wrote in message > news:A0E31A87-9A5C-4CF0-8E50-302F0081D4BA@microsoft.com... > > Susan that is an good idea, I just reset the password back the original, I > > will post back if it locks again. As far as I can tell nothing is > > failing. > > > > The morning after I changed the password, I started modifying rights on a > > public folder, then i noticed the problem I dont know if it is connected > > at > > all. > > > > Thanks for your help > > Cody > > > > "Susan" wrote: > > > >> it's not easy...in the meantime, you might want to change your password > >> back > >> to what it was, if your policies allow that, until you can track it > >> down...somewhere, your account is trying to access a network resource > >> with > >> the old password...could be a connection to something, or some service > >> running somewhere trying to run under your account...are there any > >> services > >> or functions failing somewhere? > >> > >> -- > >> Susan Conkey [MVP] > >> > >> > >> > >> "Cody Lewis" <CodyLewis@discussions.microsoft.com> wrote in message > >> news:0209DFE7-3D6F-4213-B2D8-364487ED9E5A@microsoft.com... > >> > I did change my password and that is the start of this issue. How can > >> > I > >> > track down a persistant connection? > >> > > >> > "Susan" wrote: > >> > > >> > > right...and have you changed your password lately? if you have a > >> persistent > >> > > connection to anything like Andy mentioned, and you recently changed > >> your pw > >> > > and have not disconnected and re-connected, that could be the > >> > > problem... > >> > > > >> > > -- > >> > > Susan Conkey [MVP] > >> > > > >> > > > >> > > > >> > > "Andy David - MVP" <adavid@pleasekeepinngcheesebucket.com> wrote in > >> message > >> > > news:uk52c2924a1i5agbpi6d3ekphqireegnv7@4ax.com... > >> > > > On Fri, 21 Jul 2006 10:57:02 -0700, Cody Lewis > >> > > > <CodyLewis@discussions.microsoft.com> wrote: > >> > > > > >> > > > > > >> > > > > > >> > > > >"Andy David - MVP" wrote: > >> > > > > > >> > > > >> On Fri, 21 Jul 2006 09:46:02 -0700, Cody Lewis > >> > > > >> <CodyLewis@discussions.microsoft.com> wrote: > >> > > > >> > >> > > > >> >My problem is my account locks out every 10 minutes. (W2K > >> > > > >> >domain) > >> No > >> > > other > >> > > > >> >account has a problem. Over the past 3 days I have narrowed it > >> down > >> > > to the > >> > > > >> >exchange server. > >> > > > >> > >> > > > >> What do you mean you narrowed it down to the Exch Server? > >> > > > > > >> > > > >Do these steps listed not direct the problem to the exchange > >> > > > >server? > >> > > > >Shut each DC down one at a time acct still locks. > >> > > > >Shut don exchange server account doesnt lock > >> > > > >Shut down exchange service acct still locks > >> > > > >I have also shut down all non MS services and the acct still locks > >> > > > > What do the security event logs say? > >> > > > > > >> > > > >Sorry should have included that > >> > > > >I get Event 539 Logon process ADVAPI logon type 3 followed by > >> > > > >Event > >> 681 > >> > > > >Error code was 321225572, these errors repeat until acct is > >> > > > >locked. > >> I > >> > > have > >> > > > >the policy set at 10 bad attempts until lockout. > >> > > > > >> > > > Right, but the security logs typically show the calling server > >> > > > (either > >> > > > one the server in question or on the DC the account gets locked > >> > > > on), > >> > > > so I am wondering why you went through all those steps. > >> > > > Logon type 3 is a network logon, so it could be logon to IIS, or a > >> > > > shared printer or mapped drive, etc/// > >> > > > > >> > > > > > >> > > > >> > >> > > > >> > > >> > > > >> >Shut each DC down one at a time acct still locks. > >> > > > >> >Shut don exchange server account doesnt lock > >> > > > >> >Shut down exchange service acct still locks > >> > > > >> >I have also shut down all non MS services and the acct still > >> > > > >> >locks > >> > > > >> > > >> > > > >> >I am confident the problem exists on the exchange server > >> > > > >> >seperate > >> from > >> > > the > >> > > > >> >exchange services. The MS services that are running on the > >> Exchange > >> > > 2000 > >> > > > >> >server are: > >> > > > >> > > >> > > > >> >alerter > >> > > > >> >computer browser > >> > > > >> >dist file system > >> > > > >> >dhcp cllient > >> > > > >> >logical disk mgr > >> > > > >> >dns client > >> > > > >> >event log > >> > > > >> >com+ event system > >> > > > >> >IIS admin > >> > > > >> >server > >> > > > >> >workstation > >> > > > >> >license logging service > >> > > > >> >tcp/ip netbios helper > >> > > > >> >messenger > >> > > > >> >distributed transaction coordinator > >> > > > >> >MS Exch information store > >> > > > >> >MS Exch system attendant > >> > > > >> >net logon > >> > > > >> >network connections > >> > > > >> >network news transport protocol > >> > > > >> >NT LM security support prov > >> > > > >> >plug n play > >> > > > >> >IPSEC policy agent > >> > > > >> >protected storage > >> > > > >> >remote registry > >> > > > >> >MS Exch routing engine > >> > > > >> >RPC locator > >> > > > >> >RPC > >> > > > >> >SAM > >> > > > >> >task scheduler > >> > > > >> >run as > >> > > > >> >system event > >> > > > >> >smtp > >> > > > >> >print spooler > >> > > > >> >term services > >> > > > >> >dist link tracking client > >> > > > >> >windows time > >> > > > >> >WWW publihing > >> > > > >> >windows mgt instrumentaion > >> > > > >> >windows mgt instrumentaion driver > >> > > > >> >automatic updates > >> > > > >> > > >> > > > >> >Of these which ones can I safely shut down w/o affecting > >> > > > >> >exchange > >> > > during > >> > > > >> >production. I can then shut the others down after hours. > >> > > > >> > > >> > > > >> >Any suggestions would greatly appreciated as my next step may > >> require > >> > > > >> >gasoline a match and a pack of hotdogs. > >> > > > >> > > >> > > > >> >Thanks in advance. > >> > > > >> >Cody > >> > > > >> > >> > > > >> > > > >> > > > >> > >> > >> > > >