• RSS
  • Twitter
  • FaceBook

Exchange Server Forums

Forums | Register | Login | My Profile | Inbox | RSS RSS icon | My Subscription | My Forums | Address Book | Member List | Search | FAQ | Ticket List | Log Out

RPC over HTTP Problem

Users viewing this topic: none

Logged in as: Guest
  Printable Version
All Forums >> [Microsoft Exchange 2003] >> General >> RPC over HTTP Problem Page: [1]
Login
Message << Older Topic   Newer Topic >>
RPC over HTTP Problem - 18.Apr.2008 2:56:25 PM   
colnar

 

Posts: 12
Joined: 28.Aug.2007
Status: offline
I need some help with RPC over HTTP. I have it set up on my server and can access it wothout a problem from within the network, but when I try and access it from outside the network, I get an error that the Exchange server is unavailble. I have opened ports 6001,6002, and 6004 in the router. When I run a portqry by FQDN the ports read as open, but when I run the portqry by IP, the read as filtered. I have one server that is both DC and Exchange. I am running server 2003 SP1 and Exchange 2003 SP2. Any ideas?
Post #: 1
RE: RPC over HTTP Problem - 18.Apr.2008 6:34:31 PM   
Sembee

 

Posts: 4093
Joined: 17.Jan.2008
From: Somewhere near London, UK
Status: offline
You don't need those ports open on the router. The feature is designed to work over port 443 only - so close those ports.

RPC over HTTPS fails for one of three reasons.
- SSL certificate trust issues
- authentication mismatch
- registry settings are wrong.

The troubleshooting steps and causes are well documented, I have posted them on this forum a number of times. Also see my web site at http://www.amset.info/exchange/rpc-http.asp

Simon.

_____________________________

Simon Butler,
Exchange MVP
Blog: http://blog.sembee.co.uk/
Web: http://www.amset.info/
In the UK? Hire me: http://www.sembee.co.uk/
Exchange Resources: http://exbpa.com/

(in reply to colnar)
Post #: 2
RE: RPC over HTTP Problem - 24.Apr.2008 11:14:41 AM   
colnar

 

Posts: 12
Joined: 28.Aug.2007
Status: offline
I have gone through all the settings and everything appears correct. When I run outlook /rpcdiag from inside the domain, I connect without any problems. When I try to do this from outside the domain, I get an error that exchange is not available. Any ideas? I am assuming that if it works internally that everything is configured properly.

(in reply to Sembee)
Post #: 3
RE: RPC over HTTP Problem - 25.Apr.2008 11:33:16 PM   
begineer

 

Posts: 38
Joined: 24.Mar.2008
Status: offline
sambee,

is it related to SP2 for the Exh 2003?

(in reply to colnar)
Post #: 4
RE: RPC over HTTP Problem - 27.Apr.2008 5:35:16 PM   
Sembee

 

Posts: 4093
Joined: 17.Jan.2008
From: Somewhere near London, UK
Status: offline
Has nothing to do with Exchange 2003 SP2. That should be installed anyway.

When you use rpcdiag internally, does that show a HTTPS connection or a TCP connection?

If it shows a HTTPS connection, does it show a valid internet address? If it shows anything .local or a name that doesn't resolve externally then you have a configuration issue.

Normally you can assume that if it works internally it will work externally, but that does depend on whether you are using the correct settings internally. I have seen deployments "work" with mail.domain.local as that is what the certificate is allocated to. It will work on that basis inside, but not outside because that name doesn't resolve.

Simon.

_____________________________

Simon Butler,
Exchange MVP
Blog: http://blog.sembee.co.uk/
Web: http://www.amset.info/
In the UK? Hire me: http://www.sembee.co.uk/
Exchange Resources: http://exbpa.com/

(in reply to begineer)
Post #: 5
RE: RPC over HTTP Problem - 27.Apr.2008 7:34:44 PM   
begineer

 

Posts: 38
Joined: 24.Mar.2008
Status: offline
hi Sambee,

Last few Month RPC in Outlook 2003 is working fine externally or internally. but for Outlook 2007 we need to untick the Fast network and connected via TCP and FQDN reslove as Local Server name but not the exch name.

Currently totally we are unable to connect via Outlook 2003 and 2007 externally. internally as usual we need to untic the fast network and connected via tcp ONLY.


(in reply to Sembee)
Post #: 6
RE: RPC over HTTP Problem - 27.Apr.2008 8:48:03 PM   
consultOz

 

Posts: 926
Joined: 11.Mar.2005
From: Virginia, USA
Status: offline
have a look here please
http://smtp25.blogspot.com/2007/10/rpc-over-http.html

use RPC ping from outside  as follows

rpcping -t ncacn_http -s mail.smtp25.org -o RpcProxy= mail.smtp25.org -P "oozugurlu,smtp25,*" -I "oozugurlu,smtp25,*" -H 1 -u 10 -a connect -F 3 -v 3 -E -R none

The article has a link to  Bill Boswell PDF file, Bill is covering every senario, if you go step by step I am sure you will make it work
this is one of the best document out there.
good luck
oz
 



_____________________________

Regards,
Oz Casey Dedeal
MVP (Exchange)
MCITP (EMA),MCITP (EA), MCITP (SA),
MCSE 2003 M+ S+, MCDST
Security+, Project+ ,Server+
http://smtp25.blogspot.com (Blog)
http://telnet25.wordpress.com (Blog)

(in reply to begineer)
Post #: 7
RE: RPC over HTTP Problem - 29.Apr.2008 1:40:26 AM   
begineer

 

Posts: 38
Joined: 24.Mar.2008
Status: offline
Sambee,

ipls help. after checked your amset.info the Front-End / Back-end Server Configuration <-- where should we configure this? FE or BE?
Also what if we do have virtual for FE and BE? where should the registry input?
also if i do have 2 AD which is Clustering? (once down and once will pick up) should i put both in the registry ?

answer to your question, internally it work as TCP only but not HTTPS. but we are able to use https (OWA) to check mail.

(in reply to consultOz)
Post #: 8
RE: RPC over HTTP Problem - 29.Apr.2008 5:12:32 AM   
Sembee

 

Posts: 4093
Joined: 17.Jan.2008
From: Somewhere near London, UK
Status: offline
If you have a backend frontend scenario then you do not make any registry changes at all. Simply set the relevant options in ESM for each server. If you have tried to make registry changes, remove them, remove the RPC over HTTPS component from add/remove programs and reinstall it. Set the servers back to not a part of a RPC over HTTPS topology and then wait for that change to propagate (about an hour). Then set the option correctly in ESM. DO NOT change the registry. Registry changes are only for single server users.

Simon.

_____________________________

Simon Butler,
Exchange MVP
Blog: http://blog.sembee.co.uk/
Web: http://www.amset.info/
In the UK? Hire me: http://www.sembee.co.uk/
Exchange Resources: http://exbpa.com/

(in reply to begineer)
Post #: 9

Page:   [1] << Older Topic    Newer Topic >>
All Forums >> [Microsoft Exchange 2003] >> General >> RPC over HTTP Problem Page: [1]
Jump to:

New Messages No New Messages
Hot Topic w/ New Messages Hot Topic w/o New Messages
Locked w/ New Messages Locked w/o New Messages
 Post New Thread
 Reply to Message
 Post New Poll
 Submit Vote
 Delete My Own Post
 Delete My Own Thread
 Rate Posts


Follow TechGenix on Twitter