Exchange 2010 on SBS Cannot Send

Have a new MPS cPanel server with ViaVerio.  Previously had a VPS3 Freebsd server.

Using Pop3 connector we just pointed our user to the domain, with email address and password.  Worked fine.

Now after moving to the new MPS host Pop3 connector fails to connect to the new email server.  Error is Authentication  failed error: 0x800ccc90 ("ixp_e_pop3_response_error") at d:\wssg_srv\sbs_sbs7\sbs\srs\messaging\pop3\ixppop3.com:526
Then
The credentials provided by for user account' 'xxxx' on the server are incorrect.

They are not incorrect.
bbornerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

BlueComputeCommented:
Let's clarify a few things.
Do you have a single catch-all mailbox in cPanel, or a mailbox for each user?
You're trying to set up the Microsoft Small Business POP3 Connector to retrieve emails from this/these account[s]?

In cPanel, under "Email Accounts", you should be able to select "More" --> "Configure email client" for the account in question:
cPanel configure email client This will take you to a page with all the account details you require:
cPanel email client settings
Compare this to the configuration page on the Windows SBS pop3 Connector, or post screenshots of both, and we can figure out where the differences are.
0
bbornerAuthor Commented:
The resolution to this issue was that during the switchover from one email host to another, exchange was hitting the new email host with requests for emails.   Some accounts were not yet set up on the MPS cPanel host.  So the MPS server blacklisted the exchange server's IP address with its Brute Force Security program.

Authentication was as a result declined on the sending side and on the receiving side.

We went in to Brute Force Security and whitelisted the IP of the exchange server and all is now well.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
bbornerAuthor Commented:
The resolution involved Microsoft Critical support and the technical staff from Verio web hosting
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.