2nd DHCP Scope?

Hello,

I currently have a network setup on the 172.20.4.x IP range.

I need to add another DHCP scope because I am just about out of IPs.

Now, I have configured a second scope on the Windows 2000server and
activated it.

The server is plugged into a Dell 5324 powerconnect with the default VLAN on
the .4.x network.

There is a Cisco 2811 that is the default gateway.

Servers -> PC5324 -> older power connect to be on new range 172.20.9.x

What I believe I need to do is: add a second VLAN on the PC5324 with an IP
from the new IP range. Now, do I need to add a route in the cisco since it
is the gateway?

I added an IP of the new range to the server and if I connect from the
switch at the end with the new IP and perform a ipconfig renew, I receive
an IP from the original IP range. If I assign an IP from the new range, I
can reach the server and ping the switch, however I can not get to anything
on the .4.x network.

Does this make since?

Thanks!!!

> I added an IP of the new range to the server and if I connect from the
> switch at the end with the new IP and perform a ipconfig renew, I receive
> an IP from the original IP range. If I assign an IP from the new range, I
> can reach the server and ping the switch, however I can not get to
> anything on the .4.x network.
>
> Does this make since?

sort of... it's a bit confusing. However, if your 2811 is multihomed (or has
two interfaces, each connected to a separate switch), then it needs to do
the routing for you, unless you also put the server on the second range
(might be easier, depending on your particular needs).

If you don't put the server on the second range, then each subnet needs to
point to the router as the default gw. The router will have a route to each
range by default, because they are both connected to it.

I'm not sure what else you are using the router for, but it might just be
simpler to multihome your server. You could put two NICs in it, and have it
communicate directly on each subnet.

Oliver

>
> Thanks!!!
>

Hello,

The router is the current gateway. It also connects the 3rd location with a
T1.

What I've done so far is:

Added the static route in the router/gateway.
Added VLAN to the switch and assigned it an IP from the new range.
Created the second scope on the windows 2000 server and activated it.

I can't reach the switch that is plugged into the one above that I added the
VLAN to.

Any ideas?

"Oliver O'Boyle" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>
>
>> I added an IP of the new range to the server and if I connect from the
>> switch at the end with the new IP and perform a ipconfig renew, I
>> receive an IP from the original IP range. If I assign an IP from the new
>> range, I can reach the server and ping the switch, however I can not get
>> to anything on the .4.x network.
>>
>> Does this make since?
>
> sort of... it's a bit confusing. However, if your 2811 is multihomed (or
> has two interfaces, each connected to a separate switch), then it needs to
> do the routing for you, unless you also put the server on the second range
> (might be easier, depending on your particular needs).
>
> If you don't put the server on the second range, then each subnet needs to
> point to the router as the default gw. The router will have a route to
> each range by default, because they are both connected to it.
>
> I'm not sure what else you are using the router for, but it might just be
> simpler to multihome your server. You could put two NICs in it, and have
> it communicate directly on each subnet.
>
> Oliver
>
>>
>> Thanks!!!
>>
>
>

> The router is the current gateway. It also connects the 3rd location with
> a T1.

ok. So yes, you will a static route pointing to the third location, as you
have done.

> Added the static route in the router/gateway.

> Added VLAN to the switch and assigned it an IP from the new range.
> Created the second scope on the windows 2000 server and activated it.

are your switches chained (switch 2 plugs into switch 1, which plugs into
the router)? Or are they each directly connected into the router?

Oliver


>
> I can't reach the switch that is plugged into the one above that I added
> the VLAN to.
>
> Any ideas?
>
> "Oliver O'Boyle" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>>
>>
>>> I added an IP of the new range to the server and if I connect from the
>>> switch at the end with the new IP and perform a ipconfig renew, I
>>> receive an IP from the original IP range. If I assign an IP from the
>>> new range, I can reach the server and ping the switch, however I can not
>>> get to anything on the .4.x network.
>>>
>>> Does this make since?
>>
>> sort of... it's a bit confusing. However, if your 2811 is multihomed (or
>> has two interfaces, each connected to a separate switch), then it needs
>> to do the routing for you, unless you also put the server on the second
>> range (might be easier, depending on your particular needs).
>>
>> If you don't put the server on the second range, then each subnet needs
>> to point to the router as the default gw. The router will have a route to
>> each range by default, because they are both connected to it.
>>
>> I'm not sure what else you are using the router for, but it might just be
>> simpler to multihome your server. You could put two NICs in it, and have
>> it communicate directly on each subnet.
>>
>> Oliver
>>
>>>
>>> Thanks!!!
>>>
>>
>>
>
>

