Hello everyone,I have an issue that I'd like to run by everyone:Enviornment:Windows Server 2003 running DHCP. The server is addressed with 192.168.1.7 /24. It is running two scopes - one for 192.168.1.0 /24 and one for 192.168.2.0 /24. It's gateway is 192.168.1.1.The router is configured with two interfaces. interface1 is configured with 192.168.1.1 and interface2 is 192.168.2.1. Also, interface2 is configured with a relay agent that points to 192.168.1.7.GoalThe goal is for this one dhcp server to server several subnets.IssueWhen a client connects to interface 2, it gets an address from the 192.168.1.0 scope. It should be getting an address from 192.168.2.0 /24.I have configured this in other environments and it wasn't necessary to configure any kind of superscope. The server "just knew" which addresses to give to who.Questions1. Is this considered a superscope? I have read a number of suppport.microsoft.com articles and those make superscoping sound like a different scenario. But, maybe I am wrong.2. How should the server know which pool to pull from?3. Any other suggestions?/I am also troubleshooting and researching this issue on the router side. But, am asking you all to address it it from the server side.Thanks,Ben

Hello,What type of router are you using?Is it also acting as a firewall?

Hello, Thank you for your post here. 1. Not necessary. 2. The address in the gateway IP address field (GIADDR) will be used to identify the DHCP scope from which to offer an IP address lease. The gateway IP address field (GIADDR) should be attached in the DHCP request when the router relay the request. Understanding relay agents http://technet.microsoft.com/en-us/library/cc779610(WS.10).aspx 3. For further investigation, please capture the network trace on the DHCP server to verify the parameters in the DHCP request. If you have any questions or concerns, please do not hesitate to let me know.