Damian Gardner
asked on
Clients no longer able to receive IP addresses from the primary DHCP server
What would cause a DHCP server to stop handing out IP addresses to a subnet? We have a single DHCP server that handles two different subnets - 1 & 2, that are on different VLANS on our network. After working for several months, clients that originally have an IP leased from "subnet 1", began having trouble getting an IP assigned automatically from "subnet 2" - they just sit dormant, retaining the bad IP from the other "subnet 1". To our knowledge, nothing has changed on the network - although something MUST have changed, somehow. Again - this had been working fine for some time...and then stopped. Any suggestions is much appreciated.
Update: I checked the DHCP server log, and I can see it is handing out IP's for subnet 1 to client requests coming from subnet 2. This is the problem, but I do not know why its doing this.
Update: I checked the DHCP server log, and I can see it is handing out IP's for subnet 1 to client requests coming from subnet 2. This is the problem, but I do not know why its doing this.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Could it somehow be related to the existing lease for this test machine I'm using - there is a lease on "subnet 1" that exists. this is the IP that the server keeps giving the machine, even when its on subnet 2. Could the lease somehow be "locking the machine in"??
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I'm engaging Microsoft on this. will let you know what the problem was.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Dr Dave - thanks for your replay. Assuming that this IS what's happening, how do I counteract that? Also - its interesting that this process of clients walking back and forth between buildings here (different VLANs), has been working ok for atleast a few months (since November) when we installed the new leg of the network. It just suddenly stopped working.
Assuming that this IS what's happening, how do I counteract that?That is a good question. I'm afraid I don't have an answer off the top of my head, but I'll see if I can come up with something. No changes were made to the network infrastructure around the time the issue started?
ASKER
thanks for your help guys. problem turned out to be due to the scopes being included in a superscope. we don't know how that happened. thanks again
ASKER