Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

DHCP User Experience Monitor - Unexpected error occurred

I just added the DHCP User Experience Monitor to all three of my DHCP servers and received the following error "Unexpected error occured. DHCP server X.X.X.X:67 not respond"

Any idea what the issue might be? Obviously the DHCP server is up & running and issuing leases to clients.

DHCP_Error.jpg

Find more posts tagged with

Accepted answers

MikeAsthalter

Please see the Knowledgebase Article at:

http://knowledgebase.solarwinds.com/kb/questions/1951/

Mike

All comments

aLTeReGo

Just for giggles, here's the netstat output from one of my DHCP servers

netstat.jpg

Peter.Cooper

Did you see any interesting windows events on the DHCP server?

Edit: Also, c:\windows\system32\dhcp\dhcpsrvlog-*.log should contain some useful data. Have a peek at the most recently updated log and have a look for events - Event Id 14 & 15 comes to mind.

aLTeReGo

Ok, so it would seem that the DHCP user experience monitor only works if your Orion server is on the same subnet as your DHCP server. Please correct me if I'm wrong.

It would certainly be nice if the relay agent IP address was populated with the IP address of the Orion server, or if the giAddr was populated with the router IP address that the Orion server was on (Cisco ip helper-address) so that the entire DHCP process was able to complete correctly cross-subnet. Right now the DHCP user experience monitor is a somewhat dangerous tool, as I leaned when I discovered that it had consumed all available DHCP leases on the subnet of the DHCP server. Not a big deal in my case since this address space isn't being used anyway, but someone in a similar situation may find this monitor consumes all available IP addresses on a subnet where the address space is being used for something important. Just a thought.

So in the end it appears that for me, the DHCP User Experience Monitor is pretty much useless in its current form.

aaron_daniels

So in the end it appears that for me, the DHCP User Experience Monitor is pretty much useless in its current form.

+1 For us as well. Please SW, include the relay agent IP address...

Aaron

travellermimi

Is there a DHCP relay involved in the matter above?