Outlook rpc over http

isn't possible to syncing iphone4 with an "rpc over http" configured outlook?
thanks

Helge,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://support.novell.com/forums)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://support.novell.com/forums/faq_general.html
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://support.novell.com/forums/

Similar Messages

BM 3.8 / Outlook RPC over HTTP

hello,
we want to use outlook rpc over http. did anybody know, what ports do i
need to open the firewall for that?
i think statefull from outside to dmz, but witch ports?
is is 6000 standard from ms knowledgebase?
helge
how can i check it out ? what for a filter do i need really ?

Helge,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://support.novell.com/forums)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://support.novell.com/forums/faq_general.html
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://support.novell.com/forums/

Why does Outlook 2010/2013 tries to connect by rpc over http in LAN?

Hi All,
I have Exchange 2010 (Two CAS) Published by TMG (Basic Authentication). Also outlook anywhere is configured with Basic Authentication.
Some users have issues with "authentication prompt" (randomly). By the way, Outlook Clients(2007/2010/2013) are fully updated.
What I can see when "authentication prompt" shows up, Outlook tries to connect by rpc over https.
Is this a normal behavior?
Regards
Jo

Hi,
Firstly, I'd like to say, basic authentication requires user name and password. Thus, it's an expected behavior that credential will prompt once when users login Outlook with basic authentication.
Additionally, I'd like to confirm how you confirm it's Outlook Anywhere when the credential prompts. Based on my knowledge, the credential issue may be caused by connectivity issue and we can confirm the connection method through the tool "connection status".
Thus, I'd like to confirm if the connection is established when the credential issue happens.
Press ctrl and right click Outlook icon>connection status>status, protocol
Thanks,
Angela Shi
TechNet Community Support

Trial SAN Certificate & Outlook Anywhere (RPC over HTTP) test fail

I am testing exchange 2013 where autodiscover pass while performing Outlook Anywhere (RPC over HTTP) connectivity test failed with invalid SSL certifiate . I am only using self certifiate .do any one idea if any CA provding SAN certificate trial basis.
Don't forget to mark helpful or answer
connect me :-
http://in.linkedin.com/in/satya11
http://facebook.com/satya.1000

Hi,
Agree with the above suggestion, ExRCA test cannot pass with self-signed certificate. And to ensure Outlook Anywhere work well , we need to install the self-signed certificate on all clients machines.
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

CSS load balance - Lock Outlook 2007 - RPC over http

I have problema whit load balance for configuration of client Outlook 2007. (using protocol RPC over http). Through the CSS, after a period of utilization, the Outlook lock. And without the CSS doind load balance, no ocurred the problem.
I appreciate any help.
Thanks!

Jason,
CSS is not created in a source group of "exchange2007rcvir. Is that the problem is that?
**** OWNER ****
content exchange2007rcvir
vip address 10.58.32.123
add service scmt801cto
add service scmt801cas
redundant-index 205
protocol tcp
advanced-balance sticky-srcip
sticky-inact-timeout 30
active
content exchangehtvir
vip address 10.58.32.89
add service scmt700cto
add service scmt700cas
redundant-index 201
protocol tcp
advanced-balance sticky-srcip
sticky-inact-timeout 30
active
content exchangewavir
vip address 10.58.32.33
add service scmt800cto
add service scmt800cas
redundant-index 51
protocol tcp
advanced-balance sticky-srcip
sticky-inact-timeout 30
active
***** GROUP *****
group exchangehtvir
add destination service scmt700cto
add destination service scmt700cas
vip address 10.58.32.91
active
group grp_axiavir
vip address 10.58.32.83
add destination service scxt393cas
add destination service scxt394cas
add destination service scxt395cas
add destination service scxt393cto
add destination service scxt394cto
add destination service scxt395cto
active
** No have exchange2007rcvir

Troubleshooting for RPC over https (Outlook Anywhere) connection issue

