Network switching with Windows 2003 DHCP

I try to switch from network 1.1.1.0/24 to 2.2.2.0/24 as follows:
Existing win 2003 server with DHCP server has ip 1.1.1.1
added secondary ip address to it: 2.2.2.1
added new dhcp range 2.2.2.0/24 , configured options, reservations etc.
Changed the max lease time from several days to a few minutes  and waited for the setting to propagate to clients
So far so good.
To switch networks I then disabled the old range 1.1.1.0/24 and enabled 2.2.2.0/24
According to log, all old renewal requests fail (NACK), also after the max lease time. In fact it appears that the clients sooner or later give up. I don't see any leases issued by the new range at all.
After much more thanmax lease time, I disabled the new range and enabled the old range again; almostimmediately clients started to query and successfully obtain old range leases.

Why did the transition fail?
LVL 20
thehagmanAsked:
Who is Participating?
 
Steve KnightConnect With a Mentor IT ConsultancyCommented:
In properties of the DHCP server, advanced tab there is a "bindings" button.  Maybe it is not bound to the other  address on there?   Other way may be to swap primary/secondary address on your IP settings.

Steve
0
 
thehagmanAuthor Commented:
Addon:
I'm beginning to have a suspicion:
Even though the server has the ranges 2.2.2.0/24 and a corresponding secondary) ip 2.2.2.1 the dhcp server *listens* only on 1.1.1.1 and hence can only serve a lease from 1.1.1.0/24 (which is disabled).
Could tis be the cause?

If I don't find a nice idea here, I'll try to fool the system by configureing one of the switches with an ip-helper-address, i.e. a BOOTP relay from 2.2.2.0/24 to 1.1.1.1


0
 
Steve KnightIT ConsultancyCommented:
What does
netstat -an | find ":67 "
show ... itshould show the UDP port 67 for DHCP.
0
Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
mcsweenSr. Network AdministratorCommented:
I think dragon-it has it with the bindings issue.
0
 
thehagmanAuthor Commented:
Yes, the binding shows only the primary IP. (Though IIRC, netstat showed 0.0.0.0:67 !)
0
 
Steve KnightIT ConsultancyCommented:
Great, odd about the netstat though, I guess it was listening but ignoring?!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.