Announcement

Collapse
No announcement yet.

should be public/private ip

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

  • should be public/private ip

    Hi,
    I am installing now exchange 2003 on server 2003. Should I put the direct public IP on that email server? It can be secure ? or must use NAT ? Pls kindly advice me and would appreciated for brief explanation.

    thanks

  • #2
    Re: should be public/private ip

    Normally you will give it a private IP and use port forwarding from your router. This will be marginally more secure and make communication within the LAN easier
    Tom Jones
    MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
    PhD, MSc, FIAP, MIITT
    IT Trainer / Consultant
    Ossian Ltd
    Scotland

    ** Remember to give credit where credit is due and leave reputation points where appropriate **

    Comment


    • #3
      Re: should be public/private ip

      Do you have a DMZ in your network plans?
      Wesley David
      LinkedIn | Careers 2.0
      -------------------------------
      Microsoft Certifications: MCSE 2003 | MCSA:Messaging 2003 | MCITP:EA, SA, EST | MCTS: a'plenty | MCDST
      Vendor Neutral Certifications: CWNA
      Blog: www.TheNubbyAdmin.com || Twitter: @Nonapeptide || GTalk, Reader and Google+: [email protected] || Skype: Wesley.Nonapeptide
      Goofy kitten avatar photo from Troy Snow: flickr.com/photos/troysnow/

      Comment


      • #4
        Re: should be public/private ip

        Originally posted by examplez View Post
        Hi,
        I am installing now exchange 2003 on server 2003. Should I put the direct public IP on that email server? It can be secure ? or must use NAT ? Pls kindly advice me and would appreciated for brief explanation.

        thanks
        DO NOT make it public facing. Ensure it is behind a firewall. If licenses permit have a Front End server in a DMZ with no domain connectivity and even on a differing subnet but ensure the Back End is firewalled.
        Last edited by scurlaruntings; 28th May 2009, 17:13.

        Comment


        • #5
          Re: should be public/private ip

          Originally posted by scurlaruntings View Post
          DO NOT make it public facing. Ensure it is behind a firewall. If licenses permit have a Front End server in a DMZ with no domain connectivity and even on a differing subnet but ensure the Back End is firewalled.
          Sorry but don't put Exchange in a DMZ and it definitely requires domain connectivity. If you want something in a DMZ then ISA is good but not essential.
          I agree Exchange should be firewalled though.
          cheers
          Andy

          Please read this before you post:


          Quis custodiet ipsos custodes?

          Comment

          Working...
          X