RPC over https (ROH), well known as Outlook Anywhere, is more frequently used. Even in Exchange 2013, Outlook no longer connects CAS server via MAPI.
In this thread, we will discuss about the troubleshoot checklist about the RPC over https (Outlook Anywhere) connection issue. In order to make it more logical, I’d like to divide the whole troubleshooting to the following processes:
1. Client side to CAS side
2. CAS side to MBX side
[Issues between Client side to CAS side]
In Exchange 2013, Outlook Anywhere is enabled by default. Different from this, Outlook Anywhere in Exchange 2007 and 2010 need to be manually enabled. Thus, please firstly check if the RPC over HTTP component has been installed:
Click Start, and then click Control Panel.
Double-click Programs and Features.
In the left pane of Server Manager, click Features.
In the right pane, click Add Features.
Check if the RPC over HTTP component has been selected.
If the ROH connectivity issue only happens on certain users, the property MAPIBlockOutlookRpcHTTP can be checked:
Get-CASMailbox name | fl MAPIBlockOutlookRpcHttp
2. Confirm if Exchange server is blocked. Ping the Exchange server FQDN on client machine and confirm if it can return the proper IP address.
3. Check if the RPC Proxy server is responding correctly:
rpcping -t ncacn_http -s ExchServer -o RpcProxy=RPCProxyServer -P "user,domain,*" -I "user,domain,*" -H 2 -u 10 -a connect -F 3 -v 3 -E -R none
If 200 code returns, the test is successful.
4. Check if Outlook Anywhere host names are added in the certificate:
To get host names, the following command can be used: get-outlookanywhere |fl *hostname
5. To use the Shell to test Outlook Anywhere connectivity, use the
Test-OutlookConnectivity cmdlet.
[Issues between CAS side to Mailbox side][RZ1]
A. Check if it can connect to store’s port:
RpcPing –t ncacn_http –s ExchangeMBXServer -o RpcProxy=RpcProxyServer -P "user,domain,password" -I "user,domain,password" -H 1 –F 3 –a connect –u 10 –v 3 –e 6001
If it returns as following: Completed 1 calls in 60 ms 16 T/S or 60.000 ms/T, it means the RPC Ping Utility test succeeds.
B. Check if it can Connect to DsProxy Service:
RpcPing –t ncacn_http –s ExchangeMBXServer -o RpcProxy=RpcProxyServer -P "user,domain,password" -I "user,domain,password" -H 2 –F 2 –a connect –u 10 –v 3 –e 6004
If it returns as following: Completed 1 calls in 60 ms 16 T/S or 60.000 ms/T, it means the RPC Ping Utility test succeeds.
C. Check the following registries:
[Disable the auto update]
1).Open Regedit and navigate to:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeServiceHost\RpcHttpConfigurator\RpcHttpConfigurator
2).Set the PeriodicPollingMinutes value to 0.
[Check the RpcProxy ValidPorts]
1).On the RPC proxy server, start Registry Editor (Regedit).
2). In the console tree, locate the following registry key:
HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\RpcProxy
3). In the details pane, right-click the ValidPorts subkey, and then click Modify.
4). In Edit String, in the Value data box, type the following information:
ExchangeServer :6001-6002; ExchangeServerFQDN :6001-6002; ExchangeServer :6004; ExchangeServerFQDN :6004
Note:
ExchangeServer is the NetBIOS name of your Exchange server. ExchangeServerFQDN is the fully qualified domain name (FQDN) of your Exchange server. If the FQDN that is used to access the server from the Internet differs from the internal FQDN, you must use
the internal FQDN.
[Check the 6004 port settings in registry]
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeSA\Parameters
Value name: HTTP Port
Value type: REG_DWORD
Value data: 0x1772 (Decimal 6002)
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeSA\Parameters
Value name: Rpc/HTTP NSPI Port
Value type: REG_DWORD
Value data: 0x1774 (Decimal 6004)
D. Check if the RPC ports are used by other applications instead of Exchange by using : netstat –o
Then it will return all active TCP connections and the process ID (PID) for each connection.
After that, please check the application based on the PID on the Processes tab in Windows Task Manager and confirm if it’s Exchange server.
Additionally, ExRCA is a perfect tool to test the whole connection between client side and Mailbox side:
https://testconnectivity.microsoft.com/
1. On the ExRCA website, under Microsoft Office Outlook Connectivity Tests, select Outlook connectivity, and then select Next at the bottom of the page.
2. Enter the required information on the next screen, including email address, domain and user name, and password.
3. Choose whether to use Autodiscover to detect server settings or to manually specify server settings.
4. Accept the disclaimer, enter the verification code, and then select Verify.
5. Select Perform Test.
<Resource for reference>
How does Outlook Anywhere work (and not work):
http://blogs.technet.com/b/exchange/archive/2008/06/20/3405633.aspx
How to use the RPC Ping utility to troubleshoot connectivity issues with the Exchange over the Internet feature in Outlook 2007 and in Outlook 2003:
http://support.microsoft.com/kb/831051
Test Outlook Anywhere Connectivity:
http://technet.microsoft.com/en-us/library/ee633453(v=exchg.150).aspx
[RZ1]It’s part, please re-layout
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

