Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
Could not bind an address to a socket. This might mean that the "nameserver" port (specified in the services file) which is used as default by WINS for replication and discovering other WINSs has been taken by another process/service running on this computer. You have two options - either bring down that other process/service or direct WINS to use another port. If you choose the second option, set the value "PortNo" (REG_DWORD) under Wins\Parameters key in the registry to 1512.
NOTE however that changing the port no. this way will prevent this WINS from replicating/discovering other WINSs unless they too are directed to use the same port no. as this WINS.
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is the role of the WINS service?
What is a DWORD?
|Our approach: This information is only available to subscribers. An example of Our approach|
We worked around this issue by starting the Wins service before DNS (or stop DNS, start Wins and restart DNS).
A more permanent way of making sure that Wins starts before DNS would be to make the Wins service a dependency of DNS. Modify the DependOnService registry value under
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DNS - add Wins to the
existing list of services. Use the REGEDT32 registry editor to modify this
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated