Conference decwet::winnt-clusters

791.0. "WFW won't browse, NTW will ?" by BBO010::TILBY () Fri May 09 1997 15:10

    Another interesting client situation. A customer has V1.1 running on a
    couple of AlphaServer 4100's. Chosen protocol for both servers and
    clients is IPX/SPX. Using the v1.1 client software on NTW one can
    browse the available clusters and cluster shares (although this does
    seem a little slow initially).
    
    Using a V1.1 WFW client (of which this customer is now piloting to
    implement 1000 WFW clients) the domain login is extremely slow (around
    30seconds) and browsing is even slower. Clicking the File Manager
    "share connect" button and you wait about 60 seconds before seeing the
    multiple domains the customer has. Browsing each domain to see
    individual nodes and shares is also slow. When opening the "Digital
    Clusters for Windows NT" domain to see available clusters the cluster
    name does appear. Unfortunately, when expanding the available cluster,
    no cluster shares are seen, although they are seen on the NTW box on
    the desk next door.
    
    This problem has been duplicated on more than one WFW machine to rule
    out an individual WFW client problem.
    
    I can understand the slow logins given that the time-outs for cluster
    connections is still at the defaults of 3 retries and 5 seconds per
    try, but I can't see why NTW "sees" and WFW doesn't. If it were a
    server broadcast problem due to the fact the customer has a switched
    lan that is filtering, I'd expect no clients to be able to access
    cluster shares. Although, are there significant differences in the
    IPX/SPX implementations between NTW and WFW thast make NTW more
    persistent/resilient in its connections ?
    
    
    Ideas ?
    
    
    Thanks
    Grant Tilby
    Brisbane Australia
    
    
    
    
    
    
    
    
    

    
    Just as a suggestion - ensure the WFW clients are running with the 
    updated WFW files that are on the NT 351 (may also be on 4.0) CDrom
    under the \support\client\wfw (or something like that) as these files
    fix a number of connection and browsing issues.
    
    Regards,
    
    / Kerry