The State of Server dialogs need two requirements to provide useful information:
· CDS must be available for looking up the names and locations of the CDS, time, and security servers.
· To display the state of servers of a foreign cell, you must configure your computer to use CDS to locate the security server.
The State of Server dialogs require CDS because CDS, time and security servers register themselves in CDS.
· CDS servers register themselves as clearinghouse objects in the CDS root directory.
· Time servers register themselves in the RPC profile "lan-profile" (or lan*profile for a multiple-LAN cell) in the CDS root directory.
· Security servers register themselves in the RPC group sec in the CDS root directory.
If the State of Server dialogs cannot locate the servers in CDS, then they display the following error message:
Could not get clearinghouse entries for CDS directory "/"
Timeout occurred, operation not performed (dce / cds)
The first line shows what the State of Server dialog was trying to do when it encountered an error.
The second line shows the text for the error returned by the DCE routine. It ends with a code showing the DCE facility that returned the error (in this case, CDS).
If a State of Server dialog fails in this way, diagnose and correct the problem with other DCE tools (cdscp, rpccp, DCEsetup, and so forth).
There are several possible points of failure.
Check your computer's DCE configuration first by listing the directories in the root directory:
cdscp> list dir /.:/*
If the CDS control program (cdscp) does not work correctly on your computer, try the same command from another computer.
If cdscp only fails on your computer, test the DCE configuration on your computer by running the DCE Configuration Verification program found in DCEsetup. If the Configuration Verification program encounters problems, you may need to reconfigure DCE on your computer. Refer to the Correcting Errors Encountered During Configuration help topic under Verifying and Testing Your Configuration in DCEsetup.
If cdscp fails on both computers, try running cdscp on the computer that also runs the CDS server. If the cdscp command fails on the server computer, you probably need to restart the CDS server software. If the cdscp command succeeds, you may have a problem reaching the server computer over the network from your own computer.
Return to your computer and test network connectivity with a command like ping (for IP networks). If the ping command fails, then you need to fix your network configuration so your computer can reach the CDS server computer. If the ping command succeeds, you probably need to restart the CDS server software on the server computer.
Another problem may be that the State of Server dialog fails to list all the CDS, time, or security servers that you thought were running on your network. If this is the case, use cdscp and rpccp to search for clearinghouse objects in the root directory, or the contents of the LAN*profile and sec group.
· To see the clearinghouse objects in the root directory, type the following command:
cdscp>show object /.:/* with CDS_Class = CDS_Clearinghouse
· To see the contents of the lan profile for a single-LAN cell, type the following command:
rpccp> show profile /.:/lan-profile
· To see the contents of the security group, type the following command
rpccp> show group /.:/sec
If the server fails to register itself in CDS properly, other DCE applications will not be able to use it. Restart the server and check again to see if it registers itself properly.