[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference decwet::windows-nt

Title:Windows NT
Notice:See note 15.0 for HCL location
Moderator:TARKIN::LIN.com::FOLEY
Created:Thu Oct 31 1991
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6086
Total number of notes:31449

5920.0. "DHCP: primary and secondry WINS servers inverted !" by GVPRD3::MSTEINER () Wed Apr 16 1997 06:40

From time to time, we have a strange problem with some PC that run WIN95 and
get their IP addresses from the DHCP server.

The DHCP server specifies the parameter 044 "WINS/NBNS servers" set to
16.44.32.232, 16.184.48.6.

Sometimes, on the PC, one using winipcfg can see the addresses inverted (the
16.184.48.6 is used for the primary WINS server, and 16.44.32.232 for the
secondary WINS server).

Does this mean that the PC was not able to register itself in the WINS at
16.44.32.232, but was able to do so in the WINS at 16.184.48.6 ?

Is is a known bug of the DHCP client in WIN95 ?

Michel.
T.RTitleUserPersonal
Name		DateLines
5920.1Also on Windows NTULYSSE::WEISSBECKWed Apr 16 1997 07:035
    Michel,
    
    I have seen this behaviour on Windows NT Workstation also!
    
    Jean-Marie
5920.2PYRO::RONRon S. van ZuylenWed Apr 16 1997 16:055
    It's not just the DHCP client.  If you set it manually, it can change,
    too.  It's a, uh, "feature".  I have not received a straight answer if
    this is an intended behavior.
    
    --Ron
5920.3Known problem in Windows NT 4.0ULYSSE::WEISSBECKThu Apr 17 1997 00:3965
                                                            
    
    
    It is a known problem in Windows NT 4.
    Here is the Knowledge database article from Micorsoft. Might be W95 has
    the same "feature". I had the same problem with NT 3.51. 
    
    
    Windows NT Client: Primary/Secondary WINS Servers Switch
    
    Article ID: Q164309 
    Creation Date: 26-FEB-1997
    Revision Date: 07-APR-1997 
    
    The information in this article applies to: 
    
    Microsoft Windows NT Workstation version 4.0 Microsoft Windows NT
    Server version 4.0 
    
    
    
    
    
    SYMPTOMS 
    
    
    When a Windows NT 4.0 client has a primary and a secondary WINS server
    assigned, it may unnecessarily switch the secondary server to primary
    server. 
    
    
    
    CAUSE 
    
    
    Normally, a workstation should only move the secondary WINS server into
    the primary role if the primary WINS server fails to respond to
    repeated name registration or name query attempts. However, a problem
    with Netbt.sys causes some workstations to switch when doing normal
    name refreshes. 
    
    This switch can cause unnecessary WAN traffic if the WINS server
    defined as primary is a local computer, and the one defined as
    secondary is a remote computer or across a WAN link. 
    
    
    
    RESOLUTION 
    
    
    A new version of Netbt.sys has been created that no longer exhibits
    this problem. 
    
    
    
    STATUS 
    
    
    Microsoft has confirmed this to be a problem in Windows NT version 4.0.
    A supported fix is now available, but has not been fully
    regression-tested and should be applied only to systems experiencing
    this specific problem. Unless you are severely impacted by this
    specific problem, Microsoft recommends that you wait for the next
    Service Pack that contains this fix. Contact Microsoft Technical
    Support for more information.