hi all, we already have a exchange environment(call it A.COM here): front/back-end, exchange 2003 sp2, windows 2003/outlook 2003/2007. OWA/Outlook(rpc over https) all works fine. then we add 2nd domain for our client (call it B.COM here), i create a new recipient policy for B.COM and include those users. after that, users in B.COM can log into B.COM through OWA, they can send email and received email(test with gmail), but they CAN NOT logon with outlook(rpc over https) from the eventlog of front end server shows "unknow username or bad password" , error ID=529 tests was take place from WAN(internet, NO VPN) guys any idea? thanks!

Hi Ken, Just a gues: did you add a UPN suffix for this new domain? If you did that, is the correct domain selected for the specific user in AD? (Tab Accounts = User logon name @B.com) If mentioned above is the case, they should be able to login by using their email addresses and passwords. Regards, David.

hi ,It seems that you need to troubleshoot your authentication mechanism.i Have found this articlepleasereview it .http://www.msexchange.org/tutorials/Troubleshooting-RPC-over-HTTPS-Part2.htmlclient configuration http://www.msexchange.org/tutorials/outlookrpchttp.htmlhttp://www.petri.co.il/forums/showthread.php?p=184721syed.arsalan

Hi Orsel, I have try both ways( add or no add UPN suffix) when add UPN suffix, I try user@b.com b\user a\user, all failed

Hi,Arsalan checked, already saw them before, and outlook(rpc over https) works for user at A.com ,that is the confusing point for me

update, now on both domain access rpcproxy.dll test, but outlook still failed

Hi Ken, Would you please let me know: 1. Whether the 2nd domain users are able to logon Outlook in internal network? 2. If you configure the Outlook client in internal network to connect to Exchange server through RPC over HTTP, whether the same issue occurs 3. Please let me know the symptom of the issue, whether the 2nd domain users are prompted for authentication repeatedly? 4. Please check whether any AD replication issue exists 5. I suggest you capture network package on the Front End sever when you reproduce the issue. Please check which DC server the Front End Server attempts to access and whether any authentication error is encountered. ~~~~~~~~~~~~~~~~Mike Shen TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com ~~~~~~~~~~~~~~~~

Hi, Any update regarding the issue?Thanks,Mike