DHCP "issues"

[Arxitektwn]

Hi everyone,

have the following scenario at the moment:

LAN1 ------- Router1 ------------Router2 ------------LAN2

LAN1 has 20 win2000 machines running 2000 and getting IP addresses from a
DHCP server on LAN1. LAN2 has 10 machines that "used" to get DHCP from the
server on LAN1. We recently moved DHCP from one server to another Win2k
boxes and now the machines on LAN2 cannot take IP addresses from the new
server any more.

There is full IP connectivity (ping both ways, DNS works both ways) but when
I IPCONFIG /release and /renew the machines on LAN2 get the 169.254...... IP
address. It used to work before so I know the routers allow broadcasts
through them.

Any ideas will be more than welcome.

(on another note, I would like the DHCP server to issue addresses from more
than 1 scope to various "groups" of computers. Can this be achieved and if
yes, how?)

 

[Tim Hines [MSFT]]

To obtain the best answer to you question try posting your question at
microsoft.public.win2000.networking.

--
Tim Hines, MCSE, MCSA
Windows 2000 Directory Services

=====================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Ryan]

Kou,

I can maybe answer both questions for you. To use 2
different scopes you need to have enable dhcp reley on
router2. How this works is you give router2 a static ip,
then when it receives a dhcp request it will forward it on
to the dhcp server you specify. Now how does the dhcp
server identify which ip it should give out. It uses the
ip address of the dhcp agent to figure it out. So you you
have a scope of 172.16.1.0/24 and router2 is 172.16.1.1/24
then it will know to hand out that scope.

This is probably the reason why your dhcp isn't working
anymore either (i.e. different subnets).

Ryan

BTW if you didn't know /24 means a subnet mask of
255.255.255.0