Switches are chained (switch 2 plugs into switch 1, which plugs into the
router.

What I find now is when I try to ping an IP on the new range, I get a reply
from the firewall but TTL is expired in transit. I beleive I need to add an
entry to the firewall but not sure what to put in it.


"Oliver O'Boyle" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>> The router is the current gateway. It also connects the 3rd location
>> with a T1.
>
> ok. So yes, you will a static route pointing to the third location, as you
> have done.
>
>> Added the static route in the router/gateway.
>
>> Added VLAN to the switch and assigned it an IP from the new range.
>> Created the second scope on the windows 2000 server and activated it.
>
> are your switches chained (switch 2 plugs into switch 1, which plugs into
> the router)? Or are they each directly connected into the router?
>
> Oliver
>
>
>>
>> I can't reach the switch that is plugged into the one above that I added
>> the VLAN to.
>>
>> Any ideas?
>>
>> "Oliver O'Boyle" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>>
>>>
>>>> I added an IP of the new range to the server and if I connect from the
>>>> switch at the end with the new IP and perform a ipconfig renew, I
>>>> receive an IP from the original IP range. If I assign an IP from the
>>>> new range, I can reach the server and ping the switch, however I can
>>>> not get to anything on the .4.x network.
>>>>
>>>> Does this make since?
>>>
>>> sort of... it's a bit confusing. However, if your 2811 is multihomed (or
>>> has two interfaces, each connected to a separate switch), then it needs
>>> to do the routing for you, unless you also put the server on the second
>>> range (might be easier, depending on your particular needs).
>>>
>>> If you don't put the server on the second range, then each subnet needs
>>> to point to the router as the default gw. The router will have a route
>>> to each range by default, because they are both connected to it.
>>>
>>> I'm not sure what else you are using the router for, but it might just
>>> be simpler to multihome your server. You could put two NICs in it, and
>>> have it communicate directly on each subnet.
>>>
>>> Oliver
>>>
>>>>
>>>> Thanks!!!
>>>>
>>>
>>>
>>
>>
>
>

