<div>
I assume that you have checked AD user properties and that POP3 is enbabled?<br />
<a href="https://filedb.experts-exchange.com/incoming/2009/01_w04/98291/Untitled-1.gif" target="_blank" class="file-inline" title="AD user properties (10 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>Untitled-1.gif</a>
</div>


Untitled-1.gif

<div>
Yes.<br />
<br />
This account was working with pop3 until today when Jimmy tried setting up his phone.
</div>


<div>
Check the application log on the exchange server you are telnetting too, it will provide more detail than simply &quot;bad password&quot;<br />
<br />
Has this user logged on to Outlook or OWA to initialise his mailbox?
</div>


<div>
I'd guess guswebb is right, but maybe you can check about going into the mail setup( Control Panel) for the client and choose this connection requires authentication and put in their login info here.
</div>


<div>
Check the application log on the exchange server you are telnetting too, it will provide more detail than simply &quot;bad password&quot;<br />
Has this user logged on to Outlook or OWA to initialise his mailbox?<br />
==========================<wbr />==========<wbr />==========<wbr />==========<wbr />=<br />
I assume you are referring to the event viewer logs (Application logs). Believe it or not, there is not one instance of this failure present in the logs. I have tried the telneting at least 50 times in one hour, and not a single instance of failure in event viewer (application)<br />
<br />
and Yes the user has used and continues to use OWA.
</div>


<div>
very very odd<br />
<br />
Is the server you are telnetting too the server that the mailbox is held on or is it a front-end/CAS box?
</div>


<div>
Is the server you are telnetting too the server that the mailbox is held on<br />
<br />
Yes<br />

</div>


<div>
if you log on to the server and go into a command prompt and do<br />
<br />
runas /user:&lt;yourdomain&gt;\&lt;affect<wbr />edusername<wbr />&gt; cmd &lt;enter&gt;<br />
&lt;enter password&gt;<br />
<br />
what happens? &nbsp;It should start a new command prompt running as the user specified....<br />
<br />
what if you log on to the server, go into a command prompt and do<br />
<br />
telnet localhost 110<br />
user &lt;domainname&gt;\&lt;username&gt;<br />
pass &lt;password&gt;<br />
stat<br />
<br />
??<br />
<br />

</div>


<div>
Microsoft Windows [Version 5.2.3790]<br />
(C) Copyright 1985-2003 Microsoft Corp.<br />
<br />
C:\windows&gt;runas /user:sausage\jimmy.dean cmd<br />
Enter the password for sausage\jimmy.dean :<br />
Attempting to start cmd as user &quot;sausage\jimmy.dean &quot;&nbsp;...<br />
RUNAS ERROR: Unable to run - cmd<br />
1385: Logon failure: the user has not been granted the requested logon type at t<br />
his computer.<br />
==========================<wbr />==========<wbr />==========<wbr />==========<wbr /><br />

</div>


<div>
oops, of course - sorry a bit misleading that one. &nbsp;and if you do the telnet localhost 110 on the server?
</div>


<div>
It fails as well, with the same -ERR
</div>


<div>
Create &nbsp;a new test user and try to configure the accout in affected user's phone.<br />
If it works, then reset affected user password with less complexity.<br />
==========================<wbr />==<br />
Password = password<br />
==========================<wbr />==<br />
do you have router ?<br />
Cisco ASA5505<br />
No other users are having issues. thus ruling out the router/security appliance<br />
==========================<wbr />==<br />
are you using SSL ?<br />
SSL for OWA only, does not affect pop3<br />
==========================<wbr />==<br />
Telnet &lt;ip address&gt; 110 <br />
or SSL then Telnet &lt;ip address&gt; 993<br />
<br />
I can use my credentials, and 4 other people have tested the telneting via pop3 (110). Their credentials work, where as Jimmy's continue to fail.<br />
<br />
Now the only thing that makes sense in what you have said, is to create a test user for Jimmy to configure his phone for. This may break any connection he may or may not have with the server via his phone, thus giving a chance to reset his password again.<br />
<br />
&nbsp;I will test this theory, and let you know ...
</div>


