Home > Exchange 2010 > Exchange 2010 Outlook Anywhere Not Working Windows Xp

Exchange 2010 Outlook Anywhere Not Working Windows Xp

The process of reinstalling RPC Proxy is: Disable Outlook Anywhere using EMC or EMS Remove RPC proxy component using the command: servermanagercmd -r rpc-over-http-proxy Reboot the server Install RPC proxy component Join and Comment By clicking you are agreeing to Experts Exchange's Terms of Use. Which firewall device is deployed between the internet and domain? All rights reserved. this content

Cheers!!! The one major difference for me is that I was using a wildcard ssl certificate for "*.contoso.com" which was not matching with the server name of owa.contoso.com. All rights reserved. Copyright 2005-2015 - Peter Schmidt.

A VPN provides you with a connection within an organization's network and within its firewall. Reply Aditya says: August 6, 2013 at 9:18 am How to revert back the Set-OutlookProvider EXPR -CertPrincipalName:”msstd:mail.company.com” command as my Windows 7 client failed to communicate now. Marked as answer by Karol Kislenko Friday, August 06, 2010 7:04 AM Friday, August 06, 2010 7:03 AM Reply | Quote All replies 0 Sign in to vote what I can Reply JR on May 4, 2013 12:01 am It just worked neatly.

Privacy Policy Site Map Support Terms of Use Latest Posts: New Azure AD Connect version (1.1.281.0) Released How to Access the Exchange (2013/2016) Admin Center (ECP) with Mailbox still on older He is able to login to OWA. When introducing Exchange 2013 which only relies Outlook Anywhere (MAPI is no more:) ), the CertPrincipalName gets important on internally connected Outlook clients as well. The computer belongs to sbs 2008 domain.

Proposed as answer by ressbari Wednesday, July 25, 2012 4:11 PM Wednesday, July 25, 2012 4:11 PM Reply | Quote 0 Sign in to vote Thank you. Anyway. The one place I deviated was step 6 where I just rebooted the server. A Client got a new cert where the Common Name was replaced to a new one, and the previous Common Name become one of the SANs.

Now my problem is that WindowsXP (w SP3) PC's that are not located inside domain and shoud use Outlook Anywhere cannot connect to that service. When I try to configure Outlook I will contignously promted for username and password. In resolution I opened the Exchange Shell and ran this command Set-OutlookProvider EXPR -CertPrincipalName:"msstd:mail.domain.com" Set-OutlookProvider -Identity EXCH -CertPrincipalName msstd:mail.domain.com IISreset After that everything was working perfectly for both Windows 7 and A client end fix would need to be applied to each and every client, which could quickly become a mangement nightmare.

  1. This usually results in connectivity issues with Outlook Anywhere (for example password prompts that will not apply the correct username and password).
  2. Help Desk » Inventory » Monitor » Community » MSitPros Blog Knowledge is of no value, unless you put it into practice About usOddvar MoeChristian KnarvikFrode HenriksenSem MeijerDisclaimerDownloadsPresentationsTeched PicturesVideos About usOddvar
  3. Recent Posts Creating Phishing bait with PowerShell October 24, 2016 Showing UAC bypass the GUI way September 28, 2016 Compliance search – a pentesters dream September 27, 2016 Change Admin portal
  4. Subscribe to our monthly newsletter for tech news and trends Membership How it Works Gigs Live Careers Plans and Pricing For Business Become an Expert Resource Center About Us Who We
  5. Edited by Karol Kislenko Wednesday, August 04, 2010 1:24 PM Wednesday, August 04, 2010 11:19 AM Reply | Quote Answers 10 Sign in to vote I have solved my problem!
  6. Join Now For immediate help use Live now!
  7. Reply Nagy on January 11, 2013 11:01 pm Thank you Pro.
  8. He is running Windows XP, Outlook 2010, Exchange 2010.
  9. Should I try msstd:*.domain.com ?
  10. Your cache administrator is webmaster.

Therefore I recommend to stick with basic authentication and use SSL. Automatic Failover 2. Hopefully someone else has the answer for your situation, also making a new post under Exchange 2013 forum might help You to get a faster answer. Same connectivity setups as described above.

Users with mailboxes on 2013 will get one set of EXHTTP settings for internal usage and one set of EXHTTP settings for external usage. news Do you have any issues logging into a PC with the users credentials? Wednesday, June 08, 2011 12:37 PM Reply | Quote 0 Sign in to vote Thanks for the info, I was missing the "msstd:" part of the command. The requirements include: Your computer must have Microsoft Windows XP Service Pack 2 or a later service pack.

