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

Conference decwet::winnt-clusters

Title:WinNT-Clusters
Notice:Info directories moved to DECWET::SHARE1$:[NT_CLSTR]
Moderator:DECWET::CAPPELLOF
Created:Thu Oct 19 1995
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:863
Total number of notes:3478

784.0. "NTW client can't open cluster shares" by CSC32::G_OGLESBY (Ginny Oglesby 592-4731 CSC/CS) Fri May 02 1997 16:32

NT4.0sp2, Digital Clusters 1.1.  Clients are WNT Workstation.
If there are more than 48-55 cluster shares configured on
the cluster servers, the clients cannot open any shares.

They can browse and see all the 55+ shares, but if they
try to open one it fails with 
'Network Resource Not Available'.

They remove shares one by one, from the cluster server,  until 
they get under a certain
number (48-55) and the clients can once again open the shares.

They clients are not connecting to all 55 shares, but there
are 48-55 shares available on the shared storage.

These are 4100 servers with a Madge Token Ring card.  They are using
IPX/SPX.

I have not been able to reporduce this here.

Anyone have any ideas?  

Thanks,
Ginny
T.RTitleUserPersonal
Name
DateLines
784.1LJSRV1::GOODMANMon May 05 1997 08:164
Ask the customer to try an connect via the lanman name (not the cluster alias)
If the error is the same it is not a cluster client problem.  Otherwise call me.

Donna
784.2Works if they use the server name vs. clusteraliasCSC32::G_OGLESBYGinny Oglesby 592-4731 CSC/CSMon May 05 1997 13:407
Donna,

Yes, if they connect directly to the server vs. the clusteralias
they can open the shares, even after 55.

Thanks,
Ginny
784.3no client sft required with sp1 to V1.1LJSRV1::GOODMANTue May 06 1997 08:5610
With the release of sp1 for clusters V1.1 no client cluster software is required.
This release is targeted for the end of May.  The only restriction will be NetBT 
must be bound.  In this case the customer would have to configure IP.


A NetBios name will associated with the IP object in the failover group.  You must have
a WINS server or configure the LMHOST file.  With Sp3 for NT 4.0 standard tools such as
Explorer and Network Neighborhood will enumerate these "cluster virtual servers".  They 
will look to the clients as just another server.

784.4for the 80 column impairedMSE1::PCOTEpress one now for personal nameTue May 06 1997 09:4216



With the  release  of sp1 for clusters V1.1 no client cluster software
is  required.   This release is targeted for the end of May.  The only
restriction  will  be  NetBT must be bound.  In this case the customer
would have to configure IP.


A NetBios  name  will  associated  with  the IP object in the failover
group.   You  must  have  a  WINS server or configure the LMHOST file.
With  Sp3  for  NT  4.0  standard  tools  such as Explorer and Network
Neighborhood  will  enumerate  these  "cluster virtual servers".  They
will look to the clients as just another server.

784.5Just fine but what about others LAN ClientsNNTPD::"[email protected]"Milan ZofkaWed May 07 1997 02:2226
Hello,

Your previous reply is exactly what I was expecting from D-Clusters...
It seem that Microsoft understand now a lot of things with clusters and that
they finally changed something on NT 4.0 (with sp3) to allow transparent
access to virtual nodes (clusters).

My current customer didn't want to install the client kit on his 600 NT4 ws,
he's happy to know that only the sp3 of NT will be needed (he upgrade the
workstations each time a sp becomes stable...)

BUT: you said that sp3 will allow clients to ... Does it mean that ONLY sp3
clients will be able to access transparently theses clusters aliases? What
about others Lan Man clients like WFW, W95, NT4.0 sp2, NT 3.51, Windows 3.1
with various LAN man implementation, you know, all theses mixed PCs you find
in all big enterprises...  

Do you have an idea of what will be changed in sp3 (client side) ? If sp1 of D
CLusters adds entries in WINS, any WINS aware client should be able to access
the Cluster alias or am I wrong (would solve the W95 problem)?

Thanx in advance

Milan

[Posted by WWW Notes gateway]
784.6LJSRV1::GOODMANWed May 07 1997 12:299
Sorry for the confusion.  DC V1.1 with Sp1 over NT 4.0 sp2 supports NetBT fileshare failover and
access withOUT cluster client software.  With NT 4.0 sp2 you make connections via Net Use.

When NT 4.0 sp3 is available for the servers, clients will be able to enumerate cluster shares 
with standard tools (explorer, winfile, network neighborhood).  This is true for Nt 3.51, Win95
or any client that supports WINS.

NetBIOS names are created as part of the IP object.  You would have atleast one per failover group
depending on the number of NICs in the server.
784.7wrapped to <80 columnsTARKIN::LINBill LinWed May 07 1997 15:1213
                      <<< Note 784.6 by LJSRV1::GOODMAN >>>

Sorry for the confusion.  DC V1.1 with Sp1 over NT 4.0 sp2 supports NetBT
fileshare failover and access withOUT cluster client software.  With NT 4.0
sp2 you make connections via Net Use.

When NT 4.0 sp3 is available for the servers, clients will be able to
enumerate cluster shares  with standard tools (explorer, winfile, network
neighborhood).  This is true for Nt 3.51, Win95 or any client that supports
WINS.

NetBIOS names are created as part of the IP object.  You would have atleast
one per failover group depending on the number of NICs in the server.
784.8SP3 on servers only...TYCHE::BOSTERSThu May 15 1997 14:255
    
    ..to answer .-2 in simpler wording, SP3 is needed on the cluster
    servers only. 
    From then on ANY client can browse the virtual cluster names.