Link to home
Start Free TrialLog in
Avatar of YMartin
YMartin

asked on

User cannot use POP3 to get email on Exchange 2007

I have a Windows 2008 SBS running Exchange Server.  We have some users that need to use POP3 to access their inboxes.  All users except for one can do this.  The one user keeps getting rejected for invalid login credentials.  The login name is only 3 characters so it is not the long UPN issue.

Username and password works for OWA login and remote desktop login and the account can be connected to otherwise but not POP3.

Security audit log shows Success for the login when an attempt is made to connect yet Exchange still returns incorrect username/password.

Thanks in advance for your help.
Avatar of Kris Montgomery
Kris Montgomery
Flag of United States of America image

The first thing to check is his computer time/date and time zone.  

Sorry for the lack of detail.

Thanks!

mug
Use the users email address as the username
Avatar of YMartin
YMartin

ASKER

Thanks muganthony and MegaNuk3.  

The computer time zone is fine as I can connect to one account from the computer using Outllook and POP3 without any trouble but not the other.  It is something with that user's account

MegaNuk3 - I tried using the email address as the username too and that doesn't work.
enter logon credentials as DomainName\LogonName\MailboxAlias

 

OR

 

set mailbox Alias to be the same as the account name
Avatar of YMartin

ASKER

Here is the other kicker.  I just confirmed with the user that It used to work until about 2 weeks ago and suddenly stopped working.  The user says they didn't change anything.

I have confirmed from my test system that the login doesn't work anymore so it is not something with the user's computer.  I have tried resetting the password to no effect.

Seems like Exchange is trying to do some other authentication via the POP3.  Again the login works for OWA.
Did you try my suggestion of putting
Domain\UserName\MailboxAlias
In the username box of the POP settings?
Avatar of YMartin

ASKER

Yes - I tried the Domain\UserName\MailboxAlias and that doesn't work either.  The user was able to login just via POP3 fine for about 10 months and then it stopped working.
And pop access isn't disabled on the user account?
Avatar of YMartin

ASKER

Correct - POP access is not disabled.
SOLUTION
Avatar of MegaNuk3
MegaNuk3
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of YMartin

ASKER

Can you point me in the right direction on how to increase the logging for POP to get the right diagnostic info?

Thanks
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of YMartin

ASKER

OK the  POP3\General logging is set to High.  Where can I see the log?  I looked in Program Files -> Microsoft -> Exchange Server -> Logging but there was nothing there for POP3.

BTW - We are using Small Business Server 2008.

Thanks,
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of YMartin

ASKER

Ok got something in the event log that may be a clue:
Event Type: Warning
Event Source: MSExchangePOP3
Event ID: 1009
Description: Number of simultaneous connections made by user <xxx> exceeded maximum (16).

The solution is described here: http://support.microsoft.com/kb/968626
I am going to do that but it doesn't really make sense since the user's mailbox is not shared and it was working for almost a year without this issue.
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of YMartin

ASKER

Intsalled SP3 which went off without a hitch and that fixed the issue.  Thanks MegaNuk3!
Avatar of YMartin

ASKER

I accepted my own comment because it contains the link to the Microsoft knowledge base article I found that gave the solution.  I wouldn't have found that without MegaNuk3 helping me with setting up the POP3 logs.  Also MegaNuk3 suggested upgrading to Exchange Server SP3 whereas the Microsoft knowledge base article just had me doing an SP1 roll up update.
Thanks for the points, glad you got it solved.