Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

New DHCP scope on different subnet not being used!

Status
Not open for further replies.

danclark

IS-IT--Management
Apr 9, 2001
46
NZ
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
 
when you say that &quot;will not gain IP's from the new scope after deactivating the old one.&quot; do you mean you've turned off the scope and the clients still have the old IP addresses?

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
 
no, basicly we kill the old scope, activate the new and when rebooting or doing an ipconfig/renew it doesn't see the DHCP server!
reactivate the old scope and that one works.
 
HI.

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
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top