Announcement

Collapse
No announcement yet.

RPC over HTTPS and Public Folder problems

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • RPC over HTTPS and Public Folder problems

    Hi all,

    I am having a problem with my RPC over HTTPs setup.

    We have 3 backend servers (no frontend servers). One of the Backend servers is configured as the RPC-Proxy and an RPC backend server. This works fine. I can connect to it from home and send / receive mail etc.

    There are NO public folder replicas held on this server, all of our public folders are held on a seprate box. We have enabled this as an RPC-HTTPS backend, but whenever you try and open any public folders form Outlook from the internet, Outlook just hangs.

    If you view the Connection Status, the client is trying to connect to all of our backend servers in turn and failing...

    How do i get my RPC/HTTPS client to connect to my Public Folder Server only and use an HTTPS connection?
    It has a Certificate installed on it and public fodlers are accessible when you use OWA...

    Any info would be much appreciated,

    Cheers

    Jonathan
    MCSA/MCSE 2000
    MCSA/MCSE 2003
    CCNA

    I love pies.

  • #2
    Re: RPC over HTTPS and Public Folder problems

    Hi All,

    just to update this incase anyone is interested.

    I have uncovered further information that seems to point towards having to enable ALL backend servers as RPC/HTTPS proxies when not using a Frontend.

    I am going to follow the documented steps to create an RPC proxy on a backend server and enable our public folder server for this... I am hoping that outlook will the be able to successfully establish a connection to it and bring back the public folders to the user

    I originally thought that only one RPC proxy was necessary, hence i have only configured it on the backend mailbox server.

    Cheers

    Jonathan
    MCSA/MCSE 2000
    MCSA/MCSE 2003
    CCNA

    I love pies.

    Comment


    • #3
      Re: RPC over HTTPS and Public Folder problems

      If you have multiple backend servers then I am very surprised that you do not have a frontend server. Once you get over a single Exchange server they are almost mandatory. Otherwise users have to know which server their mailbox is located on, all servers have to be exposed to the internet etc. A frontend server will act as the proxy for that traffic. Backend servers will not proxy to another server, they will simply try to redirect the traffic.

      Simon.
      --
      Simon Butler
      Exchange MVP

      Blog: http://blog.sembee.co.uk/
      More Exchange Content: http://exchange.sembee.info/
      Exchange Resources List: http://exbpa.com/
      In the UK? Hire me: http://www.sembee.co.uk/

      Sembee is a registered trademark, used here with permission.

      Comment

      Working...
      X