none
exchange server 2013 public ip RRS feed

  • Question

  • hello,

         can  any be  help  me  on  "how to assign  public  IP to exchange server  to configure   webmail  access".. please


    Mohammed Altaf Ahmed

    Monday, December 23, 2013 7:48 AM

Answers

  • The most common way to accomplish this is to have the public IP assigned to a firewall and the Exchange servers on an interior LAN. The firewall also acts as a NAT and redirects the connection on certain ports (25 and 587, for example) to the Exchange server.

    If you have only a single public IP address and share common ports such as 443 with other applications you'll need something redirect connections to specific virtual directories to the Exchange server (e.g. https://name/owa).


    --- Rich Matheisen MCSE&I, Exchange MVP

    Tuesday, December 24, 2013 2:01 AM
  • Hi,

    Rich's suggestion is pretty helpful. Public IP address is required to represent an Exchange server on the Internet. The router or Firewall will translate the public IP address to the internal one and forward communications from the internet to the Exchange server.

    Here is a related article for your reference, please refer to the "IP Addressing" topic.

    Planning for Your First Exchange Server: http://www.msexchange.org/articles-tutorials/exchange-server-2003/planning-architecture/Planning-First-Exchange-Server.html

    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.

    Hope this helps.

    Best regards,
    Belinda


    Belinda Ma
    TechNet Community Support

    Tuesday, December 24, 2013 8:33 AM
    Moderator

All replies

  • The most common way to accomplish this is to have the public IP assigned to a firewall and the Exchange servers on an interior LAN. The firewall also acts as a NAT and redirects the connection on certain ports (25 and 587, for example) to the Exchange server.

    If you have only a single public IP address and share common ports such as 443 with other applications you'll need something redirect connections to specific virtual directories to the Exchange server (e.g. https://name/owa).


    --- Rich Matheisen MCSE&I, Exchange MVP

    Tuesday, December 24, 2013 2:01 AM
  • Hi,

    Rich's suggestion is pretty helpful. Public IP address is required to represent an Exchange server on the Internet. The router or Firewall will translate the public IP address to the internal one and forward communications from the internet to the Exchange server.

    Here is a related article for your reference, please refer to the "IP Addressing" topic.

    Planning for Your First Exchange Server: http://www.msexchange.org/articles-tutorials/exchange-server-2003/planning-architecture/Planning-First-Exchange-Server.html

    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.

    Hope this helps.

    Best regards,
    Belinda


    Belinda Ma
    TechNet Community Support

    Tuesday, December 24, 2013 8:33 AM
    Moderator
  • Hello,

    Come back and mark the replies as answers if they help and unmark them if they provide no help.

    I'm marking the reply as answer as there has been no update for a couple of days.
    If you come back to find it doesn't work for you, please reply to us and unmark the answer.


    Cara Chen
    TechNet Community Support

    Friday, January 3, 2014 8:08 AM
    Moderator