DHCP wont handout addresses on new scope

My DHCP server originally setup for one subnet (192.168.0.0) hands out IP's
fine to that network. I added a scope for another network that is part of a
VLAN implementation I'm trying to set up. The other scope is the
192.168.20.0 network. My intention is for hosts to request IP's through a
Dell L3 6024 switch which has 1 interface lying on the 192.168.0.0 network.
The Dell handles the routing between the 192.168.0.0 and 192.168.20.0
networks.

Using Ethereal, I see that the DHCP server is receiving DHCP requests from
the the, but it doesn't ever seem to respond. I realize that there may be
some problem with my configuration of the switch...maybe I have to set up
some kind of static route or something, however, if I give the
192.168.20.xxx host a static IP, it can ping the DHCP server and the server
can ping it, so I'm inclined to think that's not the problem. Switch has
DHCP relay configured and points to my server as the DHCP server.

One (possible ) complicating factor is that the default route for the
192.168.0.0 network will be 192.168.0.1, ( internet ) where as the default
route for all other 192.168.xxx.0 network will be the 6024 interface.


I'm just wondering if anyone knows what conditions would cause the DHCP
server to not respond to DHCP requests. Server is Windows 2003 Server
Standard.

TimeTraveller

"TimeTraveller" <(E-Mail Removed)> wrote in message
news:%1hKg.496867$iF6.341517@pd7tw2no...
> One (possible ) complicating factor is that the default route for the
> 192.168.0.0 network will be 192.168.0.1, ( internet ) where as the default
> route for all other 192.168.xxx.0 network will be the 6024 interface.

The LAN Router between the Subnets should be the DFG of all machines on all
the subnets. The Default Gateway of the Router itself will be the
192.168.0.1 (internet).

That will solve much of your problems,...and probably some that you don't
know you have yet.

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

Thanks Phillip, I'll check it out.


"Phillip Windell" <@.> wrote in message
news:(E-Mail Removed)...
> "TimeTraveller" <(E-Mail Removed)> wrote in message
> news:%1hKg.496867$iF6.341517@pd7tw2no...
>> One (possible ) complicating factor is that the default route for the
>> 192.168.0.0 network will be 192.168.0.1, ( internet ) where as the
>> default route for all other 192.168.xxx.0 network will be the 6024
>> interface.
>
> The LAN Router between the Subnets should be the DFG of all machines on
> all the subnets. The Default Gateway of the Router itself will be the
> 192.168.0.1 (internet).
>
> That will solve much of your problems,...and probably some that you don't
> know you have yet.
>
> --
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>