| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2119.1 | they have been reported and are being worked | FOUNDR::WOODRUFF | | Mon Jan 13 1997 10:02 | 28 |
| 2119.2 | you can trick the configuration | FOUNDR::WOODRUFF | | Mon Jan 13 1997 10:09 | 17 |
| 2119.3 | need some detailed information, please | FOUNDR::WOODRUFF | | Tue Jan 21 1997 09:26 | 22 |
| 2119.4 | Current Info. | TKOVOA::MATSUNO_R | | Thu Feb 13 1997 01:27 | 49 |
|
Thank you, Garry.
Re: .2
>> also, when it fails during dcesetup, you can trick the configuration
>>into running by editing the registry bit to signal a successful configure.
>>After that things seem to start okay.
Could you tell me more detail procedure of this trick ? My customer tried to
do this, but they could not.
Re: .3
>>Could you supply some more information on their problem.
>>
>>
>>- Version of DCE for NT and Sun
NT = 1.1B, Sun = Transarc DCE V1.1 Patch Level 23
>>- Cell configuration
>> - security, cds, dts locations
>> - dts - global or local
>> - multiLAN?
>>
1 Cell, but Multiple LAN environment.
Center LAN on FDDI includes CDS, Security and DTS Server on Suns.
And 4 Classroom LANs include only DCE Clients on WNT/Intel PCs.
Currently customers try to reorganise their mapping to extend a number of
classrooms.
>>What is the error message that the customer receives?
>>
>>Where in the log? When it is trying first locate the time server(s)? or
>>near the very end when trying to create a client?
>>
>>Does the Sun machine have any other interfaces such as an ATM interface?
>>(Could you obtain the end-point map from the Sun?)
>>
Regards,
Ryouzo
|
| 2119.5 | Log data | TKOVOA::MATSUNO_R | | Thu Feb 13 1997 01:30 | 18 |
|
This is the log during dcesetup.
----------------------------------------------------------------------------
>> > 11:24:46: Gather information for dce_login
>> > 11:24:52: Logging into DCE...
>> > 11:24:53: Login to DCE successful.
>> > 11:24:53: Starting NT Service. [Dtsd]
>> > 11:24:54: NT service started. [Dtsd]
>> > 11:24:54: Checking status of service.
>> > 11:25:06: > DTSCP create type clerk
>> > 11:25:08: dtscp: error executing command: ( dce / dts )
>> > 11:25:08: dtscp: must have write permission to the DTS entity ( dce / dts )
>> > 11:25:09: DTSCP Create type clerk failed.
>> > 11:25:11: Failed to configure a DTS clerk.
>> > ----------------------------------------------------------------------------
|
| 2119.6 | could you try the 1.1c kit? | FOUNDR::WOODRUFF | | Thu Feb 13 1997 10:23 | 23 |
|
could you try this with the 1.1C kit, we made several changes that
affect dts and it's configuration.
the way to 'trick' the configuration if it fails near the end of
configuration -- namely configuring dts -- is as follows:
- start the NT registry editor
- select the HKEY_LOCAL_MACHINE\SOFTWARE\DigitalEquipmentCorporation
- select DCERuntimeServices\CurrentVersion\HostConfiguration
- double click on the ConfigurationDone item
- change the 0 to a 1
- the start the DCE setup program and tell it to Start
This seems to work most of the time. The dcestart service may
not be installed properly.
But at least you can get the DCE services to run, and then see
if dtsd will then start.
garry
|
| 2119.7 | Thanks | TKOVOA::MATSUNO_R | | Thu Feb 13 1997 20:26 | 13 |
|
Thanks for quick reply.
>> could you try this with the 1.1C kit, we made several changes that
>> affect dts and it's configuration.
I don't know the current status. Can I get the V1.1C kit from ordinary path
(SSB) ? Or MCS route ?
At this time, my customer will try your trick, since they have to hurry to
reconfigure renew system. I will report the result.
Ryouzo
|
| 2119.8 | it's in SSB | FOUNDR::WOODRUFF | | Fri Feb 14 1997 09:12 | 5 |
|
> I don't know the current status. Can I get the V1.1C kit from ordinary path
> (SSB) ? Or MCS route ?
SSB
|