×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Contact US

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

New DHCP scope on different subnet not being used!

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

RE: New DHCP scope on different subnet not being used!

when you say that "will not gain IP's from the new scope after deactivating the old one."  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

RE: New DHCP scope on different subnet not being used!

(OP)
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.

RE: New DHCP scope on different subnet not being used!

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
http://come.to/yizhar
http://teachers.sivan.co.il/yizhar

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close