[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | Kit: Note 4229; Please use NOTED::PWDOSWIN5 for V4.x server |
| Notice: | Kit: Note 4229; Please use NOTED::PWDOSWIN5 for V4.x server |
| Moderator: | CPEEDY::KENNEDY |
|
| Created: | Fri Dec 18 1992 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4319 |
| Total number of notes: | 18478 |
4195.0. "Pathworks Cluster Alias, to be or not to be!" by KERNEL::CHEWTER () Thu Mar 06 1997 12:10
Help!
I have a customer who previously was using V5.0D eco2 this fixed
Pathworks Cluster Alias connection problem which they were
experiencing. They then upgraded to V5.0E (to fix other problems)
since then the Pathworks Cluster Alias problem has re-occurred, in the
respect that they can see it but not connect to it.
The Clients involved are Windows 95 using Netbeui. The server and
license server are configured for Decnet, TCP/IP and Netbeui.
Customer did downgrade (back to V5.0D eco2) and Pathworks Cluster Alias
problem disappeared.....
I have the output from:
nbshow NB, KNB, NBSTATUS, KNBSTATUS, and DL
both before and after the upgrade.
The one noticeable difference with the files is that the Cluster Alias
is not registered as a unique name (x20) after the upgrade to V5.0E on
any transport, will this make a difference? is this the problem staring
at us?
Also one of the nodes in the cluster is not listed at all in the
session status column, could this node be carrying the Cluster Alias?
Please be gentle....
I feel this is a very strange problem, as it was previously working!
Regards
Jayne and Sam (two brains are better than one!)
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 4195.1 | | UTRTSC::SWEEP | I want a lolly... | Mon Mar 10 1997 04:54 | 14 |
| The cluster alias in v50d was displayed as a unique name,
but actually its a group name. So it was changed that
the display now shows the correct output.
This can't effect the fact that you cannot connect.
What I would like to see is an IRIS trace where you trace
the connection. Watch out because this is all multicast stuff
you need to enable the correct addresses.
Trace everything to/from the client AND
everything to/from the Multicast address that belongs to your
transport.
Adrie
|