Announcement

Collapse
No announcement yet.

RPC over HTTP stopped

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

  • RPC over HTTP stopped

    Hi

    I setup RPC over HTTP in January on a single server using the the guide on this site. Everything has been working fine up until Tuesday this week when everybody in the company lost access. Webmail still works fine and they can use Outlook if they VPN in. However just using the RPC over HTTP the client tries to connect then shows as disconnected.

    One thing I have noticed is that the ISAPI filter in IIS Website shows RPCProxy *unknown*, but the ISAPI filters for Default web site shows OWA Logon *unknown*. Could this be stopping RPC over HTTP access?

    System
    Windows 2003 R2 SP2 Domain Controller
    Exchange 2003 Enterprise SP2
    Both have up-to-date patches
    Clients all use Outlook 2003 with latest service packs and patches.

  • #2
    Re: RPC over HTTP stopped

    The unknown priority is normal and will not be the cause of the failure.
    If it was working and isn't now, and no one has touched the server, the usual reason is the SSL certificate has expired.

    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