These parameters essentially determine the image of your conventional “network environment”. For this purpose, “NetBIOS over TCP / IP” required - Do not you think? - Then turn off but please times “NetBIOS over TCP / IP” and see the contents of your “network environment” on.
HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services \ NetBT \ Parameters
Remark on older operating systems:
Older operating systems are ignoring parameter able. So seems NT4 (workstation) as did not respond to the Name Server Query Count parameters. The default value is 3. Changing this example, 1, NT4 nevertheless makes 3 request cycles. BcastNameQueryCount contrast, is accepted without hesitation. Higher operating system versions do not show this behavior in the name of service parameters.
BcastQueryTimeout: 750 (milliseconds)
NameSrvQueryTimeout: 1500 (milliseconds)
How is the request behavior of a WINS client; Node Type: 8?
A resolution is complete when it is “successful” or Timeout`s are “unsuccessful” expired with the result.
How long something takes in case of non-resolution? First, a WINS server request, after three broadcast requests to a desired name. If things go well, the customer places the requests in a timely manner from succession.
The three-time output of the request on the broadcast increases the chance that it will be “heard” by another device and this responds.
Case A: The WINS server is configured and is fast response.
The times from NameSrvQueryTimeout is negligible -
The determining factor will BcastQueryTimeout (between 750 ms - 2250 ms) per search operation.
Case B: The WINS server is configured and can not respond positively.
Now add yet added the times from NameSrvQueryTimeout to BcastQueryTimeout.
Is it possible to visualize Wins requests over time?