Setup-Windows 2003 Standard Edition Domain Controller holding FSMO\nroles running DHCP, DNS, and WINS.\n\nThe Microsoft propaganda that I've come across suggests that DHCP\nSuperscopes are best utilized when you have several logical networks\nrunning across the same physical segment.\n\nI.e. if you have 5 VLans running on one wire- it becomes appropriate to\nutilize superscopes.\nSo here is the problem I'm having. The layer 3 router which routes\nbetween the VLans is appropriately setup. We are utilizing the DHCP\nhelper command in the router to forward all DHCP requests to our\nserver. This seems to work fine *most* of the time. Spontaneously a\nfew systems seem to get stuck in this rut of being unable to contact\nthe DHCP server. The DHCP server shows a NACK in the log file. The\nresolution has been to delete the lease on the DHCP server and change\nthe VLAN of the port that the system is connected to. This has been\nthe only way to solve this problem.\n\nAlternatively we removed the affected scope from the superscope and the\nproblem goes away. Why are we having this problem if the scope is\ncontained in the Superscope? Why would the DHCP server be sending a\nNACK on the VLAN? Isn't this the point of a superscope? Is it\nnecessary to use the Superscopes? What's the freaking point of a\nsuperscope? Why if we have 7 subnets /VLans only one or two are\naffected? Why if we have 400 pcs only 20-30 affected? Why doesn't\nMicrosoft have better logging capabilities on DHCP Server? Why won't\nBill Gates loan me 0,000?