[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| 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 |
2212.0. "DCE on Windows 95/NT can't join cell" by WINDLE::SPENCE (Bugs? You mean insects?) Tue Apr 08 1997 13:59
Following on from my earlier problem with OpenVMS 6.2, DCE V1.4
and the 10,000 day problem, since the clocks jumped forward an
hour over here, ALL of our windows clients have been unable to
join our cell which is hosted on our VMS box. I've been dealing
with Graham Howland in the UK support center, however I just found
out that he's out of the office for most of the week, so I thought
I'd dump the problem in here to see if anyone can shed any light on
it.
I've got four different PCs in my area, none of which can now join
our DCE cell. Two of them (ELIZA and TPARTY) run Windows 95. One of them
(CMOT) runs Windows NT 4/Intel. The last one (CORDAY) runs Windows NT 4/Alpha,
and is the one which I mentioned in our last conversation.
I've just gone round all four machines, run DCE setup, clobbered their
configuration, created a new log file and tried to configure them as a client.
Here are the contents of the log file on each machine:
.
ELIZA (Windows 95)
-------- 04/08/97 at 08:42:53 --------------------------
========================================================
New DCEsetup log created
========================================================
-------- 04/08/97 at 08:42:56 --------------------------
========================================================
Beginning DCE client configuration.
========================================================
08:42:56: DCE service already running. [RPCSS]
08:43:09:
08:43:09: Configuration data collected for this run of dcesetup...
08:43:09: Cell Name = adi_reo
08:43:09: Host Name = eliza.reo.dec.com
08:43:09: Security Server Host Name = esme.reo.dec.com
08:43:10: CDS Server Host Name = esme
08:43:10: Gda Domain Name =
08:43:10: Lan Name =
08:43:10: Following DCE components are being configured
08:43:10: Security Client
08:43:10: Integrated Login Service
08:43:10: CDS client
08:43:11: DTS Clerk
08:43:11:
08:43:11: DCE service already running. [RPCSS]
08:43:11: Creating DCE_CF.DB file.
08:43:12: Stopping DCE services.
08:43:17: Checking for Integrated Login support in the registry
08:43:17: Removing permanent DCE database files.
08:43:17: Creating dcelocal directories.
08:43:18: Checking status of service.
08:43:33: Defining cached CDS server.
08:43:33: > cdscp define cached server esme tower ncacn_ip_tcp:16.37.5.25
08:43:39: cdscp show dir /.:/
08:43:39: Testing access to CDS clerk.
08:43:48: cdscp: SHOW
08:43:48: cdscp: DIRECTORY /.../adi_reo
08:43:49: cdscp: AT 1997-04-08-08:43:40
08:43:49: cdscp: RPC_ClassVersion = 0100
08:43:49: cdscp: CDS_CTS = 1997-04-03-12:20:27.362226100/aa-00-04-00-a6-a9
08:43:49: cdscp: CDS_UTS = 1997-04-03-12:20:35.592168100/aa-00-04-00-a6-a9
08:43:49: cdscp: CDS_ObjectUUID = a8223cf0-ac1c-11d0-96a8-08002be7a953
08:43:49: cdscp: CDS_Replicas = :
08:43:49: cdscp: Clearinghouse UUID = a73ab055-ac1c-11d0-96a8-08002be7a953
08:43:49: cdscp: Tower = ncacn_ip_tcp:16.37.5.25
08:43: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
08:43: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
08:43:49: cdscp: Tower 2 Floor 3 = 0b 00 00 connection
08:43:49: cdscp: Tower 2 Floor 4 = 02 00 00 ncacn_dnet_nsp
08:43:49: cdscp: Tower 2 Floor 5 = 04 (null)
08:43:49: cdscp: Tower 2 Floor 6 = 06 49 00 2c aa 00 04 00 1f b3 20
08:43:49: cdscp: Tower 3 Floor 1 = 0d c9 f1 7d 25 d3 c6 ca 11 85 54 08 00 2b 1c 8f 1f 01 00
00 00
08:43:49: cdscp: Tower 3 Floor 2 = 0d 04 5d 88 8a eb 1c c9 11 9f e8 08 00 2b 10 48 60 02 00
00 00
08:43:49: cdscp: Tower 3 Floor 3 = 0a 00 00 datagram
08:43:49: cdscp: Tower 3 Floor 4 = 08 00 00 port: 0, ncadg_ip_udp
08:43:49: cdscp: Tower 3 Floor 5 = 09 10 25 05 19 host: 16.37.5.25
08:43:49: cdscp: Replica type = master
08:43:49: cdscp: Clearinghouse Name = /.../adi_reo/esme_ch
08:43:49: cdscp: CDS_AllUpTo = 1997-04-08-01:07:01.366238100/aa-00-04-00-a6-a9
08:43:49: cdscp: CDS_Convergence = medium
08:43:49: cdscp: CDS_InCHName = allowed
08:43:49: cdscp: CDS_DirectoryVersion = 3.0
08:43:49: cdscp: CDS_ReplicaState = on
08:43:49: cdscp: CDS_ReplicaType = master
08:43:49: cdscp: CDS_LastSkulk = 1997-04-08-01:07:01.366238100/aa-00-04-00-a6-a9
08:43:49: cdscp: CDS_LastUpdate = 1997-04-07-14:06:56.705780100/aa-00-04-00-a6-a9
08:43:49: cdscp: CDS_RingPointer = a73ab055-ac1c-11d0-96a8-08002be7a953
08:43:49: cdscp: CDS_Epoch = a8223cef-ac1c-11d0-96a8-08002be7a953
08:43:49: cdscp: CDS_ReplicaVersion = 3.0
08:43:49: cdscp: Warning: you have no network credentials. All requests will be unauthenticated.
08:43:50: Create pe_site file
08:43:51: getcellinfo: Attempting to locate security server
08:43:51: getcellinfo: Found security server
08:43:51: getcellinfo: Creating D:\OPT\DIGITAL/dcelocal/etc/security/pe_site file
08:43:55: File deleted: D:\OPT\DIGITAL\DCELOCAL\PeSite.tmp
08:43:55: Attempting to locate time servers in the target cell.
08:43:56: Unable to get time from server.
09:05:37: File deleted: D:\OPT\DIGITAL\DCELOCAL\bindings.tmp
09:05:43: Logging into DCE...
09:05:45: Login to DCE successful.
09:05:45: Creating principal hosts/eliza.reo.dec.com/self
09:05:47: Creating account hosts/eliza.reo.dec.com/self
09:05:53: ktadd -p hosts/eliza.reo.dec.com/self -pw ******
09:05:53: ktadd -p hosts/eliza.reo.dec.com/self -a -r
09:05:58: Checking status of service.
09:06:08: Checking status of service.
09:06:18: cdscp show dir /.:/
09:06:18: Testing access to the CDS server.
09:06:31: cdscp: SHOW
09:06:31: cdscp: DIRECTORY /.../adi_reo
09:06:31: cdscp: AT 1997-04-08-09:06:19
09:06:31: cdscp: RPC_ClassVersion = 0100
09:06:31: cdscp: CDS_CTS = 1997-04-03-12:20:27.362226100/aa-00-04-00-a6-a9
09:06:31: cdscp: CDS_UTS = 1997-04-03-12:20:35.592168100/aa-00-04-00-a6-a9
09:06:31: cdscp: CDS_ObjectUUID = a8223cf0-ac1c-11d0-96a8-08002be7a953
09:06:31: cdscp: CDS_Replicas = :
09:06:31: cdscp: Clearinghouse UUID = a73ab055-ac1c-11d0-96a8-08002be7a953
09:06:31: cdscp: Tower = ncacn_ip_tcp:16.37.5.25
09:06:31: 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
09:06:31: 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
09:06:31: cdscp: Tower 2 Floor 3 = 0b 00 00 connection
09:06:31: cdscp: Tower 2 Floor 4 = 02 00 00 ncacn_dnet_nsp
09:06:31: cdscp: Tower 2 Floor 5 = 04 (null)
09:06:31: cdscp: Tower 2 Floor 6 = 06 49 00 2c aa 00 04 00 1f b3 20
09:06:31: cdscp: Tower 3 Floor 1 = 0d c9 f1 7d 25 d3 c6 ca 11 85 54 08 00 2b 1c 8f 1f 01 00
00 00
09:06:31: cdscp: Tower 3 Floor 2 = 0d 04 5d 88 8a eb 1c c9 11 9f e8 08 00 2b 10 48 60 02 00
00 00
09:06:31: cdscp: Tower 3 Floor 3 = 0a 00 00 datagram
09:06:31: cdscp: Tower 3 Floor 4 = 08 00 00 port: 0, ncadg_ip_udp
09:06:31: cdscp: Tower 3 Floor 5 = 09 10 25 05 19 host: 16.37.5.25
09:06:31: cdscp: Replica type = master
09:06:31: cdscp: Clearinghouse Name = /.../adi_reo/esme_ch
09:06:31: cdscp: CDS_AllUpTo = 1997-04-08-01:07:01.366238100/aa-00-04-00-a6-a9
09:06:31: cdscp: CDS_Convergence = medium
09:06:31: cdscp: CDS_InCHName = allowed
09:06:31: cdscp: CDS_DirectoryVersion = 3.0
09:06:31: cdscp: CDS_ReplicaState = on
09:06:31: cdscp: CDS_ReplicaType = master
09:06:31: cdscp: CDS_LastSkulk = 1997-04-08-01:07:01.366238100/aa-00-04-00-a6-a9
09:06:31: cdscp: CDS_LastUpdate = 1997-04-07-14:06:56.705780100/aa-00-04-00-a6-a9
09:06:31: cdscp: CDS_RingPointer = a73ab055-ac1c-11d0-96a8-08002be7a953
09:06:31: cdscp: CDS_Epoch = a8223cef-ac1c-11d0-96a8-08002be7a953
09:06:31: cdscp: CDS_ReplicaVersion = 3.0
09:06:32: Testing access to CDS server
09:06:37: cdscp: SHOW
09:06:37: cdscp: DIRECTORY /.../adi_reo
09:06:37: cdscp: AT 1997-04-08-09:06:33
09:06:37: cdscp: RPC_ClassVersion = 0100
09:06:37: cdscp: CDS_CTS = 1997-04-03-12:20:27.362226100/aa-00-04-00-a6-a9
09:06:37: cdscp: CDS_UTS = 1997-04-03-12:20:35.592168100/aa-00-04-00-a6-a9
09:06:37: cdscp: CDS_ObjectUUID = a8223cf0-ac1c-11d0-96a8-08002be7a953
09:06:37: cdscp: CDS_Replicas = :
09:06:37: cdscp: Clearinghouse UUID = a73ab055-ac1c-11d0-96a8-08002be7a953
09:06:37: cdscp: Tower = ncacn_ip_tcp:16.37.5.25
09:06:37: 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
09:06:37: 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
09:06:37: cdscp: Tower 2 Floor 3 = 0b 00 00 connection
09:06:37: cdscp: Tower 2 Floor 4 = 02 00 00 ncacn_dnet_nsp
09:06:37: cdscp: Tower 2 Floor 5 = 04 (null)
09:06:37: cdscp: Tower 2 Floor 6 = 06 49 00 2c aa 00 04 00 1f b3 20
09:06:37: cdscp: Tower 3 Floor 1 = 0d c9 f1 7d 25 d3 c6 ca 11 85 54 08 00 2b 1c 8f 1f 01 00
00 00
09:06:37: cdscp: Tower 3 Floor 2 = 0d 04 5d 88 8a eb 1c c9 11 9f e8 08 00 2b 10 48 60 02 00
00 00
09:06:37: cdscp: Tower 3 Floor 3 = 0a 00 00 datagram
09:06:37: cdscp: Tower 3 Floor 4 = 08 00 00 port: 0, ncadg_ip_udp
09:06:37: cdscp: Tower 3 Floor 5 = 09 10 25 05 19 host: 16.37.5.25
09:06:37: cdscp: Replica type = master
09:06:37: cdscp: Clearinghouse Name = /.../adi_reo/esme_ch
09:06:37: cdscp: CDS_AllUpTo = 1997-04-08-01:07:01.366238100/aa-00-04-00-a6-a9
09:06:37: cdscp: CDS_Convergence = medium
09:06:37: cdscp: CDS_InCHName = allowed
09:06:37: cdscp: CDS_DirectoryVersion = 3.0
09:06:37: cdscp: CDS_ReplicaState = on
09:06:37: cdscp: CDS_ReplicaType = master
09:06:37: cdscp: CDS_LastSkulk = 1997-04-08-01:07:01.366238100/aa-00-04-00-a6-a9
09:06:37: cdscp: CDS_LastUpdate = 1997-04-07-14:06:56.705780100/aa-00-04-00-a6-a9
09:06:37: cdscp: CDS_RingPointer = a73ab055-ac1c-11d0-96a8-08002be7a953
09:06:38: cdscp: CDS_Epoch = a8223cef-ac1c-11d0-96a8-08002be7a953
09:06:38: cdscp: CDS_ReplicaVersion = 3.0
09:06:39: Configuring CDS client.
09:06:39: Checking to see if directory exists: hosts/eliza.reo.dec.com
09:06:39: Creating directory: hosts/eliza.reo.dec.com
09:06:41: Creating namespace entry: hosts/eliza.reo.dec.com/self
09:06:41: Creating namespace entry: hosts/eliza.reo.dec.com/cds-clerk
09:06:41: Creating namespace entry: hosts/eliza.reo.dec.com/profile
09:06:42: Checking for the existence of multiple LAN profiles in cell.
09:06:54: Creating LAN profile for this host.
09:06:54: > rpccp add element /.:/hosts/eliza.reo.dec.com/profile -i 6f264242-b9f8-11c9-ad31-08002b0dc035,0001.0000 -m
/.:/lan-16.37.5-profile -a LAN -p 0
09:06:59: rpccp: >>> profile element added
09:07:00: File deleted: D:\OPT\DIGITAL\DCELOCAL\MultiLan.Tmp
09:07:01: rpccp add element /.:/hosts/eliza.reo.dec.com/profile -m /.:/cell-profile -d -p 0
09:07:05: rpccp: >>> default profile element added
09:07:06: Exporting cds-clerk DACL manager UUID.
09:07:07: rpccp export -i 4ea31de8-9a94-11c9-bb60-08002b0f79aa,3.0 -o dc8c6fc0-6143-11ca-b4b9-08002b1bb4f5 -b
ncacn_ip_tcp:eliza.reo.dec.com /.:/hosts/eliza.reo.dec.com/cds-clerk
09:07:11: rpccp: >>> binding information and objects exported
09:07:12: Exporting DCE endpoint mapper host binding.
09:07:13: rpccp export -i e1af8308-5d1f-11c9-91a4-08002b14a0fa,3.0 -b ncacn_ip_tcp:eliza.reo.dec.com[135]
/.:/hosts/eliza.reo.dec.com/self
09:07:17: rpccp: >>> binding information exported
09:07:19: Set up acls for host
09:07:19: Modifying acl for /.:/hosts/eliza.reo.dec.com, principal: hosts/eliza.reo.dec.com/self, permissions: rwdtcia
09:07:19: ****ERROR**** DOM library error, status: dce801a
09:07:20: ***WARNING*** DOM library error, status: dce801a, Try again.
09:07:22: ****ERROR**** DOM library error, status: dce801a
09:07:22: ***WARNING*** DOM library error, status: dce801a, Try again.
09:07:24: ****ERROR**** DOM library error, status: dce801a
09:07:25: ***WARNING*** DOM library error, status: dce801a, Try again.
09:07:27: ****ERROR**** DOM library error, status: dce801a
09:07:27: ***WARNING*** DOM library error, status: dce801a, Try again.
09:07:29: ****ERROR**** DOM library error, status: dce801a
09:07:29: ***WARNING*** DOM library error, status: dce801a, Try again.
09:07:32: ****ERROR**** DOM library error, status: dce801a
09:07:32: ***WARNING*** DOM library error, status: dce801a, Try again.
09:07:34: ****ERROR**** DOM library error, status: dce801a
09:07:34: ***WARNING*** DOM library error, status: dce801a, Try again.
09:07:37: ****ERROR**** DOM library error, status: dce801a
09:07:37: ***WARNING*** DOM library error, status: dce801a, Try again.
09:07:39: ****ERROR**** DOM library error, status: dce801a
09:07:39: ***WARNING*** DOM library error, status: dce801a, Try again.
09:07:42: ****ERROR**** DOM library error, status: dce801a
09:07:42: ***WARNING*** DOM library error, status: dce801a, Try again.
09:07:44: ****ERROR**** DOM library error, status: dce801a
09:07:55: DCE configuration either failed or was aborted
-------- 04/08/97 at 09:07:55 --------------------------
========================================================
End of DCE client configuration
========================================================
After this finished, the PC was running RPC, Security Client and CDS
Advertiser. The DTS daemon was enabled but stopped.
.
TPARTY (Windows 95)
-------- 04/08/97 at 08:42:48 --------------------------
========================================================
New DCEsetup log created
========================================================
-------- 04/08/97 at 08:42:51 --------------------------
========================================================
Beginning DCE client configuration.
========================================================
08:43:06:
08:43:06: Configuration data collected for this run of dcesetup...
08:43:06: Cell Name = adi_reo
08:43:06: Host Name = Tparty.reo.dec.com
08:43:06: Security Server Host Name = esme.reo.dec.com
08:43:07: CDS Server Host Name = esme
08:43:07: Gda Domain Name =
08:43:07: Lan Name =
08:43:07: Following DCE components are being configured
08:43:07: Security Client
08:43:07: Integrated Login Service
08:43:07: CDS client
08:43:07: DTS Clerk
08:43:07:
08:43:08: DCE service already running. [RPCSS]
08:43:08: Creating DCE_CF.DB file.
08:43:08: Stopping DCE services.
08:43:13: Checking for Integrated Login support in the registry
08:43:14: Removing permanent DCE database files.
08:43:14: Creating dcelocal directories.
08:43:26: Checking status of service.
08:43:35: Defining cached CDS server.
08:43:35: > cdscp define cached server esme tower ncacn_ip_tcp:16.37.5.25
08:43:41: cdscp show dir /.:/
08:43:41: Testing access to CDS clerk.
08:43:48: cdscp: SHOW
08:43:48: cdscp: DIRECTORY /.../adi_reo
08:43:48: cdscp: AT 1997-04-08-08:43:42
08:43:48: cdscp: RPC_ClassVersion = 0100
08:43:48: cdscp: CDS_CTS = 1997-04-03-12:20:27.362226100/aa-00-04-00-a6-a9
08:43:48: cdscp: CDS_UTS = 1997-04-03-12:20:35.592168100/aa-00-04-00-a6-a9
08:43:48: cdscp: CDS_ObjectUUID = a8223cf0-ac1c-11d0-96a8-08002be7a953
08:43:48: cdscp: CDS_Replicas = :
08:43:48: cdscp: Clearinghouse UUID = a73ab055-ac1c-11d0-96a8-08002be7a953
08:43:48: cdscp: Tower = ncacn_ip_tcp:16.37.5.25
08:43:48: 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
08:43:48: 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
08:43:48: cdscp: Tower 2 Floor 3 = 0b 00 00 connection
08:43:48: cdscp: Tower 2 Floor 4 = 02 00 00 ncacn_dnet_nsp
08:43:48: cdscp: Tower 2 Floor 5 = 04 (null)
08:43:48: cdscp: Tower 2 Floor 6 = 06 49 00 2c aa 00 04 00 1f b3 20
08:43:48: cdscp: Tower 3 Floor 1 = 0d c9 f1 7d 25 d3 c6 ca 11 85 54 08 00 2b 1c 8f 1f 01 00
00 00
08:43:48: cdscp: Tower 3 Floor 2 = 0d 04 5d 88 8a eb 1c c9 11 9f e8 08 00 2b 10 48 60 02 00
00 00
08:43:48: cdscp: Tower 3 Floor 3 = 0a 00 00 datagram
08:43:48: cdscp: Tower 3 Floor 4 = 08 00 00 port: 0, ncadg_ip_udp
08:43:48: cdscp: Tower 3 Floor 5 = 09 10 25 05 19 host: 16.37.5.25
08:43:48: cdscp: Replica type = master
08:43:48: cdscp: Clearinghouse Name = /.../adi_reo/esme_ch
08:43:48: cdscp: CDS_AllUpTo = 1997-04-08-01:07:01.366238100/aa-00-04-00-a6-a9
08:43:48: cdscp: CDS_Convergence = medium
08:43:48: cdscp: CDS_InCHName = allowed
08:43:48: cdscp: CDS_DirectoryVersion = 3.0
08:43:48: cdscp: CDS_ReplicaState = on
08:43:48: cdscp: CDS_ReplicaType = master
08:43:48: cdscp: CDS_LastSkulk = 1997-04-08-01:07:01.366238100/aa-00-04-00-a6-a9
08:43:48: cdscp: CDS_LastUpdate = 1997-04-07-14:06:56.705780100/aa-00-04-00-a6-a9
08:43:48: cdscp: CDS_RingPointer = a73ab055-ac1c-11d0-96a8-08002be7a953
08:43:48: cdscp: CDS_Epoch = a8223cef-ac1c-11d0-96a8-08002be7a953
08:43:48: cdscp: CDS_ReplicaVersion = 3.0
08:43:48: cdscp: Warning: you have no network credentials. All requests will be unauthenticated.
08:43:49: Create pe_site file
08:43:49: INTERNAL ERROR: Unable to create child process.
08:43:49: File deleted: E:\OPT\DIGITAL\W95\DCELOCAL\PeSite.tmp
09:13:12: DCE configuration either failed or was aborted
-------- 04/08/97 at 09:13:13 --------------------------
========================================================
End of DCE client configuration
========================================================
When all this had finished, I could see using the status panel in DCE setup
that the following daemons were running: RPC and CDS Advertiser. The Security
Client, Integrated Login and DTS daemons were also enabled but were not
running.
.
CMOT (Windows NT 4 / Intel)
-------- 04/08/97 at 08:50:46 --------------------------
========================================================
New DCEsetup log created
========================================================
-------- 04/08/97 at 08:50:48 --------------------------
========================================================
Beginning DCE client configuration.
========================================================
08:50:48: DCE service already running. [RPCSS]
08:50:48: Running getcells.exe to get a list of known cells.
08:51:10: File deleted: E:\OPT\DIGITAL\DCELOCAL\cells.txt
08:51:21:
08:51:21: Configuration data collected for this run of dcesetup...
08:51:21: Cell Name = adi_reo
08:51:21: Host Name = cmot
08:51:21: Security Server Host Name = esme.reo.dec.com
08:51:21: CDS Server Host Name =
08:51:21: Gda Domain Name =
08:51:21: Lan Name =
08:51:22: Following DCE components are being configured
08:51:22: Security Client
08:51:22: Integrated Login Service
08:51:22: CDS client
08:51:22: DTS Clerk
08:51:22:
08:51:22: DCE service already running. [RPCSS]
08:51:22: Creating DCE_CF.DB file.
08:51:22: Stopping DCE services.
08:51:26: Checking for Integrated Login support in the registry
08:51:27: Removing permanent DCE database files.
08:51:27: Creating dcelocal directories.
08:51:27: Starting DCE Service. [Cdsadv]
08:51:27: DCE service started. [Cdsadv]
08:51:27: Checking status of service.
08:51:30: cdscp show dir /.:/
08:51:30: Testing access to CDS clerk.
08:51:34: cdscp: SHOW
08:51:34: cdscp: DIRECTORY /.../adi_reo
08:51:34: cdscp: AT 1997-04-08-07:51:31
08:51:34: cdscp: Error on entity: /.../adi_reo
08:51:34: cdscp: Requested entry does not exist error ( dce / cds )
08:51:34: cdscp: Function: dnsEnumAttr
08:51:34: cdscp: dnsEnumAttr: partial results = %x000000000000000000000000000000000000
08:51:34: cdscp: Warning: you have no network credentials. All requests will be unauthenticated.
08:51:45: Testing access to CDS clerk.
08:51:49: cdscp: SHOW
08:51:49: cdscp: DIRECTORY /.../adi_reo
08:51:49: cdscp: AT 1997-04-08-07:51:45
08:51:49: cdscp: RPC_ClassVersion = 0100
08:51:49: cdscp: CDS_CTS = 1997-04-03-12:20:27.362226100/aa-00-04-00-a6-a9
08:51:49: cdscp: CDS_UTS = 1997-04-03-12:20:35.592168100/aa-00-04-00-a6-a9
08:51:49: cdscp: CDS_ObjectUUID = a8223cf0-ac1c-11d0-96a8-08002be7a953
08:51:49: cdscp: CDS_Replicas = :
08:51:49: cdscp: Clearinghouse UUID = a73ab055-ac1c-11d0-96a8-08002be7a953
08:51:49: cdscp: Tower = ncacn_ip_tcp:16.37.5.25
08:51: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
08:51: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
08:51:49: cdscp: Tower 2 Floor 3 = 0b 00 00 connection
08:51:49: cdscp: Tower 2 Floor 4 = 02 00 00 ncacn_dnet_nsp
08:51:49: cdscp: Tower 2 Floor 5 = 04 (null)
08:51:49: cdscp: Tower 2 Floor 6 = 06 49 00 2c aa 00 04 00 1f b3 20
08:51:49: cdscp: Tower = ncadg_ip_udp:16.37.5.25
08:51:49: cdscp: Replica type = master
08:51:49: cdscp: Clearinghouse Name = /.../adi_reo/esme_ch
08:51:49: cdscp: CDS_AllUpTo = 1997-04-08-01:07:01.366238100/aa-00-04-00-a6-a9
08:51:49: cdscp: CDS_Convergence = medium
08:51:49: cdscp: CDS_InCHName = allowed
08:51:49: cdscp: CDS_DirectoryVersion = 3.0
08:51:49: cdscp: CDS_ReplicaState = on
08:51:49: cdscp: CDS_ReplicaType = master
08:51:49: cdscp: CDS_LastSkulk = 1997-04-08-01:07:01.366238100/aa-00-04-00-a6-a9
08:51:49: cdscp: CDS_LastUpdate = 1997-04-07-14:06:56.705780100/aa-00-04-00-a6-a9
08:51:49: cdscp: CDS_RingPointer = a73ab055-ac1c-11d0-96a8-08002be7a953
08:51:49: cdscp: CDS_Epoch = a8223cef-ac1c-11d0-96a8-08002be7a953
08:51:49: cdscp: CDS_ReplicaVersion = 3.0
08:51:49: cdscp: Warning: you have no network credentials. All requests will be unauthenticated.
08:51:50: Create pe_site file
08:51:51: getcellinfo: Attempting to locate security server
08:51:51: getcellinfo: Found security server
08:51:51: getcellinfo: Creating E:\OPT\DIGITAL/dcelocal/etc/security/pe_site file
08:51:55: File deleted: E:\OPT\DIGITAL\DCELOCAL\PeSite.tmp
08:51:55: Attempting to locate time servers in the target cell.
08:51:55: Unable to get time from server.
09:19:54: File deleted: E:\OPT\DIGITAL\DCELOCAL\bindings.tmp
09:19:54: Stopping DCE service. [Cdsadv]
09:19:55: DCE service stopped. [Cdsadv]
09:19:57: Logging into DCE...
09:19:58: Login to DCE successful.
09:19:58: Creating principal hosts/cmot/self
09:19:59: Creating account hosts/cmot/self
09:20:00: ktadd -p hosts/cmot/self -pw ******
09:20:00: ktadd -p hosts/cmot/self -a -r
09:20:00: The service does not exist. [Sec_Clientd]
09:20:01: DCE service installed. [Sec_Clientd]
09:20:01: Starting DCE Service. [Sec_Clientd]
09:20:02: DCE service started. [Sec_Clientd]
09:20:02: Checking status of service.
09:20:04: Starting DCE Service. [Cdsadv]
09:20:05: DCE service started. [Cdsadv]
09:20:05: Checking status of service.
09:20:07: cdscp show clerk
09:20:07: Testing access to the CDS server.
09:20:08: cdscp: SHOW
09:20:08: cdscp: CLERK
09:20:08: cdscp: AT 1997-04-08-08:20:08
09:20:08: cdscp: Creation Time = 1997-04-08-08:20:05.984+00:
09:20:08: cdscp: Authentication Failures = 0
09:20:08: cdscp: Read Operations = 76
09:20:08: cdscp: Cache Hits = 32
09:20:08: cdscp: Cache Bypasses = 16
09:20:08: cdscp: Write Operations = 1
09:20:08: cdscp: Miscellaneous Operations = 0
09:20:09: Testing access to CDS server
09:20:14: cdscp: SHOW
09:20:14: cdscp: DIRECTORY /.../adi_reo
09:20:14: cdscp: AT 1997-04-08-08:20:09
09:20:14: cdscp: RPC_ClassVersion = 0100
09:20:14: cdscp: CDS_CTS = 1997-04-03-12:20:27.362226100/aa-00-04-00-a6-a9
09:20:14: cdscp: CDS_UTS = 1997-04-03-12:20:35.592168100/aa-00-04-00-a6-a9
09:20:14: cdscp: CDS_ObjectUUID = a8223cf0-ac1c-11d0-96a8-08002be7a953
09:20:14: cdscp: CDS_Replicas = :
09:20:14: cdscp: Clearinghouse UUID = a73ab055-ac1c-11d0-96a8-08002be7a953
09:20:14: cdscp: Tower = ncacn_ip_tcp:16.37.5.25
09:20:14: 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
09:20:14: 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
09:20:14: cdscp: Tower 2 Floor 3 = 0b 00 00 connection
09:20:14: cdscp: Tower 2 Floor 4 = 02 00 00 ncacn_dnet_nsp
09:20:14: cdscp: Tower 2 Floor 5 = 04 (null)
09:20:14: cdscp: Tower 2 Floor 6 = 06 49 00 2c aa 00 04 00 1f b3 20
09:20:14: cdscp: Tower = ncadg_ip_udp:16.37.5.25
09:20:14: cdscp: Replica type = master
09:20:14: cdscp: Clearinghouse Name = /.../adi_reo/esme_ch
09:20:14: cdscp: CDS_AllUpTo = 1997-04-08-01:07:01.366238100/aa-00-04-00-a6-a9
09:20:14: cdscp: CDS_Convergence = medium
09:20:14: cdscp: CDS_InCHName = allowed
09:20:14: cdscp: CDS_DirectoryVersion = 3.0
09:20:14: cdscp: CDS_ReplicaState = on
09:20:14: cdscp: CDS_ReplicaType = master
09:20:14: cdscp: CDS_LastSkulk = 1997-04-08-01:07:01.366238100/aa-00-04-00-a6-a9
09:20:14: cdscp: CDS_LastUpdate = 1997-04-08-08:07:04.102091300/aa-00-04-00-a6-a9
09:20:14: cdscp: CDS_RingPointer = a73ab055-ac1c-11d0-96a8-08002be7a953
09:20:14: cdscp: CDS_Epoch = a8223cef-ac1c-11d0-96a8-08002be7a953
09:20:14: cdscp: CDS_ReplicaVersion = 3.0
09:20:15: Configuring CDS client.
09:20:15: Checking to see if directory exists: hosts/cmot
09:20:15: Creating directory: hosts/cmot
09:20:16: Creating namespace entry: hosts/cmot/self
09:20:17: Creating namespace entry: hosts/cmot/cds-clerk
09:20:17: Creating namespace entry: hosts/cmot/profile
09:20:17: Checking for the existence of multiple LAN profiles in cell.
09:20:23: Creating LAN profile for this host.
09:20:24: > rpccp add element /.:/hosts/cmot/profile -i 6f264242-b9f8-11c9-ad31-08002b0dc035,0001.0000 -m
/.:/lan-16.37.5-profile -a LAN -p 0
09:20:28: rpccp: >>> profile element added
09:20:29: File deleted: E:\OPT\DIGITAL\DCELOCAL\MultiLan.Tmp
09:20:29: rpccp add element /.:/hosts/cmot/profile -m /.:/cell-profile -d -p 0
09:20:33: rpccp: >>> default profile element added
09:20:34: Exporting cds-clerk DACL manager UUID.
09:20:34: rpccp export -i 4ea31de8-9a94-11c9-bb60-08002b0f79aa,3.0 -o dc8c6fc0-6143-11ca-b4b9-08002b1bb4f5 -b
ncacn_ip_tcp:cmot /.:/hosts/cmot/cds-clerk
09:20:38: rpccp: >>> binding information and objects exported
09:20:39: rpccp export -i 4ea31de8-9a94-11c9-bb60-08002b0f79aa,3.0 -o dc8c6fc0-6143-11ca-b4b9-08002b1bb4f5 -b
ncadg_ip_udp:cmot /.:/hosts/cmot/cds-clerk
09:20:43: rpccp: >>> binding information and objects exported
09:20:44: Set up acls for host
09:20:44: Modifying acl for /.:/hosts/cmot, principal: hosts/cmot/self, permissions: rwdtcia
09:20:44: ****ERROR**** DOM library error, status: dce801a
09:20:44: ***WARNING*** DOM library error, status: dce801a, Try again.
09:20:46: ****ERROR**** DOM library error, status: dce801a
09:20:46: ***WARNING*** DOM library error, status: dce801a, Try again.
09:20:48: ****ERROR**** DOM library error, status: dce801a
09:20:48: ***WARNING*** DOM library error, status: dce801a, Try again.
09:20:51: ****ERROR**** DOM library error, status: dce801a
09:20:51: ***WARNING*** DOM library error, status: dce801a, Try again.
09:20:53: ****ERROR**** DOM library error, status: dce801a
09:20:53: ***WARNING*** DOM library error, status: dce801a, Try again.
09:20:55: ****ERROR**** DOM library error, status: dce801a
09:20:55: ***WARNING*** DOM library error, status: dce801a, Try again.
09:20:57: ****ERROR**** DOM library error, status: dce801a
09:20:57: ***WARNING*** DOM library error, status: dce801a, Try again.
09:20:59: ****ERROR**** DOM library error, status: dce801a
09:21:00: ***WARNING*** DOM library error, status: dce801a, Try again.
09:21:02: ****ERROR**** DOM library error, status: dce801a
09:21:02: ***WARNING*** DOM library error, status: dce801a, Try again.
09:21:04: ****ERROR**** DOM library error, status: dce801a
09:21:04: ***WARNING*** DOM library error, status: dce801a, Try again.
09:21:06: ****ERROR**** DOM library error, status: dce801a
09:21:07: DCE configuration either failed or was aborted
-------- 04/08/97 at 09:21:08 --------------------------
========================================================
End of DCE client configuration
========================================================
-------- 04/08/97 at 09:21:23 --------------------------
========================================================
Begin Digital DCE Setup Session
========================================================
When this finished running, RPC, Security Client and CDS Advertiser were all
running.
.
CORDAY (Windows NT 4 / Alpha)
-------- 04/08/97 at 08:37:58 --------------------------
========================================================
New DCEsetup log created
========================================================
-------- 04/08/97 at 08:38:00 --------------------------
========================================================
Beginning DCE client configuration.
========================================================
08:38:00: DCE service already running. [RPCSS]
08:38:01: Running getcells.exe to get a list of known cells.
08:38:02: Getcells.exe failed. Cellname list could not be obtained.
08:38:20:
08:38:20: Configuration data collected for this run of dcesetup...
08:38:20: Cell Name = adi_reo
08:38:20: Host Name = corday
08:38:20: Security Server Host Name = esme.reo.dec.com
08:38:20: CDS Server Host Name = esme.reo.dec.com
08:38:20: Gda Domain Name =
08:38:20: Lan Name =
08:38:20: Following DCE components are being configured
08:38:20: Security Client
08:38:21: Integrated Login Service
08:38:21: CDS client
08:38:21: DTS Clerk
08:38:21:
08:38:21: DCE service already running. [RPCSS]
08:38:21: Creating DCE_CF.DB file.
08:38:21: Stopping DCE services.
08:38:26: Checking for Integrated Login support in the registry
08:38:26: Removing permanent DCE database files.
08:38:26: Creating dcelocal directories.
08:38:26: Starting DCE Service. [Cdsadv]
08:38:26: DCE service started. [Cdsadv]
08:38:27: Checking status of service.
08:38:29: cdscp show dir /.:/
08:38:29: Testing access to CDS clerk.
08:38:34: cdscp: SHOW
08:38:34: cdscp: DIRECTORY /.../adi_reo
08:38:34: cdscp: AT 1997-04-08-07:38:30
08:38:34: cdscp: Error on entity: /.../adi_reo
08:38:34: cdscp: Requested entry does not exist error ( dce / cds )
08:38:34: cdscp: Function: dnsEnumAttr
08:38:34: cdscp: dnsEnumAttr: partial results = %x00000000000000000000000000000000000
08:38:34: cdscp: Warning: you have no network credentials. All requests will be unauthenticated.
08:38:45: Testing access to CDS clerk.
08:38:51: cdscp: SHOW
08:38:51: cdscp: DIRECTORY /.../adi_reo
08:38:51: cdscp: AT 1997-04-08-07:38:46
08:38:51: cdscp: Error on entity: /.../adi_reo
08:38:51: cdscp: Requested entry does not exist error ( dce / cds )
08:38:51: cdscp: Function: dnsEnumAttr
08:38:51: cdscp: dnsEnumAttr: partial results = %x000000000000000000000000000000000000
08:38:51: cdscp: Warning: you have no network credentials. All requests will be unauthenticated.
08:39:02: Testing access to CDS clerk.
08:39:07: cdscp: SHOW
08:39:07: cdscp: DIRECTORY /.../adi_reo
08:39:07: cdscp: AT 1997-04-08-07:39:02
08:39:07: cdscp: Error on entity: /.../adi_reo
08:39:07: cdscp: Requested entry does not exist error ( dce / cds )
08:39:07: cdscp: Function: dnsEnumAttr
08:39:07: cdscp: dnsEnumAttr: partial results = %x00000000000000000000000000000000000
08:39:07: cdscp: Warning: you have no network credentials. All requests will be unauthenticated.
08:39:18: Testing access to CDS clerk.
08:39:24: cdscp: SHOW
08:39:24: cdscp: DIRECTORY /.../adi_reo
08:39:24: cdscp: AT 1997-04-08-07:39:19
08:39:24: cdscp: Error on entity: /.../adi_reo
08:39:24: cdscp: Requested entry does not exist error ( dce / cds )
08:39:24: cdscp: Function: dnsEnumAttr
08:39:24: cdscp: dnsEnumAttr: partial results = %x000000000000000000000000000000000000
08:39:24: cdscp: Warning: you have no network credentials. All requests will be unauthenticated.
08:39:35: Testing access to CDS clerk.
08:39:40: cdscp: SHOW
08:39:40: cdscp: DIRECTORY /.../adi_reo
08:39:40: cdscp: AT 1997-04-08-07:39:35
08:39:40: cdscp: Error on entity: /.../adi_reo
08:39:40: cdscp: Requested entry does not exist error ( dce / cds )
08:39:40: cdscp: Function: dnsEnumAttr
08:39:40: cdscp: dnsEnumAttr: partial results = %x000000000000000000000000000000000000
08:39:40: cdscp: Warning: you have no network credentials. All requests will be unauthenticated.
08:39:51: Testing access to CDS clerk.
08:39:56: cdscp: SHOW
08:39:56: cdscp: DIRECTORY /.../adi_reo
08:39:56: cdscp: AT 1997-04-08-07:39:51
08:39:56: cdscp: Error on entity: /.../adi_reo
08:39:56: cdscp: Requested entry does not exist error ( dce / cds )
08:39:56: cdscp: Function: dnsEnumAttr
08:39:56: cdscp: dnsEnumAttr: partial results = %x000000000000000000000000000000000000
08:39:56: cdscp: Warning: you have no network credentials. All requests will be unauthenticated.
08:40:07: Testing access to CDS clerk.
08:40:13: cdscp: SHOW
08:40:13: cdscp: DIRECTORY /.../adi_reo
08:40:13: cdscp: AT 1997-04-08-07:40:08
08:40:13: cdscp: Error on entity: /.../adi_reo
08:40:13: cdscp: Requested entry does not exist error ( dce / cds )
08:40:13: cdscp: Function: dnsEnumAttr
08:40:13: cdscp: dnsEnumAttr: partial results = %x000000000000000000000000000000000000
08:40:13: cdscp: Warning: you have no network credentials. All requests will be unauthenticated.
08:40:24: Testing access to CDS clerk.
08:40:30: cdscp: SHOW
08:40:30: cdscp: DIRECTORY /.../adi_reo
08:40:30: cdscp: AT 1997-04-08-07:40:25
08:40:30: cdscp: Error on entity: /.../adi_reo
08:40:30: cdscp: Requested entry does not exist error ( dce / cds )
08:40:30: cdscp: Function: dnsEnumAttr
08:40:30: cdscp: dnsEnumAttr: partial results = %x000000000000000000000000000000000000
08:40:30: cdscp: Warning: you have no network credentials. All requests will be unauthenticated.
08:40:41: Testing access to CDS clerk.
08:40:46: cdscp: SHOW
08:40:46: cdscp: DIRECTORY /.../adi_reo
08:40:46: cdscp: AT 1997-04-08-07:40:41
08:40:46: cdscp: Error on entity: /.../adi_reo
08:40:46: cdscp: Requested entry does not exist error ( dce / cds )
08:40:46: cdscp: Function: dnsEnumAttr
08:40:46: cdscp: dnsEnumAttr: partial results = %x000000000000000000000000000000000000
08:40:46: cdscp: Warning: you have no network credentials. All requests will be unauthenticated.
08:40:57: Testing access to CDS clerk.
08:41:02: cdscp: SHOW
08:41:02: cdscp: DIRECTORY /.../adi_reo
08:41:02: cdscp: AT 1997-04-08-07:40:57
08:41:02: cdscp: Error on entity: /.../adi_reo
08:41:02: cdscp: Requested entry does not exist error ( dce / cds )
08:41:02: cdscp: Function: dnsEnumAttr
08:41:02: cdscp: dnsEnumAttr: partial results = %x000000000000000000000000000000000000
08:41:02: cdscp: Warning: you have no network credentials. All requests will be unauthenticated.
08:41:13: Can't access CDS clerk or server.
08:54:23: DCE configuration either failed or was aborted
-------- 04/08/97 at 08:54:23 --------------------------
========================================================
End of DCE client configuration
========================================================
And then the following dialog box:
Can't access CDS clerk or server
When all this had finished, I could see using the status panel in DCE setup
that the following daemons were running: RPC and CDS Advertiser. The Security
Client, Integrated Login and DTS daemons were also enabled but were not
running.
Needless to say, I am quite worried about this problem. The symptoms on each
PC are slightly different, but none of them can join the cell. This is causing
a real problem for me. At least two of them couldn't find a time server. The
following DCE processes have been running throughout the period that I ran the
above setups:
OpenVMS V6.2 on node ESME 8-APR-1997 09:25:46.88 Uptime 4 20:34:18
Pid Process Name State Pri I/O CPU Page flts Pages
0000015F DCE$RPCD HIB 8 304894 0 00:01:43.04 941 349
00000160 DCE$SECD HIB 10 122864 0 00:00:56.46 1639 662
00000162 DCE$SEC_CLIENTD HIB 8 57808 0 00:00:39.12 1198 415
00000163 DCE$CDSADV LEF 8 232179 0 00:01:27.55 1226 365
00000164 DCE$CDSCLERK HIB 8 378445 0 00:03:18.97 1468 551
00000165 DCE$CDSD HIB 8 499249 0 00:03:52.64 1707 623
00000166 DCE$DTSD HIB 12 396066 0 00:02:12.47 1296 439
00000167 DCE$NSID HIB 8 53939 0 00:00:30.47 1245 425
00000196 SVB$REGISTRY HIB 6 1923 0 00:00:00.72 828 463
The SVB$REGISTRY is a layered product that we developed on top of DCE. It
advertises itself within CDS, and clients find it using CDS. This all works
right now - the cell appears to be well-behaved on the main server node ESME.
I have a second VMS Alpha machine (WINDLE), on which I've just installed DCE
V1.4 and the 10,000 day patch (ALPLIBR05_070). I ran through DCE setup on this
machine (after clobbering the old configuration), to get it to join the cell
hosted by ESME, and this is what happened:
Starting DCE client configuration . . .
This system has no current DCE configuration.
Based on this configuration, there should be no active DCE daemons.
At each prompt, enter your response. You may enter <RETURN> for
the default response, displayed in [brackets], or '?' for help.
Entering a CONTROL-Z will terminate this configuration request.
Press <RETURN> to continue . . .
Removing temporary local DCE databases . . .
Removing permanent local DCE databases . . .
Starting Remote Procedure Call Services daemon (DCE$RPCD) . . .
%RUN-S-PROC_ID, identification of created process is 00000121
Please enter the DCE hostname for this system [windle]:
Do you wish to search the LAN for known DCE cells (YES/NO/?) [Y]?
Searching, please wait . . .
The following cells were discovered within broadcast range of this system:
adi_reo
Please enter the name for your DCE cell [adi_reo]:
Hostname: windle
Cellname: adi_reo
Do you want to save these names for your DCE configuration (YES/NO/?) [Y]?
Please enter the hostname of the DCE security registry [adi_reo]: esme
Checking TCP/IP local host database for address of "esme". Please wait . . .
Please enter the principal name to be used [cell_admin]:
Please enter the password for principal "cell_admin" (or ? for help):
Checking for supported protocol sequence. Please wait . . .
Do you want to enable DCE DTS (YES/NO/?) [Y]?
Do you want this host to be a DCE DTS Server (YES/NO/?) [N]?
Do you want to enable DCE integrated login support (YES/NO/?) [N]?
Remote Procedure Call Services Enabled
Security Services Client Enabled
CDS Name Service Client Enabled
PC Name Service Interface Disabled
Distributed Time Service Clerk Enabled
Integrated login Disabled
Do you want to save this service configuration (YES/NO/?) [Y]?
Establishing security environment for principal "cell_admin" . . .
Starting Security Service Client daemon (DCE$SEC_CLIENTD) . . .
%RUN-S-PROC_ID, identification of created process is 00000122
Testing access to the security registry . . .
Initializing CDS...
Starting CDS Name Service Advertiser daemon (DCE$CDSADV) . . .
%RUN-S-PROC_ID, identification of created process is 00000123
Starting CDS Name Service Client daemon (DCE$CDSCLERK) . . .
%RUN-S-PROC_ID, identification of created process is 00000124
Testing access to the CDS Master Server . . .
Not found. Retry #1 . . .
Not found. Retry #2 . . .
Not found. Retry #3 . . .
Not found. Retry #4 . . .
Configuring client host objects in the cell namespace . . .
The following objects were found in namespace directory "/.:/hosts/windle":
cds-clerk
profile
self
Deleting known objects from namespace directory "/.:/hosts/windle" . . .
**************************** WARNING ****************************
*** There are additional objects in the directory:
*** /.:/hosts/windle
***
*** These objects will not be removed and the directory will remain
*** in the namespace with it's current ACL's.
Setting up required objects in namespace directory "/.:/hosts/windle" . . .
Testing for multi-LAN cell . . .
This cell has been configured to span multiple LAN's. The known LAN's are:
16.37.5
Please enter the name of the LAN for this host [16.37.5]:
Creating namespace directories and objects . . .
Configuring required RPC information . . .
Modifying ACL's on namespace objects . . .
/.:/hosts/windle
/.:/hosts/windle/self
/.:/hosts/windle/cds-clerk
/.:/hosts/windle/profile
Starting Distributed Time Service daemon (DCE$DTSD) . . .
%RUN-S-PROC_ID, identification of created process is 00000125
Press <RETURN> to continue . . .
... and then we get back to the DCE Configuration Menu. I then selected the
TEST option, and got the following result:
Test requires that a DCE_LOGIN be performed
Please enter the principal name to be used [cell_admin]:
Please enter the password for principal "cell_admin" (or ? for help):
Logging in to DCE using principal "cell_admin" . . .
Executing DCE V1.4 for OpenVMS Alpha CVP (please wait)
Copyright (c) Digital Equipment Corporation. 1993,1996. All Rights Reserved.
.........1
DCE V1.4 for OpenVMS Alpha CVP was successful.
So it appears that I managed to get another VMS machine to join the cell, but
did get errors when trying to access the CDS Master Server. If I run an
application on the client node (WINDLE - OpenVMS/Alpha) that tries to access
our Service Broker registry on ESME via CDS, then this DOES work. However, I
can't use CDS on any of our PCs, because they did not succeed in joining the
cell.
In summary, every OpenVMS or Windows machine in our group that runs DCE has
some kind of problem when it attempts to join the cell hosted on ESME. I'm
unsure of the vintage of the DCE installation on our UNIX system, and so I
wouldn't want to cloud the issue further by trying that at the moment.
I don't know whether I've got a problem with the windows clients, the OpenVMS
server, or both. I do know that all the problems with the windows clients
started after the clocks changed.
As an experiment - ESME dual boots OpenVMS/AXP 6.2 and 7.1. An hour ago I booted
it under 7.1, installed DCE 1.4 (layered over UCX 4.1 ECO 2), configured a new
cell, and tried running DCE setup on CORDAY again (Windows NT alpha).
I got EXACTLY the same log file as I had obtained when ESME was running 6.2.
I'd really values any ideas as to what I could try to get our PCs to join
our DCE cell again.
Thanks,
Cameron
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2212.1 | What are local time and time zones on the systems | STAR::SWEENEY | | Wed Apr 09 1997 17:03 | 10 |
|
I did not wade through all the information in .1 but can you tell me what the date/time setup on the clients gives
you as the local time and the timezone? Does the local time and timezone look correct on the vms systems?
Do a
$ show logicals *time*
$ dtscp show current time
on the vms servers. Do the times, timezone and daylight savings time settings agree with the clients.
Dave
|
| 2212.2 | My time info | ESME::SPENCE | Bugs? You mean insects? | Thu Apr 10 1997 08:11 | 48 |
| --- On ESME (currently running OpenVMS V7.1 + DCE V1.4 + UCX 4.1 (ECO 2)):
$ show logical *time*
(LNM$SYSTEM_TABLE)
"SYS$LOCALTIME" = "SYS$SYSROOT:[SYS$ZONEINFO.SYSTEM]GB-EIRE."
"SYS$TIMEZONE_DAYLIGHT_SAVING" = "1"
"SYS$TIMEZONE_DIFFERENTIAL" = "3600"
"SYS$TIMEZONE_NAME" = "BST"
"SYS$TIMEZONE_RULE" = "GMT0BST-1,M3.5.0/1,M10.5.0/2"
"UCX$BIND_TIMEOUT" = "...."
"UCX$CFS_ATTR_CACHE_TIMEOUT" = "5"
(DECW$LOGICAL_NAMES)
$ dtscp show current time
DTS control program is not authenticated
No currently established network identity for which context exists (dce / sec)
Current Time = 1997-04-10-12:02:01.744+01:00I-----
--- On CORDAY (currently running Windows NT/Alpha 4.0, service pack 1, DCE V1.1B):
* On the 'Date & Time' panel: Current time zone: British Summer Time
10th April 1997, 12:03
* On the 'Time zone' panel: (GMT) Greenwich Mean Time; Dublin, Edinburgh, London, Lisbon
The 'Automatically adjust clock for daylight savings changes'
check box IS selected
--- On CMOT (running Windows NT/Intel, DCE V1.1B)
The values are identical to those on CORDAY above.
--- On ELIZA and TPARTY (running Windows 95, DCE V1.0)
* On the 'Date & Time' panel: Current time zone: GMT Daylight Time
Time and date values are correct
This all looks consistent as far as I can see. I do admit this does look related to the time
configuration, given that the problems started when the clocks changed. However, the DCE clients
and the DCE server would appear to have consistent settings. Any other ideas? Is it possible that
there is some kind of inconsistency between the Windows and VMS implementations of DCE, given that
I don't get the same problem from a VMS client node (WINDLE)?
Has anyone else tried this since the clocks changed?
Thanks,
Cameron
|
| 2212.3 | DOM library error, status: dce801a | STAR::SWEENEY | | Thu Apr 10 1997 16:24 | 10 |
|
I do not know what the error "DOM library error, status: dce801a" means. Can
you explain to me what the PC error code dce801a means from the documentation
for the PC DCE your customer is using.
Anyone out there know what this means?
Dave
|
| 2212.4 | All DEC software... | ESME::SPENCE | Bugs? You mean insects? | Fri Apr 11 1997 05:48 | 25 |
| I'm the customer here. This is a DCE cell that we use
internally for developing software products and projects
for our customers.
All the DCE implementations here are from Digital.
On Windows NT, we're using DCE V1.1B.
On Windows 95, V1.0.
On OpenVMS, V1.4.
I don't know which particular implementation is causing
the problem here. I do know however, that the problem lies
either with (a) me, for doing something wrong in configuring
the software, or (b) one of Digital's DCE products. Given that
I've had a fair amount of experience in configuring our DCE
products (which, I have to say, I think are excellent), and
that the problems all started when the clocks jumped forward
an hour, I tend to suspect the latter rather than the former.
Perhaps we need to take a top-down view on this one. I would
not be keen to see this problem bounced back and forward
between the various DCE product groups. I'll do all I can to
help resolve this.
Thanks,
Cameron
|
| 2212.5 | Ok... DEC DCE for W95 | STAR::SWEENEY | | Fri Apr 11 1997 13:25 | 11 |
|
I believe all the DCE product groups read this conference. It certainly does
seem the problem is related to the time change. What is not obvious is what
the error status being returned from your client system means. I don't have the
W95 DCE product.
Can anyone answer the question in .3 or point me to some product documentation
that defines what the error code means?
Dave
|
| 2212.6 | | TUXEDO::MAZZAFERRO | | Mon Apr 14 1997 12:08 | 29 |
| "DOM library error, status dce801a" means "acl object not found".
Have you tried the configuration by first setting the RPC_SUPPORTED_PROTSEQS
environment variable to restrict it to just ncacn_ip_tcp? I'd be curious
to find out if they're causing some difficulty.
It's not uncommon for acl_edit to return an "acl object not found" error
when a principal who is not properly authorized attempts to modify
an acl on an object. The object truly does exist, but the message is
issued as an added measure of security. On the server, check the acls
on the following entries :
.:/hosts/eliza.reo.dec.com
.:/hosts/eliza.reo.dec.com/self
.:/hosts/eliza.reo.dec.com/cds-clerk
and .:/hosts/eliza.reo.dec.com/profile
The errors were generated when trying to modify the acls for the
hosts/eliza.reo.dec.com/self principal on each of these objects.
Also, check (from the server) the keytab entries for the self principal
by issing a rgy_edit> ktlist - I'm wondering if there are multiple keytab
entries for the hosts/eliza.reo.dec.com/self principal which might be
confusing things.
I'm not that familiar with the VMS 10,000 day problem, but I'm wondering
if that might also be having some side effects here.
Laura
|
| 2212.7 | Solves 2 out of 4... | ESME::SPENCE | Bugs? You mean insects? | Mon Apr 14 1997 13:32 | 118 |
| The machines that I was having problems with are:
CMOT Windows NT 4 Intel
ELIZA Windows 95 Intel
TPARTY Windows 95 Intel
CORDAY Windows NT 4 Alpha
I tried adding the RPC_SUPPORTED_PROTSEQS environment
variable to those machines in the above list that
didn't already have it (TPARTY, CMOT and ELIZA).
This was sufficient to allow the DCE setup to run
through to completion, successfully, on CMOT and
ELIZA, so we've managed to solve 2 out of 4 so far.
I think there's some other kind of problem with the
other two machines. Bear in mind that for both of
these, I've asked DCE setup to delete and recreate
any existing namespace objects.
The situation with TPARTY remains unchanged after
adding RPC_SUPPORTED_PROTSEQS (=ncacn_ip_tcp). It
seems to have a problem creating a child process,
as can be seen in the following extract from the
setup log:
17:13:25: Create pe_site file
17:13:25: INTERNAL ERROR: Unable to create child process.
17:13:25: File deleted: E:\OPT\DIGITAL\W95\DCELOCAL\PeSite.tmp
17:13:43: DCE configuration either failed or was aborted
The situation with CORDAY, the Windows NT / Alpha machine,
also remains unchanged. Because I managed to get the DCE
Director working on ELIZA and CMOT, I was able to check
the namespace; there are no entries underneath the /hosts/
directory for TPARTY and CORDAY (the ones that I can't add).
CORDAY's problem seems to relate to the naming services,
specifically the inability to see the ADI_REO cell in
the name space, as can be seen in the following extract
from its setup log:
17:16:10: DCE service already running. [RPCSS]
17:16:10: Running getcells.exe to get a list of known cells.
17:16:11: Getcells.exe failed. Cellname list could not be obtained.
(I had to enter the cell name manually here)
17:16:25: Configuration data collected for this run of dcesetup...
17:16:25: Cell Name = adi_reo
17:16:25: Host Name = corday
17:16:25: Security Server Host Name = esme.reo.dec.com
17:16:25: CDS Server Host Name = esme.reo.dec.com
17:16:25: Gda Domain Name =
17:16:25: Lan Name =
17:16:25: Following DCE components are being configured
17:16:25: Security Client
17:16:26: Integrated Login Service
17:16:26: CDS client
17:16:26: DTS Clerk
17:16:26: DCE service already running. [RPCSS]
17:16:26: Creating DCE_CF.DB file.
17:16:26: Stopping DCE services.
17:16:31: Checking for Integrated Login support in the registry
17:16:31: Removing permanent DCE database files.
17:16:31: Creating dcelocal directories.
17:16:32: Starting DCE Service. [Cdsadv]
17:16:32: DCE service started. [Cdsadv]
17:16:32: Checking status of service.
17:16:35: cdscp show dir /.:/
And now we go round the following loop exactly 10 times:
17:16:35: Testing access to CDS clerk.
17:16:40: cdscp: SHOW
17:16:40: cdscp: DIRECTORY /.../adi_reo
17:16:40: cdscp: AT 1997-04-14-16:16:36
17:16:40: cdscp: Error on entity: /.../adi_reo
17:16:40: cdscp: Requested entry does not exist error ( dce / cds )
17:16:40: cdscp: Function: dnsEnumAttr
17:16:40: cdscp: dnsEnumAttr: partial results = %x000000000000000000000000000000000000
17:16:40: cdscp: Warning: you have no network credentials. All requests will be unauthenticated.
Finally it gives up:
17:19:30: Can't access CDS clerk or server.
17:20:26: DCE configuration either failed or was aborted
I also tried looking on the server (ESME.REO.DEC.COM - running OpenVMS 7.1/DCE 1.4)
for the keytab entries, using the commands suggested in .-1, and got the following:
$ dce_login
Enter Principal Name: cell_admin
Enter Password:
$ rgy_edit
Current site is: registry server at /.../adi_reo/subsys/dce/sec/master
rgy_edit=> ktlist
/.../adi_reo/hosts/esme/self 1
/.../adi_reo/hosts/esme/cds-server 1
/.../adi_reo/hosts/esme/cds-server 2
/.../adi_reo/hosts/esme/pc-user 1
/.../adi_reo/hosts/esme/pc-user 2
rgy_edit=>
None of the four Windows machines appears in here - even those that appear to
be working now.
The problem with TPARTY could, I suppose, be quota related - but I don't
know where to look for this on Windows 95 - any ideas?
As for CORDAY (Alpha/NT) - I have no idea either. It already has the
RPC_SUPPORTED_PROTSEQS environment variable set to restrict the transport
to TCP/IP.
Is there anything else I can try for TPARTY and CORDAY?
Thanks for the help so far,
Cameron
|
| 2212.8 | | TUXEDO::MAZZAFERRO | | Mon Apr 14 1997 14:17 | 16 |
| The Win95 box is failing when it attempts to run getcellinfo from within
DCEsetup. When it's reached that point in the configuration, try running
getcellinfo from an MS-DOS prompt. The binary should be located in
opt\<digital>\dce\bin. If you truly can't invoke any more child processes,
you may need to reboot to relinquish whatever system resources have been
used up. We don't set any quotas on these systems during installation.
It's very interesting that another binary (getcells.exe) also failed
on the NT box. Its inability to run getcells shouldn't have a detrimental
side affect though since you are able to enter the cellname manually.
Be sure to run a clobber before each new configuration attempt. Then,
reboot each system, set RPC_SUPPORTED_PROTSEQS and let us know if there's
any improvement.
Laura
|
| 2212.9 | CDS possibilities | TUXEDO::ZEE | There you go. | Mon Apr 14 1997 18:49 | 10 |
| On CORDAY, see if it knows where the CDS server is by dumping the cache
via "cdscp dump clerk cache". There should be a CACHED CLEARINGHOUSE
entry pointing to the CDS server on esme.reo.dec.com. If there is not,
that explains why the "show directory /.../adi_reo" failed. Why would
it fail? Perhaps an error in translating esme.reo.dec.com to its
address, or the "cdscp define cached server" command failed, or if
someone ran "getcells" on esme.reo.dec.com, you should restart DCE
on that node.
--Roger
|
| 2212.10 | Further attempts... | ESME::SPENCE | Bugs? You mean insects? | Tue Apr 15 1997 09:19 | 136 |
| Looking at the suggestions in .9 first, I typed the following
in a Command Prompt on CORDAY:
cdscp dump clerk cache
and got the following results:
Warning: you have no network credentials. All requests will be unauthenticated.
PRIVATE CACHE**************
Default timeout = 300 seconds
CACHED DIRECTORIES*****************
CACHED CLEARINGHOUSES***************
CACHED ATTRIBUTE VALUES**************
CACHED USERS*************************
Cannot map shared cache - check CDS Advertiser service
I then stopped and restarted DCE on ESME (the server) and
ran the CVP - which was successful.
I then clobbered the configuration on CORDAY again and
ran DCE setup (the RPC_SUPPORTED_PROTSEQS is still set
to ncacn_ip_tcp). As before, getcells.exe failed on
this node. If you type getcells in a command prompt,
you can see why it failed (DCEsetup doesn't show you
this information):
Assertion failed: rpc_status == rpc_s_ok, file .\getcells.c, line 482
abnormal program termination
Sure, I can type in the cell name manually, but maybe this indicates
that something else is wrong - is this just the symptom of an
underlying problem somewhere else?
I know that there is no problem with the communication between
CORDAY and ESME, as far as TCP/IP is concerned. PING works fine;
I'm writing this using CORDAY as an X-server, with Notes running
on ESME...
I then ran the setup for a second time, and let it go through
to completion having manually selected the cell name. As I ran
it, I noticed that the CDS Master Server WAS within Broadcast
Range. I selected 'delete and recreate existing namespace objects'.
I'm still getting the same error:
cdscp: Error on entity: /.../adi_reo
cdscp: Requested entry does not exist error (dce/cds)
cdscp: Function: dnsEnumAttr: partial results = %x0000...
Now that DCE setup is finished, I can see that the CDS Advertiser
is now running on CORDAY (although the setup failed). If I type
the 'cdscp dump clerk cache' command on CORDAY again, I get:
Warning: you have no network credentials. All requests will be unauthenticated.
PRIVATE CACHE*****
Default timeout = 300 seconds
CACHED DIRECTORIES*********
CACHED CLEARINGHOUSES*********
CACHED ATTRIBUTE VALUES**********
CACHED USERS**************
SHARED CACHE**************
Default timeout = 300 seconds
CACHED DIRECTORIES***********
CACHED CLEARINGHOUSES*********
CACHED ATTRIBUTE VALUES************
CACHED USERS**************
There does not seem to be an entry for ESME in here.
I tried the DEFINE SERVER routine manually in a command prompt
on CORDAY:
cdscp> define cached server esme.reo.dec.com tower ncacn_ip_tcp:16.37.5.25
This did not generate any error messages. I then tried the dump command again,
and got, in the SHARED CACHE section:
CACHED DIRECTORIES************************
/.../adi_reo
ReadOnly at /.../adi_reo/esme_ch
Clearinghouse UID: ff018998-b025-11d0-addf-08002be7a953
Clearinghouse Address:
ncacn_ip_tcp:16.37.5.25
ncacdg_ip_tcp:16.37.5.25
CACHED CLEARINGHOUSES*********************
/.../adi_reo/esme_ch
Clearinghoue UID: ff018998-b025-11d0-addf-08002be7a953
Clearinghouse Address:
ncacn_ip_tcp:16.37.5.25
ncacdg_ip_tcp:16.37.5.25
Clearinghouse management name: esme.reo.dec.com
AddressUsed Sticky Ok
It looks like entering this command has made CORDAY 'see' the name
services on ESME. I'd like to know why DCE setup couldn't make this
work. Could it be that it tried to use UDP, which is disabled on
my machine (via RPC_SUPPORTED_PROTSEQS)? Just a guess.
I then ran DCE setup again, to see if having entered this information
once manually, the setup could get any further. It looks like the setup
program deletes lots of files, including the one which had stored my
cached clearinghouse information, so the SHOW DIRECTORY command is
failing again.
If I define the cached server manually, and then do the SHOW DIRECTORY
comamnd manually as well, instead of letting DCE setup trash my
configuration, then the SHOW DIRECTORY command works:
SHOW
DIRECTORY /.../adi_reo
AT 1997-04-15-12:13:48
RPC_ClassVersion = 0100
.
.
.
So - if I define the CDS SERVER manually then this works, and I can
do a SHOW DIRECTORY on /.../adi_reo successfully. Moreover, both
DCE_LOGIN and the DCE Director work! However, if I try and use DCE
setup, this fails, and breaks my configuration.
This might lead one to the conclusion that this is a problem primarily
with the setup program.
I'm going to track the progress on the Windows 95 machine in a separate
'thread' of replies, as it seems that their problems are different.
- Cameron
|
| 2212.11 | | TUXEDO::MAZZAFERRO | | Tue Apr 15 1997 10:50 | 8 |
| I believe the assertion failure in getcells is on a rpc_use_protseq
since rpc_supported_protseqs was set to ncacn_ip_tcp and the advertiser
(at least as far as getcells is concerned) requires the use of udp.
So, please unset rpc_supported_protseqs and try this again. Setting
the protseqs may have let us astray from resolving a real problem
elsewhere.
Laura
|
| 2212.12 | Restoring ncadg_ip_udp on Windows NT/AXP didn't help | ESME::SPENCE | Bugs? You mean insects? | Tue Apr 15 1997 11:12 | 16 |
| I restored the RPC_SUPPORTED_PROTSEQS environment
variable on CORDAY to include ncadg_ip_udp, and then
tried both DCE setup and (manually) typing getcells.exe.
In both cases getcells failed, with the assertion on
line 482 of getcells.c, after this was restored.
I'm going to remove ncadg_ip_udp now - because having
this enabled has caused the RPC server within Windows NT
to fall over previously, and I'm anxious to keep this
NT box up and running.
Would it make sense to give me a copy of getcells.c
so I can build it myself, and run it in debug to see
exactly what error codes are being returned?
- Cameron
|
| 2212.13 | no udp means you don't know about CDS servers on your LAN | TUXEDO::ZEE | There you go. | Tue Apr 15 1997 12:24 | 7 |
| The CDS advertiser uses udp to broadcast on the LAN. With udp effectively
disabled on your node, you do not hear the CDS server broadcasts, thus
your cache is empty, thus a "cdscp show dir" fails since you have no
idea where a CDS clearinghouse is. With no udp, you need to go the
CDS WAN configure route in dcesetup.
--Roger
|
| 2212.14 | Taken offline for the moment... | TUXEDO::MAZZAFERRO | | Tue Apr 15 1997 14:06 | 0
|