• 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 not over HTTPS

Users viewing this topic: none

Logged in as: Guest
  Printable Version
All Forums >> [Microsoft Exchange 2003] >> Installation >> RPC over HTTP not over HTTPS Page: [1]
Login
Message << Older Topic   Newer Topic >>
RPC over HTTP not over HTTPS - 29.Jan.2008 7:51:24 AM   
sidai

 

Posts: 8
Joined: 29.Jan.2008
Status: offline
Hi all!

Atlast after reading hundred manuals online, restudy 70-284 msce book, I got rpc over http to work.

The problem is, it only works with HTTPS. How can I get it to work with http (port 80) and not HTTPS? I have played around with the settings like the authentication, still nothing.

Please help
Post #: 1
RE: RPC over HTTP not over HTTPS - 29.Jan.2008 8:06:29 AM   
ismail.mohammed

 

Posts: 3018
Joined: 9.May2007
From: India
Status: offline
hi,

Do you have any certificate installed like SSL configuration?

(in reply to sidai)
Post #: 2
RE: RPC over HTTP not over HTTPS - 29.Jan.2008 8:18:14 AM   
sidai

 

Posts: 8
Joined: 29.Jan.2008
Status: offline
quote:

ORIGINAL: ismail.mohammed

hi,

Do you have any certificate installed like SSL configuration?


I had a SSL certificate installed. And it worked.

I left some info out, I have an Internal website that must run on HTTPS (SSL), our router automaticly forward all port 443 request to the webserver. The webserver is currently my Rpc over http front-end server aswell.

The thing is that I have an dyndns domain on the webserver, thus the ssl certificate is not going to work from the internet ie. Exchange wants to revert back to Tcp/ip.

(in reply to ismail.mohammed)
Post #: 3
RE: RPC over HTTP not over HTTPS - 29.Jan.2008 8:23:35 AM   
ismail.mohammed

 

Posts: 3018
Joined: 9.May2007
From: India
Status: offline
hi,

Could please explain me your current topology.

(in reply to sidai)
Post #: 4
RE: RPC over HTTP not over HTTPS - 29.Jan.2008 8:30:23 AM   
sidai

 

Posts: 8
Joined: 29.Jan.2008
Status: offline
quote:

ORIGINAL: ismail.mohammed

hi,

Could please explain me your current topology.


Ok here it goes:

Mind my English (am afrikaans)

I have an Linux proxy server ( not mine) that forwards traffic to the right destination.( 1 adsl line, 1 sdsl line to university). Very basic.

behind that I have an PDC,BDC and a Webserver, my BDC is an Exchange Backend server, the Webserver is an Exchange front-end srever.

The Pdc runs dyndns client, and all ports are forwarded from the router to the proxy. Port 443 and 80 is forwarded to the webserver from the proxy.

Hope that was ok.

(in reply to ismail.mohammed)
Post #: 5
RE: RPC over HTTP not over HTTPS - 29.Jan.2008 9:30:32 AM   
Sembee

 

Posts: 4093
Joined: 17.Jan.2008
From: Somewhere near London, UK
Status: offline
Simple answer is that RPC over HTTP cannot be run over HTTP only. It is designed to run over HTTPS only. It is also hard coded to use port 443, therefore if you have something else on port 443 then you will either need to change it, get another IP address or not use the feature at all.

Furthermore this feature works best with a commercial SSL certificate. Trying to use a home grown SSL certificate will cause a lot of headache.

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 sidai)
Post #: 6
RE: RPC over HTTP not over HTTPS - 29.Jan.2008 9:35:17 AM   
sidai

 

Posts: 8
Joined: 29.Jan.2008
Status: offline
quote:

ORIGINAL: Sembee

Simple answer is that RPC over HTTP cannot be run over HTTP only. It is designed to run over HTTPS only. It is also hard coded to use port 443, therefore if you have something else on port 443 then you will either need to change it, get another IP address or not use the feature at all.

Furthermore this feature works best with a commercial SSL certificate. Trying to use a home grown SSL certificate will cause a lot of headache.

Simon.


Hehe. had an idea someone is gonna give an awnser like that.

Thanks for the reply.

PS. I only have Intranet comodo SSL cert, and made and cert with CA server, both worked fine.

Just funny that they made a option that you can choose rpc over HTTP (port 80).

Thanks

(in reply to Sembee)
Post #: 7
RE: RPC over HTTP not over HTTPS - 29.Jan.2008 9:58:19 AM   
paresh_md

 

Posts: 129
Joined: 12.Dec.2007
From: United Kingdom
Status: offline
Hi,

The option is given as you can setup for HTTP. I've done this in my lab and production and it works fine.

http://technet.microsoft.com/en-us/library/aa998950.aspx

See the link above.

PD

_____________________________

Microsoft PSS - X Team Leader - Messaging
Systems

Have you ever run ExBPA on your Exchange server ? (Exchange Best Practises Analyzer)
Download from ExBPA.com

(in reply to sidai)
Post #: 8
RE: RPC over HTTP not over HTTPS - 29.Jan.2008 10:24:08 AM   
Sembee

 

Posts: 4093
Joined: 17.Jan.2008
From: Somewhere near London, UK
Status: offline
The methods for getting RPC over HTTP to work without an SSL certificate are unsupported and unreliable. It is not something that I have ever tried and wouldn't want to. I don't want domain credentials going across the internet in the clear.
There is some functionality in the feature for using HTTP only, for example when SSL offloading is used, such as with an ISA server.

The feature is badly named - it should have been called RPC over HTTPS, but now they call it Outlook Anywhere.

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 paresh_md)
Post #: 9
RE: RPC over HTTP not over HTTPS - 29.Jan.2008 12:41:43 PM   
sidai

 

Posts: 8
Joined: 29.Jan.2008
Status: offline
quote:

ORIGINAL: Sembee

The methods for getting RPC over HTTP to work without an SSL certificate are unsupported and unreliable. It is not something that I have ever tried and wouldn't want to. I don't want domain credentials going across the internet in the clear.
There is some functionality in the feature for using HTTP only, for example when SSL offloading is used, such as with an ISA server.

The feature is badly named - it should have been called RPC over HTTPS, but now they call it Outlook Anywhere.

Simon.


Fair enough. Do someone atleast know if its possible so that Exchange can comunicate over a different port, like 442, also ssl?

SSL certificate is VERY expensive, atleast for us.. (R6.5 * 139$ = ALOT)

(in reply to Sembee)
Post #: 10
RE: RPC over HTTP not over HTTPS - 29.Jan.2008 2:04:00 PM   
Sembee

 

Posts: 4093
Joined: 17.Jan.2008
From: Somewhere near London, UK
Status: offline
The feature is hard coded to port 443. Part of the point of the feature is to get it to connect over the standard port.

I don't know where you are looking for SSL certificates, but you can get SSL certificates for US$20/year from places such as GoDaddy (http://www.certificatesforexchange.com/) or RapidSSL for US$60 a year (less if you look for a reseller) (http://www.rapidssl.com/)

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 sidai)
Post #: 11

Page:   [1] << Older Topic    Newer Topic >>
All Forums >> [Microsoft Exchange 2003] >> Installation >> RPC over HTTP not over HTTPS 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