Preacher Man said:
In studying for 70-216 I am having a conflict of information about how often
a WINS client will renew. One place says that at 1/2 of the TTL if the
primary WINS is not available it will continue every 10 minutes. Another
place says every 2 minutes until half of the TTL is expired.
I think you are misreading it -- or misreporting it:
It tries to renew AT 50% of the TTL or Renew interval
(given it by the WINS server when it registered.)
Probably a different default for different operating systems.
As the article below says one place:
"Other [not NT] client stacks may refresh at different frequencies"
Hint: You are overinvolved in unimportant details
when it is better to understand how things like browsing
take advantage of WINS server in multi-subnet networks.
For finding answers to this issue:
Google:
[ "wins server" client renewal ttl | "Renew interval"
site:microsoft.com ]
This one is pretty complete but has WAY more detail than
you need (for the test or daily life either one):
Windows Internet Naming Service (WINS):
Architecture and Capacity Planning
<
http://www.microsoft.com/ntserver/techresources/commnet/wins/winswp98/wins03-12.asp?bPrint=True >
Why is WINS important even with Win2003 networks?
(When is it not needed?)
What's the biggest error most people make with WINS
servers from a client perspective?
What about those people who have more than one WINS
server?
What's the different (the REAL difference) between
a pull and a push partner?
Why would someone setup two WINS servers across
a WAN (from each other) as PULL partners of each
other ONLY?
[/QUOTE]
