MrEastwood
New Member
- Reaction score
- 7
- Location
- British Columbia, Canada
Client computer, Win 10 Pro, Outlook 2013. They have an externally hosted POP/IMAP email for their office. Not my choice, I've suggested they move to something better ala Hosted Exchange but they don't want to switch. I can log into the account using webmail (not OWA, this is not Exchange, just plain webmail) just fine. Thus I know the username and password are working.
Delete the Windows email profile, create a new one from scratch. Used their instructions for both POP and IMAP, neither work, they just keep looping over and over asking for username and password. I called their tech support and they confirmed the settings were correct. They changed the password for me and the new one works on webmail.
Tried it on my own test machine, Win 10 Pro, different version of Outlook, 2016. I am in a completely different city, so there's literally nothing the same here. Anyhow, I can log into webmail just fine. However, the same issue occurs using Outlook 2016, I've double and triple and quadruple checked the settings. Called their tech support back, asked them if they'd remote in to check my settings but they said "we don't do remote support", huh? This is an ISP that is also an MSP... ok wow. So I had her read and confirm their tech support web page URL settings and she confirmed what the previous support tech said, the settings are all correct.
No, I'm not making any typos. Tried both POP and IMAP on both my test machine and client machine, same issue. No SSL on incoming, only on outgoing. Ports are set correctly, SSL is set correctly. I've done this a bazillion times over my 30 year career and never had this much trouble.
FYI all the other 20-odd staff are using their Outlook 2013 and 2016 with these accounts and it's working fine with same settings! Am afraid that if I remove another staff profile and try to re-add it, I will get the same problem so I don't want to do that.
Next, I telnetted into their pop server, and could telnet into it, I could connect fine and set the user, but when I set the password it says "-ERR could not determine server". I couldn't find anything useful about that error, perhaps it's a clue?
For now, customer is using web mail until I get this solved. Any further suggestions?
Delete the Windows email profile, create a new one from scratch. Used their instructions for both POP and IMAP, neither work, they just keep looping over and over asking for username and password. I called their tech support and they confirmed the settings were correct. They changed the password for me and the new one works on webmail.
Tried it on my own test machine, Win 10 Pro, different version of Outlook, 2016. I am in a completely different city, so there's literally nothing the same here. Anyhow, I can log into webmail just fine. However, the same issue occurs using Outlook 2016, I've double and triple and quadruple checked the settings. Called their tech support back, asked them if they'd remote in to check my settings but they said "we don't do remote support", huh? This is an ISP that is also an MSP... ok wow. So I had her read and confirm their tech support web page URL settings and she confirmed what the previous support tech said, the settings are all correct.
No, I'm not making any typos. Tried both POP and IMAP on both my test machine and client machine, same issue. No SSL on incoming, only on outgoing. Ports are set correctly, SSL is set correctly. I've done this a bazillion times over my 30 year career and never had this much trouble.
FYI all the other 20-odd staff are using their Outlook 2013 and 2016 with these accounts and it's working fine with same settings! Am afraid that if I remove another staff profile and try to re-add it, I will get the same problem so I don't want to do that.
Next, I telnetted into their pop server, and could telnet into it, I could connect fine and set the user, but when I set the password it says "-ERR could not determine server". I couldn't find anything useful about that error, perhaps it's a clue?
For now, customer is using web mail until I get this solved. Any further suggestions?