Announcement

Collapse
No announcement yet.

Remote web workplace / Exchange

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

  • Remote web workplace / Exchange

    Hi guys,

    I am using a draytek 2800 v router and i seem to be having problems accessing both the remote web workplace and OWA pages. Error 404. I've opened port 4125 and 443. Is there something i am missing?

  • #2
    Re: Remote web workplace / Exchange

    assuming that you have NATed correctly, also make sure that the router does not have remote management (or the equivalent for that make/model) enabled.
    "...if I turn out to be particularly clear, you've probably misunderstood what I've saidĒ - Alan Greenspan

    Comment


    • #3
      Re: Remote web workplace / Exchange

      Do they work internally ie //<server>/remote and //<server>/exchange?
      If yes then remember to use https://<FQDN>/Remote, as you don't have port 80 open from your description.
      Otherwise try a different router.
      If they don't work internally, then re-run the ICW until they do!
      TIA

      Steven Teiger [SBS-MVP(2003-2009)]
      http://www.wintra.co.il/
      sigpic
      Iím honoured to have been selected for the SMB 150 list for 2013. This is the third time in succession (no logo available for 2011) that I have been honoured with this award.

      We donít stop playing because we grow old, we grow old because we stop playing.

      Comment


      • #4
        Re: Remote web workplace / Exchange

        As teiger said check first internally if you can access the exchange and /remote by the https://(server)/exchange and /remote

        Make sure your router is correctly configured and you are pointing to right IP on the server with the ports 443/4125 in case you have 2 NIC cards

        Maybe you should post here your TCP status ( Ipconfig/all )

        Aslo try to run posqry tool against your router from outside to see if the ports 443,4125 are opened and in LISTENING mode

        I had very similar issue and we found our that the ISP was filering out these ports .. we have found out this by running the portqry tool

        If everything is set and the port forwarded and open you should see status LISTENNING not CLOSEd or FILTERED

        Comment

        Working...
        X