3 NICS, 3 NETWORKS, 2 SERVERS.

I have two locations that I need to add an addition NIC card to the
servers. Here is how it needs to be set up.

Location A.
Server has 3 nics in it currently, which nic1 goes to 10.0.0.x and nic2
goes to 172.30.2.x, which both nics go into the switch. Nic1 will go
from the router out a t1 line and connect to the other location. Okay,
well what I need is to add an addition network using a 3rd NIC using a
10.25.161.x Ip address, which can that go into the switch, and into
another router which uses another t1 line to connect to our other
location??

Location B.
Server has 2 nics in it currently, which nic1 goes to 10.0.0.x and nic2
goes to 172.30.2.x which both nics goes into the switch. Nic1 will go
from the switch to the router and out a t1 line back to the main
office. Nic2 will go from the switch to a router and out a 56k line to
a 3rd party network. I need to install a 3rd nic card using an IP
address of 10.25.161.x that will connect into the switch then use its
own router and out a t1 line to connect to the main location.

I need to know if this even possible, and what needs to be done. I am
not sure if I explain it enough to get a decent response. I have
diagrams drawn up, if you need them you can email me at
(E-Mail Removed).

Thanks

<(E-Mail Removed)> wrote in message
news:(E-Mail Removed) oups.com...
> I need to know if this even possible, and what needs to be done. I am
> not sure if I explain it enough to get a decent response. I have
> diagrams drawn up, if you need them you can email me at

Possible? I suppose,...but a horribly bad design. For one thing, unless the
Switch has been "VLAN'ed" they shouldn't all be running into the same
switch, and there is no just cause for the servers to be multi-homed in this
way.

The real question here is Why!?

What you really need is a Layer3 Switch at each location. It can go in place
of the existing Switch in some cases. The Switch is simply "VLAN'ed" with
certain ports dedicated to each of the three segments at each site. An L3
Switch is just a Switch and Router built into the same device and they will
act as the LAN Router for the respective Site they are in. Then the Servers
just plug into the main segment of the repective Site they are in. They will
have only one Nic with one IP# and will use the L3 Switch as their Default
Gateway.

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

I know its a bad design, but our switch isnt layer 3, or routable
switch. So that was the only way that I know how to make it work. I
do no want to put all the load on the server to act as a router either.
I do not know which way to get around this.


Phillip Windell wrote:
> <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed) oups.com...
> > I need to know if this even possible, and what needs to be done. I am
> > not sure if I explain it enough to get a decent response. I have
> > diagrams drawn up, if you need them you can email me at
>
> Possible? I suppose,...but a horribly bad design. For one thing, unless the
> Switch has been "VLAN'ed" they shouldn't all be running into the same
> switch, and there is no just cause for the servers to be multi-homed in this
> way.
>
> The real question here is Why!?
>
> What you really need is a Layer3 Switch at each location. It can go in place
> of the existing Switch in some cases. The Switch is simply "VLAN'ed" with
> certain ports dedicated to each of the three segments at each site. An L3
> Switch is just a Switch and Router built into the same device and they will
> act as the LAN Router for the respective Site they are in. Then the Servers
> just plug into the main segment of the repective Site they are in. They will
> have only one Nic with one IP# and will use the L3 Switch as their Default
> Gateway.
>
> --
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com

<(E-Mail Removed)> wrote in message
news:(E-Mail Removed) oups.com...
>I know its a bad design, but our switch isnt layer 3, or routable
> switch. So that was the only way that I know how to make it work.

No it isn't the only way. Buy a Layer3 Switch.

> do no want to put all the load on the server to act as a router either.
> I do not know which way to get around this.

Yes, you do. :-)
Buy a Layer3 Switch.

If the company wants something done,...then they need to spend the money to
do it. I have no patients at all for companies that say they want something
done, but refuse to spend the money to do the job they asked for. If they
say "We want job "X" done but you can't spend anything",...then I say "If I
can not spend anything, then you don't get job "X" done."


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

Now would I need a layer 3 switch at Location A and Location B? I
would still need to have 3 nics in the server correct, but will let the
switch do all the correct routing for me instead of the server? Now
would this be a simple swap out with the stacked switches i have in
place now? They are willing to buy the equipment if it is going to work
100%. Now I will be able to install all the equipment, but making the
switch work correctly is another story! lol

I basically need to have 3 seperate networks at 2 locations communicate
between each other at any given time. Is this possible?


Phillip Windell wrote:
> <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed) oups.com...
> >I know its a bad design, but our switch isnt layer 3, or routable
> > switch. So that was the only way that I know how to make it work.
>
> No it isn't the only way. Buy a Layer3 Switch.
>
> > do no want to put all the load on the server to act as a router either.
> > I do not know which way to get around this.
>
> Yes, you do. :-)
> Buy a Layer3 Switch.
>
> If the company wants something done,...then they need to spend the money to
> do it. I have no patients at all for companies that say they want something
> done, but refuse to spend the money to do the job they asked for. If they
> say "We want job "X" done but you can't spend anything",...then I say "If I
> can not spend anything, then you don't get job "X" done."
>
>
> --
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com

