Solved

RPC OVER HTTP WORKS INTERNALLY BUT NOT EXTERNALLY

Posted on 2006-06-27
15
411 Views
Last Modified: 2010-03-06
I setup RPC over HTTP on my Exchange 2003 box that runs windows 2003 server.  RPC over HTTP works internally but not externally.  Can anyone give me some clue??  I do have a firewall and its a sonicwall. Do I need to add specific ports.  I added ports 6001, 6002, and 6004 and forwarded them to my exchange server.
0
Comment
Question by:Matt Pessolano
  • 6
  • 5
  • 4
15 Comments
 
LVL 31

Expert Comment

by:LeeDerbyshire
ID: 16992909
Depending on whether your using HTTP or HTTPS, you will need to forward port 80 or 443.
0
 
LVL 6

Expert Comment

by:Michael S
ID: 16992935
Those ports don't need to be forwarded on your firewall - they are ports that Exchange uses internally.

You need to have SSL forwarded with a certificate installed in IIS, and configure RPC over HTTPS to point to your external DNS.

Follow this link for more info:

http://www.amset.info/exchange/rpc-http-server.asp

Jay
0
 
LVL 1

Author Comment

by:Matt Pessolano
ID: 16993078
i deleted those other post and forwarded port 80 to my exchange server and I get the login prompt but then it never connects
0
 
LVL 31

Expert Comment

by:LeeDerbyshire
ID: 16993183
Have a look under the Tutorials section of this link:
http://www.msexchange.org/pages/search.asp?query=rpc
There are lots of RPC/HTTPS articles there.
0
 
LVL 31

Expert Comment

by:LeeDerbyshire
ID: 16993346
Come to think of it, do you have a computer (say a laptop) that can be connected to the server either directly via the LAN, and also from the Internet?  Since you said that it works internally, it would be good if you could use a computer that is known to work internally, and then try to get it to connect externally.  That way, you can be sure that all your settings are right, and that you need to look at the firewall.
0
 
LVL 1

Author Comment

by:Matt Pessolano
ID: 16993419
yea I do that is what I am using.  A laptop.  
0
 
LVL 31

Expert Comment

by:LeeDerbyshire
ID: 16993507
Is there any way you can get the laptop connected externally, get the IP address, and then temporarily allow all traffic from that IP to the server - just to see if there is a firewall problem?  As far as I know, this doesn't require any other ports beside the HTTP/S ones, but it's possible that a sophisticated firewall might need to be told more about the kind of traffic going through it.
0
Why You Should Analyze Threat Actor TTPs

After years of analyzing threat actor behavior, it’s become clear that at any given time there are specific tactics, techniques, and procedures (TTPs) that are particularly prevalent. By analyzing and understanding these TTPs, you can dramatically enhance your security program.

 
LVL 6

Expert Comment

by:Michael S
ID: 16993547
You have to have an SSL certificate in order for it to work externally.  It is a misnomer to call it RPC over HTTP, when it is in reality RPC over HTTPS.  If you try to connect just over HTTP, you'll be banging your head against a wall for days.
0
 
LVL 1

Author Comment

by:Matt Pessolano
ID: 16993566
no right now im just doing rpc/http  im still not getting anywhere
0
 
LVL 1

Author Comment

by:Matt Pessolano
ID: 16993572
i tried the firewall portion as well. Im allowed access.  Does the global catalog server have to be windows 2003 in order for this to work?
0
 
LVL 6

Expert Comment

by:Michael S
ID: 16993646
On the computer that you say works internall, go to Start/Run and type in outlook.exe /rpcdiag.

Under the Conn heading if it is working properly it will say HTTPS.  If it is not working properly it will say TCP/IP.
0
 
LVL 1

Author Comment

by:Matt Pessolano
ID: 16994158
when i type that in Outlook just pops up.  I dont get anything else.
0
 
LVL 31

Expert Comment

by:LeeDerbyshire
ID: 16994361
Make sure that you don't already have OL running.  The /rpcdiag switch will open OL as normal, but there should be another window appearing on the screen somewhere.
0
 
LVL 1

Author Comment

by:Matt Pessolano
ID: 16994381
it says tcp/ip
0
 
LVL 6

Accepted Solution

by:
Michael S earned 500 total points
ID: 16994447
I would start over and follow this link:

http://www.amset.info/exchange/rpc-http.asp

You will need an SSL certificate.  You can either use your own CA or download a temporary one from www.rapidssl.com

Simon's guide works very well, along with the one at http://www.petri.co.il/configure_rpc_over_https_on_a_single_server.htm

Good luck!
0

Featured Post

Why spend so long doing email signature updates?

Do you spend loads of your time carrying out email signature updates? Not very interesting are they? Don’t let signature updates get you down. Let Exclaimer Cloud - Signatures for Office 365 make managing email signatures a breeze.

Join & Write a Comment

We are happy to announce a brand new addition to our line of acclaimed email signature management products – CodeTwo Email Signatures for Office 365.
Find out how to use Active Directory data for email signature management in Microsoft Exchange and Office 365.
In this video we show how to create a Resource Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: Navigate to the Recipients >> Resources tab.: "Recipients" is our default selection …
This video discusses moving either the default database or any database to a new volume.

747 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now