With the current low prices for servers and the need for processing power, even a small company may end up with quite a few of them. If ten years ago it was still common to see an entire company using just one server, these days that's no longer the case.
New computers are added to the network with the understanding that they will be taken care of by the admins. Keeping an eye on these servers is a tedious, time-consuming process. Even with 5 minutes per server (to check the logs and other parameters), it may take an hour to make sure that everything is ok and no "red lights" are blinking on any of the servers.

Comments:EventID.Net
As per Microsoft: "WINS binds to the first adapter in a computer with more than one adapter bound to TCP/IP. Check the binding order of adapters and make sure the first one has a valid IP address for the WINS server". See MSW2KDB for additional information about this event.
x
3

EventID.Net
As per Microsoft: "This issue can occur if your computer does not have a network adapter that is enabled and configured with a valid Transmission Control Protocol/Internet Protocol (TCP/IP) address". See ME240708 for more details.
x
3

EventID.Net
As per ME328377, this error is due to "a problem in the code" when there are more than 14 network adapters. The number may seem high, but it is possible when using virtual adapters, like VPN connections.
"To resolve this problem, install the hotfix that is described in the Microsoft Knowledge Base article 318419. To work around this problem, use 13 or fewer network adapters."
x
5