<(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ps.com...

What is below may seem like a lot of work, but it is not once you realise
what you are doing with it. When finished you will have a very dependable
and very flexible system that is well worth what the new Switches cost.

A network consists of Switches, Routers, Hubs, and Cables,...not Computers.
You can have a network with no computers on it at all. The computers just
"live" on the network when it is finished. You have to start thinking of it
that way for what is below to make sense.

> Now would I need a layer 3 switch at Location A and Location B?

Correct
Each L3S will be the "Center" of each Site with the subnets branching off
from it. The L3S *is* the Site. One of those subnets will connect the two
L3S's together which is how the Sites will be joined.

> would still need to have 3 nics in the server correct,

No.
One Nic. One subnet. The server lives in only the subnet of the Site is
sits in. Its Default gateway is the L3 Switch. Effectively, the L3 Switch
is the one with the "3 nics", except it is made to work like that,...the
server is not.

> but will let the switch do all the correct routing for me instead of the
> server?

Correct

> would this be a simple swap out with the stacked switches i have in
> place now?

Kinda-sorta. You can just also add it to the existing Switches, and just
have lots 'a switches.

> They are willing to buy the equipment if it is going to work
> 100%. Now I will be able to install all the equipment, but making the
> switch work correctly is another story! lol
>
> I basically need to have 3 seperate networks at 2 locations communicate
> between each other at any given time. Is this possible?

Determine how many of the L3S's ports you want to "assign" to each subnet.
Then create the VLANs in the configuration of each L3S and make the correct
ports part of the correct VLAN. So each device will have three VLANs.

Remember that these are also Routers built into the same device. But each
port on the device is not an "interface". The "interface" of each segment
is each *group* of ports according to how you assinged them to the VLANs.
Each interface (group of ports) will have an IP# that will become Router IP#
(or Nic IP#) for the Router on that segment.

Routers are always "aware" of the subnets connected directly to them so no
"routes" are required. They only need "routes" for segments that are not
directly connected. This can be done with Static Routes manually added or
by using routing Protocols like RIP, IGRP, ect. RIP is the simplest one.
So the two devices "talk" to each other using the routing protocols and are
then fully aware of all 5 segments. I started to say "6",..but one segment
is common to both sites and is the one that links them together.

The Internet is classified as an "unknown route" and is always handled by
the Default Gateway. If you use one Internet link to serve both
sites,...then the first L3S uses the Default Gateway of the Internet Device
and the second L3S uses the first L3S as its Default Gateway.

All the machines on the LAN (both sites) will use their own site's L3S as
their Default Gateway and will use the IP# of the "interface" that directly
faces them.

What you do with your other switches is up to you. It is doubtful there are
enough ports on the L3S's for everything so you will need to reuse and add
in your old switches,...it is all in how/where you hookup the physical
cables.

I looked back over this several times, I don't hink I forgot anything, but
if I did I'll post more later.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/IS...cessRules.html

Troubleshooting Client Authentication on Access Rules in ISA Server 2004
http://download.microsoft.com/downlo...7/ts_rules.doc

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/t...dance/2004.asp
http://www.microsoft.com/isaserver/t...dance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp

Deployment Guidelines for ISA Server 2004 Enterprise Edition
http://www.microsoft.com/technet/pro...isaserver.mspx
-----------------------------------------------------

"Phillip Windell" <@.> wrote in message
news:(E-Mail Removed)...
> I looked back over this several times, I don't hink I forgot anything, but
> if I did I'll post more later.

I did forget one thing. The Internet Device (whatever that is) will need a
Static Route added to it that tells it to use the L3S at its location as the
"gateway" for all the LAN's segments. Once it is handed off to the L3S it
will know what to do with it from that point.

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

would it be possible to email me instead of using this forum.

I am little confused on how to set this up and i dont think i described
the network itself correctly and what we need it to do.

thanks



Phillip Windell wrote:
> "Phillip Windell" <@.> wrote in message
> news:(E-Mail Removed)...
> > I looked back over this several times, I don't hink I forgot anything, but
> > if I did I'll post more later.
>
> I did forget one thing. The Internet Device (whatever that is) will need a
> Static Route added to it that tells it to use the L3S at its location as the
> "gateway" for all the LAN's segments. Once it is handed off to the L3S it
> will know what to do with it from that point.
>
> --
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com

Sure.

Phil

<(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ups.com...
> would it be possible to email me instead of using this forum.
>
> I am little confused on how to set this up and i dont think i described
> the network itself correctly and what we need it to do.
>
> thanks
>
>
>
> Phillip Windell wrote:
>> "Phillip Windell" <@.> wrote in message
>> news:(E-Mail Removed)...
>> > I looked back over this several times, I don't hink I forgot anything,
>> > but
>> > if I did I'll post more later.
>>
>> I did forget one thing. The Internet Device (whatever that is) will need
>> a
>> Static Route added to it that tells it to use the L3S at its location as
>> the
>> "gateway" for all the LAN's segments. Once it is handed off to the L3S
>> it
>> will know what to do with it from that point.
>>
>> --
>> Phillip Windell [MCP, MVP, CCNA]
>> www.wandtv.com
>

okay...

(E-Mail Removed) is the best way.

Phillip Windell wrote:
> Sure.
>
> Phil
>
> <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed) ups.com...
> > would it be possible to email me instead of using this forum.
> >
> > I am little confused on how to set this up and i dont think i described
> > the network itself correctly and what we need it to do.
> >
> > thanks
> >
> >
> >
> > Phillip Windell wrote:
> >> "Phillip Windell" <@.> wrote in message
> >> news:(E-Mail Removed)...
> >> > I looked back over this several times, I don't hink I forgot anything,
> >> > but
> >> > if I did I'll post more later.
> >>
> >> I did forget one thing. The Internet Device (whatever that is) will need
> >> a
> >> Static Route added to it that tells it to use the L3S at its location as
> >> the
> >> "gateway" for all the LAN's segments. Once it is handed off to the L3S
> >> it
> >> will know what to do with it from that point.
> >>
> >> --
> >> Phillip Windell [MCP, MVP, CCNA]
> >> www.wandtv.com
> >