Outlook 2007 problem - network lockout - PLEASE HELP

S

Sergej Prokoviev

I didn't get an answer from last week, so I am re-posting this:

I recently installed Office 2007 Pro on one of our workstations, which
runs on Windows XP Pro SP2. Our email runs via an app on a server I am
connecting to through the very simple POP3 service Server 2003 came
with. When you create a mailbox, it creates a local user with it (with
a password that does not expire). That local user (SERVERNAME\123) has
the same name as my network logon (DOMAIN\123). I am not an admin on
either machine, just a poweruser on the workstation and a normal user
on the server that is only allowed access to the mailbox.

It used to work fine with Outlook 2003. Now that I have installed
Outlook 2007, it keeps trying to log me on with my network credentials
to the server and ultimately locks me out on the domain controller if I

have Outlook up ("unknown username or password"; "account locked out").

I did check the registry on the workstation, which was missing one key
that Microsoft said I needed. It has been added. However, that did
nothing to fix it. It won't let me unistall TCP/IP as the local admin.


Any thoughts? I'll have to revert back to 2003 if I can't fix it.


Thanks!
 
S

Sergej Prokoviev

Thanks for the prompt reply. I will try and recreate the mail profile
as described in the article you mentioned. However, when I recreated
the same scenario on another computer with the same setup, only a
different user, the exact same thing happened. It seemed to check every
so many minutes for mail, and in doing so locked out the network user.
The local mail user on the server is fine.

Any more thoughts?

Thanks a bunch!
Have you tried it with a new mail profile already?
http://www.howto-outlook.com/faq/newprofile.htm

Also see if you can reproduce this behavior when you logon as a different
user.

--
Robert Sparnaaij [MVP-Outlook]
Coauthor, Configuring Microsoft Outlook 2003


-----
Sergej Prokoviev said:
I didn't get an answer from last week, so I am re-posting this:

I recently installed Office 2007 Pro on one of our workstations, which
runs on Windows XP Pro SP2. Our email runs via an app on a server I am
connecting to through the very simple POP3 service Server 2003 came
with. When you create a mailbox, it creates a local user with it (with
a password that does not expire). That local user (SERVERNAME\123) has
the same name as my network logon (DOMAIN\123). I am not an admin on
either machine, just a poweruser on the workstation and a normal user
on the server that is only allowed access to the mailbox.

It used to work fine with Outlook 2003. Now that I have installed
Outlook 2007, it keeps trying to log me on with my network credentials
to the server and ultimately locks me out on the domain controller if I

have Outlook up ("unknown username or password"; "account locked out").

I did check the registry on the workstation, which was missing one key
that Microsoft said I needed. It has been added. However, that did
nothing to fix it. It won't let me unistall TCP/IP as the local admin.


Any thoughts? I'll have to revert back to 2003 if I can't fix it.


Thanks!
 
S

Sergej Prokoviev

I just created another mailbox that has no associated network user.
Here is the failure audit:

Event Type: Failure Audit
Event Source: Security
Event Category: Logon/Logoff
Event ID: 529
Date: 1/22/2007
Time: 9:25:39 AM
User: NT AUTHORITY\SYSTEM
Computer: ABC-SERVER
Description:
Logon Failure:
Reason: Unknown user name or bad password
User Name: 123N
Domain: domain.com
Logon Type: 3
Logon Process: NtLmSsp
Authentication Package: NTLM
Workstation Name: PC-PCIDABC
Caller User Name: -
Caller Domain: -
Caller Logon ID: -
Caller Process ID: -
Transited Services: -
Source Network Address: -
Source Port: -


For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Then, right after that, I see this:

Event Type: Success Audit
Event Source: Security
Event Category: Account Logon
Event ID: 680
Date: 1/22/2007
Time: 9:25:39 AM
User: ABC-SERVER\123N
Computer: ABC-SERVER
Description:
Logon attempt by: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
Logon account: 123N
Source Workstation: ABC-SERVER
Error Code: 0x0


For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

I honestly don't think that it has to do with the local machine, but
with the way Outlook2007 talks to the server. Please help!
Have you tried it with a new mail profile already?
http://www.howto-outlook.com/faq/newprofile.htm

Also see if you can reproduce this behavior when you logon as a different
user.

--
Robert Sparnaaij [MVP-Outlook]
Coauthor, Configuring Microsoft Outlook 2003


-----
Sergej Prokoviev said:
I didn't get an answer from last week, so I am re-posting this:

I recently installed Office 2007 Pro on one of our workstations, which
runs on Windows XP Pro SP2. Our email runs via an app on a server I am
connecting to through the very simple POP3 service Server 2003 came
with. When you create a mailbox, it creates a local user with it (with
a password that does not expire). That local user (SERVERNAME\123) has
the same name as my network logon (DOMAIN\123). I am not an admin on
either machine, just a poweruser on the workstation and a normal user
on the server that is only allowed access to the mailbox.

It used to work fine with Outlook 2003. Now that I have installed
Outlook 2007, it keeps trying to log me on with my network credentials
to the server and ultimately locks me out on the domain controller if I

have Outlook up ("unknown username or password"; "account locked out").

I did check the registry on the workstation, which was missing one key
that Microsoft said I needed. It has been added. However, that did
nothing to fix it. It won't let me unistall TCP/IP as the local admin.


Any thoughts? I'll have to revert back to 2003 if I can't fix it.


Thanks!
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top