[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference tuxedo::dce-products

Title:DCE Product Information
Notice:Kit Info - See 2.*-4.*
Moderator:TUXEDO::MAZZAFERRO
Created:Fri Jun 26 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2269
Total number of notes:10003

2234.0. "DCE1.1C for WNT, DCEsetup fails in Japan?" by OSTV03::K_HORIE () Mon Apr 28 1997 13:52

Hi

DCE 1.1C, WNT 4.0, Time Zone JST-9 (Tokyo, Japan)

I've been trying DCEsetup on WNT 4.0 with DCE 1.1C to join my intel box
to the existing cell but I have not yet succeded. The following dialogue box
appears during the DCEsetup. 

+--------------------------------------------------------------------------+
|Time Check                                                              |X|
+--------------------------------------------------------------------------+
| DCEsetup has detected an unacceptable difference between   +-------+     |
| the time maintained by your system clock and the time      |  OK   |     |
| maintained by the DCE Cell you are joining                 +-------+     |
|                                                            +-------+     |
|                                                            | Cancel|     |
|                                                            +-------+     |
|         Cell Time: Mon Apr 28 08:49:02 1997 (unknown inaccuracy)         |
|                                                                          |
| Local System Time: Tue Apr 29 00:48:59 1997                              |
|                                                                          |
| is it OK to adjust your                                                  |
| system clock?                  (*) Yes      ( )No                        |
|                                                                          |
+--------------------------------------------------------------------------+

The Displayed Local System Time is strange. It is not local time and it is
not also UTC. If I press the OK button, it fails. Please see the following
dcesetup.log .


          -------- 04/28/97 at 17:47:38 --------------------------
          ========================================================
          New DCEsetup log created
          ========================================================

          -------- 04/28/97 at 17:47:39 --------------------------
          ========================================================
          Beginning DCE client configuration.
          ========================================================
17:47:39: DCE service already running. [RPCSS]
17:47:39: Running getcells.exe to get a list of known cells.
17:48:00: File deleted: C:\OPT\DIGITAL\DCELOCAL\cells.txt
17:48:19:  
17:48:19: Configuration data collected for this run of DCEsetup...
17:48:19: 	Cell Name = jit133_cell
17:48:19: 	Host Name = wombat
17:48:19: 	Security Server Host Name = jit133
17:48:19: 	CDS Server Host Name = jit133
17:48:19: 	Gda Domain Name = 
17:48:19: 	Lan Name = 
17:48:19: Following DCE components are being configured
17:48:19: 	Security Client
17:48:19: 	Integrated Login Service
17:48:19: 	CDS client
17:48:19: 	DTS Clerk
17:48:19:  
17:48:19: DCE service already running. [RPCSS]
17:48:19: Creating DCE_CF.DB file.
17:48:19: Stopping DCE services.
17:48:24: Checking for Integrated Login support in the registry
17:48:24: Removing permanent DCE database files.
17:48:24: Creating dcelocal directories.
17:48:24: Starting DCE Service. [Cdsadv]
17:48:24: DCE service started. [Cdsadv]
17:48:25: Checking status of service.
17:48:37: Defining cached CDS server.
17:48:37: > cdscp define cached server jit133 tower ncacn_ip_tcp:16.161.64.169
17:48:39: Testing access to the CDS server.
17:48:43: cdscp: SHOW
17:48:43: cdscp: DIRECTORY   /.../jit133_cell
17:48:43: cdscp: AT   1997-04-29-00:48:39
17:48:43: cdscp: RPC_ClassVersion = 0100
17:48:43: cdscp: CDS_CTS = 1996-09-13-01:52:33.125799100/4a-49-54-31-33-33
17:48:43: cdscp: CDS_UTS = 1996-12-24-15:34:46.925214100/4a-49-54-31-33-33
17:48:43: cdscp: CDS_ObjectUUID = 79189ea7-0d09-11d0-b351-08002be4b52c
17:48:43: cdscp: CDS_Replicas = :
17:48:43: cdscp: Clearinghouse UUID = 786db6df-0d09-11d0-b351-08002be4b52c
17:48:43: cdscp: Tower = ncacn_ip_tcp:16.161.64.169[]
17:48:43: cdscp: Tower  2 Floor 1  = 0d c9 f1 7d 25 d3 c6 ca 11 85 54 08 00 2b 1c 8f 1f 01 00 	00 00 		
17:48:43: cdscp: Tower  2 Floor 2  = 0d 04 5d 88 8a eb 1c c9 11 9f e8 08 00 2b 10 48 60 02 00 	00 00 		
17:48:43: cdscp: Tower  2 Floor 3  = 0b 	00 00 		connection
17:48:43: cdscp: Tower  2 Floor 4  = 02 	00 00 		ncacn_dnet_nsp
17:48:43: cdscp: Tower  2 Floor 5  = 04 	(null) 		
17:48:43: cdscp: Tower  2 Floor 6  = 06 	49 00 3e aa 00 04 00 85 f8 20 	
17:48:43: cdscp: Tower = ncadg_ip_udp:16.161.64.169[]
17:48:43: cdscp: Replica type = master
17:48:43: cdscp: Clearinghouse Name = /.../jit133_cell/jit133_ch
17:48:43: cdscp: CDS_Replicas = :
17:48:43: cdscp: Clearinghouse UUID = 5f4fb12f-5d4f-11d0-a113-08002b309463
17:48:43: cdscp: Tower = ncacn_ip_tcp:16.161.64.107[]
17:48:43: cdscp: Tower  2 Floor 1  = 0d c9 f1 7d 25 d3 c6 ca 11 85 54 08 00 2b 1c 8f 1f 01 00 	00 00 		
17:48:43: cdscp: Tower  2 Floor 2  = 0d 04 5d 88 8a eb 1c c9 11 9f e8 08 00 2b 10 48 60 02 00 	00 00 		
17:48:43: cdscp: Tower  2 Floor 3  = 0b 	00 00 		connection
17:48:43: cdscp: Tower  2 Floor 4  = 02 	00 00 		ncacn_dnet_nsp
17:48:43: cdscp: Tower  2 Floor 5  = 04 	(null) 		
17:48:43: cdscp: Tower  2 Floor 6  = 06 	49 00 3e aa 00 04 00 ab f8 20 	
17:48:43: cdscp: Tower = ncadg_ip_udp:16.161.64.107[]
17:48:43: cdscp: Replica type = readonly
17:48:43: cdscp: Clearinghouse Name = /.../jit133_cell/jp0637_ch
17:48:43: cdscp: CDS_AllUpTo = 1997-04-28-02:07:54.882172100/4a-49-54-31-33-33
17:48:43: cdscp: CDS_Convergence = medium
17:48:43: cdscp: CDS_InCHName = allowed
17:48:43: cdscp: CDS_DirectoryVersion = 3.0
17:48:43: cdscp: CDS_ReplicaState = on
17:48:43: cdscp: CDS_ReplicaType = master
17:48:43: cdscp: CDS_LastSkulk = 1997-04-28-02:07:54.882172100/4a-49-54-31-33-33
17:48:43: cdscp: CDS_LastUpdate = 1997-04-28-04:08:07.631806300/4a-49-54-31-33-33
17:48:43: cdscp: CDS_RingPointer = 786db6df-0d09-11d0-b351-08002be4b52c
17:48:43: cdscp: CDS_Epoch = 79189ea6-0d09-11d0-b351-08002be4b52c
17:48:43: cdscp: CDS_ReplicaVersion = 3.0
17:48:43: cdscp: Warning: you have no network credentials. All requests will be unauthenticated.
17:48:44: cdscp show dir /.:/
17:48:44: Testing access to CDS clerk.
17:48:49: cdscp: SHOW
17:48:49: cdscp: DIRECTORY   /.../jit133_cell
17:48:49: cdscp: AT   1997-04-29-00:48:44
17:48:49: cdscp: RPC_ClassVersion = 0100
17:48:49: cdscp: CDS_CTS = 1996-09-13-01:52:33.125799100/4a-49-54-31-33-33
17:48:49: cdscp: CDS_UTS = 1996-12-24-15:34:46.925214100/4a-49-54-31-33-33
17:48:49: cdscp: CDS_ObjectUUID = 79189ea7-0d09-11d0-b351-08002be4b52c
17:48:49: cdscp: CDS_Replicas = :
17:48:49: cdscp: Clearinghouse UUID = 786db6df-0d09-11d0-b351-08002be4b52c
17:48:49: cdscp: Tower = ncacn_ip_tcp:16.161.64.169[]
17:48:49: cdscp: Tower  2 Floor 1  = 0d c9 f1 7d 25 d3 c6 ca 11 85 54 08 00 2b 1c 8f 1f 01 00 	00 00 		
17:48:49: cdscp: Tower  2 Floor 2  = 0d 04 5d 88 8a eb 1c c9 11 9f e8 08 00 2b 10 48 60 02 00 	00 00 		
17:48:49: cdscp: Tower  2 Floor 3  = 0b 	00 00 		connection
17:48:49: cdscp: Tower  2 Floor 4  = 02 	00 00 		ncacn_dnet_nsp
17:48:49: cdscp: Tower  2 Floor 5  = 04 	(null) 		
17:48:49: cdscp: Tower  2 Floor 6  = 06 	49 00 3e aa 00 04 00 85 f8 20 	
17:48:49: cdscp: Tower = ncadg_ip_udp:16.161.64.169[]
17:48:49: cdscp: Replica type = master
17:48:49: cdscp: Clearinghouse Name = /.../jit133_cell/jit133_ch
17:48:49: cdscp: CDS_Replicas = :
17:48:49: cdscp: Clearinghouse UUID = 5f4fb12f-5d4f-11d0-a113-08002b309463
17:48:49: cdscp: Tower = ncacn_ip_tcp:16.161.64.107[]
17:48:49: cdscp: Tower  2 Floor 1  = 0d c9 f1 7d 25 d3 c6 ca 11 85 54 08 00 2b 1c 8f 1f 01 00 	00 00 		
17:48:49: cdscp: Tower  2 Floor 2  = 0d 04 5d 88 8a eb 1c c9 11 9f e8 08 00 2b 10 48 60 02 00 	00 00 		
17:48:49: cdscp: Tower  2 Floor 3  = 0b 	00 00 		connection
17:48:49: cdscp: Tower  2 Floor 4  = 02 	00 00 		ncacn_dnet_nsp
17:48:49: cdscp: Tower  2 Floor 5  = 04 	(null) 		
17:48:49: cdscp: Tower  2 Floor 6  = 06 	49 00 3e aa 00 04 00 ab f8 20 	
17:48:49: cdscp: Tower = ncadg_ip_udp:16.161.64.107[]
17:48:49: cdscp: Replica type = readonly
17:48:49: cdscp: Clearinghouse Name = /.../jit133_cell/jp0637_ch
17:48:49: cdscp: CDS_AllUpTo = 1997-04-28-02:07:54.882172100/4a-49-54-31-33-33
17:48:49: cdscp: CDS_Convergence = medium
17:48:49: cdscp: CDS_InCHName = allowed
17:48:49: cdscp: CDS_DirectoryVersion = 3.0
17:48:49: cdscp: CDS_ReplicaState = on
17:48:49: cdscp: CDS_ReplicaType = readonly
17:48:49: cdscp: CDS_LastSkulk = 0
17:48:49: cdscp: CDS_LastUpdate = 0
17:48:49: cdscp: CDS_Epoch = 79189ea6-0d09-11d0-b351-08002be4b52c
17:48:49: cdscp: CDS_ReplicaVersion = 3.0
17:48:49: cdscp: Warning: you have no network credentials. All requests will be unauthenticated.
17:48:50: Create pe_site file
17:48:50: getcellinfo: Attempting to locate security server
17:48:50: getcellinfo: Found security server
17:48:50: getcellinfo: Creating C:\OPT\DIGITAL/dcelocal/etc/security/pe_site file
17:48:54: File deleted: C:\OPT\DIGITAL\DCELOCAL\PeSite.tmp
17:48:54: Attempting to locate time servers in the target cell.
17:48:59: Getting local time servers from lan-profile
17:48:59: Comparing system time to unauthenticated time service.
17:48:59: Obtained time from time server.
17:48:59: System time differs from cell time by more than two minutes.
17:51:01: Local system clock reset to cell time.
17:51:01: File deleted: C:\OPT\DIGITAL\DCELOCAL\bindings.tmp
17:51:01: File deleted: C:\OPT\DIGITAL\DCELOCAL\MultiLan.Tmp
17:51:01: File deleted: C:\OPT\DIGITAL\DCELOCAL\lans.tmp
17:51:01: Stopping DCE service. [Cdsadv]
17:51:02: DCE service stopped. [Cdsadv]
17:51:04: Logging into DCE...
17:51:09: 
17:51:09: Clock skew too great ( dce / krb )
17:51:24: DCE configuration either failed or was aborted

          -------- 04/28/97 at 17:51:24 --------------------------
          ========================================================
          End of DCE client configuration
          ========================================================


I have confirmed that the time zone and system time is appropriately set
(Control Panel, Date/Time icon.) and the cell time is also right.

After setting the TZ system environment variable JST-9, I tried DCEsetup
again. The dialogue box did not appear in that time, but DCEsetup failed in
the later phase. I have attached the dcesetup.log .


          -------- 04/28/97 at 18:27:41 --------------------------
          ========================================================
          New DCEsetup log created
          ========================================================

          -------- 04/28/97 at 18:27:42 --------------------------
          ========================================================
          Beginning DCE client configuration.
          ========================================================
18:27:42: DCE service already running. [RPCSS]
18:27:42: Running getcells.exe to get a list of known cells.
18:28:03: File deleted: C:\OPT\DIGITAL\DCELOCAL\cells.txt
18:28:52:  
18:28:52: Configuration data collected for this run of DCEsetup...
18:28:52: 	Cell Name = jit133_cell
18:28:52: 	Host Name = wombat
18:28:52: 	Security Server Host Name = jit133
18:28:52: 	CDS Server Host Name = jit133
18:28:52: 	Gda Domain Name = 
18:28:52: 	Lan Name = 
18:28:52: Following DCE components are being configured
18:28:52: 	Security Client
18:28:52: 	Integrated Login Service
18:28:52: 	CDS client
18:28:52: 	DTS Clerk
18:28:52:  
18:28:53: DCE service already running. [RPCSS]
18:28:53: Creating DCE_CF.DB file.
18:28:53: Stopping DCE services.
18:28:57: Checking for Integrated Login support in the registry
18:28:57: Removing permanent DCE database files.
18:28:58: Creating dcelocal directories.
18:28:58: Starting DCE Service. [Cdsadv]
18:28:58: DCE service started. [Cdsadv]
18:28:58: Checking status of service.
18:29:10: Defining cached CDS server.
18:29:10: > cdscp define cached server jit133 tower ncacn_ip_tcp:16.161.64.169
18:29:13: Testing access to the CDS server.
18:29:17: cdscp: SHOW
18:29:17: cdscp: DIRECTORY   /.../jit133_cell
18:29:17: cdscp: AT   1997-04-29-01:29:13
18:29:17: cdscp: RPC_ClassVersion = 0100
18:29:17: cdscp: CDS_CTS = 1996-09-13-01:52:33.125799100/4a-49-54-31-33-33
18:29:17: cdscp: CDS_UTS = 1996-12-24-15:34:46.925214100/4a-49-54-31-33-33
18:29:17: cdscp: CDS_ObjectUUID = 79189ea7-0d09-11d0-b351-08002be4b52c
18:29:17: cdscp: CDS_Replicas = :
18:29:17: cdscp: Clearinghouse UUID = 786db6df-0d09-11d0-b351-08002be4b52c
18:29:17: cdscp: Tower = ncacn_ip_tcp:16.161.64.169[]
18:29:17: cdscp: Tower  2 Floor 1  = 0d c9 f1 7d 25 d3 c6 ca 11 85 54 08 00 2b 1c 8f 1f 01 00 	00 00 		
18:29:17: cdscp: Tower  2 Floor 2  = 0d 04 5d 88 8a eb 1c c9 11 9f e8 08 00 2b 10 48 60 02 00 	00 00 		
18:29:17: cdscp: Tower  2 Floor 3  = 0b 	00 00 		connection
18:29:17: cdscp: Tower  2 Floor 4  = 02 	00 00 		ncacn_dnet_nsp
18:29:17: cdscp: Tower  2 Floor 5  = 04 	(null) 		
18:29:17: cdscp: Tower  2 Floor 6  = 06 	49 00 3e aa 00 04 00 85 f8 20 	
18:29:17: cdscp: Tower = ncadg_ip_udp:16.161.64.169[]
18:29:17: cdscp: Replica type = master
18:29:17: cdscp: Clearinghouse Name = /.../jit133_cell/jit133_ch
18:29:17: cdscp: CDS_Replicas = :
18:29:17: cdscp: Clearinghouse UUID = 5f4fb12f-5d4f-11d0-a113-08002b309463
18:29:17: cdscp: Tower = ncacn_ip_tcp:16.161.64.107[]
18:29:17: cdscp: Tower  2 Floor 1  = 0d c9 f1 7d 25 d3 c6 ca 11 85 54 08 00 2b 1c 8f 1f 01 00 	00 00 		
18:29:17: cdscp: Tower  2 Floor 2  = 0d 04 5d 88 8a eb 1c c9 11 9f e8 08 00 2b 10 48 60 02 00 	00 00 		
18:29:17: cdscp: Tower  2 Floor 3  = 0b 	00 00 		connection
18:29:17: cdscp: Tower  2 Floor 4  = 02 	00 00 		ncacn_dnet_nsp
18:29:17: cdscp: Tower  2 Floor 5  = 04 	(null) 		
18:29:17: cdscp: Tower  2 Floor 6  = 06 	49 00 3e aa 00 04 00 ab f8 20 	
18:29:17: cdscp: Tower = ncadg_ip_udp:16.161.64.107[]
18:29:17: cdscp: Replica type = readonly
18:29:17: cdscp: Clearinghouse Name = /.../jit133_cell/jp0637_ch
18:29:17: cdscp: CDS_AllUpTo = 1997-04-28-02:07:54.882172100/4a-49-54-31-33-33
18:29:17: cdscp: CDS_Convergence = medium
18:29:17: cdscp: CDS_InCHName = allowed
18:29:17: cdscp: CDS_DirectoryVersion = 3.0
18:29:17: cdscp: CDS_ReplicaState = on
18:29:17: cdscp: CDS_ReplicaType = master
18:29:17: cdscp: CDS_LastSkulk = 1997-04-28-02:07:54.882172100/4a-49-54-31-33-33
18:29:17: cdscp: CDS_LastUpdate = 1997-04-28-04:08:07.631806300/4a-49-54-31-33-33
18:29:17: cdscp: CDS_RingPointer = 786db6df-0d09-11d0-b351-08002be4b52c
18:29:17: cdscp: CDS_Epoch = 79189ea6-0d09-11d0-b351-08002be4b52c
18:29:17: cdscp: CDS_ReplicaVersion = 3.0
18:29:17: cdscp: Warning: you have no network credentials. All requests will be unauthenticated.
18:29:18: cdscp show dir /.:/
18:29:18: Testing access to CDS clerk.
18:29:23: cdscp: SHOW
18:29:23: cdscp: DIRECTORY   /.../jit133_cell
18:29:23: cdscp: AT   1997-04-29-01:29:19
18:29:23: cdscp: RPC_ClassVersion = 0100
18:29:23: cdscp: CDS_CTS = 1996-09-13-01:52:33.125799100/4a-49-54-31-33-33
18:29:23: cdscp: CDS_UTS = 1996-12-24-15:34:46.925214100/4a-49-54-31-33-33
18:29:23: cdscp: CDS_ObjectUUID = 79189ea7-0d09-11d0-b351-08002be4b52c
18:29:23: cdscp: CDS_Replicas = :
18:29:23: cdscp: Clearinghouse UUID = 786db6df-0d09-11d0-b351-08002be4b52c
18:29:23: cdscp: Tower = ncacn_ip_tcp:16.161.64.169[]
18:29:23: cdscp: Tower  2 Floor 1  = 0d c9 f1 7d 25 d3 c6 ca 11 85 54 08 00 2b 1c 8f 1f 01 00 	00 00 		
18:29:23: cdscp: Tower  2 Floor 2  = 0d 04 5d 88 8a eb 1c c9 11 9f e8 08 00 2b 10 48 60 02 00 	00 00 		
18:29:23: cdscp: Tower  2 Floor 3  = 0b 	00 00 		connection
18:29:23: cdscp: Tower  2 Floor 4  = 02 	00 00 		ncacn_dnet_nsp
18:29:23: cdscp: Tower  2 Floor 5  = 04 	(null) 		
18:29:23: cdscp: Tower  2 Floor 6  = 06 	49 00 3e aa 00 04 00 85 f8 20 	
18:29:23: cdscp: Tower = ncadg_ip_udp:16.161.64.169[]
18:29:23: cdscp: Replica type = master
18:29:23: cdscp: Clearinghouse Name = /.../jit133_cell/jit133_ch
18:29:23: cdscp: CDS_Replicas = :
18:29:23: cdscp: Clearinghouse UUID = 5f4fb12f-5d4f-11d0-a113-08002b309463
18:29:23: cdscp: Tower = ncacn_ip_tcp:16.161.64.107[]
18:29:23: cdscp: Tower  2 Floor 1  = 0d c9 f1 7d 25 d3 c6 ca 11 85 54 08 00 2b 1c 8f 1f 01 00 	00 00 		
18:29:23: cdscp: Tower  2 Floor 2  = 0d 04 5d 88 8a eb 1c c9 11 9f e8 08 00 2b 10 48 60 02 00 	00 00 		
18:29:23: cdscp: Tower  2 Floor 3  = 0b 	00 00 		connection
18:29:23: cdscp: Tower  2 Floor 4  = 02 	00 00 		ncacn_dnet_nsp
18:29:23: cdscp: Tower  2 Floor 5  = 04 	(null) 		
18:29:23: cdscp: Tower  2 Floor 6  = 06 	49 00 3e aa 00 04 00 ab f8 20 	
18:29:23: cdscp: Tower = ncadg_ip_udp:16.161.64.107[]
18:29:23: cdscp: Replica type = readonly
18:29:23: cdscp: Clearinghouse Name = /.../jit133_cell/jp0637_ch
18:29:23: cdscp: CDS_AllUpTo = 1997-04-28-02:07:54.882172100/4a-49-54-31-33-33
18:29:23: cdscp: CDS_Convergence = medium
18:29:23: cdscp: CDS_InCHName = allowed
18:29:23: cdscp: CDS_DirectoryVersion = 3.0
18:29:23: cdscp: CDS_ReplicaState = on
18:29:23: cdscp: CDS_ReplicaType = readonly
18:29:23: cdscp: CDS_LastSkulk = 0
18:29:23: cdscp: CDS_LastUpdate = 0
18:29:23: cdscp: CDS_Epoch = 79189ea6-0d09-11d0-b351-08002be4b52c
18:29:23: cdscp: CDS_ReplicaVersion = 3.0
18:29:23: cdscp: Warning: you have no network credentials. All requests will be unauthenticated.
18:29:24: Create pe_site file
18:29:25: getcellinfo: Attempting to locate security server
18:29:25: getcellinfo: Found security server
18:29:25: getcellinfo: Creating C:\OPT\DIGITAL/dcelocal/etc/security/pe_site file
18:29:28: File deleted: C:\OPT\DIGITAL\DCELOCAL\PeSite.tmp
18:29:28: Attempting to locate time servers in the target cell.
18:29:33: Getting local time servers from lan-profile
18:29:34: Comparing system time to unauthenticated time service.
18:29:34: Obtained time from time server.
18:29:34: System time is within acceptable range of cell time.
18:29:34: File deleted: C:\OPT\DIGITAL\DCELOCAL\bindings.tmp
18:29:34: File deleted: C:\OPT\DIGITAL\DCELOCAL\MultiLan.Tmp
18:29:34: File deleted: C:\OPT\DIGITAL\DCELOCAL\lans.tmp
18:29:34: Stopping DCE service. [Cdsadv]
18:29:35: DCE service stopped. [Cdsadv]
18:29:37: Logging into DCE...
18:29:42: Login to DCE successful.
18:29:42: Creating principal hosts/wombat/self
18:29:50: Creating account hosts/wombat/self
18:29:54: ktadd -p hosts/wombat/self -pw ******
18:29:56: ktadd -p hosts/wombat/self -a -r
18:30:04: Starting DCE Service. [Sec_Clientd]
18:30:04: DCE service started. [Sec_Clientd]
18:30:04: Checking status of service.
18:30:07: Starting DCE Service. [Cdsadv]
18:30:07: DCE service started. [Cdsadv]
18:30:07: Checking status of service.
18:30:26: cdscp show dir /.:/
18:30:26: Testing access to the CDS server.
18:30:32: cdscp: SHOW
18:30:32: cdscp: DIRECTORY   /.../jit133_cell
18:30:32: cdscp: AT   1997-04-29-01:30:27
18:30:32: cdscp: Error on entity: /.../jit133_cell
18:30:32: cdscp: auth ticket expired ( dce / rpc )
18:30:32: cdscp: Function: dnsEnumAttr
18:30:43: Testing access to the CDS server.
18:30:48: cdscp: SHOW
18:30:48: cdscp: DIRECTORY   /.../jit133_cell
18:30:48: cdscp: AT   1997-04-29-01:30:43
18:30:48: cdscp: Error on entity: /.../jit133_cell
18:30:48: cdscp: auth ticket expired ( dce / rpc )
18:30:48: cdscp: Function: dnsEnumAttr
18:30:59: Testing access to the CDS server.
18:31:06: cdscp: SHOW
18:31:06: cdscp: DIRECTORY   /.../jit133_cell
18:31:06: cdscp: AT   1997-04-29-01:30:59
18:31:06: cdscp: Error on entity: /.../jit133_cell
18:31:06: cdscp: auth ticket expired ( dce / rpc )
18:31:06: cdscp: Function: dnsEnumAttr
18:31:17: Testing access to the CDS server.
18:31:23: cdscp: SHOW
18:31:23: cdscp: DIRECTORY   /.../jit133_cell
18:31:23: cdscp: AT   1997-04-29-01:31:17
18:31:23: cdscp: Error on entity: /.../jit133_cell
18:31:23: cdscp: auth ticket expired ( dce / rpc )
18:31:23: cdscp: Function: dnsEnumAttr
18:31:34: Testing access to the CDS server.
18:31:39: cdscp: SHOW
18:31:39: cdscp: DIRECTORY   /.../jit133_cell
18:31:39: cdscp: AT   1997-04-29-01:31:34
18:31:39: cdscp: Error on entity: /.../jit133_cell
18:31:39: cdscp: auth ticket expired ( dce / rpc )
18:31:39: cdscp: Function: dnsEnumAttr
18:31:50: Testing access to the CDS server.
18:31:56: cdscp: SHOW
18:31:56: cdscp: DIRECTORY   /.../jit133_cell
18:31:56: cdscp: AT   1997-04-29-01:31:50
18:31:56: cdscp: Error on entity: /.../jit133_cell
18:31:56: cdscp: auth ticket expired ( dce / rpc )
18:31:56: cdscp: Function: dnsEnumAttr
18:32:07: Testing access to the CDS server.
18:32:13: cdscp: SHOW
18:32:13: cdscp: DIRECTORY   /.../jit133_cell
18:32:13: cdscp: AT   1997-04-29-01:32:07
18:32:13: cdscp: Error on entity: /.../jit133_cell
18:32:13: cdscp: auth ticket expired ( dce / rpc )
18:32:13: cdscp: Function: dnsEnumAttr
18:32:24: Testing access to the CDS server.
18:32:29: cdscp: SHOW
18:32:29: cdscp: DIRECTORY   /.../jit133_cell
18:32:29: cdscp: AT   1997-04-29-01:32:24
18:32:29: cdscp: Error on entity: /.../jit133_cell
18:32:29: cdscp: auth ticket expired ( dce / rpc )
18:32:29: cdscp: Function: dnsEnumAttr
18:32:40: Testing access to the CDS server.
18:32:45: cdscp: SHOW
18:32:45: cdscp: DIRECTORY   /.../jit133_cell
18:32:45: cdscp: AT   1997-04-29-01:32:40
18:32:45: cdscp: Error on entity: /.../jit133_cell
18:32:45: cdscp: auth ticket expired ( dce / rpc )
18:32:45: cdscp: Function: dnsEnumAttr
18:32:56: Testing access to the CDS server.
18:33:02: cdscp: SHOW
18:33:02: cdscp: DIRECTORY   /.../jit133_cell
18:33:02: cdscp: AT   1997-04-29-01:32:57
18:33:02: cdscp: Error on entity: /.../jit133_cell
18:33:02: cdscp: auth ticket expired ( dce / rpc )
18:33:02: cdscp: Function: dnsEnumAttr
18:33:13: Can't access CDS clerk or server.
18:33:28: DCE configuration either failed or was aborted

          -------- 04/28/97 at 18:33:28 --------------------------
          ========================================================
          End of DCE client configuration
          ========================================================

I looked into this some more and found that in areas that do not observe
Daylight Saving Time such as Japan, Hong Kong, Taiwan, etc., VC++ RTL can not
retrieve the UTC appropriately without the TZ environment variable.  If
the TZ environment variable isn't set, PST8PDT is used instead of the time
zone information set in the Control Panel, Date/Time icon. It seems like a
bug ( _tzset function is suspicious ). I have submitted a service request
to Microsoft Japan today.

I suspect that DCEsetup program unsets the TZ environment variable during the
setup. If the TZ environment variable is set, VC++ RTL can retrieve the UTC
correctly. According to the dcesetup.log, the cdscp show dir/.:/ command looks
like it failed at that time. At the same time, I succeded with the cdscp show
dir /.:/ from the command prompt with the TZ environment variable.

Has anyone succeded in setting up DCE 1.1C for WNT in areas that do not observe
daylight savings time??? I guess no one in these areas has succeded with
DCEsetup.

Please help me!


Kouji Horie

T.RTitleUserPersonal
Name
DateLines
2234.1we'll look at itdce018.lkg.dec.com::phalenBeth Phalen Digital DCETue Apr 29 1997 16:548
We're going to have someone here look at this starting tomorrow. 

I'm assuming that the cell that you are configuring into is in the 
same time zone. 

Did this start occuring once the U.S. started daylight savings time?

I'll update this note when we have more info
2234.2They are in the same time zone.OSTV03::K_HORIETue Apr 29 1997 22:2215
Hi, Beth
Thanks for your reply.

>I'm assuming that the cell that you are configuring into is in the 
>same time zone. 

Yes, the servers of the cell are also in the same time zone (JST-9).
There are two servers (OpenVMS Alpha V6.2, DCE1.3B) in the cell.

>Did this start occuring once the U.S. started daylight savings time?

I don't think so.


Kouji Horie
2234.3are machines synchronized?dce018.lkg.dec.com::phalenBeth Phalen Digital DCEWed Apr 30 1997 17:4514
Is it possible that there is more than a 2 minute time difference
between your client and server? 

We found that if the client and server were off by more than
2 minutes, than DCE failed in just the way that you describe. 

But if the two machines were in synch the configuration succeeded. 

We are investigating why the DCE client is unable to correctly 
recover from a time skew. I'll update this note when we have an
answer for that. In the meantime, you might be able to keep working
by manually synchronizing the time on the two machines. 

 
2234.4VC++ 4.1 and 4.2 have a bugOSTV03::K_HORIEThu May 01 1997 12:51106
Beth,

>Is it possible that there is more than a 2 minute time difference
>between your client and server? 

No, the time difference between the client and the server was less than 
4 seconds at that time. I've checked the system time and the time zone on 
both the client and the server and everything is right.

I have used DCE1.1B for seven months. It looks a little bit buggy but 
works fine. I could join the PCs in the same cell with DCEsetup many times.


There are three problems in DCEsetup (1.1C).

1. Why does the DCEsetup retrieve the wrong local system time?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
As described in .0, the local system time displayed in the dialogue box 
is very strange. It was seven hours earier than Japan time(GMT+9). There 
is no such area in the world (GMT+16).

I have written the following small program. I have compiled it with VC++ 4.2 
and run it. The output UTC time was seven hours earier than Japan time like 
the displayed time in the dialogue box.

------ cut here --------------------------
#include <time.h>
#include <stdio.h>

void main( void )
{
   struct tm *newtime;
   long ltime;

   time( &ltime );

   newtime = gmtime( &ltime );
   printf( "UTC : %s\n", asctime( newtime ) );
}
------ cut here --------------------------

Regarding this, I have submitted a service request to Microsoft Japan and 
received a reply yesterday. (wow! quick response)

The original text is in Japanese, so I summarized it as follows.

  1). This is a _tzset() function's bug in VC++ 4.1 and VC++ 4.2. If a
      computer belongs a timezone that does not observe daylight savings
      time, GetTimeZoneInformation() returns TIME_ZONE_ID_UNKNOWN on WNT.
      However, _tzset() function handles it improperly.
      They are planning to correct this in VC++ 5.0.

  2). To avoid this problem, there are some methods like the following.
      a). Use VC++ 4.0 runtime library.
      b). Don't use C runtime library and use Win32 API (GetSystemTime,
          GetLocalTime, etc.).
      c). Based on the result of GetTimeZoneInformation, set the TZ
          environment variable.
      d). Correct _tzset() function and use it.


