a. There is no easy way. But you can do some troubleshooting to try to find out where it resides.
b. Note down the ip address of the legitimate DHCP server on your network. (cmd ipconfig/all) Take a couple of test workstations, from cmd you can do release/renew multiple times and see if the DHCP server ip changes to one that not the legitimate DHCP server.
c. So now that you know the ip of the rogue DHCP server, ping the ip from the switch. Then do a show arp . This will map the ip to a mac-address. Then do a show mac-address-table <>. This will map the mac-address to a port. Go on to the next networking device till you find the port the DHCP server is connected to.
d. Additionally, you can try to configure DHCP snooping which can prevent rougue DHCP servers to reply to DHCP requests.
Just to add on to what Sid already said. DHCP snooping will report where these rogue servers are. We support it on just about all of our switches, so likely its an option...and overall its really easy to configure...even if you are just configuring it for an evening to find out where these rogues are.
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.