I've just restored the M11 to Windows XP with the disks provided and Outlook Anywhere connected without issue. As strange as it sounds, this looks to be isolated to this particular model of laptop and Windows 7.
I've used the same Enterprise copy of Windows 7 and Office on a variety of laptops and pc's and none have come across this problem. The only commonality I can see is the hardware and OS.
Aftery trying to troubleshoot this unsuccessfully with Microsoft tech support for a few hours, they eluded to the fact that this +could+ be a hardware related problem. (driver, adapter properties, etc)

Outlook 2010 RPC over HTTP to Exchange 2003 users remain disconnected after login

Greetings Guys,
I am unable to find a solution, Windows 2003 DC, Exchange 2003, all user were working great, RPC over HTTP, until Tuesday at about the same time perhaps before the MS update KB3002657
all remote users using outlook 2010 did not have authentication popups as was noted from this KB. But instead all login successfully, ( looking at the security logs in the exchange) , but all are remaining disconnected, immediately after login.
The users had already been configured with the registry DefConnectOpts RPC key, so I doubt their Outlook profiles are the problem.
I suspect the DC's ( we have 2 ) or the exchange have picked up an issue. I am out of ideas.
Any help would be awesome
Barry

Hi,
According to your description, I understand that Outlook(Outlook Anywhere) client display disconnected after install MS update KB3002657.
If I misunderstand your concern, please do not hesitate to let me know.
KB3002657 is a security update to prevent attacker logging on to a domain-joined system and being able to monitor network traffic. More details about this update, please refer to:
https://technet.microsoft.com/library/security/ms15-027
For your question, please try to reconfigure a Outlook profile for testing.
If it works, you can try to below steps to pop sign in page in Outlook client:
1. Open Outlook---> File and click “Account setting”, then select account name and click “Change”.
2. Click “More settings”, switch “Security” and check “Always Prompt for logon credentials”。
3. Restart Outlook to login your account.
Once this done, you can uncheck this setting for convenience.
Besides, I find an similar thread about your question, for your reference:
https://social.technet.microsoft.com/Forums/exchange/en-US/7199811f-ee41-4b81-aafe-698bdb5a0b49/recently-outlook-cannot-auth-username-and-password?forum=exchangesvrclients
Thanks
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Allen Wang
TechNet Community Support

Exchange 2007 - enabling RPC over HTTP in add/remove windows components

Does adding this component require a reboot or interrupt Exchange functionality?

Hi,
Based on my knowledge, there is no need to reboot the Exchange server 2007 when you install the Windows RPC over HTTP Proxy component.
What's more, here is an article for your reference.
How to Enable Outlook Anywhere
http://technet.microsoft.com/en-us/library/bb123889(v=exchg.80).aspx
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

500 Internal server error on RPC over HTTP using TS Gateway

I've been happily using TS Gateway on Windows Server 2008 x64 for 18 months and everything was working perfectly. Suddenly this week it started giving "access denied" errors to any user who tried to connect, evidenced in event viewer as a failed login attempt.
After restarting the server, it got worse in that if I browse to the /rpc folder it gives me 500 Internal server error and I don't even get as far as authenticating credentials. I've tried removing IIS, RPC over HTTP and TS Gateway, and re-adding all of them,
but I still get the same error 500. The RPC and TS Gateway services are both running. What could be causing this and how can I fix it?

Hi,
Thanks for your post.
Firstly, check the following KB article to troubleshoot this issue.
This computer can't connect to the remote computer because the Terminal Services Gateway server is temporarily unavailable
http://support.microsoft.com/default.aspx?scid=kb;EN-US;969743
If the issue still persists, you may perform the below steps:
Uninstalled TSGateway, IIS role, all IIS related components.
Delete all files in the folder %windir%\system32\inetsrv\config
Delete all files in the folder %windir%\system32\inetsrv\metaback
Restart the server and try to re-install TSGateway again
Best Regards,
Aiden
Aiden Cao
TechNet Community Support
Thank you very much for this. I confirm it fixed the problem, although there was an error in reinstalling IIS and TS Gateway until I also removed Windows Process Activation Service.

