Our problem is similar to the one in the thread below on 11/25 talking
about
"error = 24", but following the suggestions in that thread did not
help. I
will try to be as specific as possible; we are getting desperate
trying to
solve this.

I won't use our actual IP addresses in my explanation, but instead
will
substitute fake ones that will illustrate our problem.

NW65 DHCP server bound to 192.168.164.183. We want to manually assign

addresses on the following subnets:

192.168.164.x
192.168.166.x
192.168.167.x

We created a subnet pool that contains the above subnets.

We created a manual assignment of 192.168.164.173 (this is on the same

subnet as the server) for a workstation. That worked fine. We then
deleted
this assignment, and created another manual assignment to the same MAC

address, but this time we used 192.168.166.174 for the address.
Looking at
the DHCP server debug screen, we get the message:

48 : Get type:4, IPAddr:0.0.0.0, LeaseTime:0, MacIndx:462,
pIP:B62DF5A0
old pIP addr: 192.168.166.174 is MANUAL cannot be deleted.
AMAGet() exit err:24, subnet:192.168.164.0, addr:0.0.0.0
2003/12/04 09:04:57 <DHCPDISCOVER> packet received from client<0:C0:F0:47:3D:51>.
2003/12/04 09:04:57 Error code = 24 after DHCPSRVR cache has
been
queried for client <0:C0:F0:47:3D:51>.

If we delete this assignment and go back to ANY address on the
192.168.164
subnet, all is well again. We have tried all 3 options on the DHCP
server
options screen (relating to mobile users). All this does is change
the
error message. Any ideas? Do we need to bind an IP address from each
of
the 3 target subnets to the DHCP server? Is this even possible?

Any help would be GREATLY appreciated.

Stan