What about for Wild Card certificates, how do I set the "Only connect to proxy servers that have this principal name in their certificate" MSSTD value for these for legacy Windows How my settings was when running powershell - Get-OutlookAnywhere | Fl Identity,*auth* Identity : Exch2013Server\Rpc (Default Web Site) ExternalClientAuthenticationMethod : Negotiate InternalClientAuthenticationMethod : Negotiate IISAuthenticationMethods : {Negotiate} What I did to The concept of internal Outlook Anywhere and External Outlook Anywhere is new in Exchange 2013 as we got rid of direct RPC to the Exchange server. http://intrascol.org/exchange-2010/exchange-2010-owa-not-working-after-windows-update.html Best Regards, Karol Thursday, October 20, 2011 2:31 PM Reply | Quote 0 Sign in to vote Hi Karol, thanks for your answer.

For some reason Outlook Anywhere stopped working and the Outlook Anywhere (RPC over HTTP) clients were no longer able to connect. Thanks in advance for your help. About Advertising Privacy Terms Help Sitemap × Join millions of IT pros like you Log in to Spiceworks Reset community password Agree to Terms of Service Connect with Or Sign up

I am pretty much an Exchange novice, but I suspect that is not what I should be seeing.

What is wrong in XP and Outlook 2007 combination not being able to connect to Echange 2010? BR, Karol Wednesday, June 01, 2011 4:50 PM Reply | Quote 0 Sign in to vote Matt99hi, There isn't a way to do this on the client side, and I'm thinking SAN-Cert.JPG 0 Comment Question by:R2_D2 Facebook Twitter LinkedIn Email https://www.experts-exchange.com/questions/28037028/Outlook-Anywhere-not-working-on-XP.htmlcopy LVL 30 Best Solution byflubbster Your solution may be here: http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/a7c25d6a-7cfc-40a1-a17e-a1f05f637d53/ Appears to be the same exact problem and the solution, I would start from scratch and try to re-setup the connection, taking your time and being careful when typing.

The Outlook Anywhere External Hostname did not match the CertPrincipal Name, right ? pickettsproblems says: August 30, 2013 at 6:13 pm It's fine you can just rerun the command with nothing in it and it will blank out the certificate principal name like it I work as a Infrastructure Architect for EG A/S in Denmark. check my blog Regards.

Also I used the Set-OutlookProvider cmdlet to set EXPR to msstd:mail.domainname.ee and also tried msstd:excha.domainname.ee this change did not have any effect on XP pc. These are my exchange 2010 names in the certificate -Exchange Internal name = Server.mydomain.local -Exchange external name = Exch.mydomainlongname.com -Exchange external name = mail.mydomainlongname.com Anyway, i have attached an screenshot of Only on Windows XP computers password prompts for Office 2007 persist, I´ve set as suggested the new MSSTD. I've read this post and if I could I want to suggest you some interesting things or advice.

No change. Thansk for your support ! And guess what, suddenly both XP clients and W7 clients could connect both internally and externally:) Cheers!! The internal name of the server is excha.domainname.ee, external name is mail.domainname.ee.

Reply pickettsproblems says: August 30, 2013 at 3:40 pm Yes you can. What about Autodiscover? If not do you have Outlook Anywhere and autodiscovery set up properly? -Jay   0 Cayenne OP Donald Sewell Jun 25, 2012 at 9:31 UTC Maybe this: http://www.howexchangeworks.com/2009/09/cant-connect-outlook-2003-to-exchange.html Login.

HKEY_CURRENT_USER\Software\Microsoft\Exchange\Exchange Provider 0 Habanero OP Brandon.A Jun 25, 2012 at 12:32 UTC Pittsburgh Computer Solutions is an IT service provider.   Jay6111 wrote: Does setting up the user Add Cancel × Insert code Language Apache AppleScript Awk BASH Batchfile C C++ C# CSS ERB HTML Java JavaScript Lua ObjectiveC PHP Perl Text Powershell Python R Ruby Sass Scala SQL As my situation was not solved with setting CertPrincipalName to my Exchange external URL. Set this parameter to the external host name that Outlook clients use to connect to Outlook Anywhere .

Whatever is the first name after DNS Name= should be used in MSSTD. Have you compared the settings in the “Security” tab of mail account between windows XP and windows 7? The problem actually was in my SAN certificate, mainly on the Subject Alternative Names field. We pretend to use the remote exchange rather the local one.

That fixed my issue on SBS 2011. Recent Posts New Azure AD Connect version (1.1.281.0) Released How to Access the Exchange (2013/2016) Admin Center (ECP) with Mailbox still on older Exchange Awarded Microsoft Most Valuable Professional (MVP) 2016 But the Exchange server, which has a certificate from internal CA server, had servers FQDN as common name and outlook.mail.com only as SAN name !! Reply Mike V on April 24, 2012 12:29 am Thank you Peter for posting this.