Re: Enable RPC over http

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

With all my clients the cert matches the FQDN that the A record points to
for your server external IP address. You mentioned MX record and most likely
it is using the same FQDN?

"Johnny" <jstraumann@xxxxxxxxxxx> wrote in message
news:%23chQ7CosHHA.1184@xxxxxxxxxxxxxxxxxxxxxxx
LOL, 2 answers...which one is correct?? :) Well I tried
email.ourdoamin.com, I'll try ourdomain.com and see what happens...

--
John.

http://mscrmguy.blogspot.com/

"Stacemen" <staceman3@xxxxxxxxxxx> wrote in message
news:1182264235.449455.28350@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Jun 19, 9:34 am, "Johnny" <jstraum...@xxxxxxxxxxx> wrote:
Hi:

Ok so say the domain is: ourdomain.com, and the MX record points at
email.ourdomain.com...

What name do I use to generate the certificate? ourdomain.com or
email.ourdomain.com?

--
John.

http://mscrmguy.blogspot.com/

"Stacemen" <stacem...@xxxxxxxxxxx> wrote in message

news:1182262985.990053.233680@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx



On Jun 19, 7:03 am, "Johnny" <jstraum...@xxxxxxxxxxx> wrote:
Hi all:

As I continue my SBS journey for my friend (he is regretting asking
me
for
help :), this is an SBS server with 1 NIC connecting to the internet
via
a
router, and Exchange, RWW, and OWA are working fine. The last thing I
need
to do is enable RPC over HTTP, so I connected to RWW and followed the
steps
generated by SBS *exactly*. However, when I get to step 7 of the
instructions under "Configure the computer for RPC over HTTP" I do
not
see
that "Exchange over the internet" option on the connection tab:

7. On the Connection tab, under Exchange over the Internet, select
Connect
to my Exchange mailbox using HTTP, and then click Exchange Proxy
Settings.
The Exchange Proxy Settings dialog box appears.

I rant through the steps once previously, and I did have that setting
and
set it to the URL as directed, email.ourdomain.com (which is what DNS
points
to), but I was unable to successfully connect.

I have been searching and searching but have been unable to find a
good
info
source as to how to start troubleshooting this. Can anyone offer some
advice?

Thanks all.

--
John.

http://mscrmguy.blogspot.com/

Make sure that domain information is what was specified when the
ceritificate was created using the CEICW wizard..they must match
EXACTLY.- Hide quoted text -

- Show quoted text -

ourdomain.com




.

Relevant Pages

  • Re: RPC over HTTP - Solution?!
    ... I followed a bunch of different instructions on how to make a Single Server ... RPC HTTP work, ... I have an Exchange Server 2003 Ent. ... > when on the LAN and you run outlook /rpcdiag, are you connecting via HTTP ...
    (microsoft.public.exchange.connectivity)
  • Re: RPC over HTTP - Solution?!
    ... I followed a bunch of different instructions on how to make a Single Server ... RPC HTTP work, ... I have an Exchange Server 2003 Ent. ... > when on the LAN and you run outlook /rpcdiag, are you connecting via HTTP ...
    (microsoft.public.exchange2000.connectivity)
  • Re: RPC over HTTP - Solution?!
    ... I followed a bunch of different instructions on how to make a Single Server ... RPC HTTP work, ... I have an Exchange Server 2003 Ent. ... > when on the LAN and you run outlook /rpcdiag, are you connecting via HTTP ...
    (microsoft.public.exchange2000.protocols)
  • Re: Outlook http access
    ... Are you able to connect Outlook to Exchange using RPC over HTTPS and you ... connecting through a firewall? ... > required HTTP methods" ...
    (microsoft.public.exchange.clients)
  • Re: owa
    ... OWA is installed and enabled by default in Exchange 2000 and 2003. ... just need to connect to the server using http or https and the server's ... Getting the FQDN to work will require the name to be registered in DNS. ...
    (microsoft.public.exchange.admin)