Announcement

Collapse
No announcement yet.

Hello

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

  • Hello

    Dear All,

    This is my first post.I like this site forum and decided to join you guys to take advantage of manu features.

    I have a problem with the Exchange server RPC over HTTP.Let me explain clearly.

    I have exchange server with the MX record registered with mail.mymail.com
    and the server name is mysrv.I have installed and configured the exchange server with RPC over HTTP (it is HTTP only not the HTTPS).The AD is running on the same server.I also have PIX firewall installed in my network.

    The RPC over HTTP is working fine with the LAN.But when i try from my home it does not work.I am using different computer at home.

    Please help me.
    Last edited by sskumar_1971; 16th June 2006, 07:36. Reason: Change of Title

  • #2
    Re: Hello

    Welcome to our forums. In order to help you will need to provide a more detailed description of your setup.

    In the meantime, does the remote computer belong to the same domain? Or is it a stand alone computer?
    Cheers,

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

    Comment


    • #3
      Re: Hello

      O.K Let me explain the setup to you..

      ADS 2003 standard with Exchange 2003 standard.Exchange is setup do RPC over HTTP (HTTP only).The PIX firewall is installed after the router so it is the gateway for the local LAN.The server local IP is NATed in the PIX firewall for port 80 & 25.

      The RPC Over HTTP works fine in a LAN w/o any problem as long as the computer is part of that domain.I tried w/o joining to the domain it was keep on asking me the user name and pasword and it never succeed.

      The laptop is set for RPC over HTTP in a LAN and it took the local server name as mysrv.mymail.com.But my DNS is registred as mail.mymail.com.I am trying to connect from home it is nnot connecting either with the names.I can ping the registred name.

      Hope this information is clear.

      Comment


      • #4
        Re: Hello

        First - are you sure that it is working on the LAN?

        Close Outlook completely, then click start, run and type

        outlook.exe /rpcdiag

        Outlook will start with an extra box. That box shows the connection. If it says the protocol as TCP/IP then the feature isn't working.

        Second - the feature should really be called RPC over HTTPS as it is designed to run over HTTPS only. I wouldn't dream of running it over HTTP as that is unencrypted.
        Any reason you don't want to run it over https? Get a cheap SSL certificate from RapidSSL and you will be working in no time.
        You want to limit the traffic on port 80 as much as possible - I don't have any http traffic coming in to networks I run - it is all https only.

        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: Hello

          sskumar_1971, my apologies for jumping into your thread.

          Simon, is it necessary to have a "real" certificate or can one created on your own certificate server suffice?
          1 1 was a racehorse.
          2 2 was 1 2.
          1 1 1 1 race 1 day,
          2 2 1 1 2

          Comment


          • #6
            Re: Hello

            I always deploy the feature with a commercial certificate. I have very little success using home grown certificates and don't really want the additional overhead.

            The same certificate can then be used for OWA, OMA, indeed anything on the same server. Something I do for a lot of clients is setup a secure Extranet, which has internal information that can be accessed from outside.

            What you need to avoid is the popup security warnings. Internet Explorer 7.0 blocks access to sites with a non-trusted certificate, so if you are deploying OWA to the users and they are likely to use other machines that are under your control then you should be using a commercial certificate. Saving $70 just isn't worth it (that is less than an hour of my time commercially - and it will take much longer to run around all of the machines updating the certificate).

            I blogged about why you shouldn't use home grown certificates: http://www.sembee.co.uk/archive/2006/03/05/5.aspx

            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
              Hello

              Hi, All


              This is stephen here and i have problem with my server, I am having terminal server and when i print from from Excel it say Please install the printer where printer is already installed and it can be seen inthe printer dialog box, It print from word and pdf can u Please help????


              Help would apprecited.thanks in advance.

              if want reply send reply on [email protected] or [email protected]

              Note: How to post new message

              Comment


              • #8
                Re: Hello

                Thanks Simon (and sskumar_1971)

                stephenbarboza, this is the Exchange Forum. Your problem is not an Exchange one so this is the WRONG forum. You have also double posted the same question in Office XP/2003 General Issues Forum. Double posting is NOT allowed. I also think that you really should have posted your question in the Terminal Services Forum. I'll see if I can get it moved to there. Better chance of getting an answer about a TS problem.
                1 1 was a racehorse.
                2 2 was 1 2.
                1 1 1 1 race 1 day,
                2 2 1 1 2

                Comment


                • #9
                  Re: Hello

                  I finally got it working.it seems RPC over HTTP is not success out side the office.So i installed a local Certificate server and configured the IIS.It is working fine with out any problem.

                  Thanks for all your effort.

                  For the RPC Over HTTP(S) Beginners please follow the following steps which made me successful.Please follow the link for detailled configuration.

                  I exactly follow the below steps and i could make it working..Hope this is useful to you guys

                  1.Configure the server for RPC

                  http://www.petri.com/configure_rpc_o...gle_server.htm

                  2.Install CA in the domain.

                  http://www.petri.com/install_windows_server_2003_ca.htm

                  3.Configure the IIS for SSL

                  http://www.petri.com/configure_ssl_o...e_with_iis.htm

                  4.Install the certificate from your CA server

                  http://www.petri.com/obtain_digital_..._online_ca.htm

                  5.Configure outlook 2003 for RPC over HTTPS

                  http://www.petri.com/configure_outlo..._over_http.htm

                  6.Test the RPC over HTTPS connection

                  http://www.petri.com/testing_rpc_ove...connection.htm

                  Comment


                  • #10
                    Re: Hello

                    Well done and thanks for posting back with the steps you took. It is appreciated and I sure will be helpful to someone in the future.
                    1 1 was a racehorse.
                    2 2 was 1 2.
                    1 1 1 1 race 1 day,
                    2 2 1 1 2

                    Comment

                    Working...
                    X