Devices not reaching the DHCP server... bad switch gateway to blame?
-
DHCP Renewals appear to be working just fine from anywhere. New DHCP Leases appear to never work, possibly not for a week or more. It is only that today there are new things going onto the network.
-
Looked at the logs, there does not appear to be any issues with the pool being exhausted. Both logs and manually looking at DHCP Service confirm that IP addresses are available.
-
Could you pinpoint the place where the packets get dropped? Wireshark before / behind the switch?
-
@thwr said in Devices not reaching the DHCP server... bad switch gateway to blame?:
Could you pinpoint the place where the packets get dropped? Wireshark before / behind the switch?
Potentially, I just mentioned that on the call as a potential next step.
-
@scottalanmiller said in Devices not reaching the DHCP server... bad switch gateway to blame?:
@thwr said in Devices not reaching the DHCP server... bad switch gateway to blame?:
Could you pinpoint the place where the packets get dropped? Wireshark before / behind the switch?
Potentially, I just mentioned that on the call as a potential next step.
Probably your best bet. Don't know the Netgears or how smart (dumb) they are, but you never know.
-
Is this a wired or wireless connection through this switch having a problem?
I wonder if there is a latency issue on that specif cable?
tried restarting the DHCP service - Gene said it's on the same device as the gateway, so probably not a windows box.. so might require a reboot of the whole gateway.
-
@Dashrender said in Devices not reaching the DHCP server... bad switch gateway to blame?:
Is this a wired or wireless connection through this switch having a problem?
I wonder if there is a latency issue on that specif cable?
tried restarting the DHCP service - Gene said it's on the same device as the gateway, so probably not a windows box.. so might require a reboot of the whole gateway.
Wired for sure, but AFAIK eveyrthing has been tested at this point.
-
@Dashrender said in Devices not reaching the DHCP server... bad switch gateway to blame?:
tried restarting the DHCP service - Gene said it's on the same device as the gateway, so probably not a windows box.. so might require a reboot of the whole gateway.
It's not. It's on the main AD server along with AD and DNS.
-
@Dashrender said in Devices not reaching the DHCP server... bad switch gateway to blame?:
I wonder if there is a latency issue on that specif cable?
We thought that that was the case, but appears not to be.
-
@art_of_shred said in Devices not reaching the DHCP server... bad switch gateway to blame?:
I should note that the gateway and DHCP server are one and the same.
I mispoke.. it was Art, not Gene.
-
Scope out of IPs?
First thing I would check if renewals work but new isn't
-
@Dashrender said in Devices not reaching the DHCP server... bad switch gateway to blame?:
What does STP have to do with this? Clearly the PC isn't a loopback to the switch.
by default STP on most switches puts ports in blocking mode then in fowarding mode after it checks it. RSTP does a better job of handling and fowards first then checks and blocks if need. if you don't enable rapid-pvst on most cisco switches you will have issues with DHCP once in a while but you will always have issues with PXE etc.
-
Have you restarted the DHCP server? It's hosted on a Windows box I wonder if there is some rot or an update that needs to be applied.
-
Maybe sure the Whitelist isn't enabled on the DHCP server.
-
@scottalanmiller said in Devices not reaching the DHCP server... bad switch gateway to blame?:
@Dashrender said in Devices not reaching the DHCP server... bad switch gateway to blame?:
tried restarting the DHCP service - Gene said it's on the same device as the gateway, so probably not a windows box.. so might require a reboot of the whole gateway.
It's not. It's on the main AD server along with AD and DNS.
how is a DC the default gateway?
-
Looks like split brain. That's a guess.
-
@Jason said in Devices not reaching the DHCP server... bad switch gateway to blame?:
@scottalanmiller said in Devices not reaching the DHCP server... bad switch gateway to blame?:
@Dashrender said in Devices not reaching the DHCP server... bad switch gateway to blame?:
tried restarting the DHCP service - Gene said it's on the same device as the gateway, so probably not a windows box.. so might require a reboot of the whole gateway.
It's not. It's on the main AD server along with AD and DNS.
how is a DC the default gateway?
It's not. No relationship.
-
I was having a brain fart when I said the gateway was the dhcp server. The primary dc is the server. It ended up being that it was set up to failover to a secondary dc (dhcp, that is) but the config wasn't completed on the second dc. It must have tried to failover and got stuck. It would renew leases just fine, but no new leases handed out. Removed that config and it recovered instantly. Problem solved.
-
@art_of_shred said in Devices not reaching the DHCP server... bad switch gateway to blame?:
I was having a brain fart when I said the gateway was the dhcp server. The primary dc is the server. It ended up being that it was set up to failover to a secondary dc (dhcp, that is) but the config wasn't completed on the second dc. It must have tried to failover and got stuck. It would renew leases just fine, but no new leases handed out. Removed that config and it recovered instantly. Problem solved.
It's easy enough to have them sync their configs to keep failover setup. works great for reboots and such.
-
@Jason said in Devices not reaching the DHCP server... bad switch gateway to blame?:
@art_of_shred said in Devices not reaching the DHCP server... bad switch gateway to blame?:
I was having a brain fart when I said the gateway was the dhcp server. The primary dc is the server. It ended up being that it was set up to failover to a secondary dc (dhcp, that is) but the config wasn't completed on the second dc. It must have tried to failover and got stuck. It would renew leases just fine, but no new leases handed out. Removed that config and it recovered instantly. Problem solved.
It's easy enough to have them sync their configs to keep failover setup. works great for reboots and such.
True, but it was even easier to remove the config on the dc that wasn't even in use.
