Announcement

Collapse
No announcement yet.

outlook 2003 Exchange accounts on LAN without rpc/https

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

  • outlook 2003 Exchange accounts on LAN without rpc/https

    I think I am missing something fundamental here. I have scoured the net for references to this and have come up with nothing...

    How do I set up (server side) for "Microsoft Exchange Server" accounts through Outlook 2003 without having to go the RPC/HTTPS route. I just want my lan computers to use the shared calendars etc. without the unecessary security. Is this possible? I already have rpc/https working for remote clients. Closest I can get is IMAP, but it doesn't support anything but shared messages. Am I out of my mind here? Anybody point me in the right direction? Thanks.

  • #2
    The mailboxes are already setup on the server.

    In outlook create a new profile, and when selecting which account type (where you are selecting IMAP), choose "Microsoft Exchange Server" instead, then type your servername and username.

    and that's it.

    topper
    * Shamelessly mentioning "Don't forget to add reputation!"

    Comment


    • #3
      OK, thanks for the reply.

      Does it require a virtual server? What protocol is being used (just rpc over tcp?)... where can I find documentation on this so I can begin to troubleshoot? I have two virtual http servers. One for external connectivity within which the virtual rpc directory was created. This works fine for external access. The second http server is used for internal owa. Do I need to adjust this one somehow? I can't believe I cannot find anything out there concerning this. Thanks for your help.

      Comment


      • #4
        nothing to do with virtual servers, or HTTP. It does just run over RPC (over TCP).

        I would be very surprised if you have a problem.

        It's all setup by default. It will just be your outlook clients that need to be configured.

        topper
        * Shamelessly mentioning "Don't forget to add reputation!"

        Comment


        • #5
          Internal: OWA, POP3, SMTP all work fine.
          External: OWA, POP3, SMTP, RPC/HTTPS all work fine.

          I configure a client on my LAN with outlook 2003 using an Exchange account. my settings:

          server name: have tried both fqdn and netbios (serverx.domain.com or serverx)

          username: same login that works for all other connections. even tried domain\name and [email protected]

          I can communicate with the server. Whenever I try to run the account, it hangs for 10-20 seconds and gives me the following error:

          The action could not be completed. The connection to the Microsoft Exchange Server is unavailable. Outlook must be online or connected to complete this action.
          What needs verification on the server side to insure that it is not the source of my problem?
          Thanks for your help on this.

          Comment


          • #6
            You say that the server works fine, and that other protocols work ok? The problem is just with Outlook?

            How did you test the communication between the workstation and the server?

            Try using RPCPING to test the connection. Try using OUTLOOK /RPCDIAG from the run command and see where the connection is refused.

            Does this happen on all workstations?

            Is there a firewall on the LAN, blocking some sort of traffic? Is the server running SP1? If so, perhaps the Windows Firewall is enabled? Is there any IPSec policy?

            Can you connect with OWA?
            Cheers,

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

            Comment


            • #7
              Yes, all other protocols are working fine.

              I tested comm through telnet,ping, and a combo of RPCPing and Rpings: I started Rpings on the server, RPCPing on the client returned positive results. When I don't run Rpings on the server, RPCPing on the client returns negative results.

              I try OUTLOOK /RPCDIAG and the window is blank, even after hitting "reconnect"

              This occurs on all workstations(XPsp2,2ksp4)

              Firewall does not restrict LAN communication unless explicitly stated. Just to cover myself I set up explicit rules to allow rpc traffic amongst the servers and clients.

              The server is running sp1. Firewall enabled with port 135 listed as an exception. IPsec policy has not been implemented.

              I connect through OWA fine. This is a multihomed server. Default http virtual server services external connections for owa(ssl) and rpc/https. Second http virtual server runs OWA(no ssl) on the lan without problems.

              The ValidPorts registry setting was configured for rpc proxy server(same as exchange server) to use ports 6001-6002, 6004. the default was 100-5000. Could this be interfering somehow?

              Comment


              • #8
                Daniel, you were right on in regards to the windows firewall. I disabled it on my internal connection and rpc/tcp works like a charm. I guess i could go in and finesse the settings, but my LAN is relatively secure for now. Thanks for the direction and time from yourself and topper.

                Comment


                • #9
                  Thanks for sharing the result.

                  Cheers,

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

                  Comment

                  Working...
                  X