General setup

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Tony Su (anonymous_at_discussions.microsoft.com)
Date: 05/11/04


Date: Mon, 10 May 2004 22:08:57 -0700

Most security?
Most performance?
:)
Boy, aren't you asking for the world...

Recommend you consider security as a sliding scale, not
black and white. With an unlimited budget, you can
<always> figure out a way to make your configuration more
secure and maybe even perform better.

And, in most situations I work with people don't
necessarily want the "most secure" because that would not
only make it difficult for hackers to compromise your
machines, it would also make it extraordinarily difficult
to access and support.

Life is a compromise and you have to determine what is
best for your specific situation.

Tony Su

>-----Original Message-----
>Hi Folks,
>
>My company currently has a Win2k Network Setup. This
network consist of Isa
>Server, Exchange Server, Internal Web Server, and a few
Storage and App
>server. We are in the process of building a new seperate
network. We want to
>create this network so that we can connect to the
existing network and use
>it's resources. At the same time the existing network
will not be able to
>access the new network. This network will be a win2k3
network with
>Exchange2000, Isa2000, SQL2000 and a Web Server. My
question is which is the
>best possible way to set this network up in a way where
we will have the
>most possible security and the most possible performance.
For example: where
>should we place the servers? should the exchange server
be in the DMZ or in
>the internal network. Should SQL Server be in the DMZ or
the inside. Keep in
>mind that the webserver will be accessing the SQL Server.
Where do we put
>the webserver? We also plan to use the webserver to host
not only corporate
>sites but client's sites. Just looking for some gerneral
ideas and reasons
>why you would set it up like this.
>
>Thanks
>D
>
>
>.
>



Relevant Pages

  • << SBS News of the week - Sept 26 >>
    ... And he points to the info you need to put the file on the server in the ... at the network perimeter. ... The Symantec Firewall/VPN and the Gateway Security ... by the firewall at risk. ...
    (microsoft.public.backoffice.smallbiz)
  • << SBS News of the week - Sept 26 >>
    ... And he points to the info you need to put the file on the server in the ... at the network perimeter. ... The Symantec Firewall/VPN and the Gateway Security ... by the firewall at risk. ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: << SBS News of the week - Sept 26 >>
    ... > And he points to the info you need to put the file on the server in the ... > at the network perimeter. ... The Symantec Firewall/VPN and the Gateway Security ... An attacker can exploit these flaws in tandem via specially ...
    (microsoft.public.backoffice.smallbiz2000)
  • << SBS News of the week - Sept 26 >>
    ... And he points to the info you need to put the file on the server in the ... at the network perimeter. ... The Symantec Firewall/VPN and the Gateway Security ... by the firewall at risk. ...
    (microsoft.public.windows.server.sbs)
  • Re: << SBS News of the week - Sept 26 >>
    ... > And he points to the info you need to put the file on the server in the ... > at the network perimeter. ... The Symantec Firewall/VPN and the Gateway Security ... An attacker can exploit these flaws in tandem via specially ...
    (microsoft.public.windows.server.sbs)