> Switches are chained (switch 2 plugs into switch 1, which plugs into the
> router.

I'm assuming these are layer 2 switches. please tell me if I'm wrong.

>
> What I find now is when I try to ping an IP on the new range, I get a
> reply from the firewall but TTL is expired in transit. I beleive I need
> to add an entry to the firewall but not sure what to put in it.
>

what vlan nunber are you using, and on which switch? if you want both
subnets to go through both switches, each switch need to be on the same
vlan, or you need to configure the uplink ports as vlan trunks (they will
pass traffic on both vlans).

Oliver

>
> "Oliver O'Boyle" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>>> The router is the current gateway. It also connects the 3rd location
>>> with a T1.
>>
>> ok. So yes, you will a static route pointing to the third location, as
>> you have done.
>>
>>> Added the static route in the router/gateway.
>>
>>> Added VLAN to the switch and assigned it an IP from the new range.
>>> Created the second scope on the windows 2000 server and activated it.
>>
>> are your switches chained (switch 2 plugs into switch 1, which plugs into
>> the router)? Or are they each directly connected into the router?
>>
>> Oliver
>>
>>
>>>
>>> I can't reach the switch that is plugged into the one above that I added
>>> the VLAN to.
>>>
>>> Any ideas?
>>>
>>> "Oliver O'Boyle" <(E-Mail Removed)> wrote in message
>>> news:(E-Mail Removed)...
>>>>
>>>>
>>>>> I added an IP of the new range to the server and if I connect from the
>>>>> switch at the end with the new IP and perform a ipconfig renew, I
>>>>> receive an IP from the original IP range. If I assign an IP from the
>>>>> new range, I can reach the server and ping the switch, however I can
>>>>> not get to anything on the .4.x network.
>>>>>
>>>>> Does this make since?
>>>>
>>>> sort of... it's a bit confusing. However, if your 2811 is multihomed
>>>> (or has two interfaces, each connected to a separate switch), then it
>>>> needs to do the routing for you, unless you also put the server on the
>>>> second range (might be easier, depending on your particular needs).
>>>>
>>>> If you don't put the server on the second range, then each subnet needs
>>>> to point to the router as the default gw. The router will have a route
>>>> to each range by default, because they are both connected to it.
>>>>
>>>> I'm not sure what else you are using the router for, but it might just
>>>> be simpler to multihome your server. You could put two NICs in it, and
>>>> have it communicate directly on each subnet.
>>>>
>>>> Oliver
>>>>
>>>>>
>>>>> Thanks!!!
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>

I bet that is what is wrong.

According to DELL they are layer 3 switches. Power connect 5324.

on the switch that will have both ip ranges, I added a VLAN called 2. maybe
I should do the vlan trunks. What would suggest?

"Oliver O'Boyle" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>> Switches are chained (switch 2 plugs into switch 1, which plugs into the
>> router.
>
> I'm assuming these are layer 2 switches. please tell me if I'm wrong.
>
>>
>> What I find now is when I try to ping an IP on the new range, I get a
>> reply from the firewall but TTL is expired in transit. I beleive I need
>> to add an entry to the firewall but not sure what to put in it.
>>
>
> what vlan nunber are you using, and on which switch? if you want both
> subnets to go through both switches, each switch need to be on the same
> vlan, or you need to configure the uplink ports as vlan trunks (they will
> pass traffic on both vlans).
>
> Oliver
>
>>
>> "Oliver O'Boyle" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>>> The router is the current gateway. It also connects the 3rd location
>>>> with a T1.
>>>
>>> ok. So yes, you will a static route pointing to the third location, as
>>> you have done.
>>>
>>>> Added the static route in the router/gateway.
>>>
>>>> Added VLAN to the switch and assigned it an IP from the new range.
>>>> Created the second scope on the windows 2000 server and activated it.
>>>
>>> are your switches chained (switch 2 plugs into switch 1, which plugs
>>> into the router)? Or are they each directly connected into the router?
>>>
>>> Oliver
>>>
>>>
>>>>
>>>> I can't reach the switch that is plugged into the one above that I
>>>> added the VLAN to.
>>>>
>>>> Any ideas?
>>>>
>>>> "Oliver O'Boyle" <(E-Mail Removed)> wrote in message
>>>> news:(E-Mail Removed)...
>>>>>
>>>>>
>>>>>> I added an IP of the new range to the server and if I connect from
>>>>>> the switch at the end with the new IP and perform a ipconfig renew,
>>>>>> I receive an IP from the original IP range. If I assign an IP from
>>>>>> the new range, I can reach the server and ping the switch, however I
>>>>>> can not get to anything on the .4.x network.
>>>>>>
>>>>>> Does this make since?
>>>>>
>>>>> sort of... it's a bit confusing. However, if your 2811 is multihomed
>>>>> (or has two interfaces, each connected to a separate switch), then it
>>>>> needs to do the routing for you, unless you also put the server on the
>>>>> second range (might be easier, depending on your particular needs).
>>>>>
>>>>> If you don't put the server on the second range, then each subnet
>>>>> needs to point to the router as the default gw. The router will have a
>>>>> route to each range by default, because they are both connected to it.
>>>>>
>>>>> I'm not sure what else you are using the router for, but it might just
>>>>> be simpler to multihome your server. You could put two NICs in it, and
>>>>> have it communicate directly on each subnet.
>>>>>
>>>>> Oliver
>>>>>
>>>>>>
>>>>>> Thanks!!!
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>

> According to DELL they are layer 3 switches. Power connect 5324.

Ah. well. Layer 3 switches work differently. They switch by IP, not by mac
(for the most part). So you also have that to deal with.

>
> on the switch that will have both ip ranges, I added a VLAN called 2.
> maybe I should do the vlan trunks. What would suggest?
>

if you want to keep them chained, and you want them in separate VLANs, then
create 2 VLANs; one on each switch. Configure the uplink ports as trunks,
and make sure they have both VLANs in the trunk. Make sure the router
interface has 2 VLANs configured with the same numbers as your switch VLANs
(you'll need to use subinterfaces; one for each vlan) and give each VLAN an
IP address for the appropriate subnet.

This will effectively allow the switches to see the router, but keep the
segments separate. Once the router can be pinged by the switches, it should
be able to route automatically, because it will show the VLANs as connected
interfaces. This means the routing table will automatically be populated
according to your needs.

You might, however, want to consider putting your server (with 2 NICs) on
both switches (VLANs). If you don't do this, you will need to configure the
router to act as a DHCP relay agent, otherwise your second VLAN won't get
their IP addresses. It works, but it's probably better for you to add 2 NICs
in this case. Doing so will have the added benefit of taking some strain off
your router and server's first NIC.

Oliver






> "Oliver O'Boyle" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>>> Switches are chained (switch 2 plugs into switch 1, which plugs into the
>>> router.
>>
>> I'm assuming these are layer 2 switches. please tell me if I'm wrong.
>>
>>>
>>> What I find now is when I try to ping an IP on the new range, I get a
>>> reply from the firewall but TTL is expired in transit. I beleive I need
>>> to add an entry to the firewall but not sure what to put in it.
>>>
>>
>> what vlan nunber are you using, and on which switch? if you want both
>> subnets to go through both switches, each switch need to be on the same
>> vlan, or you need to configure the uplink ports as vlan trunks (they will
>> pass traffic on both vlans).
>>
>> Oliver
>>
>>>
>>> "Oliver O'Boyle" <(E-Mail Removed)> wrote in message
>>> news:(E-Mail Removed)...
>>>>> The router is the current gateway. It also connects the 3rd location
>>>>> with a T1.
>>>>
>>>> ok. So yes, you will a static route pointing to the third location, as
>>>> you have done.
>>>>
>>>>> Added the static route in the router/gateway.
>>>>
>>>>> Added VLAN to the switch and assigned it an IP from the new range.
>>>>> Created the second scope on the windows 2000 server and activated it.
>>>>
>>>> are your switches chained (switch 2 plugs into switch 1, which plugs
>>>> into the router)? Or are they each directly connected into the router?
>>>>
>>>> Oliver
>>>>
>>>>
>>>>>
>>>>> I can't reach the switch that is plugged into the one above that I
>>>>> added the VLAN to.
>>>>>
>>>>> Any ideas?
>>>>>
>>>>> "Oliver O'Boyle" <(E-Mail Removed)> wrote in message
>>>>> news:(E-Mail Removed)...
>>>>>>
>>>>>>
>>>>>>> I added an IP of the new range to the server and if I connect from
>>>>>>> the switch at the end with the new IP and perform a ipconfig renew,
>>>>>>> I receive an IP from the original IP range. If I assign an IP from
>>>>>>> the new range, I can reach the server and ping the switch, however I
>>>>>>> can not get to anything on the .4.x network.
>>>>>>>
>>>>>>> Does this make since?
>>>>>>
>>>>>> sort of... it's a bit confusing. However, if your 2811 is multihomed
>>>>>> (or has two interfaces, each connected to a separate switch), then it
>>>>>> needs to do the routing for you, unless you also put the server on
>>>>>> the second range (might be easier, depending on your particular
>>>>>> needs).
>>>>>>
>>>>>> If you don't put the server on the second range, then each subnet
>>>>>> needs to point to the router as the default gw. The router will have
>>>>>> a route to each range by default, because they are both connected to
>>>>>> it.
>>>>>>
>>>>>> I'm not sure what else you are using the router for, but it might
>>>>>> just be simpler to multihome your server. You could put two NICs in
>>>>>> it, and have it communicate directly on each subnet.
>>>>>>
>>>>>> Oliver
>>>>>>
>>>>>>>
>>>>>>> Thanks!!!
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>

Well, there is more to it.

I actually have two of the power connect 5324's in the room. The server has
2 nics, one going to each switch. There is a fibre run from each switch to
another area os the building where there are 2 more switches. This was done
for some redundancy.

Basically, All I want to do is have PC's be able to obtain an IP from the
new range that is on the same subnet. I also want to be able to access the
PCs on either ip range.Without getting to difficult.

I added an IP from the new range to the one server nic. Added the static
router in the router/gateway, added a static route in the firewall under
router, added the second VLAN on the one switch with an IP from the new
range, then the new switch at the end has the default vlan with the new IP
range.

So, now when I try to ping an IP on the new subnet, it goes to the
router/gateway, that passes it to the firewall and hten it expires in
transit.

With all this, what do you think would be the easiest way to move forward.
Routing is not my strong point.



"Oliver O'Boyle" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>> According to DELL they are layer 3 switches. Power connect 5324.
>
> Ah. well. Layer 3 switches work differently. They switch by IP, not by mac
> (for the most part). So you also have that to deal with.
>
>>
>> on the switch that will have both ip ranges, I added a VLAN called 2.
>> maybe I should do the vlan trunks. What would suggest?
>>
>
> if you want to keep them chained, and you want them in separate VLANs,
> then create 2 VLANs; one on each switch. Configure the uplink ports as
> trunks, and make sure they have both VLANs in the trunk. Make sure the
> router interface has 2 VLANs configured with the same numbers as your
> switch VLANs (you'll need to use subinterfaces; one for each vlan) and
> give each VLAN an IP address for the appropriate subnet.
>
> This will effectively allow the switches to see the router, but keep the
> segments separate. Once the router can be pinged by the switches, it
> should be able to route automatically, because it will show the VLANs as
> connected interfaces. This means the routing table will automatically be
> populated according to your needs.
>
> You might, however, want to consider putting your server (with 2 NICs) on
> both switches (VLANs). If you don't do this, you will need to configure
> the router to act as a DHCP relay agent, otherwise your second VLAN won't
> get their IP addresses. It works, but it's probably better for you to add
> 2 NICs in this case. Doing so will have the added benefit of taking some
> strain off your router and server's first NIC.
>
> Oliver
>
>
>
>
>
>
>> "Oliver O'Boyle" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>>> Switches are chained (switch 2 plugs into switch 1, which plugs into
>>>> the router.
>>>
>>> I'm assuming these are layer 2 switches. please tell me if I'm wrong.
>>>
>>>>
>>>> What I find now is when I try to ping an IP on the new range, I get a
>>>> reply from the firewall but TTL is expired in transit. I beleive I
>>>> need to add an entry to the firewall but not sure what to put in it.
>>>>
>>>
>>> what vlan nunber are you using, and on which switch? if you want both
>>> subnets to go through both switches, each switch need to be on the same
>>> vlan, or you need to configure the uplink ports as vlan trunks (they
>>> will pass traffic on both vlans).
>>>
>>> Oliver
>>>
>>>>
>>>> "Oliver O'Boyle" <(E-Mail Removed)> wrote in message
>>>> news:(E-Mail Removed)...
>>>>>> The router is the current gateway. It also connects the 3rd location
>>>>>> with a T1.
>>>>>
>>>>> ok. So yes, you will a static route pointing to the third location, as
>>>>> you have done.
>>>>>
>>>>>> Added the static route in the router/gateway.
>>>>>
>>>>>> Added VLAN to the switch and assigned it an IP from the new range.
>>>>>> Created the second scope on the windows 2000 server and activated it.
>>>>>
>>>>> are your switches chained (switch 2 plugs into switch 1, which plugs
>>>>> into the router)? Or are they each directly connected into the router?
>>>>>
>>>>> Oliver
>>>>>
>>>>>
>>>>>>
>>>>>> I can't reach the switch that is plugged into the one above that I
>>>>>> added the VLAN to.
>>>>>>
>>>>>> Any ideas?
>>>>>>
>>>>>> "Oliver O'Boyle" <(E-Mail Removed)> wrote in message
>>>>>> news:(E-Mail Removed)...
>>>>>>>
>>>>>>>
>>>>>>>> I added an IP of the new range to the server and if I connect from
>>>>>>>> the switch at the end with the new IP and perform a ipconfig
>>>>>>>> renew, I receive an IP from the original IP range. If I assign an
>>>>>>>> IP from the new range, I can reach the server and ping the switch,
>>>>>>>> however I can not get to anything on the .4.x network.
>>>>>>>>
>>>>>>>> Does this make since?
>>>>>>>
>>>>>>> sort of... it's a bit confusing. However, if your 2811 is multihomed
>>>>>>> (or has two interfaces, each connected to a separate switch), then
>>>>>>> it needs to do the routing for you, unless you also put the server
>>>>>>> on the second range (might be easier, depending on your particular
>>>>>>> needs).
>>>>>>>
>>>>>>> If you don't put the server on the second range, then each subnet
>>>>>>> needs to point to the router as the default gw. The router will have
>>>>>>> a route to each range by default, because they are both connected to
>>>>>>> it.
>>>>>>>
>>>>>>> I'm not sure what else you are using the router for, but it might
>>>>>>> just be simpler to multihome your server. You could put two NICs in
>>>>>>> it, and have it communicate directly on each subnet.
>>>>>>>
>>>>>>> Oliver
>>>>>>>
>>>>>>>>
>>>>>>>> Thanks!!!
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>

I've tried one other thing. I removed the second VLAN from the switch and
added an IP from the new range to the default VLAN. Does this make anything
easier?


"Oliver O'Boyle" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>> According to DELL they are layer 3 switches. Power connect 5324.
>
> Ah. well. Layer 3 switches work differently. They switch by IP, not by mac
> (for the most part). So you also have that to deal with.
>
>>
>> on the switch that will have both ip ranges, I added a VLAN called 2.
>> maybe I should do the vlan trunks. What would suggest?
>>
>
> if you want to keep them chained, and you want them in separate VLANs,
> then create 2 VLANs; one on each switch. Configure the uplink ports as
> trunks, and make sure they have both VLANs in the trunk. Make sure the
> router interface has 2 VLANs configured with the same numbers as your
> switch VLANs (you'll need to use subinterfaces; one for each vlan) and
> give each VLAN an IP address for the appropriate subnet.
>
> This will effectively allow the switches to see the router, but keep the
> segments separate. Once the router can be pinged by the switches, it
> should be able to route automatically, because it will show the VLANs as
> connected interfaces. This means the routing table will automatically be
> populated according to your needs.
>
> You might, however, want to consider putting your server (with 2 NICs) on
> both switches (VLANs). If you don't do this, you will need to configure
> the router to act as a DHCP relay agent, otherwise your second VLAN won't
> get their IP addresses. It works, but it's probably better for you to add
> 2 NICs in this case. Doing so will have the added benefit of taking some
> strain off your router and server's first NIC.
>
> Oliver
>
>
>
>
>
>
>> "Oliver O'Boyle" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>>> Switches are chained (switch 2 plugs into switch 1, which plugs into
>>>> the router.
>>>
>>> I'm assuming these are layer 2 switches. please tell me if I'm wrong.
>>>
>>>>
>>>> What I find now is when I try to ping an IP on the new range, I get a
>>>> reply from the firewall but TTL is expired in transit. I beleive I
>>>> need to add an entry to the firewall but not sure what to put in it.
>>>>
>>>
>>> what vlan nunber are you using, and on which switch? if you want both
>>> subnets to go through both switches, each switch need to be on the same
>>> vlan, or you need to configure the uplink ports as vlan trunks (they
>>> will pass traffic on both vlans).
>>>
>>> Oliver
>>>
>>>>
>>>> "Oliver O'Boyle" <(E-Mail Removed)> wrote in message
>>>> news:(E-Mail Removed)...
>>>>>> The router is the current gateway. It also connects the 3rd location
>>>>>> with a T1.
>>>>>
>>>>> ok. So yes, you will a static route pointing to the third location, as
>>>>> you have done.
>>>>>
>>>>>> Added the static route in the router/gateway.
>>>>>
>>>>>> Added VLAN to the switch and assigned it an IP from the new range.
>>>>>> Created the second scope on the windows 2000 server and activated it.
>>>>>
>>>>> are your switches chained (switch 2 plugs into switch 1, which plugs
>>>>> into the router)? Or are they each directly connected into the router?
>>>>>
>>>>> Oliver
>>>>>
>>>>>
>>>>>>
>>>>>> I can't reach the switch that is plugged into the one above that I
>>>>>> added the VLAN to.
>>>>>>
>>>>>> Any ideas?
>>>>>>
>>>>>> "Oliver O'Boyle" <(E-Mail Removed)> wrote in message
>>>>>> news:(E-Mail Removed)...
>>>>>>>
>>>>>>>
>>>>>>>> I added an IP of the new range to the server and if I connect from
>>>>>>>> the switch at the end with the new IP and perform a ipconfig
>>>>>>>> renew, I receive an IP from the original IP range. If I assign an
>>>>>>>> IP from the new range, I can reach the server and ping the switch,
>>>>>>>> however I can not get to anything on the .4.x network.
>>>>>>>>
>>>>>>>> Does this make since?
>>>>>>>
>>>>>>> sort of... it's a bit confusing. However, if your 2811 is multihomed
>>>>>>> (or has two interfaces, each connected to a separate switch), then
>>>>>>> it needs to do the routing for you, unless you also put the server
>>>>>>> on the second range (might be easier, depending on your particular
>>>>>>> needs).
>>>>>>>
>>>>>>> If you don't put the server on the second range, then each subnet
>>>>>>> needs to point to the router as the default gw. The router will have
>>>>>>> a route to each range by default, because they are both connected to
>>>>>>> it.
>>>>>>>
>>>>>>> I'm not sure what else you are using the router for, but it might
>>>>>>> just be simpler to multihome your server. You could put two NICs in
>>>>>>> it, and have it communicate directly on each subnet.
>>>>>>>
>>>>>>> Oliver
>>>>>>>
>>>>>>>>
>>>>>>>> Thanks!!!
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>