Hi,

I have been told by Barracuda Support to verify my Exchange 2013 RPC url is working correctly using the following address in a Web Browser: 

https://RoH server address/rpc

When I hit this URL I input my credentials and get a Error 404 - Page Not Found. 

I dont have any issues with Outlook Anywhere and clients are working fine. The tests come from this article and I am wondering if they are still valid for Exchange 2013 so need some help:

https://techlib.barracuda.com/BMA/EnableRoH

Does anyone else get the 404 error when they try the RPC virtual directory? If I got rpc/rpcproxy.dll that works fine and no issues. 

We have Outlook Anywhere configured for NTLM authentication so maybe this is an issue and should be Basic?

I did some digging in the CAS RPC logs and I found this connection attempt:

<snip>

2014-06-18T15:22:40.902Z,CAS-SERVER,RpcHttp,"S:Stage=EndRequest;S:UserName=domain\admin;S:OutlookSessionId=""{1A731432-5548-402F-892A-C9FE489BB78D}"";S:AuthType=Basic;S:Status=404 Not Found;S:HttpVerb=RPC_IN_DATA;S:UriQueryString=?pdc.domain.local:593;S:RequestId=7b1e355e-6448-4ed4-8112-8ab13d88a76f;S:ClientIp=192.168.0.17"

</snip>

As you can see the 404 Not Found is for the request to /rpc. I am wondering if maybe this has changed in Exchange 2013 SP1? Or have I got a bigger issue here? 

Issue is now fixed. It was not an issue with Exchange at all.

It was a configuration issue on the third party appliances. With Exchange 2013 I totally forgot the server name is now the GUID like seen in Outlook Account Settings and not the actual Outlook Anywhere URL.

Example:

2a93619e-040a-4d48-976c-9d895e34ad86@internal.local 

I then had to set the Proxy Server as the Outlook Anywhere URl and this solved the issue. 

So turns out it was actually a misconfiguration on the third party appliance and no issue with the Exchange 2013 server installation. :-)

• Marked as answer by JRATechNet 20 hours 6 minutes ago

Issue is now fixed. It was not an issue with Exchange at all.

It was a configuration issue on the third party appliances. With Exchange 2013 I totally forgot the server name is now the GUID like seen in Outlook Account Settings and not the actual Outlook Anywhere URL.

Example:

2a93619e-040a-4d48-976c-9d895e34ad86@internal.local 

I then had to set the Proxy Server as the Outlook Anywhere URl and this solved the issue. 

So turns out it was actually a misconfiguration on the third party appliance and no issue with the Exchange 2013 server installation. :-)

• Marked as answer by JRATechNet Friday, June 20, 2014 2:47 PM

Issue is now fixed. It was not an issue with Exchange at all.

It was a configuration issue on the third party appliances. With Exchange 2013 I totally forgot the server name is now the GUID like seen in Outlook Account Settings and not the actual Outlook Anywhere URL.

Example:

2a93619e-040a-4d48-976c-9d895e34ad86@internal.local 

I then had to set the Proxy Server as the Outlook Anywhere URl and this solved the issue. 

So turns out it was actually a misconfiguration on the third party appliance and no issue with the Exchange 2013 server installation. :-)

• Marked as answer by JRATechNet Friday, June 20, 2014 2:47 PM

Hi,

Thanks for your generous sharing : )

 

Thanks

Mavis