RPC over HTTP trouble Exchange 2013/2007 coexistence, 2013 RPCProxy cannot ping GC.

I currently have an Exchange 2013/2007 coexistence scenario which gives me trouble with the RPC over HTTP part with users with a 2007 mailbox. the MS RCA website performs 2 tests with the MAPI address book endpoints, once against a 2007 mailbox server and
once a against a GC/DC, the last one fails. The logs are from our test domain, but the exact same happens in the production domain. running CU8 (recently upgraded, but problem was exactly the same with CU7)
Testing the MAPI Address Book endpoint on the Exchange server.
The address book endpoint was tested successfully.
Additional Details
Elapsed Time: 7872 ms.
Test Steps
Attempting to ping the MAPI Address Book endpoint with identity: exmb11.domain.test:6004.
The endpoint was pinged successfully.
Additional Details
The endpoint responded in 156 ms.
Elapsed Time: 4153 ms.
Testing the MAPI Address Book endpoint on the Exchange server.
An error occurred while testing the address book endpoint.
Additional Details
Elapsed Time: 3079 ms.
Test Steps
Attempting to ping the MAPI Address Book endpoint with identity: tdc01421.domain.test:6004.
The attempt to ping the endpoint failed.
<label for="testSelectWizard_ctl12_ctl06_ctl02_ctl09_ctl00_tmmArrow">Tell
me more about this issue and how to resolve it</label>
Additional Details
The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process.
Elapsed Time: 3079 ms.
texmb11 = ex2007 mailbox
texfr11 = ex2007 CAS
tdc01421 = DC/GC
texch31 = 2013 multirole
other symptoms :
Browser test
https://texch31.domain.test/rpc/rpcproxy.dll?texmb11:6004
--> 503 (which is correct)
https://texch31.domain.test/rpc/rpcproxy.dll?tdc01421:6004
--> 404.0 Not Found
RPCPing
rpcping -t ncacn_http -s texmb11 -o RpcProxy=texch31.domain.test -P "user,dom,*" -I "user,dom,*" -H 2 -u 9 -a connect -F 3 -v 3 -e 6004
Success
rpcping -t ncacn_http -s tdc01421 -o RpcProxy=texch31.domain.test -P "user,dom,*" -I "user,dom,*" -H 2 -u 9 -a connect -F 3 -v 3 -e 6004
Fails!
so the Ex2013 RPCProxy doesn't proxy to the DC/GC, but the RPCProxy to an ex2007 mailbox server works fine, so the authentication methods configured are correct i'd say..
the same tests using the ex2007CAS server as RPC proxy all succeed!:
MS RCA is all green
https://texfr11.domain.test/rpc/rpcproxy.dll?texmb11:6004
--> 503
https://texfr11.domain.test/rpc/rpcproxy.dll?tdc01421:6004
--> 503
rpcping -t ncacn_http -s texmb11 -o RpcProxy=texfr11.domain.test -P "user,dom,*" -I "user,dom,*" -H 2 -u 9 -a connect -F 3 -v 3 -e 6004
Success
rpcping -t ncacn_http -s tdc01421 -o RpcProxy=texfr11.domain.test -P "user,dom,*" -I "user,dom,*" -H 2 -u 9 -a connect -F 3 -v 3 -e 6004
Success!!
Logs
all tries against the 2013 CAS server generate '404' log entries in several logs int the Logging directory, the most explicit being the one in Program Files\Microsoft\Exchange Server\V15\Logging\HttpProxy\RpcHttp : HttpProxy_xxxxxx.LOG
2015-04-30T19:58:00.153Z,895cdf07-f2eb-4beb-b787-da02ba11b0c2,15,0,1076,0,,RpcHttp,webmail.domain.test,/rpc/rpcproxy.dll,,Basic,true,DOM\user,,,MSRPC,10.10.142.132,TEXCH31,404,,MailboxGuidWithDomainNotFound,RPC_IN_DATA,,,,,,,,,4,,,,1,,,0,,0,,0,0,,0,2,0,,,,,,,,,1,1,0,,1,,2,2,,?TDC01422.domain.test:6004,,BeginRequest=2015-04-30T19:58:00.153Z;CorrelationID=<empty>;ProxyState-Run=None;ProxyState-Complete=CalculateBackEnd;EndRequest=2015-04-30T19:58:00.153Z;,HttpProxyException=Microsoft.Exchange.HttpProxy.HttpProxyException:
RPC server name passed in by client could not be resolved: TDC01422.domain.test at Microsoft.Exchange.HttpProxy.RpcHttpProxyRequestHandler.ResolveToDefaultAnchorMailbox(String originalRpcServerName String reason) at
Microsoft.Exchange.HttpProxy.RpcHttpProxyRequestHandler.ResolveAnchorMailbox() at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.InternalBeginCalculateTargetBackEnd(AnchorMailbox& anchorMailbox) at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.<BeginCalculateTargetBackEnd>b__3b();
the error suggests the name could not be resolved. but nslookup works fine. i can ping the tdc01421 correctly form texch31, it returns me the ipv4 address. i can telnet to port 6004 from texch31 server to tdc01421 giving me the correct 'ncacn_http' answer..
i look at the 'ValidPorts' and ValidPorts_Autoconfig_Exchange reg keys and filled them with the same i have on the 2007cas servers (all ex servers, all dc/gc's, all of them with netbios & fqdn ports 6001,6002 & 6004..) but also no success.
im out of ideas by now..

Hello togehter,
if anyone is using the Interim Update (Hotfix) "Exchange2013-KB2997209_2997847-x64-en.msp" please be aware of the following bug in this hotfix:
NOTE: Another issue that we have seen only from some E2013 On-Premises customers who installed
fixes for any of the above E2013 CU6 related issues is that “Using OWA, users cannot create new messages or reply to existing messages” – These are mostly installer issues where OWA files are not copying correctly in the new version directory. Ideally the
content of these two folders, i.e. “V15\ClientAccess\Owa\prem\15.0.995.31” and “V15\ClientAccess\Owa\prem\15.0.995.29” should be identical, now if for any reason, they are not then it can break the OWA experience like described above. Take these steps if you
run into related issues:
-Backup the contents of “15.0.995.31” folder to a different folder/directory
-Copy the files and folders from “15.0.995.29” to “15.0.995.31” folder – this should fix the issue …
Best,
Martin

Is there any apps for iphone to support rpc over http or any software yet

Hi,
Am wondering if there is any kind of app or software that supports rpc over http in exchange 2003 enviroment for iphone?? I am looking for solution for my company employees so that they can get emails securly to their hand held devices. I found one called "good" but havent used yet and dont know if there is any configuration fro rpc over http. Any suggestion would be greatly appreciated.
Many thanks,

The number of apps currently available in the App Store compatible with both iOS 4.2.1 and the iPhone 3G hardware (a major limitation) is dwindling rapidly. If you don't already have a supply of apps, your choices are getting fewer and fewer. TIme to consider upgrading the phone.

RDS 2012 Disable HTTP transport - Enable only RPC over HTTP for both pre 8 and 8 RDP clients

Hi,
Is it possible to enable only RPC over HTTP for both pre 8 and 8 RDP clients?
Thank you

I would like to know this as well.

Exchange 2010 RPC over HTTPs failing with authentication error

Hi. I have my remote.xxx.co.uk domain and autodiscover.xxx.co.uk domain pointing to my SBS2011 server, have ports 25, 80, 443 open. The Microsoft Connectivity Analyzer fails with the below error.
Outlook will autodiscover happily on the local network, and works fine. Phones etc do too.
Outlook at a remote VPN connected site won't connect through autodiscover, but will if you do it manually (ignoring the RPC Proxy settings). Everything works for a while, but then I guess outlook decides to use autodiscover to complete all the connection
details, and then these machines can no longer connect to exchange as I guess they decide the speed is too slow and try to connect using RPC instead.
Users can access OWA happily, and activesync is working on phones etc.
SSL cert is a wildcard type on my domain, and certs are installed - all green and happy when visiting OWA on both remote.xxxxx.co.uk and autodiscover.xxxxx.co.uk domains.
I cannot work out why I have an authentication error for RPC?
Any advice would be great!
Testing HTTP Authentication Methods for URL https://remote.xxxxx.co.uk/rpc/rpcproxy.dll?xxxxxx.xxxxxx.local:6002.
The HTTP authentication test failed.
Additional Details
Exception details:
Message: The operation has timed out
Type: System.Net.WebException
Stack trace:
at System.Net.HttpWebRequest.GetResponse()
at Microsoft.Exchange.Tools.ExRca.Extensions.RcaHttpRequest.GetResponse()
Elapsed Time: 100065 ms

Hi.
To update.
I tried to recreate the virtual directories in the Exchange Management Console, using the recreate links and via the shell, but while they were recreated, they did not function as they should due to issues in the meta database.
I then found the following which worked.
Looking at the ActiveSync virtual directories, when running the below command, the result showed the directory was there, so I then knew to delete it.
In EMS I ran,
=> Ran "$site = [ADSI]"IIS://localhost/W3SVC/1/Root/Microsoft-Server-ActiveSync""
Result: Carriage return.
=> Ran "$site"
Result:
distinguishedName:
Path: {C:\Program Files\Microsoft\ExchangeServer\V14\Client Access\Sync}
In EMS I then ran,
=> Ran "$Site = [ADSI]"IIS://localhost/W3SVC/1/Root""
Result: Carriage return.
=> Ran "$site.Delete("IIsWebVirtualDir","Microsoft-Server-ActiveSync")"
Result: Carriage return.
=> Ran "$site.SetInfo()"
Result: Carriage return.
=> Ran "$site"
Result: Carriage return.
=> Ran "iisreset"
I then recreated the virtual directories.
In EMS I ran,
=> Ran "New-ActiveSyncVirtualDirectory -WebSiteName "Default Web Site""
Results: Successfully recreated.
=> Ran "iisreset"
I am not sure exactly, but I did this for multiple virtual directories, and everything came to life just as it should.

Exchange 2003 - Can't connect RPC over HTTP

I'm running a Windows SBS 2003 with Exchange, and am trying to configure Outlook anywhere.
Slowly I've been making progress on the Microsoft Connection analyzer, but this one has me stumped. (I'm not much of an IT professional.)
Can anyone help me out?
Testing RPC/HTTP connectivity.
The RPC/HTTP test failed.
Additional Details
Test Steps
Attempting to resolve the host name mail.****.com in DNS.
The host name resolved successfully.
Additional Details
Testing TCP port 443 on host mail.****.com to ensure it's listening and open.
The port was opened successfully.
Additional Details
Testing the SSL certificate to make sure it's valid.
The certificate passed all validation requirements.
Additional Details
Test Steps
Checking the IIS configuration for client certificate authentication.
Client certificate authentication wasn't detected.
Additional Details
Testing HTTP Authentication Methods for URL https://mail.****.com/rpc/rpcproxy.dll?PTESVR1.****.local:6002.
The HTTP authentication test failed.

