Question:

has anyone increased the dhcp scope (yes I realise that MS say it can't be done:D)on NT 4 ??
long story cut short, a company I know has this problem & needs to streeeetch the current scope, can it be done ??

/not expecting too many answers on this one

shunty

As in....

Currently is 192.168.1.32 through .64 and you want to make it 32. through 128?

Or am I :confused:?

Add another scope.....?

yup your right, sounds simple Chris, but according to MS, can't be done, & if you try the options are greyed out.
I have done a google on it & didn't find anything.
If anyone has done this, with either reg hack or whatever, let me know as this company is stuck.

cheers

shunty

can't add another scope....don't ask:rolleyes:

shunty

Remove the scope and recreate it..

Or do you have loads of static entrys?

Can you convert to a superscope?

Take it this is down the road?

David

Best bet looks like it may be delete the scope.. which you say you cant, but you can! :D Just back up the dhcp database etc first... + part of the reg.

then have a look at dhcpcmd at http://support.microsoft.com/default...EN-US;q232213& export the scope to a file.. then use the contents of this file to create a script that will re-create a new but extended scope with all reservations, exclusions etc.

Make sense??

David

Erm, here's why I'm confused:

http://images.cxi.org.uk/dhcp.jpg

NT 4 with SP4 (SBS 4.5 Box)

Daid, I did see that doc (honest), but not used it before & I am unsure, remember this is live.
yes it is down the road & they have numerous static entires & firewall rulebase tied in:rolleyes:, they have static's for clients as well, not just servers/print servers etc.

Chris - If you activate a scope in NT4, you can't just change the range, hence the prob.

whoever mentioned the superscope option, did you mean convert to superscope, then add another scope just up from the last one ??

cheers for the replies btw, escpecially as it's "bondy" night:D

shunty

Hmm why use DHCP to assign IP addresses when you have clients on static ones?

I thought the whole point in DHCP was to minimise confusion over what ip was where and ease of network neighbourhood config using dhcp options! I might be missing something though, so i'll shut up now.

Afaik the best way to do it is as david mentioned back scope up and re-create a larger one accounting for extra ip's as well. I have approx 250 workstations on the network i support all of which use DHCP, apart from the servers/proxy servers/routers etc.

Hope that helped?? :)

Quote "Hmm why use DHCP to assign IP addresses when you have clients on static ones?"

some clients require static IP's RB5, if they are running specialised software, financial stuff, sometimes it's legacy stuff that's tied into other machines etc, & nobody knows how to reinstall the software because it's 40 versions behind;) & has a dos interface:eek: (even though I am a command line guru;) gimme a GUI anyday)

cheers anyway though:)

ps - I have done this before with DNS & WINS (you can drop new databases in from foreign servers with a reg change), just not DHCP & I wanted to know if anyone has actually done it before. Looks like I might try it then.

shunty

That was an active scope on a production server.

{By active scope you mean serving out addresses?}

Theres very good reasons for using DHCP even if every device is reserved a static map. Anyone who's had to change the default gateway on 50 individually configured PCs in their younger support days would appreciate the ability to change the settings in DHCP once only.....

Deano

Because it makes it a damn site easier... I work in a team of 12/13 supporting 4500 users... we use 4x dhcp servers 2 per site with a superscope (mask of 255.255.240.0) we used to do static ip's now it's easier to do a reservation for a client.

Either way this doesnt sort the problem!

if you get really stuck.. drop me a mail at work and I'll waste some time on it!

David