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

Testing RPC over HTTP inside the network

I'm looking to setup and configure RPC over HTTP.  I want to setup a test mailbox to configure and test it.  Is it possible to test RPC over HTTP on a computer that is never outside the domain?  It is a desktop on the domain.  
0
pcmb
Asked:
pcmb
  • 3
  • 2
1 Solution
 
weareitCommented:
Yes it is.  In the configuration of the Outlook Client, choose to use HTTP connections on a fast network before TCP/IP.

Start --> Settings --> Control Panel --> Mail
Click Email Accounts
Choose view or change existing Email accounts
Click Change
Click More Settings
On the Connection Tab, click Exchange Proxy Settings (if greyed out, select Connect to my Exchange Server using HTTP)
Select On fast network, connect using HTTP first, then connect using TCP/IP

You can visually see which connection you are using by using Start --> Run
Type in OUTLOOK.EXE /RPCDIAG and press enter.

This will give you a monitor to tell you what you are connecting to and what kind of protocol.  Included is information regarding successfull connections and failed connections.

http://www.petri.co.il/configure_rpc_over_https_on_a_single_server.htm
http://www.petri.co.il/testing_rpc_over_http_connection.htm

-saige-
0
 
pcmbAuthor Commented:
Upon completing your instructions, I click OK to close the "Microsoft Exchange Proxy Settings" window and it states that "The proxy server you have specified is invalid. Please correct it and try again".  I don't have a proxy server.  I entered the URL to access OWA externally in the field for connection settings for Exchange Proxy.  Any thoughts on what that would be?  Thanks.
0
 
weareitCommented:
Did you configure the server side first?

As Simon has stated in the past:

Basically RPC over HTTPS fails on three points....

- SSL certificate acceptance
- Authentication
- Registry settings

If you configured your server-side properly then this is a case of DNS and IIS.  If you are using mail.mycompany.com as the external address for your mail server, then your internal domain would need to be configured to recognize the address at it's internal location.  This is for a variety of reasons, prevents uneeded DNS lookup's/queries to outside servers just to loopback to an internal address, allows for faster access for internal clients, prevents uneeded/unwanted bandwith usage.

Essentially you would accomplish this by doing the following on your DNS server.
1.  Create a new forward lookup zone in DNS called mydomain.com (mydomain would be substituted with your actuall external domain name).
2.  Create a host record for your mail server.
3.  Make your DNS Server a Name Server for the new zone.
4.  If your internal clients are going to use multiple host headers to go to different addresses, i.e. mail.domain.com, smtp.domain.com, www.domain.com, create assosciated Host Records for each header value.
5.  Create associated CNAME Records for any header value that is associated with your server:

MYDOMAIN.COM
(same as parent folder)      Name Server (NS)            DNS1.MYDOMAIN.LOCAL
DNS1                  Host (A)                   192.168.1.3
MAIL1                  Host (A)                   192.168.1.5
MAIL                  Alias (CNAME)            MAIL1.MYDOMAIN.LOCAL
MYSITE                  Host (A)                  62.48.192.51 <---- Assumes an offsite hosted mysite
WWW                  Host (A)                  66.142.78.23 <---- Assumes an offsite hosted www

You may also want to create an ALIAS record on your internal DNS primary zone that points back to the host specified on your external record, in my example above I would create a CNAME/ALIAS record on my DNS server that would be named MAIL.

MYDOMAIN.LOCAL
(same as parent folder)      Name Server (NS)            DNS1.MYDOMAIN.LOCAL
DNS1                  Host (A)                   192.168.1.3
MAIL1                  Host (A)                   192.168.1.5
MAIL                  Alias (CNAME)            MAIL1.MYDOMAIN.LOCAL

After that, open IIS Manager and modify the OWA website (generally Default Web Site)
Right-click on Default Web Site and choose Properties
Click on Advanced
You will be presented with a screen that has ip adresses, ports and host header values.
By default for the Default Web Site the first entry is:

Default               80

You would need to add the following (using my example):

Default               80               mail
Default               80               mail.mycompany.local
Default               80               mail.mycompany.com

HTH,

-saige-
0
 
pcmbAuthor Commented:
Thanks.  I'll try these steps and give you feedback.
0
 
pcmbAuthor Commented:
I setup an Outlook 2007 client to work with RPC over HTTP while on the LAN and it worked.  Then I dropped of the LAN on to a Mobile air card and it is still working.  However, I then tried to set it up remotely on another computer that is not a member of that domain and has Outlook 2003 and I was not able to get it to connect.  Does the client need to be a domain member?  Does the initial setup need to occur on the LAN?
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.

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