General discussion

Locked

Calling all WINS gurus

By carl_ramkarran ·
Is the role of the Primary and Seconday WINS severs similar to that of DNS in which if a name resolution can not be attained from the Primary it will then try the Secondary. Or is the role of the secondary ONLY to provide another WINS server to contact if the Primary is unreachable (ie down or off network).

This conversation is currently closed to new comments.

9 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Calling all WINS gurus

by calves In reply to Calling all WINS gurus

The idea of having a primary and a secondary WINS database, is so that you create redundancy. Should one WINS server be down, the request tries the second WINS, just like DNS. It's possible to have entries in one WINS and not in the other, for thissetup will not have a syncronization in place or depending on the lenght between syncronizations, it has not happened, yet.

I hope that answers yout question!

Collapse -

Calling all WINS gurus

by carl_ramkarran In reply to Calling all WINS gurus

Poster rated this answer

Collapse -

Calling all WINS gurus

by SyscoKid In reply to Calling all WINS gurus

Commonly a computer has a Primary and Secondary WINS address configured in the TCP/IP setup. If the Primary WINS does not respond to the registrations, the computer tries the Secondary WINS.

See here: http://www.neohapsis.com/resources/mskb/q150737.htm

Collapse -

Calling all WINS gurus

by carl_ramkarran In reply to Calling all WINS gurus

Poster rated this answer

Collapse -

Calling all WINS gurus

by Tony Hogan In reply to Calling all WINS gurus

Actually a little of both. It asks the primary for name resolution - if it does not respond -or- gives a negative name response, it asks the secondary WINS server [like DNS name resolution]. Here's a twist/issue on this - if the secondary resolves the name, the client will switch the primary and secondary WINS servers so that the client now uses the original secondary as its primary. If you view the TCP/IP properties on the client it will still show the original configuration; however, if you view the TCP/IP configuration through either Ipconfig.exe or Winipcfg.exe it will display the WINS servers switched.

Why is this a twist/issue? If the secondary is across a slow LAN or WAN link, after the server settings are switched, all the nameresolution and registration traffic for the client is going across the slower connection.

-tony

Collapse -

Calling all WINS gurus

by carl_ramkarran In reply to Calling all WINS gurus

Poster rated this answer

Collapse -

Calling all WINS gurus

by ustutz In reply to Calling all WINS gurus

Additinal notes:

On the client you have to enter both a primary and a secondary WINS IP address (either hard coded under network properties or pushed dynamically via DHCP). If you have only one WINS, enter it twice.

On the WINS server set both primary and secondary addresses to itself.

Primary and secondary WINS are actually determined at boot time: The WINS server (of the two identified) that responds first will be the primary server for this session. The WINS client (PC/Workstation/non-WINS server) will then register itself with that WINS server.

If replication is set up and working both WINS server have access to the same database (a merged database of both servers' data).

Unlike DNS, WINS runs on a dynamic database (also static mappings are possible), where clients register themselves. Also WINS has additional mappings (for NT services and users) beyond the scope of DNS.

OK, this was the quarter answer to the nickel question. :-)

Collapse -

Calling all WINS gurus

by carl_ramkarran In reply to Calling all WINS gurus

Poster rated this answer

Collapse -

Calling all WINS gurus

by carl_ramkarran In reply to Calling all WINS gurus

This question was closed by the author

Back to Windows Forum
9 total posts (Page 1 of 1)  

Related Discussions

Related Forums