[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | DECmcc user notes file. Does not replace IPMT. |
Notice: | Use IPMT for problems. Newsletter location in note 6187 |
Moderator: | TAEC::BEROUD |
|
Created: | Mon Aug 21 1989 |
Last Modified: | Wed Jun 04 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 6497 |
Total number of notes: | 27359 |
3214.0. "MCC problems in the corporate namespace." by ZEKE::PARADISE () Fri Jun 19 1992 10:48
Hello,
I am currently running DECmcc 1.2.7, DECelm 1.2 and
DECtsam 1.0 on my master DNS server here at ZKO. When
I installed these products I had no errors during the
installation.I am using the corporate namespace.
I have worked with John Regan and Brad Woodcock to try
and fix the problems that I am having. I can register
node4 entities with no problem. It's only when I try to register
Bridges and Terminal servers is when the problems occurs.
On the iconic map when I go to register the bridges or
terminal servers I get entity partically registered. Please
try again later message. But it does put the entity on the map.
If anyone can shed some light on what might be my problem
please feel free to send me mail or even give me a call. My DTN
is 381-2288 or I can be reached on ZEKE::PARADISE.
Thanks
Rick Paradise
Below is what John Regan sent me with info on the DNS accesses
to the DEC: namespace:
Trying to Register a bridge with DECmcc using the Corporate DEC:
namespace. I apparently have all the access I need for all the
related directories...
Problem:
Can't "completely" register a bridge = DEC:.zko.b.zk2620
Object gets created,,,,no softlink created,
Can create softlink manually via DNS$Control..so access control doesn't
seem to be the problem.
Access to DEC: MCC Bridge Backtran dir.....
SHOW
DIRECTORY DEC:.mcc_bridge_backtranslation
AT 05-JUN-1992:10:56:00
DNS$ACS (set) = :
.
.
.
DNS$ACS (set) = :
Flags = propagate
Rights = read, write, delete, test, control
(IV) Principal = zkodns::system
(V) Principal = DEC:.DNS$IV.zkodns.system
DNS$ACS (set) = :
Flags = propagate
Rights = read, write, delete, test, control
(IV) Principal = zkodns::dns$server
(V) Principal = DEC:.DNS$IV.zkodns.dns$server
DNS$ACS (set) = :
Flags = default, propagate
Rights = read, write, delete, test, control
(IV) Principal = zkodns::dns$server
(V) Principal = DEC:.DNS$IV.zkodns.dns$server
DNS$ACS (set) = :
Flags = default, propagate
Rights = read, write, delete, test, control
(IV) Principal = zkodns::system
(V) Principal = DEC:.DNS$IV.zkodns.system
DNS$ACS (set) = :
Flags = propagate, group
Rights = read, write, delete, test, control
Group = DEC:.mcc_admin
Access to local object dir ...
SHOW
DIRECTORY DEC:.zko.b
AT 05-JUN-1992:10:56:26
.
.
.
DNS$ACS (set) = :
Flags = propagate
Rights = read, write, delete, test, control
(IV) Principal = zkodns::dns$server
(V) Principal = DEC:.DNS$IV.zkodns.dns$server
DNS$ACS (set) = :
Flags = propagate
Rights = read, write, delete, test, control
(IV) Principal = zkodns::system
(V) Principal = DEC:.DNS$IV.zkodns.system
DNS$ACS (set) = :
Flags = default, propagate
Rights = read, write, delete, test, control
(IV) Principal = zkodns::system
(V) Principal = DEC:.DNS$IV.zkodns.system
T.R | Title | User | Personal Name | Date | Lines |
---|
3214.1 | | TOOK::KWAK | | Fri Jun 19 1992 12:36 | 13 |
|
RE: .0
When using a large namespace like DEC:, the MCC backtranslation
directories (e.g. mcc_bridge_backtranslation) are centralized and
shared by all the systems in the namespace.
It happens that the master DECdns server for the directory may not be
available to MCC users during MCC registration. And, the users will often
get DNS-NoCommunication error. In such case, the users can re-try later
when the DNS server becomes accessible.
William
|
3214.2 | fix at last! | ZEKE::PARADISE | | Wed Jul 15 1992 09:36 | 6 |
| We ended finding the prblem I was having. It turned out to be
that the vms drivers on my node were only 90% complete. I had
the VMS people fix it and now everything looks great.
Rick Paradise
|