Windows Server 2022 don't respond to DHCP inquiries over snmp after upgrade from Windows Server 2016

Hello

Thank you for posting in Microsoft Community forum.

Based on your description, here are some possible causes and solutions:

1. Ensure that the configuration of the SNMP service has not been reset or changed on the DHCP server. Check the configuration file of the SNMP service to ensure that the DHCP-related OIDs (e.g. 1.3.6.1.4.1.311.1.3.2) are still allowed to access. Confirm that the SNMP proxy is configured to allow requests from specific IP addresses, and make sure that the IP address of your monitoring tool is within the allowed range.
2. In Windows Server 2022, security settings may vary. Check the settings of Windows Firewall and any other security software to make sure that SNMP traffic is not blocked.

Ensure that the permissions for the SNMP service are set correctly, especially for DHCP related OIDs, specific permissions may be required to access.

3. Check whether the DHCP service depends on other services (such as RPC, WMI, etc.) and make sure that these services are also running normally. If there is a problem with these dependent services, it can affect the response of SNMP.
4. Looking at the logs in the Windows Event Viewer, especially those related to SNMP and DHCP, may provide more clues about the problem. Look for any error or warning messages that may indicate a problem with your configuration or service.
5. Ensure that the SNMP version you are using, such as SNMPv1, SNMPv2c, or SNMPv3, matches the configuration of the DHCP server. Some versions of SNMP may have different security and authentication requirements.
6. Try restarting the SNMP service and the DHCP service, sometimes the service may need to be restarted after the upgrade to load the configuration properly.
7. Make sure Windows Server 2022 has the latest updates and patches installed. Sometimes, a specific update may fix a known SNMP or DHCP related issue.
8. Use other SNMP tools (such as snmpwalk or snmpget) to test the OID directly from the command line to see if you can get DHCP related information. This can help confirm if the problem is with a specific monitoring tool.

I hope the information above is helpful.

If you have any questions or concerns, please feel free to let us know.



Regards,

Jill Zhou

I had this Error in Server 2012 and now after Migration to a Server 2022 again...

SNMP is fine working, but in the OID Tree from DHCP no respone...

This helps:

https://social.technet.microsoft.com/Forums/windowsserver/en-US/73c00321-496a-4898-ad5b-5ceb909610c7/snmp-oid-to-get-dhcp-scopes-from-2012-server?forum=winserver8gen

>> one else found a workaround for this, and I thought I'd share:

>> On the DHCP server,:

>> - Disable the SNMP service.

>> - Create a Scheduled Task, set it to run at startup of the server, use SYSTEM (not a domain user), start snmp.exe

>> - After doing this, I'm able to monitor my DHCP scopes via SNMP...

I had this Error in Server 2012 and now after Migration to a Server 2022 again...

SNMP is fine working, but in the OID Tree from DHCP no respone...

This helps:

https://social.technet.microsoft.com/Forums/windowsserver/en-US/73c00321-496a-4898-ad5b-5ceb909610c7/snmp-oid-to-get-dhcp-scopes-from-2012-server?forum=winserver8gen

>> one else found a workaround for this, and I thought I'd share:

>> On the DHCP server,:

>> - Disable the SNMP service.

>> - Create a Scheduled Task, set it to run at startup of the server, use SYSTEM (not a domain user), start snmp.exe

>> - After doing this, I'm able to monitor my DHCP scopes via SNMP...

OK, so that worked, but why?? I'm glad this got it working but it's an odd workaround to have to perform.

I had the same issue and I think I solved it.

As I assume it, you installed the SNMP Role before adding the DHCP Role to the server. This causes the dhcp MIB-Data not to be correctly installed. Remove the SNMP-Role from the server and reinstall it. (Server needs a reboot inbetween)

Then the DHCP Scope should be visible through SNMP again. Worked for me on all DHCP Servers I had this issue on.

Cheers!

I had the same issue and I think I solved it.

As I assume it, you installed the SNMP Role before adding the DHCP Role to the server. This causes the dhcp MIB-Data not to be correctly installed. Remove the SNMP-Role from the server and reinstall it. (Server needs a reboot inbetween)

Then the DHCP Scope should be visible through SNMP again. Worked for me on all DHCP Servers I had this issue on.

Cheers!

I have the same issue.

I also removed and re-install SNMP feature. That seemed to solve the issue but after the server rebooted again, the same issue came back. This cycle continues. There must be some other reason causing this issue.

Disabling SNMP service and run C:\Windows\System32\snmp.exe (pc-nico 's workaround) fixes the problem. However, I think the solution should not be something like this. Seems to be related to service..

Regards,

Oguzhan