| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2796.1 | | IDNTCR::RHOTON | John Rhoton @TNO - DTN 871.7947 | Thu Jun 03 1993 09:36 | 20 |
| re: .0
While it probably has something to do with your DECnet alias
characteristics, I can't tell from reading the note what the problem is
but I can tell you what I would do to find out. With restricted VAX
Notes conferences the server will compare the DECnet node and username
pair with those of all members of the conference. If any match then
it will open the conference. So you need to find out what the incoming
DECnet node and username pair are for the users where access is failing.
One way to do this would be to create a dummy unrestricted conference
(on the same node as the restricted conference where access is failing)
and have the users in question write a note each in the conference.
You can look at who is recorded as the authours of those notes and then
compare these node-username pairs with those in the membership list of
the conference. The problem should become apparent at that point.
I hope this helps,
John
|
| 2796.2 | twilight zone addressing | GIDDAY::BURT | Chele Burt - CSC Sydney, DTN 7355693 | Wed Jun 09 1993 03:19 | 17 |
| Hello John ('n'all)
Customer set up the dummy conference as requested, wrote a few notes and
replies, then had the person who initalially reported the problem (accessing
the restricted conference) add a note.
The person with the orginal problem is accessing the new conference via MEL01V
(ie the actual Nnode name) wheras everyone else is accessing it via the
cluster alias, MEL.
Where is the network address being picked up from? Cos his User profile entry
doesn't have anything in the NODE field, and his Network Profile Network
Address is set to MEL, as is everyone else.
Thanks & regards,
Chele
|
| 2796.3 | | IDNTCR::RHOTON | John Rhoton @TNO - DTN 871.7947 | Wed Jun 09 1993 10:06 | 13 |
| re: .2
The node name of the network address is picked up from the volatile NCP
database of the server node. I have never heard of it working
inconsistently on a per-user basis. Is it possible that the new
conference is on a cluster and the user with the problem is accessing
it through a different node?
By the way, this problem should not be limited to Group Conferencing so
you may want to cross-post it in the main VAX Notes conference where
they are more knowledgeable in this area.
John
|
| 2796.4 | One possible difference | IOSG::SHOVE | Dave Shove -- REO2-G/M6 | Wed Jun 09 1993 16:47 | 5 |
| Are they all referring to the conference (in their notebooks) in the
same way? Especially local users - do they refer to it as Filename or
0::Filename or node::Filename or cluster-alias::Filename ?
Dave.
|
| 2796.5 | thankyou | GIDDAY::BURT | Chele Burt - CSC Sydney, DTN 7355693 | Fri Jun 18 1993 08:36 | 19 |
| Hello and greetings,
Most users were accessing the conference via filename, ie no node number,
nodename or alias-name.
We tried (with me coaching over the phone) to get the moderator-who-couldn't
access to add the conference in a variety of flavours. No dice - still unable
to access conference. Did an Update. Tried again. He got in - yay - had him
modified all moderators so they could access via either alias or node name.
There is now joy in mudville.
But fears are held for the time when they eventually get their node-names &
alias sorted out...
Thanks & regards,
Chele
|