IBM Distributed Computing Environment (DCE) for Windows NT, V1.1

Fixes for this product can be found at URL: ftp://service.boulder.ibm.com/ps/products/ntdce/fixes

List of Known Problems

These items have been reported and are being addressed by the product development organization. Refer to this web page for the latest fix information.

Problems with Workarounds Identified

Legend = (A=Abstract;F=Fix;W=Workaround)

• A: Unable to configure DCE/NT Security server replica to an OS/2 DSS DCE Cell.
  • F: Permanent restriction. DCE Security master server at OSF level 1.1 or higher cannot be configured with a lower level Security replica server.
  
  
  
• A: DCE/NT client cannot be configured to an OS/2 DSS DCE cell that is configured to support NetBIOS.
  • F: NEW OS/2 DSS DCE cell that will contain NT DCE clients: Deselect the checkbox for "Use NetBIOS Socket access" in the Protocol Options section of the DSS configuration menu.
  • F: EXISTING OS/2 DSS DCE cell, adding NT DCE clients: Apply fix: libdce.dll. Obtain from the web, stop DCE, copy fix file to \opt\dce\bin directory on the NT client, and and restart DCE.
  
  
  
• A: Memory leak in CDS master server: Under certain conditions, cdsd may experience memory growth over time. This problem is not evident in the CDS replica.
  • F: Apply fix: cdsd.exe and libdce.dll. Obtain from the web, stop DCE, copy fix files to \opt\dce\bin directory on the CDS server, and start DCE.
    • W: Increase page file size if possible and/or restart cdsd.
  
  
  
• A: Time servers, clients not synchronizing time correctly. The time synchronization method that has a current problem is:
  ->(3) DTS Local Servers, one running "\opt\dce\bin\dts_ntp_provider" referencing an external time provider machine, with all other DCE machines running DTS clerk.
  • F: Two time synchronization methods were proven correct and reliable. Choose either of these methods:
  1. ->(3) DTS Local Servers, one running "\opt\dce\bin\dts_null_provider", with all other DCE machines running DTS clerk.
  2. ->(1) DTS Local Servers, no time provider running, with all other DCE machines running DTS clerk. Change minimum time servers required using command "dtscp set servers required 1".
  
  
  
• A: Instructions to deinstall an OS/2 DCE client are not included in the OS/2 release notes package.
  • F: From the OS/2 client machine:
  1. Remove the DCE icons from the "DCE Services" folder.
  2. Remove the "DCE Services" folder from the OS/2 desktop.
  3. Backup the "config.sys", then edit to remove all references to "dcelocal" and "dce".
  4. REBOOT the system so the modified "config.sys" can take effect.
  5. Remove directory trees "opt" and "dssinst" from the drive DCE was installed on plus the root drive (if different).
  6. Delete files named "*.pkg", "install.exe", "*dce.rsp", and "som*" from the drive DCE was installed on.
  
  
  
• A: Interoperability problem between DCE and IBM Database Server.
  • W: If using IBM Database Server and DCE on the same server machine, DCE must be configured without enabling the Integrated Login feature on the machine that has the IBM Database Server installed.

    To verify that your environment is correct, check the NT Registry and confirm that "DCEcm" is not in the Network Provider Order entry.

    You SHOULD see: HKEY_LOCAL_MACHINE->SYSTEM->CurrentControlSet->Control->Network Provider->Order->ProviderOrder:REG_SZ:LanmanWorkstation

    You should NOT see: HKEY_LOCAL_MACHINE->SYSTEM->CurrentControlSet->Control->Network Provider->Order->ProviderOrder:REG_SZ:LanmanWorkstation,DCEcm

  
  
  
• A: rgy_edit defaults to the Security replica server (read-only). Requests to update the registry will fail.
  • W: Issue the command "site -u" to explicitly change the site in rgy_edit.
  
  
  
• A: Memory leak in SEC master server: Under certain conditions, secd may experience memory growth over time. This problem is not evident in the SEC replica.
  • W: Increase page file size if possible and/or restart secd.
  
  
  
• A: Security master server exhibits 100% CPU. Under certain conditions, the secd process grows to 100% CPU utilization. If this happens to the SEC master, it will also happen to the SEC replica after a period of time.
  • W: Restart secd.