New Network Design Ideas

Hi,
We have several sites running all different levels of software and
hardware that we wish to scrap. We wish to design a new network layout that
will allow for all the services that we require. Currently we have Cisco
2600 series routers and 3500 XL serries Switches at each site that we wish
to keep. We also have a 10mb Internet connection at our main site that we
will keep. I would like to know of some web sites to look at on the web that
could help us to design and configure our new network layout along with
setting up a new domain structure and all the other servers.
Some ideas we are looking for are:
- Network Infrastructure Setup
- Network Security
- Domain Structure and Setup
- Web Server setup and Security
- Data Server Setup (ie clustering)

Services we wish to have.
- Public Web Site.
- Private Web Site.
- Sql Server accessed from both Web Sites.
- Data Servers
- Print Servers
- Email Server
- Lowest possible presents to Internet. (ie Public only able to see our
public website)

Any help would be great.
Kenneth

"Kenneth Keeley" <(E-Mail Removed)> wrote in message
news:e4w1%(E-Mail Removed)...
> Hi,
> We have several sites running all different levels of software and
> hardware that we wish to scrap.

That's my favorite way. Rip it all out and start over :-)

>Currently we have Cisco
> 2600 series routers and 3500 XL serries Switches at each site that we wish
> to keep.

Sounds fine.

>We also have a 10mb Internet connection at our main site that we
> will keep. I would like to know of some web sites to look at on the web
that
> could help us to design and configure our new network layout along with

Everybody's situation is different, I don't know of any site that would give
a "template". My approach is to always keep the system as simple,
straight-forward, and streamlined as possible. People in general have way
too much tendency to create wild mind-bending monstrosities that they have
no hope of understanding, troubleshooting, and maintaining after they are
finished. The design should be based primarily on "needs" and not "wants",
from there the complexity will simply follow the design. I say "needs"
instead of "wants" because people's wants tend to get out of hand and
unrealistic,...they want to "shoot for the moon" because they think they can
rather than because they should.

> Services we wish to have.
> - Public Web Site.
> - Private Web Site.
> - Sql Server accessed from both Web Sites.
> - Data Servers
> - Print Servers
> - Email Server
> - Lowest possible presents to Internet. (ie Public only able to see
our
> public website)

This last one will give you trouble. In order for the public web server to
see the SQL server, the SQL Server will have to be avialble to the public
side as well,...if the web server can see it, so can everyone else.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

Hi Phillip

> Everybody's situation is different, I don't know of any site that would
give
> a "template". My approach is to always keep the system as simple,
> straight-forward, and streamlined as possible. People in general have way
> too much tendency to create wild mind-bending monstrosities that they have
> no hope of understanding, troubleshooting, and maintaining after they are
> finished. The design should be based primarily on "needs" and not
"wants",
> from there the complexity will simply follow the design. I say "needs"
> instead of "wants" because people's wants tend to get out of hand and
> unrealistic,...they want to "shoot for the moon" because they think they
can
> rather than because they should.

I am more after some sites with good information about designing the layout.
Like the pros and cons of a DMZ, our how to find information about creating
a DMZ with our routers, how best to setup SQL server and a Web site, etc.

> This last one will give you trouble. In order for the public web server to
> see the SQL server, the SQL Server will have to be avialble to the public
> side as well,...if the web server can see it, so can everyone else.

Can the Sql server not be behind a firewall, and then use something like an
Odbc connection from the web server to the SQL.

These are the sort of questions and answers I am looking for.

Kenneth

"Kenneth Keeley" <(E-Mail Removed)> wrote in message
news:umtW%(E-Mail Removed)...
> I am more after some sites with good information about designing the
layout.
> Like the pros and cons of a DMZ, our how to find information about
creating
> a DMZ with our routers, how best to setup SQL server and a Web site, etc.

One good site for that would be www.isaserver.org . It is centered around
using ISA Server as the Proxy/Firewall, but all the principles should be
similar no matter what you use.

> > This last one will give you trouble. In order for the public web server
to
> > see the SQL server, the SQL Server will have to be avialble to the
public
> > side as well,...if the web server can see it, so can everyone else.
>
> Can the Sql server not be behind a firewall, and then use something like
an
> Odbc connection from the web server to the SQL.

ODBC (using DSNs) is considered old and ineffiecient, but you should contact
those who specialize in Databases for details on that, ...you want to ask
about using a "DSN-less" connection. But no matter what method you use, you
cannot connect to a Database Server that is on the opposite side of the
firewall or proxy. You must use the firewall or proxy to make the Database
server available to the external side and then you connect to the firewall
or proxy as if *it* was the Database Server and then the firewall/proxy will
know what to do with it from there. The exact method for doing that varies
with whoever built the firewall or proxy. The www.isaserver.org site will
have information for doing this with MS ISA Server & MS SQL Server and it
would be refered to as "Server Publishing".


--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com