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

Conference azur::mcc

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

5157.0. "DNS problem - cannot add objects/directory" by HGOVC::LILLIANTANG () Mon Jun 07 1993 11:04

Was unable to use "create group" or "create directory" from DNS after
upgrading from BMS v1.2 to v1.3.   While running "MCC_DNS_SETUP.COM"
option 3 to create ".MCC_bridge_backtranslation" prior to installing
ELM v1.3, DNS seemed to hang at the "create" command, and returned with
message "DNS server" not available.  In fact, the DNS server was installed
in the same workstation as MCC.  Version of DNS is v1.1.   Accessing
MCC was ok but unable to add any node - operation seemed to hang
during the add command.  Reading existing node status was ok.

Once DNS seemed to hang, wasn't even able to run DNS>STOP NAMESERVER.
Have to reboot system.  Following is a snapshot of the child entities
from DNS and access control.  All commands done via SYSTEM account
with all necessary privileges.  Any help is appreciated.


DNS> show clearinghouse hgsw70_ch
showed a 'next scheduled update = 10-july-1993' - more than a month
from today's date !!

$ mc dns$control
DNS> 
DNS> show dir . child *
 Child ______ DNA_BackTranslation
 Child ______ DNA_Node
 Child ______ DNA_NodeSynonym
 Child ______ DOMAIN
 Child ______ DTSS_GlobalTimeServers
 Child ______ IP
 Child ______ MCC
 Child ______ MCC_Concentrator_BackTranslation
 Child ______ MCC_Sample_BackTranslation
 Child ______ MCC_SNMP_BackTranslation
 Child ______ MCC_Station_BackTranslation 
 Child ______ MCC_Terminal_Server_BackTranslation

DNS> 
DNS> show access dir .
  Entry ______ HGSW70::SYSTEM _ (HGSW70_NS:.DNS$IV.HGSW70.SYSTEM)
  Flags _____ NOPROPAGATE
  Rights ____ READ WRITE DELETE TEST CONTROL
  Entry ______ HGSW70::DNS$SERVER _ (HGSW70_NS:.DNS$IV.HGSW70.DNS$SERVER)
  Flags _____ NOPROPAGATE
  Rights ____  READ WRITE DELETE TEST CONTROL
  Entry ______ HGSW70_NS:.hgsw70_ch
  Flags _____ NOPROPAGATE
  Rights ____  READ WRITE DELETE TEST CONTROL
  Entry ______ *::* _ (HGSW70_NS:.DNS$IV.*.*)
  Flags _____ PROPAGATE
  Rights ____ READ WRITE DELETE TEST CONTROL
  Entry ______ *::* _ (HGSW70_NS:.DNS$IV.*.*)
  Flags _____ DEFAULT PROPAGATE
  Rights ____  READ WRITE DELETE TEST CONTROL
T.RTitleUserPersonal
Name
DateLines
5157.1Check access to DNS directoriesCUJO::HILLDan Hill-Net.Mgt.-Customer ResidentWed Jun 16 1993 22:055
    It seems as though the access did not get propogated from your root
    (".") directory.  Can you verify this by showing access for all node4
    directories?
    
    -Dan