Announcement

Collapse
No announcement yet.

Outlook could not log on....

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Outlook could not log on....

    I get this message with a few people when trying to set up Outlook with Exchange Server 2003:
    Outlook cold not log on. check to make srue you re connected to the network and are using the proper server and mailbox name. The Microsoft Exchange Address Book was unable to log on to the Microsoft Exchange Server computer. Contact your system administrator if the problem persists.

    These acccounts are able to access their e-mail from OWA. One of the things they have in common is they are using roaming profiles (I have many others running roaming profiles with no problems with Outlook). I have tried wiping out their profiles.

    Some other background info on our system. Exchange 2003 running latest service packs on a W2K3 Server running latest service packs. Using AD for authentication (on another W2K3 server). Any help or guidance would be greatly appreciated!
    TIA
    Terry

  • #2
    Re: Outlook could not log on....

    Try restarting the server. That might help.

    Comment


    • #3
      Re: Outlook could not log on....

      Thanks for the suggestion. This is a production server and has been rebooted many times since it has first come up. The problem is I have random people that this affects. Another possibility I think may contribute to the problem is when people change their Windows logon while Outlook is running. I've seen this a couple of times and has been resolved by changing their password back to the original one. Maybe I'll give that a try with the most recent one. Any more ideas would be appreciated. Perhaps a KB? I couldn't find one, and typing in the message in google hasn't led me in the right direction yet!

      Comment


      • #4
        Re: Outlook could not log on....

        Originally posted by tashland
        Thanks for the suggestion. This is a production server and has been rebooted many times since it has first come up. The problem is I have random people that this affects. Another possibility I think may contribute to the problem is when people change their Windows logon while Outlook is running. I've seen this a couple of times and has been resolved by changing their password back to the original one. Maybe I'll give that a try with the most recent one. Any more ideas would be appreciated. Perhaps a KB? I couldn't find one, and typing in the message in google hasn't led me in the right direction yet!
        I have a similar problem, and i cannot reset to the original password.

        I have a user who was let go. Account was disabled, password changed. Now with the account re-enabled, I cannot access the mailbox. Basically treats it like i have the wrong password. And there is no way i can get the original password from the user.

        I guess i am just going to have to forward all of his mail to the other guy, instead of setting up a 2nd profile on his machine. Either way works, i was just hoping to seperate them.
        Last edited by tnelson008; 8th July 2006, 00:44.

        Comment


        • #5
          Re: Outlook could not log on....

          How have you waited since enabling the account? Exchange caches permissions and only flushes those permissions every couple of hours. If you only enabled the account in the last hour or so then there is a good chance that you haven't waited long enough.

          If you can't wait, reboot the server.

          As a rule, I don't disable a user's account when they leave. That avoids these sorts of problems.

          Simon.
          --
          Simon Butler
          Exchange MVP

          Blog: http://blog.sembee.co.uk/
          More Exchange Content: http://exchange.sembee.info/
          Exchange Resources List: http://exbpa.com/
          In the UK? Hire me: http://www.sembee.co.uk/

          Sembee is a registered trademark, used here with permission.

          Comment


          • #6
            Re: Outlook could not log on....

            Originally posted by Sembee
            How have you waited since enabling the account? Exchange caches permissions and only flushes those permissions every couple of hours. If you only enabled the account in the last hour or so then there is a good chance that you haven't waited long enough.

            If you can't wait, reboot the server.

            As a rule, I don't disable a user's account when they leave. That avoids these sorts of problems.

            Simon.
            Its been around an hour since it was re-enabled. I didnt have much choice on the disabling, my boss called me and said to disable it. I will have to reboot the server later on this weekend if it doesnt kick over by tomorrow morning.

            Comment


            • #7
              Re: Outlook could not log on....

              Originally posted by tnelson008
              Its been around an hour since it was re-enabled. I didnt have much choice on the disabling, my boss called me and said to disable it. I will have to reboot the server later on this weekend if it doesnt kick over by tomorrow morning.
              It should have kicked over by the morning.
              If you get a call like that again, still don't disable. Simply change the password on the user account. If they are still accessing the account, Outlook will lock the account out in about two minutes.

              Simon.
              --
              Simon Butler
              Exchange MVP

              Blog: http://blog.sembee.co.uk/
              More Exchange Content: http://exchange.sembee.info/
              Exchange Resources List: http://exbpa.com/
              In the UK? Hire me: http://www.sembee.co.uk/

              Sembee is a registered trademark, used here with permission.

              Comment


              • #8
                Re: Outlook could not log on....

                Originally posted by Sembee
                It should have kicked over by the morning.
                If you get a call like that again, still don't disable. Simply change the password on the user account. If they are still accessing the account, Outlook will lock the account out in about two minutes.

                Simon.
                So you think it has more to do with the account being disabled previously than with the password not passing from AD to exchange? Makes sense, but i figured it would replicate much faster than that.


                Edit: just tested it again. Account was re-activate around 5 pm today, just came back up @ almost 7 in exchange. Thanks for the help. Guess time was my real help. At least i know more about it now.

                Thanks
                Tyler
                Last edited by tnelson008; 8th July 2006, 01:02.

                Comment


                • #9
                  Re: Outlook could not log on....

                  Originally posted by tnelson008
                  So you think it has more to do with the account being disabled previously than with the password not passing from AD to exchange? Makes sense, but i figured it would replicate much faster than that.


                  Edit: just tested it again. Account was re-activate around 5 pm today, just came back up @ almost 7 in exchange. Thanks for the help. Guess time was my real help. At least i know more about it now.

                  Thanks
                  Tyler
                  It isn't the domain that is fault. It is how Exchange caches information. The account was re-enabled immediately. Exchange doesn't read the information "live" as a performance enhancement - it caches that information.
                  You were simply inpatient.

                  Simon.
                  --
                  Simon Butler
                  Exchange MVP

                  Blog: http://blog.sembee.co.uk/
                  More Exchange Content: http://exchange.sembee.info/
                  Exchange Resources List: http://exbpa.com/
                  In the UK? Hire me: http://www.sembee.co.uk/

                  Sembee is a registered trademark, used here with permission.

                  Comment

                  Working...
                  X