The WINS server completed the burst handling of incoming requests because the queue length became a quarter of what it was when burst handling began.
The WINS Scavenger thread could not scavenge a record. This record will be ignored. The Scavenger will continue on to the ...
The WINS server %s denied the replication request because the current WINS server is not listed among its replication partners. ...
The WINS server can use multicast to automatically configure itself for replication. Use this option only on small networks. ...
The WINS server cannot make or accept this connection since the connections limit has been reached. This situation is temporary ...
The WINS server completed the burst handling of incoming requests because the queue length became a quarter of what it was ...
The WINS server received a pull request from the non-configured WINS server with the address, %1. The WINS server rejected ...
The WINS server received an update notification from the non-configured WINS server at the address, %1. The WINS server rejected ...
The WINS server started the burst handling of incoming requests. WINS does this to handle a sudden increase of incoming requests. ...
The WINS server you specified cannot be located. The WINS server might be down, there might be network problems, or the WINS ...