Does DCE1.1C use VC++ runtime library?
What version of VC++ have been used to compile DCE1.1C?

If DCE1.1C uses VC++ runtime library to get UTC and it has been compiled 
with VC++ 4.1 or 4.2, DCE1.1C can not get UTC correctly without the TZ 
environment variable in the areas that do not observe daylight savings
time.


2. Why is the DCE client unable to correctly recover from a time skew?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
It might be a bug, but it is not so important in this case.


3. Why does "cdscp show dir /.:/" fail during the DCEsetup with TZ?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
As described in .0, I succeded with the cdscp show dir /.:/ from the command 
prompt with the TZ environment variable. At that time, I deleted the TZ and 
tried the cdscp show dir /.:/ command again, and it failed.

Does the DCEsetup unset the TZ environment variable?  If so, there is no 
alternative way to get a correct UTC during the DCEsetup. Please modify 
the DCEsetup so it will not unset the TZ environment variable.


>In the meantime, you might be able to keep working
>by manually synchronizing the time on the two machines. 

If I manually synchronize the time for DCE1.1C, I probably need to set back 
the system time 16 hours from Japan time.

Beth, I think you are misunderstanding this problem. It's probably very easy 
to reproduce the problem. If you havn't tried to reproduce it, please try it 
as follows.

