Re: rpc over http connection problem



SSL Cert expired is definitely a problem. You must first sort this out.

When you browse to https://<servername>/rpc, you should be prompted for user
name and password, and then after that you should get something like,

HTTP Error 403.2 - Forbidden: Read access is denied.
Internet Information Services (IIS)

Now, it is important that you don't get any warning or etc. for certificate.
If you do, that means, it will not work.

Also, try Basic Auth instead.

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Also, the use of included script samples are subject to the terms specified
at http://www.microsoft.com/info/cpyright.htm



"Reg" <Reg@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:396BFA8D-89EA-4A6C-A971-A118D289FEEE@xxxxxxxxxxxxxxxx
> HI Jo, Did you ever figure out this problem. I'm having it now and thought
> it
> was because our SSL Cert had expired.
> Any info will be appreciated
>
> "Jo" wrote:
>
>> i read all the post about the argument.. but found no solution for my
>> problem.
>> i have single exch2003sp1 on w2003ent server.
>> i deployed rpc over http. i followed all the tips.
>> edited the registry for the GC in the domain (the server is only exch and
>> isa not dc), edited registry on exch server for port 6001/6002/6004.
>> installed a certificate on the server with the name of the https site.
>> deployed a new client notebook for testing. winxpsp2 office2003
>> configured OL2003 as stated in the documentation and tryed it.
>> imported the root ca of my enterprise in the trusted root certificate and
>> created a computer certificate for the notebook.
>> while inside the LAN the whole works perfectly
>> when i connect through a normal internet connection i have no
>> connectivity:
>> - i'm requested for authentication both for the mail server both for the
>> AD
>> server, but the status keeps on remaining trying connection.
>> In the connection status i have several attempt of connection to the FQDn
>> of
>> both the mail and AD servers, both in HTTPS and --- Conn, but they remain
>> in
>> connecting status no matter what kind of authentication i give them..
>> if i try a send/receive action i get the 0x8004011D exch server not
>> available.
>>
>> i tryed browsing the same address of the rpc proxy server (regularly
>> published on isa2004) and i'm regularly asked for authentication and then
>> go
>> on.
>>
>> checked again all rpc over http configuration and all seems ok.
>>
>> CAN SOMEONE HELP ME PLEASE??.. IT'S URGENT !!
>>


.



Relevant Pages

  • Re: Configuring SBS2003 for OWA and RWW
    ... And make sure certificate will not be ... On the Connection Type page, click Broadband, and then click Next. ... next to Preferred DNS server and next to ... If you are using ISA, please go to ISA management console, and navigate ...
    (microsoft.public.windows.server.sbs)
  • Re: RPCoHTTP always has 4 failures
    ... ON fast networks, connect using HTTP first, then connect using TCP/IP ... Outlook doesn't even prompt me to log in, it just says the server is ... Warning If you use Registry Editor incorrectly, ... It always shows HTTPS as the protocol in the connection ...
    (microsoft.public.exchange.admin)
  • Re: RPC over HTTP
    ... We have already set up Outlook Web Access and purchase a SSL Certificate ... I have used the "outlook.exe /rpcdiag" to see if it uses the HTTP ... firewall through to the exchange server. ...
    (microsoft.public.windows.server.sbs)
  • RE: Outlook RPC over HTTp deosnt work
    ... i have same problem .and try to export certificate to a pfx file .and ... when you try to use RPC over HTTP to connect the Exchange Server. ... we don't have to manually configure RPC over HTTP. ... Make sure you have enabled "Outlook over the Internet" and "Remote Web ...
    (microsoft.public.windows.server.sbs)
  • Re: Outlook RPC over HTTp deosnt work
    ... Certificate, click Install Certificate, and then follow the instructions. ... when you try to use RPC over HTTP to connect the Exchange Server. ... In SBS 2003, we don't have to manually configure RPC over HTTP. ...
    (microsoft.public.windows.server.sbs)