Username and password are incorrect connecting to IMAP server on a iphone

When you try to connect to the Exchange Server, Exchange 2003, 2007 using iphone you receive an error message, indicating that your Username and password is incorrect, even though you know that you are typing the correct username and password to connect to the Exchange Server.

Solution:

For IMAP the Username must be in the format Domain\Username, make sure that you enter your username in the above format. And if your Email alias is different from your username then you need to enter your username as follows Domain\Username\Alias. See examples below:

1. In this case the Username is Asmith and the default email alias is allensmith@example.com
So in the iphone IMAP userid field you will put the username in the format
Example\asmith\allensmith

2. In this case the Username is Asmith and the default email alias is asmith@example.com
So in the iphone IMAP userid field you will put the username in the format
Example\Asmith

Please note that there are other requirements for IPHONE to connect to the IMAP server such as Port 143 should be open on your firewall and Port 993 must be open if you are using SSL, also IMAP must be enabled on the Exchange server and the User must be enabled for IMAP in the Active Directory Users and Computers

The above username format is not required for SMTP to work.

440 Login Timeout in Exchange 2007 OWA

After I installed my SSL Cert on the Exchange 2007, and I tinkered around with some security in IIS my OWA stopped working both internally and externally.

I kept receiving this message:

"440 Login Timeout"

After couple days of struggling with this error and trying to fix the issue, I finally landed on the fix, so I wanted to put this out here for anyone who might experience this issue.

I basically had to blow the OWA virtual directory and then recreate it through Exchange Management shell. Please follow the specifics below

Solution:

here's what i did to solve the problem on my server:
We have only one Exchange server (2007), so all the roles are on the same box.

a) In the Exchange management console, I made a note of all the settings for OWA.
Go to "server configuration\ClientAccess", then pick the correct server, then "OWA" tab, right click owa (default web site): properties (Make a note of all the settings for your environment, you will need to restore these settings manually.

b) use the Exchange Management shell and run the following:
(please refer to http://technet.microsoft.com/en-us/library/aa998624.aspx for details)
1) Get-OwaVirtualDirectory -Server to check the settings
2) Remove-OwaVirtualDirectory -Identity to remove the existing virtual dir (only owa in this case, I didn't touch the others)
3) New-OWAVirtualDirectory --Name "owa" (I only used the -name parameter, that worked for me)

c)Go back to the management console and restore properties of owa.

d) restart IIS via command iisreset /noforce

Web Outlook was running again after that.

Setting Mailbox Quota Powershell

I will provide an example of powershell script that you can customize to use in order to setup the Exchange 2007 Mailbox Quota. In the example below the Powershell script will set the Quota Warning for 200mb and then Prohibit Send at 250mb and Prohibit Send and Receive at 280mb. Also it will run the Quota Notification between 2:00 AM - 3:AM on Sunday and Wednesday

Set-MailboxDatabase -Identity "Server1\MailboxDatabase1" -IssueWarningQuota 209715200 -ProhibitSendQuota 262144000 -ProhibitSendReceiveQuota 293601280 -QuotaNotificationSchedule "Sun.2:00-Sun.3:00","Wed.2:00-Wed.3:00"

Using NSLookup to find mx records

If you need to find mx record for a domain you can use the NSlookup tool within Windows. This is often used when you are having problems sending emails across to a certain server. You can lookup their mail servers and see if you can ping them. The best test is to be able to telnet them on port 25.

I can show you that in a short tutorial. In my example below I am trying to get the mx records for the domain microsoft.com

Quick NSlookup commands

If you are wondering how to use the NSLookup tool it is quite handy.

The tool is used from the command prompt and can be used to determine the name of your DNS server. Often used by us I.T support Engineers/professionals/guys whatever you want to call us to troubleshoot DNS problems. So to use NSlookup simply go to a command prompt and type:

nslookup

this should give you the IP address of all the DNS servers that you are using on your computer to resolve IP address from domain names, see below

C:\Documents and Settings\rajk>nslookup
*** Can't find server name for address 10.10.1.3: Non-existent domain
*** Default servers are not available
Default Server: UnKnown
Address: 10.10.1.3

>

At the next prompt type ? (this will give you all the commands that you can use), see the list below

> ?
Commands: (identifiers are shown in uppercase, [] means optional)
NAME - print info about the host/domain NAME using default server
NAME1 NAME2 - as above, but use NAME2 as server
help or ? - print info on common commands
set OPTION - set an option
all - print options, current server and host
[no]debug - print debugging information
[no]d2 - print exhaustive debugging information
[no]defname - append domain name to each query
[no]recurse - ask for recursive answer to query
[no]search - use domain search list
[no]vc - always use a virtual circuit
domain=NAME - set default domain name to NAME
srchlist=N1[/N2/.../N6] - set domain to N1 and search list to N1,N2, etc.
root=NAME - set root server to NAME
retry=X - set number of retries to X
timeout=X - set initial time-out interval to X seconds
type=X - set query type (ex. A,ANY,CNAME,MX,NS,PTR,SOA,SRV)
querytype=X - same as type
class=X - set query class (ex. IN (Internet), ANY)
[no]msxfr - use MS fast zone transfer
ixfrver=X - current version to use in IXFR transfer request
server NAME - set default server to NAME, using current default server
lserver NAME - set default server to NAME, using initial server
finger [USER] - finger the optional NAME at the current default host
root - set current default server to the root
ls [opt] DOMAIN [> FILE] - list addresses in DOMAIN (optional: output to FILE)
-a - list canonical names and aliases
-d - list all records
-t TYPE - list records of the given type (e.g. A,CNAME,MX,NS,PTR etc.)
view FILE - sort an 'ls' output file and view it with pg
exit - exit the program

>

To see how you can get mx records for a domain please see my posting called Using NSLookup to find mx records






If for some reason you

Error when moving mailbox

Problem:

When moving a mailbox from Legacy E2k Server to E2k7 server, you receive an error message:
Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:00:00


Error:
Domain Controller 'OLDDCNAME' Operating System version is 5.0 (2195) Service Pack 4. The minimum version required is 5.2 (3790) Service Pack 1.

Solution:

Just to give you a little background I have a Windows 2000 DC with Exchange 2000 installed on it, and a Windows 2003 R2 running SP2. So what I had to do to fix the problem was to Remove the checkbox for Global Catalog for Windows 2000 DC from Active Directory Sites and Services and then restart the Windows 2000 DC.

After that the Mailbox Move did not give me the above error message

Problem:

While installing or Uninstalling Microsoft Exchange 2007 from the command line using Setup.com and various applicable switches you receive the following error message:
"An unexpected error has occurred and a Watson dump is being generated: Unexpect
ed error [0x116DCE11] while executing command '$error.Clear(); uninstall-Exsetda
taAtom -AtomName SMTP -DomainController $RoleDomainController'.
Unexpected error [0x116DCE11] while executing command '$error.Clear(); unin
stall-ExsetdataAtom -AtomName SMTP -DomainController $RoleDomainController'.

Exchange Server Encountered and Error

Solution:

Background

I was installing the hub transport, client access, mailbox and management tools using the setup.com

setup.com /mode:install /r:h,c,m,t /t:"d:\program files\Microsoft Exchange Server"

So when Uninstalling i received the error message. I was using the following command

setup.com /mode:uninstall

Changing the above command slightly by including the roles that I wanted to uninstall I was able to complete the command successfully

setup.com /mode:uninstall /r:h,c,m,t