• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2273
  • Last Modified:

RPC over HTTP

I am trying to configure Outlook Anywhere but failing the connectivity test at  exrca.com and I receive the following message Testing RPC/HTTP connectivity.
  The RPC/HTTP test failed.

 Attempting to resolve the host name mail.domain.com/exchweb in DNS.
  The host name couldn't be resolved.
   Tell me more about this issue and how to resolve it
 
 Additional Details
 
Host mail.domain.com/exchweb couldn't be resolved in DNS InfoDomainNonexistent.

Elapsed Time: 79 ms.  
 
 The onsite server is a Windows 2003 Standard and Exchange 2003 Standard. I've installed RPC over HTTP . I've been following the article  http://www.msexchange.org/articles-tutorials/exchange-server-2003/migration-deployment/Implementing-RPC-over-HTTPS-single-Exchange-Server-2003-environment.html

I've stopped at "Set the NT Directory Services (NTDS) port on all Global Catalog Servers that act as Exchange Server 2003 back-end Servers". I have not configured this before and would like to know if there would be any negative impact on the production servers.

The aim is to use Outlook Anywhere rpc over http in migrating mailboxes from the onsite Exchange to office 365.

Any guidance will be useful.
0
mail2clk
Asked:
mail2clk
  • 2
  • 2
1 Solution
 
Simon Butler (Sembee)ConsultantCommented:
"mail.domain.com/exchweb"

That is the wrong URL to be using. You should enter JUST mail.domain.com, nothing else.

RPC over HTTPS either works or it doesn't. On Exchange 2003 there are only three things that are wrong - the SSL certificate isn't trusted, the wrong authentication type or the registry entries are wrong.

Compare the instructions you are using to the ones I wrote years ago:
http://exchange.sembee.info/2003/rpcoverhttp/default.asp

Simon.
0
 
mail2clkAuthor Commented:
Very useful.
The tests are failing on the authentication. Where should I be looking and what should the authentication should be set as?

      The HTTP authentication test failed.
       
      Additional Details
       
Exception details:
Message: The underlying connection was closed: The connection was closed unexpectedly.
Type: System.Net.WebException
Stack trace:
at System.Net.HttpWebRequest.GetResponse()
at Microsoft.Exchange.Tools.ExRca.Extensions.RcaHttpRequest.GetResponse()
Elapsed Time: 454 ms.
0
 
Simon Butler (Sembee)ConsultantCommented:
Authentication usually comes down to having integrated/NTLM enabled on the server and trying to use basic (or vice versa). Furthermore, some firewalls can break NTLM, meaning you have to use Basic.

Simon.
0
 
mail2clkAuthor Commented:
Issue is now resolved. Thank you Simon all tests are now passed.
0

Featured Post

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now