Re: RPC over HTTP only works with remote computers attached to the domain

From: Lanwench [MVP - Exchange] (lanwench_at_heybuddy.donotsendme.unsolicitedmail.atyahoo.com)
Date: 10/09/04

  • Next message: Lee: "Re: Clean Database Corrupt???"
    Date: Fri, 8 Oct 2004 20:43:52 -0400
    
    

    Tim wrote:
    > I have an interesting problem with RPC over HTTP. It works but only
    > for computers that have been joined to the domain. These computers
    > when connected from home without a VPN connection can use RPC over
    > HTTP but if I take that same computer and remove it from the domain
    > and use the exact same Outlook profile settings RPC over HTTP will
    > fail.

    I'm not an RPC/HTTP expert, but did you change the Exchange server service
    (advanced properties) to specify "logon network security" = none? So the
    user gets prompted for credentials?
    >
    >
    >
    > I have a 3 server configuration:
    >
    >
    >
    > Test-ISA-01: ISA 2000 SP2 Server
    >
    >
    >
    > Test-MSG-01: W2003 STD running Exchange 2003 SP1 (also GC,
    > Enterprise Certificate Server, Windows SharePoint Services, Internet
    > Authentication services)
    >
    >
    >
    > Test-DC-01: W2003 Std also acting as a GC
    >
    >
    >
    > Internal Domain Name is: Test.local
    >
    > External Domain Name is: Test.org
    >
    >
    >
    > I used enterprise certificate server to create a certificate that is
    > installed in IIS on the Exchange 2003 server with a name of
    > owa.Test.org.
    >
    >
    >
    > I have installed the certificate on the ISA server
    >
    >
    >
    > OWA works correctly with the https://owa.test.org url although a
    > certificate warning comes up saying that certificate has been issue
    > by a company you have not chosen to trust. If the user clicks Yes
    > then they access OWA successfully.
    >
    >
    >
    > When configuring the outlook profile the Exchange server name is
    > Test-MSG-01.Test.local while the proxy name is owa.test.org and the
    > setting to mutually authenticate is msstd:owa.test.org.
    >
    >
    >
    > As I've mentioned these settings for RPC over HTTP work correctly for
    > Outlook clients whose computers are attached to the domain but not
    > with computers that are not attached to the domain. This leads me to
    > believe it might be a certificate issue
    >
    >
    >
    > Any help would be appreciated. Tim


  • Next message: Lee: "Re: Clean Database Corrupt???"

    Relevant Pages

    • 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)
    • 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)
    • RE: Outlook RPC over HTTp deosnt work
      ... 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 ... popup warning about the certificate. ...
      (microsoft.public.windows.server.sbs)