New DHCP scope on different subnet not being used!
New DHCP scope on different subnet not being used!
(OP)
Hi all,
I have setup a new subnet under DHCP on our Win2K PDC but clients (mostly Win95) will not gain IP's from the new scope after deactivating the old one.
Old Scope:- 172.31.48.40-172.31.48.59/24
New Scope:- 172.31.49.100-172.31.49.199/24 <-this .49 has been added to our core router as a new subnet also.
Client PC's will not get IP's? Any information would be appreciated.
Regards
Dan Clark
Network Manager
Wickliffe Ltd
I have setup a new subnet under DHCP on our Win2K PDC but clients (mostly Win95) will not gain IP's from the new scope after deactivating the old one.
Old Scope:- 172.31.48.40-172.31.48.59/24
New Scope:- 172.31.49.100-172.31.49.199/24 <-this .49 has been added to our core router as a new subnet also.
Client PC's will not get IP's? Any information would be appreciated.
Regards
Dan Clark
Network Manager
Wickliffe Ltd
Talk To Other Members
RE: New DHCP scope on different subnet not being used!
If so on win95 you need to run winipcfg from the run command click release then click renew.
depending on the lifetime of your lease they will not all drop the old address immediately.
let me know if that's not it....
Jeff
RE: New DHCP scope on different subnet not being used!
reactivate the old scope and that one works.
RE: New DHCP scope on different subnet not being used!
The server NIC primary ip address should also be in the same new subnet for this to work.
Why are you changing the internal ip addressing?
If you just need more addresses, better delete the old .48 scope and create a new .48 scope with a broader range.
You can use the whole 172.31.48.1-254 range and then exclude whatever you want to exclude.
Bye
Yizhar Hurwitz
http://come.to/yizhar
http://teachers.sivan.co.il/yizhar