You have the Microsoft DNS server configured as the ip helper address on the 10.1.21.1 interface?
Main Topics
Browse All TopicsI'll keep our problems description simple at first. Ask questions and I'll try to add more.
We have 2 core 4510s, which feed via fiber other buildings, their cores are 3750s, these are either stacked or fiber connected to other 3750s or 3560s.
Originally the core 3750s were configured to hand out DHCP. Because of a network access appliance we were forced to go central on our DHCP, so we started up 2 Microsoft DHCP server. This has been set up with a single Superscope and 50 scopes underneath. Each scope has a single class C pool, server options include: Router, DNS Servers, DNS name, and WINS. The Cisco Switches have had the DHCP removed and IP helper statements have been added to the port configs.
Let me add, all Windows XP SP3 shop. Here is the issue. Now when a user moves from one scope to another, the PC will not let go of their address. A simple /release /renew will not do anything, Deleting the DHCP entry won't do anything, removing the DNS records will not do anything. The only Event view that I get that may mean anything is:
Event Type: Error
Event Source: Dhcp
Event Category: None
Event ID: 1002
Date: 1/8/2009
Time: 9:24:12 AM
User: N/A
Computer: ISD622-784F7B37
Description:
The IP address lease 192.168.11.23 for the Network Card with network address 0000F08504FB has been denied by the DHCP server 10.1.21.1 (The DHCP Server sent a DHCPNACK message).
This would be an example of the PC moving from the .11.X scope to the .21.X scope. The 10.1.21.1 server it's referring to was the Cisco 3750 that used to dole out addresses, now all commands have been removed and the switch rebooted.
Ideas??
Shane
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
We are a switched network, no routers. Here is the snippet from the switch referring to the .21.X Vlan and then the .11.X Vlan.
interface Vlan201
ip address 192.168.21.2 255.255.255.0
ip helper-address 192.168.252.3
ip helper-address 192.168.10.235
no ip redirects
standby 201 ip 192.168.21.254
standby 201 preempt
interface Vlan201
ip address 192.168.11.2 255.255.255.0
ip helper-address 192.168.252.3
ip helper-address 192.168.10.235
standby 201 ip 192.168.11.254
standby 201 priority 90
standby 201 preempt
I have seen this before with superscopes. Have you tried creating separate scopes instead? Also, you can not specify the router at a server level, as each subnet will have have different first hop router. Here is what I suggest:
1) Remove the superscope
2) Create Individual Scopes for Each Subnet
3) Set the Router as a Scope Option rather than a Server Option
4) Set the DNS domain name, DNS and WINS servers as Server Options
I realize this will be time consuming in an environment with 50 scopes, so you may just want to remove two of your subnet from the superscope and test with them initially before implementing this throughout the entire environment.
Let me know if that helps.
Thx
GED125
Business Accounts
Answer for Membership
by: devinnoelPosted on 2009-01-08 at 11:30:59ID: 23329055
Do the routers have IP helper enabled? DHCP requests can't cross a router, so need help. You need to enable IP helper on the routers and tell IP helper where to forward the DHCP requests to.
rcd/cc/td/ doc/produc t/software / ssr83/rpc _r/48383.h tm and search down the page for "ip helper".
Check http://www.cisco.com/unive