Hi,
According to the test result, there may be improper authentication method which your RPC virtual directory has.
Start the Internet Information Service Manager, navigate to the Default Website and right click the RPC Virtual Directory. Navigate to the Directory Security tab and confirm if you disable the Checkbox for Enable Anonymous Access and enable the Basic Authentication
checkbox.
And here is a similar thread you can refer to:
http://social.technet.microsoft.com/Forums/exchange/en-US/3021fc19-ed26-48e0-8d77-094b0ac6eb85/client-certificate-authentication-wasnt-detected?forum=exchangesvr3rdpartyappslegacy
And we can also check the settings in the RPC virtual directory.
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

Exchange 2013 SP1 - Unable to test Mapi-over-HTTP Outlook Connectivity

I've configured MAPI over HTTP in my testing environment. It is working fine. But i'm unable to test this configuration using the Powershell Test-OutlookConnectivity CMDlet.
Outlook is working fine and is using MAPI over HTTP, so i'm pretty sure there are no configuration problems. But the CMD-let gives me the following output:
[PS] C:\Windows\system32>Test-OutlookConnectivity -RunFromServerId <myserver> -ProbeIdentity OutlookMapiHttpSelfTestProbe
WARNING: An unexpected error has occurred and a Watson dump is being generated: Failed to find the probe result for
invoke now request id 1ad0cb55e6cc45c791194b34641fe3c2 and probe workdefinition id 241.
Failed to find the probe result for invoke now request id 1ad0cb55e6cc45c791194b34641fe3c2 and probe workdefinition id
241.
    + CategoryInfo          : NotSpecified: (:) [Test-OutlookConnectivity], InvalidOperationException
    + FullyQualifiedErrorId : System.InvalidOperationException,Microsoft.Exchange.Management.Tasks.TestOutlookConnecti
   vity
    + PSComputerName        : <fqdn of my serer>
Does anyone have a sollution for this?

Hello @all,
I got the same issue. The configuration is functional (Outlook connects over http). But the test-cmdlet raises this error. Is there any solution?
Greetings from Germany

Outlook rpc over http

Similar Messages

Maybe you are looking for