<div>
I had the user connect to the server with a testuser. And Jimmy was successful in the connection. He still can not connect to his account though, and telnet testing fails on his account as well. <br />
<br />
Next¿ 
</div>


<div>
Ok no next???<br />
<br />
Well whats the easiest way to delete jimmy and recreate Jimmy with same login credentials?
</div>


<div>
.spt should of course read .pst!
</div>


<div>
Import the previously exported items to his mailbox.<br />
<br />
How do I restore his .pst to the server?
</div>


<div>
Using Outlook--&gt;File--&gt;Import and Export--&gt;Import from another program or file--&gt;Personal Folder FIle (.pst)--&gt;Browse (and point to the .pst file you created when exporting from Outlook)--&gt;Next--&gt; accept default options on next steps and Finish.
</div>


<div>
how does that save the information in the pst to the server? I ask, because i have restored the pst to the users account by way of the client terminal, however i checked and the pst was restored to client not the server.
</div>


<div>
It sounds as if you are using a .pst file as the default data store on the Outlook client and that's why the email isn't showing in their Exchange mailbox. Please check Outlook--&gt;Email accounts/Account settings--&gt;Data files. Do you see the Exchange mailbox in the data files lists? Is it selected by default? If not, select it, and then you will be reading the contents of the user's mailbox from Exchange. If you still have the .pst contents visible in Outlook under Personal Folders container (or similar) on the left-hand directory tree, then you can simply drag contents from this store in to the Exchange mailbox folders which should now be displayed at the top of the directory tree in Outlook.<br />
<br />
Hope this helps.
</div>


<div>
I appreciate the experts assistance with this debacle. Unfortunately I was forced to delete/recreate this account. Guswebb, was the closest since I had to delete and recreate. I split the points between the experts, based on the effort put forth. Thank you for your help.
</div>


<div>
<div class="content wysiwyg-content">
I have a user named jimmy dean. Jimmy is setting up his phone for email, and instead of using IMAP4, he wants to use Pop3. Outlook clients outside the office use pop3 including the owner, and no one has had an issue for years. Jimmy tries setting up pop3 on his phone, and keeps getting a username password error. He brings this to my attention and I laugh he obviously forgot his password. <br />
<br />
I reset Jimmys password to password, and tested the login with a local terminal, and it worked. He logged into the domain with no problems. He tried accessing mail through pop3 and once again it fails. saying Bad user/password. I tried telneting into the server <br />
telnet mail.domain.com<br />
user jimmy.dean<br />
pass password<br />
-ERR Logon failure: unknown user name or bad password.<br />
<br />
I can login to the domain and I can login to OWA with jimmys credentials, only pop3 fails. No one else that uses the exchange server is having an issue. What do I do short of deleting jimmy and re-creating him?<br />

</div>
</div>


I have a user named jimmy dean. Jimmy is setting up his phone for email, and instead of using IMAP4, he wants to use Pop3. Outlook clients outside the office use pop3 including the owner, and no one has had an issue for years. Jimmy tries setting up pop3 on his phone, and keeps getting a username password error. He brings this to my attention and I laugh he obviously forgot his password. 

I reset Jimmys password to password, and tested the login with a local terminal, and it worked. He logged into the domain with no problems. He tried accessing mail through pop3 and once again it fails. saying Bad user/password. I tried telneting into the server 
telnet mail.domain.com
user jimmy.dean
pass password
-ERR Logon failure: unknown user name or bad password.

I can login to the domain and I can login to OWA with jimmys credentials, only pop3 fails. No one else that uses the exchange server is having an issue. What do I do short of deleting jimmy and re-creating him?


Telnet not working for pop3/exchange2003

Interactions between email servers and clients are governed by email protocols. The three most common email protocols are POP, IMAP and MAPI. Most email software operates under one of these (and many products support more than one).  The correct protocol must be selected, and correctly configured, if you want your email account to work.

Email Protocols

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).

Windows Server 2003

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.