DCE-NT DCEPNT20E06 DCE V2.0 for Windows NT ECO Summary
TITLE: DCE-NT DCEPNT20E06 DCE V2.0 for Windows NT ECO Summary
*DCE-NT] DCEPNT20E06 DCE V2.0 for Windows NT ECO Summary
Copyright (c) Compaq Computer Corporation 1998, 1999. All rights reserved.
Modification Date: 25-MAR-1999
Modification Type: Replaced Kit: Updated Release Notes
Modification Date: 26-JAN-99
Modification Type: Updated Kit: Supersedes DCEPNT20E06
PRODUCT: DIGITAL DCE for Windows NT V2.0 through V2.0B
OP/SYS: Windows NT [TM]
SOURCE: Compaq Computer Corporation
ECO INFORMATION:
ECO Kit Name: DCEPNT20E06
ECO Kits Superseded by This ECO Kit: DCEPNT20E05
DCEPNT20E04
DCEPNT20E03
ECO Kit Approximate Size: 97016 Blocks
Kit Applies To: DIGITAL DCE for Windows NT V2.0 - V2.0B
Microsoft Windows NT V3.51
Microsoft Windows NT V4.0 with
Service Pack 3 installed
System/Cluster Reboot Necessary: No
ECO KIT SUMMARY:
An ECO kit exists for DIGITAL DCE Privacy Option for Windows NT V2.0 on
Microsoft Windows NT V3.51 and V4.0 with Service Pack 3 installed. This
kit addresses the following problems:
Problems Addressed in DCEPNT20E06:
o A Daylight Saving Time problem, which used to affect DTS under some
time zones (example: GMT+1) during late fall, is fixed. The changes
required for this fix are reflected in PTHREADS.DLL, PTHREADS.LIB,
LIBDCE.DLL, LIBDCE.DBG and LIBDCE.LIB.
Problems Addressed in DCEPNT20E05:
o DHCP is now supported for DCE clients.
o Users who had installed ECO 3 or ECO 4 lost the ability to use
RPC_SUPPORTED_PROTSEQS environment variable to restrict protocol
sequences used by RPC runtime. This problem has been fixed.
o Users with non-administrative privilege level on NT systems, with the
NTFS file system, who log in to DCE with integrated login can now view
their credentials and perform authenticated DCE operations. During
integrated login, the user's DCE credential files are now created
under administrator authority. This change sets the logged-in user
as the owner of the files, giving the user access privileges to the files.
o Previously, R1.0.3-based VMS servers occasionally logged Wrong Principal
errors when DCE for Windows NT V2.0 clients were configured into the cell.
These errors appeared as '(RPC_CN_AUTH_VFY_CLIENT_REQ) on server failed
status = 14129090' in the server dce$secd.out log file. This problem
has been fixed.
o The dts_acts_provider.exe has been updated to include support for the
year 2000.
o See also the section "New Release Notes" in this document.
Problems Addressed in DCEPNT20E04:
o A memory leak in dcecp has been fixed. Previously, incidental use
of the message catalogues by dcecp resulted in memory growth of the
process.
o It is now possible to boot a client configuration even if the CDS
master is not available. However, the DCE administrator must manually
run a new script, dcelocal\bin\make_cds_replist.bat, after the client
configuration is initially created. The adminstrator supplies the IP
addresses of all CDS replicas. Type make_cds_replist -? for more
information. A future DCE NT release may make this step unnecessary.
o Persuant to the previous problem, you can now start dtsd, even though
the CDS master is not available.
o DCE autostart now ensures that Rpcss is running correctly. This
fixes sporadic DCE autostart problems.
o The DCE configuration will not add a lan profile to the cell profile if
the lan profile had been added previously.
o On Alpha systems, the DCE installation now upgrades the system
msvcrt.dll and msvcirt.dll files to version 5.0, enabling access to bug
fixes available only in this later release. This version upgrade has
been provided by the DCE installation on Intel machines since DCE NT V2.0
ECO 2.
o RPC Runtime performance has been improved.
Problems Addressed in DCEPNT20E03:
o RPC Runtime performance has been improved.
If you have installed DCE from the CD labeled DCE V2.0B for Windows NT
(40 Bit Encryption), the following fixes have already been applied:
o The dcecp -c cell ping command no longer returns incorrect additional
text with the DCE services available message.
o The dcecp registry stop command has been fixed so that it now stops
the Security replica process.
o The cdscp set directory to new epoch master command no longer results
in an access violation.
o When the DCE_AUTOSTART_CLEAN system environment variable is set, the
DCEStart service used to create the following NT Registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DCEcm\Parameters\
SYSTEM with no value. This problem has been fixed.
o utc_asclocaltime() has been fixed to return a correct ASCII string of
local time on a non-English Windows NT machine.
o Windows flashed during DCEsetup Clean or dcecp clean.dce, when it
attempted to shut down DCE processes that were started from dced.
This problem has been fixed.
o The problem of the cell name being erased from the DCEsetup status
window after a remote client was successfully configured and deleted
has been fixed.
o If a client was configured into a cell that had both TCP and UDP
enabled and the RPC_SUPPORTED_PROTSEQS on the client machine was
restricted to either TCP or UDP only, \etc\security\pe_site
would not be updated automatically on the client system. An error
message 0xdce605d, "Protocol sequence not supported" was logged in
\var\svc\error.log. The problem existed in any configuration
where the cell master exported more bindings than client supports, such
as a Windows NT client system configured into an OpenVMS cell that
exported DECnet bindings in addition to TCP and UDP. This problem has
been fixed.
o The DCEsetup status window now correctly displays the status of
Auto-start after DCE is stopped.
o The problem of viewing a foreign UNIX cell from a Windows NT cell has
been fixed. To view attribute information about the foreign cell, do
the following:
1. Configure two cells.
2. Do a dce_login as cell_admin.
3. Use cdscp define cached server commands on both cells to
create information about the foreign cell in the local cache.
4. Do a kdestroy on both cells. If you log in as root on the
UNIX machine, do a klist and make sure that you are not
inheriting machine credentials.
5. Issue a cdscp show directory command as an
unauthenticated user.
o The Problem Determination Guide has been updated.
o Date and timestamps have been added to the entries in the configuration
log file, \etc\cfgdce.log.
o DCE sometimes failed to start with "Insufficient rights to perform
requested operation" after a hard reboot of the system. This problem
has been fixed.
o The performance delay during DCE thread creation has been fixed.
o Configuring DCE after DCEsetup Clean sometimes failed with "No
Credentials cache file found" error. The problem has been fixed.
o The Security daemon failed to restart after the audit daemon was
configured if a directory was not created under \var\audit\
client. If the audit daemon was configured, the Security daemon created a
directory in dcelocal\var\audit\client using its process ID (PID) as
the directory name. The directory stored a file that contained a
string binding to the audit daemon. Previously, the Security daemon
would fail to restart if a directory of the same name already existed.
This problem has been fixed.
o exc_handling.h in the ADK has been changed. It now checks if a
user-defined exception is initialized with the EXCEPTION_INIT macro
before raising an exception.
o If your monitor is in VGA mode, DCEsetup client and server configuration
wizard dialogs were displayed off the screen. This problem has been
fixed.
o Audit control interfaces were not cleaned up from the endpoint map
after a dcecp clean.dce operation. dcecp clean.dce now deletes
audit control interfaces from the endpoint map.
o The IDL compiler did not generate correct function prototypes for the
user-supplied procedures when the IDL option -call_std cdecl is specified.
The problem is fixed with the new idl.exe.
o DCEStart used to perform the clean operation even after the system
environment variable DCE_AUTOSTART_CLEAN was deleted. This problem
has been fixed. DCEStart now performs the clean operation only if
DCE_AUTOSTART_CLEAN is set.
o A member of the Windows NT local Administrators Group could not start
DCE if that member belonged to a large number of groups. This problem
has been fixed.
New Release Notes
o If you have installed FX!32 on an Alpha system after installing DCE,
you must tell FX!32 to ignore certain DCE exectuables. To do this:
1. Start the FX!32 Manager application.
2. Select Options on the Menu bar and choose Preferences...
3. On the Preferences dialog, click the Advanced... button.
4. In the Runtime Options/Disable FX!32 for these Applications
box, add the following three lines:
dcelocal\bin\dcemapp.exe
dcelocal\bin\acl.exe
winhlp32.exe
5. Click the OK button (on Advanced Preferences dialog).
6. Click the OK button (on Preferences dialog).
7. Exit FX!32 Manager.
You do not need to reboot your system after making these changes.
You can also re-install DCE on the system and the installation
procedure will make the appropriate modifications.
o DCE r1.2.1 has set up a mechanism whereby a warning message is placed
in stderr if the cell_admin account password has not been changed. This
is just a warning message, encouraging DCE administrators to change
certain privileged accounts, such as cell_admin password, after DCE
configuration. However, the dcecp exec command checks to see if there
is anything in the stderr file before returning from the exec command.
Since the warning, "Password must be changed!" is in the stderr file,
the exec command returns an error. To avoid this, change the cell_admin
account password.
NOTE: The dcecp command:
dcecp> account modify cell_admin -password foo2
does change the password but does not affect the stderr message.
Use the rgy_edit> change command to change the password and avoid
the stderr message.
o The commands dcecp -c cell ping and dcecp -c cell ping -client do not
work correctly on a OSF DCE 1.0.3 code base server.
o The first Auto-start after migrating a DCE for Windows NT Version 1.1c
cell (including a Security Master and CDS Master) to DCE for Windows
Version 2.0 takes longer than usual. It may appear that the Auto-start
is failing, when, in fact, it is still not completed. A DCEsetup or a
dcecp show.cfg command immediately after a reboot of an installation
or upgrade from Version 1.1c of the product to Version 2.0 (with
Auto-start enabled) will fail with "another configuration is in
progress" message.
To avoid this, check the task list to see that dcestart has completed
before trying to invoke DCEsetup or a dcecp command.
o The dcecp -c host show /.:/hosts/ command does not properly
display the state of running processes on a system.
o DIGITAL DCE for Windows NT does not support passwd_override and
group_override functionality. The dcecp hostdata show and acl show
commands will fail with a "permission not valid for this acl" error
if you attempt to show the information for these objects.
o The DCEsetup Remote Client>Delete option executes an unconfig command using
the all qualifier. The all qualifier is necessary because the local system
does not know what is configured on the remote system and must attempt to
unconfigure everything. During this type of unconfiguration, a number of
warnings are issued and these can be safely ignored.
o If you leave the DCEsetup window up beyond the ticket expiration time, the
next operation sometimes fails with "authentication ticket expired" error.
The workaround is to exit and restart DCEsetup.
o The successful start of DCE on a client in a cell where the CDS master
is down but a CDS replica is available depends on whether the
appropriate directories have been individually replicated into the
CDS replica and skulked prior to CDS master shutdown.
1. Use dcecp directory create -replica
-clearinghouse , or cdscp create replica
commands to replicate the following directories:
/.:/hosts,
/.:/hosts/
/.:/hosts/
/.:/hosts/
2. If skulking has not occurred, use dcecp directory synchronize
commands, or cdscp set directory
CDS_Convergence = high followed by cdscp set directory
to skulk commands to /.:/hosts and /.:
directories to ensure that skulking takes place immediately.
3. Now issue a Stop command followed by a Clean command on the
client. Once this is done, use the Start command on the client
to start DCE.
To start a client with a CDS replica when no other CDS master
and replicas are available, you need to manually start the CDS
replica using the Service Applet from the system Control Panel:
1. Start DCE from DCEsetup.
2. After the CDS Advertiser starts successfully, start the DCE
CDS server service by hand:
a) Bring up the system Control Panel and select Services.
b) Select DCE CDS Server Service.
c) Click the Start button.
o To successfully delete a client from a cell where multiple CDS replicas
are available, the following commands must be issued prior to
unconfiguring the client:
1. dcecp directory delete /.:/hosts/ -replica
-clearinghouse /.:/ for each CDS replica
2. dcecp directory synchronize /.:/hosts
3. dcecp directory synchronize /.:
o A Client configuration fails if the DNS server is not available on
the system. To work around the problem, add the IP address and the
hostname of the cell to the client's local HOSTS file,
\system32\etc\hosts. Turn off the CDS Server
is within Broadcast Range option from the Configuration Wizard, and
use the IP address of the cell host to configure a client.
o When building the dtss example program, the file dtsprovider.h should
be deleted prior to the build. If this file is not deleted, the build
will not complete successfully.
o If you have a Security master running the DIGITAL DCE for Windows NT
Version 2.0 product and you issue the rgy_edit> properties command
from a client running DIGITAL DCE for Windows NT V1.x, or from a
client running DCE based on pre-r.1.2 code, you may experience
unpredictable results. In order to view the registry properties, you
must issue the command from a machine running DIGITAL DCE for Windows
NT Version 2.0.
o The dcecp -c errtext command may return text with
unprintable characters in the event that the status_code in question
contains variable data that needs to be translated at runtime.
o If a credentials file is found under the NT Registry key,
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\ Services\DCEcm\Parameters\
SYSTEM some of the DCE daemons may not start properly or may exhibit
unexpected behaviors. To avoid the problem, make sure to delete the above
key from the NT Registry before starting DCE.
INSTALLATION NOTES:
The installation of this ECO may not proceed correctly when certain
anti-virus software is running. It is recommended that you disable
anti-virus software during installation of this ECO. You may re-enable
anti-virus software after installation is finished.
Install this ECO by running setup.exe from the ECO kit. The installation
procedure will detect which DCE products are installed (Runtime, Security,
CDS, or ADK) and update those products as necessary. If, after the
installation of the ECO, the DCE installation is modified by adding
other DCE products, the ECO must be reapplied.
The ECO may be applied while DCE is running. In order for the ECO changes
to take effect, DCE must be restarted after installing the ECO.
Disk space required for the ECO kit:
Intel 23 MB
Alpha 26 MB
This patch can be found at any of these sites:
Colorado Site
Georgia Site
Files on this server are as follows:
dcepnt20e06.README
dcepnt20e06.CHKSUM
dcepnt20e06.CVRLET_TXT
dcepnt20e06.zip
|
