These are the only fixes that come to mind currently, so if I've missed any other useful fixes that are rarely seen but very useful then please drop them in this thread. This will tell you if the mail server is down, if they don't have authorisation to use it etc. If it's exchange, navigate to the OWA web server, and then enter the domain\username and sign in password for the user. This will then let you know if the user's details are incorrect, or if the Office server is down etc. If you use M365, go to and try the users details. Try signing into the web version of the mail
Once recreated it will then test the connection, and if the connection fails or hangs then you know that there's something happening in between the mail connection and the mail server.ĥ. You can also choose to manually set it up, but doing this will also mean that you have to know the mail server off by heart to enter it, but if you're already this far into it then that shouldn't be an issue. Then go to Control Panel, search for "Mail", click the first option, and then press "Show Profiles" and "Add.".ĭoing this will allow you to see entry for all of the information about the user (if you don't see the prompt for a password, re-enter the user's auto-filled email address). This is the one I always try, and never actually fixes the issue (At least not for me), but I see it on every article about this so I thought it best to include it anyway.Ĭomputer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Outlook\Īnd create the DWord: ExcludeExplicitO365Endpoint with the value of 1.įor this, gather the user's email, login username, and password (if their on 365 then also get the email password). A simple ping to the webmail server/exchange server can tell you a lot more than a user can, so this is always one of my go-to's now. This is another one I've had, where I've remoted into a PC, the client failed to tell me they were working from home with no VPN, and left me scratching my head for a few minutes before realising what was happening. I rolled my eyes and connected to the OWA, and lo and behold, the "change password" prompt appeared.Īfter changing the password, and entering the new one into Outlook when the dialogue box appeared, it immediately connected to the exchange server.
After test after test, and regedit after regedit, the user eventually told me that "a weird prompt kept appearing saying that they needed to change their password, but they just ignored it. Please let me know if you have any other suggestions!ġ. I had this issue for a user recently, and while fixing it I noticed that the solution was something that I didn't see on any other lists for this issue, so I decided to post it on here (as well as some other well known fixes).
0 kommentar(er)
