2010 IMAP, 2007 outlook. logon failing
We offer IMAP on our 2003 exchange server on our internal network for any Linux users or users that dont wish to use outlook. Ive brought up a 2010 exchange server into the mix, and I've been testing IMAP with a user on the server using outlook (as it offers
the most troubleshooting i find). 2003 is setup to use Basic authentication and simple authentication and security layer. I've tried setting up 2010 in the same fashion using plain text logon(basic authentication).
In outlook i manually set the information.
your name: name
email address: name@domain.com
account type: imap
incoming mail server: exc2010.domain.com
outgoing mail server: exc2010.domain.com
username: name@domain.com
password: password
I then click test account settings. It fails to log on to imap. It says the connection to the server failed.
For sending a test email, it says outlook cannot connect to your outgoing smtp server.
The firewall is open for port 25,143 on all profiles. Setting up outlook as an exchange client works.
May 24th, 2011 9:41am
From the client can you telnet to port 143 to the Exchange server? If so can you login and issue any imap commands?
How to verify basic IMAP connectivity by using Telnet
http://support.microsoft.com/kb/189326James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com
Free Windows Admin Tool Kit Click here and download it now
May 24th, 2011 9:56am
I was able to login and run the LIST command.
May 24th, 2011 10:07am
Try solution from past thread, I recall another user having same issue but with POP, user was able to telnet and log into POP and issue list command but getting 421 4.3.2 Service not available when creating outlook profile.
http://social.technet.microsoft.com/Forums/en-US/exchangesvradmin/thread/87d963fa-c5b8-4dc1-8757-8a48ea00c230/
Install Windows 2008 support tools on the mail server. Go to Server Manager, Select Features, then select Active Directory Lightweight Directory Services.
2. Start, Run, type ADSIEDIT.MSCOpen Configuration, then navigate to Services, Exchange, ORGNAME, Administrative Groups, Exchange Admin Group, Servers, MailServer, Protocols, SMTP Receive Connector. Go to the Properties of the Client, Default and Inbound
SMTP relay. Select Security tab, Authenticated Users, Accept Authoritative Domain Send (ALLOW).
3. Added remote IP address of the device that’s trying to use POP3 to Default and Inbound SMTP Relay.
4.Under Authentication tab of the receive connector, uncheck OFFER BASIC AUTHENTICATION ONLY AFTER STARTING TLS for all 3 connectors (default, client and inbound SMTP relay). (no need to change the Anonymous relay)
5.Restarted Exchange Transport and POP3 service
6.Outlook client: go to More Settings and change the following under Outgoing server tab: Outgoing server requires authentication (use same settings as my incoming.)
as an alternative, we were able to use port 587 instead of 25 under the Advanced tab.James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com
Free Windows Admin Tool Kit Click here and download it now
May 24th, 2011 10:15am
No luck with this either
May 24th, 2011 11:37am
It looks to be IPv6 related. I had IPv6 unchecked on my vm and the server. i did a wireshark scan when hitting test account settings. They were talking ipv6 to eachother. trying to figure out how to add ipv6 to imap.
edit:
It is IPv6 related. I changed an entry in the registry following these instructions. http://support.microsoft.com/kb/929852 Then did a reboot. After which the IMAP worked fine.
Free Windows Admin Tool Kit Click here and download it now
May 24th, 2011 2:43pm