| 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 |
Hi,
I would like to find out how about to make sure that MCC is actually
trying to communicate with the DNS server node whenever this error
message occurs ?
I have a DECdns server which is separate from the MCC node, but whenever
I issue the REGISTER command on MCC, I get this error
%DNS....Can't communicate with DNS server
I have checked all access and rights on the DNS system and I (MCC)
have full rights to access the directories ( top to bottom ).
Also, I would like to where to find out more information regarding the
details ( decnet objects, accounts,..) of the entire process from the
time the command ( REGISTERED ) is parsed to the time it get to talk to
the server and get back the information. Is it document anywhere ( specs )
??? This is something is lacking since we need to know to troubleshoot
current and futures problems between MCC and DNS.
Thank you very much in advance for your help.
Thien Doan
EIS/Network Consulting Group
PS: DTNM-264-1484
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 571.1 | Answered my own question | VIDOAN::DOAN | EIS/Network Consulting Group of the 90's | Thu Dec 20 1990 09:55 | 30 |
Hi,
After simultated and isolated the problem, this error message can occurs
by various causes,
1) Access problems with the remote DNS database ( no access rights )
2) The remote DNS$TA,DNS$BACK on the server node has very low process
priority, therefore the timeout of the connected link will resulted.
3) Bad DNS images on either/both the client and server node.
To troubleshoot it, you can try to initiate a link by issue a MCC
command from the client node (i.e. REGISTER ) , and then using
NCP to monitor the state of the logical links so see if it's actually
get created or NOT.
Another way to check it out is to use DECnet event 353.5 on the server
node, in this way, you can actually see and understand the nature of
the errors.
If any of you have any other suggestions, please includes them in the
following replies because this is the hardest error to correct and it
occurs very often.
Thanks for your future contributions to the very well built set of
products ( the DECmcc family ).
Thien Doan
EIS/Network Consulting Group
| |||||
| 571.2 | trouble shooting | GOSTE::CALLANDER | Thu Dec 20 1990 11:06 | 4 | |
The infomration here is quote useful. It has been passed to the
writers to be considered for inclusion in the DIR Use manual (trouble
shooting is in the last chapter).
| |||||