I am having a problem with Exchange Server 2010, eventually updated with SP1. Exchane Server 14.01.0218.013 installed together with TMG 2010 and decorated with Kaspersky Security for Exchange Servers. All set up on Windows Server 2008 R2. Critical updates applied. Currently my Outlook 2007 clients can't make a working connection to it. The client application starts, claims it has made a connection and stays that way - showing empty folders and placing new messages into the "Outgoing" folder. Sometimes such messages even get sent. Later the connection gets dropped and restored occasionally, without any progress. Eventually it crashes. In the connection status I can see a small number of connections and a somewhat lesser number of errors. But the number is not in the hundreds or thousands I'd expect it to be. To date I have gone through "Doesn't work at all", "Connects, but drops the connection right away", "Autodiscovers fine, then says 'There isn't an Exchange server available. Can't open folders, need a connection", "Doesn't autodiscover and doesn't work" (this one was right after I installed SP1, which made a mess because it couldn't handle the remains of Kaspersky Security for Exchange Servers) and "Doesn't autodiscover, connects manually, but takes minutes to load, while pretending to download some data" stages. The Event Log on the client computer is filled with "Can't perform EcDoRpcExt on transport ncacn_ip_tcp" and "Can't perform EcDoDisconnect on transport ncacn_ip_tcp" messages. OWA works fine, incoming mail comes in, outgoing mail goes out. Just no deal with the whole MAPI thing. I have used The Wizards and meditated over Google, without result. Except that one topic, where a person with a similar problem got directed towards a huge "Solve your RPC problems in 21 day or your money back" KB article and vanished from the forum without trace. Interestingly, the Best Practices Analyzer claims that I have incorrect permissions set on the OAB folder, namely that the Read permissions clearly set on it (verified through Effective Permissions) are not actually there. Still, OAB isn't exactly something I care about right now. It just makes me think The Wizards aren't exactly competent. What else... Traffic between the Exchange computer and the local network is allowed fully without filtering. This is a fresh install, without any migration baggage. The computers experiencing the problem used to work through Kerio Outlook Offline Connector (sort of a MAPI emulator working with Kerio's private mail server), but that has been exorcised.

Hi, The Event Log on the client computer just seems as a time out error code. I have some suggestion as follows: 1.As you have tested that Auto Discover services works fine. I hope you restart the Microsoft Exchange IMAP4 and Microsoft Exchange RPC Client Access services at first. 2. Run the command “Get-RpcClientAccess”, make sure Outlook configuration matches the Exchange setting. 3.Install Outlook 2007 Service Pack2 (SP2), you can download it via: http://support.microsoft.com/kb/968774 4. You can download EBPA to determine the overall health of Exchange servers and topology. http://www.microsoft.com/downloads/details.aspx?familyid=dbab201f-4bee-4943-ac22-e2ddbd258df3&displaylang=en 5. Disabled TCP Chimney on the Exchange server using the Netsh command. http://support.microsoft.com/kb/951037Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Maybe the logs from Outlook will give you any information? http://office.microsoft.com/en-us/outlook-help/what-is-the-enable-logging-troubleshooting-option-HA001230421.aspx Jonas Andersson | Microsoft Community Contributor Award 2011 | MCITP: EMA 2007/2010 | Blog: http://www.testlabs.se/blog | Follow me on twitter: jonand82

As of today, I have partially solved the problem by removing TMG2010 completely, then applying it back and allowing full unrestricted and unfiltered access for the local network's computers as well as manually allowing SMTP, HTTPS and other necessary traffic to and from the outside world. Outlook clients work for now. My guess is that the primary difference here is that first time around I trusted TMG and used it's built in "Publish Exhcnage server" wizard, which lead to aforementioned problems (even though back then RPC checked fine through the traffic emulator). Woe is me. TODO: Painstakingly cut internal network's access bit by bit until I'm satisfied with the balance between perceived security and Outlook's functionality. I might try your advice on my next installation, for I want to believe that the goal can be achieved from null access by building up, not from full by cutting down.