Announcement

Collapse
No announcement yet.

Setting up RPC over HTTP (NO S) on an Exchange 2003 standalone server

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

  • Setting up RPC over HTTP (NO S) on an Exchange 2003 standalone server

    I setup following the instructions given to setup rpc over http without ssl on a single server. But, i cant login, it keeps asking for the username password again and again.

    My setup is as under

    I have two servers:

    1.Windows 2003 server as DC
    2. Exchange 2003 server on a member server running windows 2003 again.

    PIX515e port 80 configured

    I am a little confused here. In this kind of a scenario, should i configure the rpc over http following the same methods that are described under the article - Configure RPC over HTTP/S on a single exchange server, as in this case the exchange server is single but DC is running on a separate server.

    Awaiting your valuable comments

    Thanks

    amit bhatta
    india

  • #2
    Re: Setting up RPC over HTTP (NO S) on an Exchange 2003 standalone server

    Why have you decided to not use the S part of the name?
    1 1 was a racehorse.
    2 2 was 1 2.
    1 1 1 1 race 1 day,
    2 2 1 1 2

    Comment


    • #3
      Re: Setting up RPC over HTTP (NO S) on an Exchange 2003 standalone server

      coz i dont have a CA server and if i use the built in 2003 certificate server then everytime it notifies the certificate cant be verified

      so i thot its risky but still let me check if this works

      with or without ssl i will decide later on

      thanks

      Comment


      • #4
        Re: Setting up RPC over HTTP (NO S) on an Exchange 2003 standalone server

        Simon, your Certificate speech is needed yet again.
        1 1 was a racehorse.
        2 2 was 1 2.
        1 1 1 1 race 1 day,
        2 2 1 1 2

        Comment


        • #5
          Re: Setting up RPC over HTTP (NO S) on an Exchange 2003 standalone server

          I'm not Simon, but here goes

          Buy a cheap certificate from e.g. godaddy.com. It will cost about $40 for 2 years.
          It makes your life SO much easier and increases security

          Normally my advice costs far more than the certificate would, so you're getting a double bonus here
          Tom Jones
          MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
          PhD, MSc, FIAP, MIITT
          IT Trainer / Consultant
          Ossian Ltd
          Scotland

          ** Remember to give credit where credit is due and leave reputation points where appropriate **

          Comment


          • #6
            Re: Setting up RPC over HTTP (NO S) on an Exchange 2003 standalone server

            So you guys are saying that RPC over HTTP does not work???

            It has to be RPC over HTTPS. In that case, i can ever try the built in CA of windows 2003. But my question is why it does not work without the SSL.

            Comment


            • #7
              Re: Setting up RPC over HTTP (NO S) on an Exchange 2003 standalone server

              My certificate speech?
              Which one will that be?

              This one?
              http://www.sembee.co.uk/archive/2006/03/05/9.aspx

              RPC over HTTPS pretty much requires an SSL certificate. There are some hacks around to get it to work without, but then you have zero security. Your usernames and passwords are going across in the clear.
              Plus I have a poor track record in getting RPC over HTTPS to work on home grown SSL certificates.

              And why bother when you can get an SSL certificate for US$20. The same certificate will protect RPC over HTTPS, OWA, OMA, Exchange ActiveSync.

              Couple of suppliers to choose from.
              Go Daddy as already mentioned: http://www.certificatesforexchange.com/
              RapidSSL (Geotrust) http://www.rapidSSL.com/ - not trusted by Windows Mobile but easily imported
              InstantSSL http://www.instantssl.com/ - watch that they issue from the correct root if Windows Mobile support is required.

              RapidSSL also do a 30 day trial certificate that is trusted, which is good if you want to play around with the procedure to see how it works.

              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