Troubleshooting Configuration Problems

 

Problem

Solution

 

Clock skew too great (dce/krb).

 

The time skew between your PC's local time and that of the Security server is greater than the five-minute threshold specified by DCE. DCE_login will fail if the clock skew is greater than five minutes.

Manually synchronize your PC clock with the clock on the Security server. Verify that your system's time zone setting is correct for your geographic location.

If you are not running the Distributed Time Service (DTS) on Windows 2000 or Windows NT systems, you can run the timesync.exe program to correct time skew errors.

 

Solicitation of remote CDS advertiser on nodename failed. Please make sure CDS is running on that machine.

 

CDS services are unavailable on the node that you specified during the configuration procedure.

Verify that the node name of the server you specified during the configuration to provide CDS services is correct. If it is, try to contact the CDS server from another client system in the same cell. If communication cannot be established with the CDS server from other machines, contact your CDS or cell administrator to determine the status of the server. If the server is likely to be unavailable indefinitely, use the PC-DCE configuration program to select another CDS server in your cell from which your system can obtain CDS services.

 

Unable to find security server on nodename. Communications failure (dce/rpc).

 

Security services are unavailable on the node you specified during the configuration procedure.

Verify that the node name of the server system that you specified to provide Security services is correct. If it is, try to contact the Security server from another DCE client system in the same cell. If communication cannot be established with the server from other machines, contact your Security or cell administrator to determine the status of the server. If the server is likely to be unavailable indefinitely, use the PC-DCE configuration program to select another server in your cell from which your system can obtain Security services.

 

User Identification Failure - Registry object not found (dce/sec).

 

The cell name or administrator name you specified during the configuration procedure is incorrect.

Verify that the name you entered is correct.

After a configuration error, please note that any changes made to a cell name in the dce_config client page will not be valid. To change a cell name, you must exit PC-DCE and select the configure button on the PC-DCE Service Panel.

 

Unable to configure
PC-DCE within a Terminal Server environment

 

From the About button on the PC-DCE Service Panel, confirm that the PC-DCE version installed is a version that supports Windows Terminal Server. If the PC-DCE version does not support Windows Terminal Server, contact Entegrity Solutions for information on how to purchase the version of PC-DCE that functions within a terminal server environment