Closed kistelek2 closed 9 months ago
Thanks for the details. From the netstat output, it looks like 67xx ports belong to the DNS server's UDP socket pool. So the DNS server's process ID seems to be 8396.
UDP 192.168.1.254:67 : 5108
There seems to be another process with ID 5108 that is occupying UDP port 67. This looks like the reason why the DHCP scope is failing to activate.
I would suggest to run the netstat command again and the match the process ID with tasklist
command and find out which process is actually using the UDP port 67.
FIxed. Suffered from Idiot Operator error. Had 2 DHCP servers accidentally running on same box. Thanks.
Good to know you got it fixed.
DHCP stopped working last night after Windows11 host updated and rebooted. DNS works fine. Backed update out. No change. Service starts but doesn't enable scope. Manually enabling scope adds correct interface address on gui but still doesn't serve address. Posted on Reddit.
C:\Windows\System32>netstat -ano | find ":67" TCP 127.0.0.1:6789 0.0.0.0:0 LISTENING 5108 UDP 0.0.0.0:6700 : 8396 UDP 0.0.0.0:6749 : 8396 UDP 0.0.0.0:6750 : 8396 UDP 0.0.0.0:6761 : 8396 UDP 0.0.0.0:6792 : 8396 UDP 192.168.1.254:67 : 5108