Announcement

Collapse
No announcement yet.

RPC over HTTPS Config problem

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

  • RPC over HTTPS Config problem

    Hi All,

    I'm having a bit of trouble setting up outlook anywhere on Exchange 2003 / Outlook 2007.

    I've set it up ok (I think) and got it running but when I try to connect via the WAN I am asked for my username and password.

    I put in the correct details but the login box keeps coming up.

    I think the problem is something to do with the rpc settings in IIS as I've tried www.testexchangeconnectivity.com and got the attached result.

    Can someone please point me in the right direction!

    Thanks,

    Steev
    Attached Files

  • #2
    Re: RPC over HTTPS Config problem

    You should be prompted for your credentials using RPC over HTTPS, that is expected behaviour. What authentication method do you have configured in Outlook?
    BSc, MCSA: Server 2008, MCSE, MCSA: Messaging, MCTS
    sigpic
    Cruachan's Blog

    Comment


    • #3
      Re: RPC over HTTPS Config problem

      I'm using basic authentication.

      Should the username essentially be the domain logon account (domain\Username)

      Do I have to activate each account for external access?

      Comment


      • #4
        Re: RPC over HTTPS Config problem

        Basic is what it should be set to, and you will need to logon as domain\username. No need to individually activate accounts, you will need to install the Root Certificate on the client machines so that they trust your CA if you are using an internal only CA. Not an issue with verisign etc.

        Daniel's KB articles on the main Petri site are well worth reading for troubleshooting RPC over HTTPS.
        BSc, MCSA: Server 2008, MCSE, MCSA: Messaging, MCTS
        sigpic
        Cruachan's Blog

        Comment


        • #5
          Re: RPC over HTTPS Config problem

          Ok, I've got past that error but now I'm getting...

          Attempting to ping RPC Endpoint 6001 (Exchange Information Store) on server (FQDN)
          Failed to ping Endpoint

          Tell me more about this issue and how to resolve it
          Additional Details

          Do I need to open the port on the firewall?

          Comment


          • #6
            Re: RPC over HTTPS Config problem

            The "ping" is an internal thing, done by the RPC Proxy component. You do not open the port on your firewall.

            The usual reason for that error is that the registry keys are not correct.

            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