Connecting to remote MS Exchange using BEFSX41 and RPC over HTTPS

Discussion in 'Cisco/Linksys Wireless Routers' started by jameshurrell, Jul 27, 2007.

  1. jameshurrell

    jameshurrell LI Guru Member

    I have a Linksys BEFSX41 on a serviced office 2MB/2MB connection that is providing internet access to 5 users in an office. Up until recently the router has functioned extremely well and not let us down.

    Last week we moved our email platform (provided by an external third party) from simple POP3/SMTP, to hosted Microsoft Exchange (mainly for the collaboration tools and Outlook Web Access). We have been advised to connect to the external Exchange server with Outlook using RPC over HTTPS. This is where the problem has started. With one Outlook client open and connected to the Exchange server, everything is fine, it runs smoothly and we're not seeing any hangs or lost connections. However, as soon as another Outlook client is fired up on the same network, all Outlook clients start to hang, lose their connection to the Exchange server or completely lock up. This has got so bad that Outlook is now unusable so we have had to downgrade the mailboxes to POP3 in the interim.

    I tested the connection overnight - I left one Outlook client open conneted to Exchange and loaded up the Outlook connection diagnostics box (run Outlook using the /rpcdiag switch). No failed requests, no disconnections at all. As soon as I load up another Outlook client however, both clients start to hang and misbehave. The connection to Exchange is also perfect on another totally unrelated internet connection.

    I have ruled out the Exchange servers (my provider insists they are seeing no issues (the mailboxes are on 3 different Exchange servers anyway)), and Outlook itself (it works flawlessly with only one client open on the network) so that leaves the router. I have fiddled and messed about with the settings in the router but to no avail (changed MTU, disabled firewall, watched the logs etc...).

    Does anyone have any suggestions or has anyone ever experienced this and found a workaround? My next step is to test another router to see if the problem is still apparent.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice