Router – Laptop being assigned IPv4 address out of router’s DHCP range

The only thing needed for static IP assignment from DHCP is the MAC address. The other items must be there for administrative convenience. I have found it easier to use Excel or a wiki page, "hard code" the static devices, and take the static IP ranges out of the DHCP pool.

Now, there is no convenient way to have a "primary" and "backup" DHCP servers, particularly with low end gear. I don't think it will work as you are expecting, and you will see random confusion in IP addresses.

It also looks like you are over-thinking the IP protocol, pre-assigning too many statics and leaving the DHCP space too small. Are you really going to have 126 fixed IP devices? I would have 1-60 set as fixed, 61-254 on DHCP. Having a DHCP server with no free addresses is a tough problem to fix on the fly.

My suggestion is to put the wireless devices on a separate subnet and have the WRT54G serve DHCP and do NAT. An alternative is to have the RV082 be the DHCP server and have the WRT54G proxy DHCP requests and not do it's own DHCP.

My understanding has always been that the Windows DHCP service will shut itself down if it detects the presence of another DHCP server on the network. As a first step, I would suggest shutting down the Linksys DHCP component and using only the W2K3R2 server as the DHCP server. Make sure the server and scope are configured correctly and reboot one of the affected client computers and see what happens. In addition, you can install and run a packet capture program on the DHCP server (and client if needed) and capture network traffic to see what DHCP traffic is being receieved and sent by the server and the client.