Conference tuxedo::dce-products

2208.0. "Can not configure 1.1c in a LAN" by VIRGIN::BILL (BILL is my lastname !!!) Fri Apr 04 1997 09:50

Hi friends

I've got a strange customer problem happening on NT4.0 (us version)
and DCE 1.1c clients. The server is on DCE 1.4 for VMS (6.2)

Maybe somebody saw a similiar problem. I saw this problem before
but thought it was caused by the network layout.


The customer can NOT configure a DCE 1.1c client on NT4.0 if
the client is in the same subnet as the CDS and Sec Server.
Even getcells is not able to see a cell in the same subnet.

I tried it also using the transport restriction to TCP and UDP.

If the client is not in the same subnet it works perfectely.

The workaround is to specify the cds server during the setup.

Obviously the problem has something to do with the
broadcast or the rpc service ? 

Here more details, in every case the failing is the same 
as below


Any help appreciated

Marco


DETAILS
=======

Transport restrictions enabled, client in the same subnet as SEC-svr/CDS-svr,
DCE 1.1 c
=============================================================================


          -------- 04/02/97 at 19:28:01 --------------------------
          ========================================================
          New DCEsetup log created
          ========================================================

          -------- 04/02/97 at 19:28:01 --------------------------
          ========================================================
          Beginning DCE client configuration.
          ========================================================
19:28:01: DCE service already running. [RPCSS]
19:28:01: Running getcells.exe to get a list of known cells.
19:28:23: getcells.exe did not produce an output file.
19:29:11:  
19:29:11: Configuration data collected for this run of DCEsetup...
19:29:11: 	Cell Name = test5.fh.zh.ubs.com
19:29:11: 	Host Name = zhpc35038
19:29:11: 	Security Server Host Name = bb9446
19:29:11: 	CDS Server Host Name = bb9446
19:29:11: 	Gda Domain Name = 
19:29:11: 	Lan Name = 
19:29:11: Following DCE components are being configured
19:29:11: 	Security Client
19:29:11: 	CDS client
19:29:12:  
19:29:12: DCE service already running. [RPCSS]
19:29:12: Creating DCE_CF.DB file.
19:29:12: Stopping DCE services.
19:29:16: Checking for Integrated Login support in the registry
19:29:17: Removing permanent DCE database files.
19:29:17: Creating dcelocal directories.
19:29:17: The service does not exist. [Cdsadv]
19:29:18: DCE service installed. [Cdsadv]
19:29:18: Starting DCE Service. [Cdsadv]
19:29:18: DCE service started. [Cdsadv]
19:29:19: Checking status of service.
19:32:34: Timed out waiting for service to respond to remote request.
19:33:33: DCE configuration either failed or was aborted

          -------- 04/02/97 at 19:33:33 --------------------------
          ========================================================
          End of DCE client configuration
          ========================================================

If tried to start the daemons or programs manually:

C:\>getcells
Assertion failed: rpc_status == rpc_s_ok, file .\getcells.c, line 506

abnormal program termination

C:\>cdsadv -dve\*
Error in rpc_ep_resolve_binding (231628823) - Exiting
inquired binding ncacn_ip_tcp:192.168.104.218[1063]
rpc_binding_from_string_binding
rpc_binding_reset
rpc_ep_resolve_binding( 6c8620b9-c6d3-11ca-bb96-08002b1c8f1f,
ncacn_ip_tcp:192.168.104.218[] )
inquired binding ncadg_ip_udp:192.168.104.218[1064]
rpc_binding_from_string_binding
rpc_binding_reset
rpc_ep_resolve_binding( 6c8620b9-c6d3-11ca-bb96-08002b1c8f1f,
ncadg_ip_udp:192.168.104.218[] )
(cdsadv) Error in rpc_ep_resolve_binding - Exiting
RPC daemon communications failure ( dce / rpc )
Cannot initialize RPC server, exiting



C:\>rpccp
rpccp> show mapping

>>> no matching mappings found

Marco,

Just a thought, but I wonder if you're actually experiencing problems
on the VMS cell server with regard to the delta time patch required on
VMS systems. 

Laura

> I've got a strange customer problem happening on NT4.0 (us version)
> and DCE 1.1c clients. The server is on DCE 1.4 for VMS (6.2)

 you need to only use TCP on NT 4.0, there is a problem with the UDP transport.
 (it's in the release notes).

 i've seen the RPC die if I don't restrict the transport, even the local
 RPC traffic stops and the system takes a long time to come up.

garry

Thanks,

I'll try to restrict to TCP.

/Marco
[Posted by WWW Notes gateway]