Yesterday I found that my server, a DELL PowerEdge SC440, repeatedly beeped. Very annoying and concerning, because beeping usually means hardware fault. I did some diagnostics and could not find anything out of the usual, so I rebooted the server and noticed, that the beeping seemed only to occur whenever Windows Server 2003 was up and running.

Using Task Manager I noticed that my DynDNS service was using more CPU than usual and that my indexing service did the same. Although stopping the indexing service did not solve the problem, stopping the DynDNS service did.

Apparently the DynDNS service beeps, whenever it fails, unfortunately it does not leave any message about this in the event log. I upgraded the DynDNS service to the latest version and the problem went away. I do not know, what DynDNS have changed, but my service was unable to update DNS until it was upgraded.