Announcement

Collapse
No announcement yet.

RPC-HTTP on 2k3 AD domain with a 2k dc member server

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

  • RPC-HTTP on 2k3 AD domain with a 2k dc member server

    Setup: Single Exchange 2k3 on Srvr2k3 was added to an existing 2k AD domain. Added an additional 2k3 server to act as DC/GC and AD integrated DNS. Demoted the 2k server from GC status, but kept it as a DC for now. Will this 2k DC on what should now be a 2k3 AD domain, interfere with RPC over HTTP. In Daniel's tute (http://www.petri.com/configure_rpc_o...gle_server.htm) the server reqs are as follows:
    RPC over HTTP/S requires Windows Server 2003 and Exchange Server 2003. RPC over HTTP/S also requires Windows Server 2003 in a Global Catalog role.
    Is there some obscure means by which a 2k dc is meddling with my attempts to get RPC/HTTP to work? Is my AD Domain not entirely a 2k3 domain as long as I have a 2k DC (2k3 dc/gc owns all FSMOs)? Thanks for any help.

  • #2
    There is nothing to do with w2k server

    What are the requirements for RPC over HTTPS?
    And
    How do I setup RPC over HTTPS?

    Here:
    http://www.itap.purdue.edu/email/exc..._RPCconfig.cfm


    Server Requirements

    Windows 2003 Server
    Exchange 2003 Server
    or Small Business Server 2003 with Exchange 2003 installed.
    SSL Certificate (use SelfSSL for testing or get a trial SSL fromRapidSSL)

    Client Requirements

    Outlook 2003
    Windows XP SP1 with RPC hotfix (get here) or Windows XP SP2
    If you are using SelfSSL, then install the Certificate on your test machine.


    http://www.amset.info/exchange/rpc-http-tips.asp


    I hope it help
    MCSE w2k
    MCSA w2k - MCSA w2k MESSAGING
    MCDBA SQL2k

    Comment


    • #3
      Originally posted by windux
      There is nothing to do with w2k server
      Yes there is. Check to see if the Exchange 2003 server(s) aren't still configured to use the W2K server as their GC (it's on the properties of each Exchange server object in ESM).

      Also, are you getting any errors? If so, what are they?

      Last but not least - is RPC over HTTP working inside the LAN?
      Cheers,

      Daniel Petri
      Microsoft Most Valuable Professional - Active Directory Directory Services
      MCSA/E, MCTS, MCITP, MCT

      Comment


      • #4
        Danielp, he already take GC from w2k srv!

        Exchange can not still configured to use the W2K server as their GC because that one no more exists.

        That was i mean to say.
        MCSE w2k
        MCSA w2k - MCSA w2k MESSAGING
        MCDBA SQL2k

        Comment


        • #5
          I thank you windux for your insight, however we're talking about troubleshooting, not about normal cases. There are instances where something in the Exchange DC+GC discovery goes wrong, and the servers continue to look for non-existing DCs.
          Cheers,

          Daniel Petri
          Microsoft Most Valuable Professional - Active Directory Directory Services
          MCSA/E, MCTS, MCITP, MCT

          Comment


          • #6
            OK, thanks for the responses. It appears i have more to investigate before I bring this to the forum. I attempted to setup RPC/HTTP for external users without testing it on the LAN for the following, possibly foolish, reason: I have two virtual http servers. My default is for external connectivity, and the internal is for LAN usage. When installing RPC, the virtual directories were created under my default "external" http server. I wasn't sure If I should make a copy of those in the internal virtual server, or ideally, create yet a third virtual server for internal rpc use only. Additionaly, I created my own certificate, which all client computers absolutely refuse to accept as root authority(even doing it through mmc snap-in). So...the more the smoke clears, the further the horizon appears. Thanks for any help. I'll notify you as to the DC issue once I get to a point where i'm confident that it is the singular remaining obstacle.

            Comment


            • #7
              Update

              For anybody who may find this thread...

              I ended up demoting the 2k dc to a member server, removed it from the domain to sever all ties, then added it back on as a member server for a NAS role. I finally got rpc/https to work, and that only after a quasi-accidental reboot. I have no evidence to offer as to whether or not the 2k dc was an obstacle to running rpc/http.

              Comment

              Working...
              X