Announcement

Collapse
No announcement yet.

Multiple Domains One Exchange 2003 Server & RPC over HTTPs

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

  • Multiple Domains One Exchange 2003 Server & RPC over HTTPs

    I have been hosting multiple domains on my single Exchange 2003 server for quite some time now. That is working fine, even with OWA. Now I would like to enable RPC over HTTPs for all of my hosted domains. I followed Daniel's instructions to setup RPC over HTTPs and it works great for my main domain. How do I get the other domains to work? Any help would be greatly appreciated. Trying to get this project done ASAP.

  • #2
    Re: Multiple Domains One Exchange 2003 Server & RPC over HTTPs

    There is nothing different to do for the other domains. You simply use the same information for everyone.

    If you want to do something like have a unique URL for each domain, then you will need an SSL certificate for every domain, a separate IP address and separate virtual server. That is a complete waste, I don't think any hosters do that - it is all routed through generic host names.

    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


    • #3
      Re: Multiple Domains One Exchange 2003 Server & RPC over HTTPs

      When I try that....I am getting the message "The name cannot be matched to a name in the address list." I am using unique UPNs for all of the domains. What am I missing? Thanks.

      Comment


      • #4
        Re: Multiple Domains One Exchange 2003 Server & RPC over HTTPs

        Do all users have an email address in the default domain?
        It doesn't have to be the default email address, but should be present.
        Have you attempted to customise the RPC virtual directory in any way?

        If you use domain\username does it work correctly?

        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


        • #5
          Re: Multiple Domains One Exchange 2003 Server & RPC over HTTPs

          I have tried that format and I get the same result. I do have a separate OUs inside of AD. As far as Exchange goes, I am using separate Storage Groups for each domain as well. Could this be causing my problem? Any suggestions?

          The users don't have an email address in the default domain.

          I haven't done anything to the RPC virtual directory outside of what is in the tutorial on this site.

          Very strange, but if I access OWA like this https://mail.mydomain.com/exchange and login with one of the hosted users [email protected], I can access their mailbox all day long.

          But when I try and do the same thing using Outlook and RPC over HTTPs, it says the name cannot be matched. What am I missing here? This makes no sense to me.
          Last edited by ctconline; 13th June 2007, 03:55. Reason: *Update*

          Comment


          • #6
            Re: Multiple Domains One Exchange 2003 Server & RPC over HTTPs

            Should be no difference in having the users spread out over storage groups etc. What you are doing is what hosters do all the time.

            Can you convert an account that doesn't work from regular Outlook connection (TCP/IP) to RPC over HTTPS connection? To do that, configure Outlook as normal then ADD the additional settings, leaving the original settings in place.

            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


            • #7
              Re: Multiple Domains One Exchange 2003 Server & RPC over HTTPs

              I'm not following you on this. Do I have any accounts that don't work in Outlook? I haven't even tried that. My guess would be that if I connect to my server from my LAN and configure one of those accounts that it is in fact going to work.

              Comment


              • #8
                Re: Multiple Domains One Exchange 2003 Server & RPC over HTTPs

                If you can connect to those accounts on your LAN using TCP/IP connections then that is fine. What I am then suggesting is after confirming a connection is successful on TCP/IP the connection is converted to RPC over HTTPS. If that fails, then it gives an indication of where the problem is.
                If it works on your LAN using HTTPS then the problem is caused by some difference between external and internal clients.

                Obviously if all testing has been carried out internally to date, then the above is a null point.

                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


                • #9
                  Re: Multiple Domains One Exchange 2003 Server & RPC over HTTPs

                  Okay. I solved my problem, but of course I introduced a new problem. When I was provisioning Exchange for multiple domains, I wanted each company to have their own GAL and not be able to see the other companies GALs. So, in following a tutorial, I deleted the Default GAL. This obviously caused this problem. It doesn't cause a problem when using OWA, but now that I'm implementing RPC over HTTPs, that Default GAL has to be there.

                  So, my new problem is that I don't know how to keep the companies GALs separate from each other.

                  Any help on that?

                  Comment


                  • #10
                    Re: Multiple Domains One Exchange 2003 Server & RPC over HTTPs

                    Why did you delete the default GAL?
                    The usual methods involve blocking access to the default GAL, not deleting it.

                    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


                    • #11
                      Re: Multiple Domains One Exchange 2003 Server & RPC over HTTPs

                      I was just following a tutorial from msexchange.org. Now I have another huge problem!

                      I was trying to adjust the permissions of the All Global Address Lists container and have managed to lock myself out. (I'm such an idiot)

                      I have researched like crazy and everything I have tried is not allowing me to get that container back. What are the options when DSACLS.exe doesn't work? When I run DSACLS.exe on that particular object, I get "parameter is incorrect" EVERY time.

                      I know I am using the correct syntax because I can run it on other objects with no problem.

                      The other weird thing is that using DSACLS.exe, I can see the perms of children objects of All Global Address Lists. So, the changes I made aren't affecting the child objects.

                      Does anyone know how I can fix this?

                      Comment

                      Working...
                      X