Microsoft DHCP windows 2000

[RichP]

Got a windows 2000 server, two of them, running dhcp. needed to change the scope, was 10.1.4.100 - 10.1.4.200, changed it to 10.1.4.170 - 10.1.4.210.
Changed the lease time to 3 hours, figured the server would force a renew into the new scope range. Nothing, restarted the DHCP server, the secondary server updated but the workstations are still keeping the old address.
I did go around to several of them and manually gave them a new address in the new scope/range as a hard address then switched them back to dhcp and it stuck [except of course on the ONE vista machine, figures], the new ones show up in the dhcp server leases but I'm wondering if I missed something. I even got everyone to power off their workstations on friday, figured it would clear out any cache or arp tables, so WTF... I don't feel like walking around and manually having to do this on the remaining ones.

 

[kastein]

If you can push out scripts to all the systems, just script them all to run ipconfig /release ipconfig /renew (and for good measure because they need it anyways) ipconfig /flushdns

If you can't, I'd just support the old range till they've all run out of time on their leases naturally. This is why I always set my DHCP servers to give ~1 hour leases; DHCP is not enough of a load on the server for me to care about the extra traffic.

 

[ehall]

they'll keep the previous lease for at least half the time of the previous lease, the new lease doesn't change the old one

 

[RichP]

If you can push out scripts to all the systems, just script them all to run ipconfig /release ipconfig /renew (and for good measure because they need it anyways) ipconfig /flushdns

If you can't, I'd just support the old range till they've all run out of time on their leases naturally. This is why I always set my DHCP servers to give ~1 hour leases; DHCP is not enough of a load on the server for me to care about the extra traffic.

Nope, tried that, release renew, even this laptop which has not been plugged into my network here at famous picked up an old address. The only thing that worked was to hard assign an address in the new scope, apply it then once it 'took' change it to dhcp and then it shows up on the server leases but not before then, it also renews to the correct one after that. The servers are also active directory, DNS and DHCP, one primary the other backup.

 

[kastein]

:soapbox: windows :soapbox:

(yeah I know I know)

Had another issue something like this back in the day, I had a gigabit private network set up between all the systems in the dorm I was living in so we could game without lag and stuff... all addresses on the private network were statically assigned from 172.16.0.0/16. Each system had two ethernet interfaces, with one going to the school's residential network and the other going to our private network. res-net was DHCP allocated. Every windows system worked great till they rebooted for the first time with everything hooked up... for some idiotic reason, the windows network stack was assuming that the statically assigned interface was more important (but only once rebooted), and pushing the default route across it. Obviously this went absolutely nowhere...

Turns out there is a way to fix this now, but it was another idiotic default setting and it annoyed the crap out of me. I ended up fixing it by throwing ISC DHCPD on one of the random FreeBSD boxes I had around and assigning the IPs for the private network using DHCP as well.

 

[RichP]

:soapbox: windows :soapbox:

(yeah I know I know)

Had another issue something like this back in the day, I had a gigabit private network set up between all the systems in the dorm I was living in so we could game without lag and stuff... all addresses on the private network were statically assigned from 172.16.0.0/16. Each system had two ethernet interfaces, with one going to the school's residential network and the other going to our private network. res-net was DHCP allocated. Every windows system worked great till they rebooted for the first time with everything hooked up... for some idiotic reason, the windows network stack was assuming that the statically assigned interface was more important (but only once rebooted), and pushing the default route across it. Obviously this went absolutely nowhere...

Turns out there is a way to fix this now, but it was another idiotic default setting and it annoyed the crap out of me. I ended up fixing it by throwing ISC DHCPD on one of the random FreeBSD boxes I had around and assigning the IPs for the private network using DHCP as well.

Yes, I have been eyeing a linksys router on my parts shelf that has ddwrt installed all morning, mulling it over.

 

[JNickel101]

Did you go into DHCP and kill the old addresses/leases before you created the new scope? No funky subnetting going on, right?

 

[WB9YZU]

We need a new sub forum for Rich so he can ask work related Tech questions.



Ron

 

[RichP]

Did you go into DHCP and kill the old addresses/leases before you created the new scope? No funky subnetting going on, right?

No I just changed the range of the IP's being assigned. Should be a simple thing no ?
As for asking questions, gotta figure that during the day it's people like me, systems and network people, who are mostly on here though now that finals are just about over in most colleges there will probably be more students on here now.