none
Port 443

    Question

  • I have port 443 being forwarded onto the exchange server but i also have an Moneris terminal that will only work with port 443 according to them...

    How do I get exchange to move onto another port like 8443 and have it function. I have added the port in IIS under bindings. Removed 443 from there.I have gone into exchange and added that port to the external OWA settings. I have port forwarded 8443 onto my exchange server in my router. Still nothing ..

    get error code 501.. 

    The requested method is not implemented by this server.



    • Edited by bazzell Tuesday, September 18, 2012 8:02 PM
    Tuesday, September 18, 2012 7:49 PM

Answers

  • It will be easier if you simply take another Public IP address and NAT port 443 on the private ip of your Momeris Terminal. Don't you think?
    Tuesday, September 18, 2012 8:40 PM
  • Either get another address as mentioned and if you have a single server (some custom setup) that is sharing IIS that Exch is using, ,I'd advise to move that app to another server.

    I would leave Exch on 443 and contact the vendor and ask them and get an official response.


    Sukh

    Tuesday, September 18, 2012 10:04 PM
  • Microsoft really really wants you to stay on TCP/443 for SSL, as that's where Outlook and any ActiveSync clients are hard coded to find it. You'll have better luck binding a second IP address to your IIS/OWA server and binding OWA on the new IP.


    ExchangeGeek (MCITP,Enterprise Messaging Administrator)

    ***Don't forget to mark helpful or answer***

    Wednesday, September 19, 2012 3:39 AM

All replies

  • It will be easier if you simply take another Public IP address and NAT port 443 on the private ip of your Momeris Terminal. Don't you think?
    Tuesday, September 18, 2012 8:40 PM
  • Either get another address as mentioned and if you have a single server (some custom setup) that is sharing IIS that Exch is using, ,I'd advise to move that app to another server.

    I would leave Exch on 443 and contact the vendor and ask them and get an official response.


    Sukh

    Tuesday, September 18, 2012 10:04 PM
  • Microsoft really really wants you to stay on TCP/443 for SSL, as that's where Outlook and any ActiveSync clients are hard coded to find it. You'll have better luck binding a second IP address to your IIS/OWA server and binding OWA on the new IP.


    ExchangeGeek (MCITP,Enterprise Messaging Administrator)

    ***Don't forget to mark helpful or answer***

    Wednesday, September 19, 2012 3:39 AM