1). On WNT, from Control Panel, Date/Time icon, Time Zone tab, change the 
    time zone to an area that does not observe daylight savings time (Tokyo,
    Hong Kong, Hawaii, etc.). Modify the system time and check whether
    it is correct.

2). Configure the PC with DCEsetup to join an existing cell. The servers of 
    the cell must not be WNT(DCE1.1C).


Thanks for your cooperation.
2234.5modifying C runtimedce018.lkg.dec.com::phalenBeth Phalen Digital DCEFri May 02 1997 15:458
V1.1C is built against MSVC++ 4.2.  We are working on building a 
modified C runtime library, with a fixed tzset().  We should have
it built by Monday. I'll contact you via email when we have something
for you to try.  

You're information from Microsoft was very helpful. Thanks. 


2234.6Modified C runtimedce018.lkg.dec.com::phalenBeth Phalen Digital DCEMon May 12 1997 09:599
Kouji, 

I wanted to be sure that you received the mail that I sent.
We have rebuilt the C runtime and preliminary testing shows that
it fixes the problems.  We can now successfully do client 
configurations when set to your timezone.  Let us know if you
still need this fix. The caveat is that Microsoft will not support
a modified C runtime.
beth
2234.7Kit location?OSTV03::K_HORIEWed May 14 1997 12:456
I'm sorry for the late reply to your mail. I send you the reply
yesterday.

Please tell me by e-mail how I get the new DCE 1.1C.

Thanks a lot.