Re: RPC over HTTP

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hi Jon,

Try this http://www.exchange-forums.com/phpBB2/viewtopic.php?t=4. I've used
these instructions to configure RPC over HTTP on a single server many times.

Will
http://www.exchange-forums.com

"Jon Rowlan" <jon.rowlan@xxxxxxxx> wrote in message
news:uqCGQ%23ycFHA.796@xxxxxxxxxxxxxxxxxxxxxxx
> Matt, I really appreciate that - its exactly what I was after on the certs
> side, I suspected that this was how the certs worked.
>
> The problem that I now have seems to be a bit of a paradox ...
>
> a) Exchange Server 2003 enterprise requires the Recipient Update service
> to be run (we only have one Exchange server) on the Exchange server.
>
> b) This means that it cannot be a Front End server
>
> c) RPC over HTTP does not allow me to configure the server as a back end
> server as there are no front end servers
>
> d) I cannot configure the server as a front end server because of a)
>
>
> Am I in an impossible position?
>
> jON
>
> "Matt Cosand [MSFT]" <mathewco@xxxxxxxxxxxxxxxxxxxx> wrote in message
> news:270C501A-900F-49D6-9CA1-DDA678C541FD@xxxxxxxxxxxxxxxx
>> Jon,
>>
>> Have you seen KB 833401
>> [http://support.microsoft.com/default.aspx?scid=kb;en-us;833401]? It
>> details
>> how to configure RPC over HTTP on a single server.
>>
>> Self-signed and third party SSL certificates are essentially the same
>> thing,
>> and provide the same encryption across the connection. The difference has
>> to
>> do with the verification of the certificate itself. The certificate
>> essentially says "I am who I say I am, as proven by this third party (the
>> issuer)". If you trust the third party (VeriSign, Thwate, or yourself),
>> then
>> you can trust that the server you got when you typed in a URL is really
>> the
>> server you intended to connect to. The OWA prompt is simply saying "I
>> can't
>> prove that this is the OWA server you're looking for. Do you believe that
>> it
>> is?"
>>
>> Self-signed certificates should be more than sufficient when you control
>> both the server and clients. I believe they can even be more secure, if
>> you
>> trust yourself more than a third party company such as VeriSign or
>> Thwate.
>> The above article has a link to KB 297681, which explains how to
>> configure
>> the client machines to trust a certificate that you've generated.
>>
>> Let me know if this helps,
>>
>> Matt Cosand
>> Microsoft Exchange
>>
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> Use of included script samples are subject to the terms specified at
>> http://www.microsoft.com/info/cpyright.htm
>>
>>
>> "Jon Rowlan" wrote:
>>
>>> I am trying to get RPC over http working in my Outlook/Exchange 2003
>>> server
>>> environment and I am hitting two brick walls.
>>>
>>> a) I only have one server, this is neither a back end or front end
>>> server -
>>> the documentation does not suggest whether I need to make my server a
>>> front
>>> end server but, having applied SP1 for Exchange, I cannot seem to
>>> configure
>>> RPC over HTTP from the tab without my server being one or other of back
>>> end
>>> or front end. If I make it a front end server is this going to cause me
>>> any
>>> problems elsewhere?
>>>
>>> b) I need to have a certificate to enable SSL. An SBS server that I have
>>> recently installed seems to have automatically created a cert. Now I
>>> thought
>>> that to get this job done properly I would have to get a proper cert
>>> from an
>>> authority and install it on my server. If SBS install creates one itself
>>> during the install process, this does not seem to be the case. Also, I
>>> can
>>> see how this can be considered secure??? When I go to the OWA server I
>>> am
>>> prompted that there is a cert that I have not trusted but if I click on
>>> the
>>> YES/OK button it just lets me view the site anyway. I really cannot get
>>> my
>>> head around where this is a secure and trusted connection. There are
>>> literally books and books of articles explaining it all but I could
>>> really
>>> do with a "Certifcate management for dummies" ... I just want to secure
>>> my
>>> OWA and Outlook 2003 so that only my staff can view, is there a simple
>>> article that anyone knows of that will help me to determine my core
>>> requirements?
>>>
>>> I would really appreciate some pointers here ...
>>>
>>> thanks all,
>>>
>>> jON
>>>
>>>
>>>
>
>


.

Quantcast