Announcement

Collapse
No announcement yet.

RPC over HTTPS initial setup only issue

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

  • RPC over HTTPS initial setup only issue

    Hi all,

    I have an Exchange 2007 Standard box, all recent updates, with all Outlook 2003 clients connecting via RPC over HTTPS on new PCs fully patched. Everything has always worked fine until about a month ago.

    When I set up a new machine and I'm on the network, everything is fine.

    When I set up a new machine remotely, I can't connect to the mailbox unless I set up a VPN first. Once I have made the initial conection to the mailbox with Outlook, I can disconnect the VPN and never us it again. Even after subsequent reboots, everything is OK, it's only the initial connection to the server which is causing the problem....

    Scratching my head here...

    What should I be looking for? Is the timeout period different for initial setup then subsequent connections?

  • #2
    Re: RPC over HTTPS initial setup only issue

    There should be no difference with the clients on or off the network, as long as you are entering the correct information.

    Is this Outlook 2003 or 2007?
    If it is 2007 then it will be wanting to use Autodiscover to configure things. Have you confirmed that Autodiscover is working 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


    • #3
      Re: RPC over HTTPS initial setup only issue

      Simon,

      It's Exchange 2007 and both Outlook 2003 and 2007 react the same way. That's what's got me so confused, once I'm beyond the first time use message, I can disconnect the VPN and never use it again.....

      Comment


      • #4
        Re: RPC over HTTPS initial setup only issue

        My own fault, moved the GC role to a new server and forgot to set the NSPI interface protocol sequences value on it......fixed

        Comment

        Working...
        X