So yes, my rant may have been a bit uncalled for, and yes, your suggestion did fix it. Normally I wouldn't even bother with someone who insults me first, but I'm in a generous mood and know how it feels to beat your head over something. Thursday, October 20, 2011 3:20 PM Reply | Quote 0 Sign in to vote I would try to set msstd:*.domain.com then. And guess what, suddenly both XP clients and W7 clients could connect both internally and externally:) Cheers!! Check This Out
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 Outlook will then connect and after some time or when I close and open Outlook again, it will prompt me for credentials again and the setting have changed back to Negotiate. The key changes that seemed to fix this for us were to make these updates - Set-OutlookProvider EXPR -CertPrincipalName msstd:*.contoso.com alternatively if you dont care whether the proxy server name exactly Outlook must be online or connected to complete this action" I have setup the HTTP Proxy with the external hostname mentioned above. https://social.technet.microsoft.com/Forums/exchange/en-US/a7c25d6a-7cfc-40a1-a17e-a1f05f637d53/exchange-2010outlook-anywherewindows-xp-not-working-together?forum=exchange2010
Does that need to be changed to the external hostname? Avantgarde Technologies IT Support Perth Thursday, October 9, 2014 Windows XP clients must match the Certificate Common Name in Outlook for RPC over HTTP Back in 2009 I wrote an article This would never work no matter what I did until I entered the internal FQDN of the mail server in the Settings screen.
Again, if this is working fine from the outside (IE; OWA is available via HTTPS), then you have nothing further to configure on the certificate end. 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 have put in : msstd:*.servername.com (outlook working) it autochanges to: msstd:mailserver.servername.com (outlook not working) i can change it back every time, but after closing outlook it is changed back. What is the SCCM Management Point? ► September (5) ► August (2) ► July (3) ► June (3) ► May (4) ► April (8) ► March (10) ► February (9) ►
After hitting Cancel you'll get another window. outlook.JPG 0 Message Author Comment by:R2_D22013-03-01 Comment Utility Permalink(# a38942216) Restarted the server and that fixed. 0 Featured Post Find Ransomware Secrets With All-Source Analysis Promoted by Recorded Future Ransomware What am I talking about? http://clintboessen.blogspot.com/2014/10/windows-xp-clients-must-match.html Any ideas?
Closed Outlook and it connected again. One External IP and One Internal 192.168.1.1 I'm not using ISA and never have. What else can be or check? Windows 7/Vista matches mail.domainname.ee to *.domainname.ee, but XP doesn’t Your method will match the CertPrincipalName to the subject field, and then solve the password prompt.
Microsoft Customer Support Microsoft Community Forums TechCenter Sign in United States (English) Brasil (Português)Česká republika (Čeština)Deutschland (Deutsch)España (Español)France (Français)Indonesia (Bahasa)Italia (Italiano)România (Română)Türkiye (Türkçe)Россия (Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 http://forums.msexchange.org/Outlook_Anywhere_not_working/m_1800438631/tm.htm Well let me show you... How can we improve it? Any ideas?
The internal name of the server is excha.domainname.ee, external name is mail.domainname.ee. his comment is here So Exchange was presenting itself to XP machines wrongly and it seems that XP is not willing to look at next lines on a SAN certificate. Thanks, Cesar Reply ↓ Glenn Matthys October 14, 2013 at 10:17 AM Nice summary on connecting XP clients. One External IP and One Internal 192.168.1.1 2.
WindowsNetworking.com Windows Server 2008 / 2003 & Windows 7 networking resource site. Is there anything else that needs to be done as far as enabling exchange anywhere? What is wrong in XP and Outlook 2007 combination not being able to connect to Echange 2010?
I have a Windows 2008 R2 with Exchange 2010 SP1 server. actually my Company's Internet Link suddenly went down that's why iwas unable to access my Network Remotely. Edited by Karol Kislenko Thursday, October 20, 2011 4:02 PM Thursday, October 20, 2011 4:01 PM Reply | Quote 6 Sign in to vote I was suffering from a very similar To use the Exchange Management Console to enable Outlook Anywhere In the console tree, expand Server Configuration, and then click Client Access.
After a while, you have entered a loop for Auto repair which does not fix anything and you will be in a panic as all your work w… Windows 10 Windows Same connectivity setups as described above. When the CertPrincipalName is missing from the AutoDiscover information, Outlook defaults to msstd:
MSPAnswers.com Resource site for Managed Service Providers. quote:I have installed RPC/HTTP on Exchange Server and enabled but i don't know that how should i configure the DNS Settings on my Domain Controller and on my clients. Thank you. I mean seriously, "Oh I entered the internal name of the server since it's on a proxy and it worked"
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 Just in case I installed godaddy certificates again. Set-OutlookAnywhere -Identity "Exch2013Server\Rpc (Default Web Site)" -IISAuthenticationMethods Basic,Ntlm,Negotiate This was the result running the Get command above again Identity : Exch2013Server\Rpc (Default Web Site) ExternalClientAuthenticationMethod : Negotiate InternalClientAuthenticationMethod : Negotiate IISAuthenticationMethods Related Categories Uncategorized 9 Comments Post your own or leave a trackback: Trackback URL Philipp says: May 26, 2013 at 10:19 am There could also be another problem, for the ActiveSync/Exchange