Operating System - HP-UX
1835162 Members
2535 Online
110077 Solutions
New Discussion

Ignite-UX RPC exception: "Connection failure (dce / rpc)

 
SOLVED
Go to solution
MikeL_4
Super Advisor

Ignite-UX RPC exception: "Connection failure (dce / rpc)

I am trying to setup a new client on my Ignite server and am receiving message: RPC exception, Connection failure (dce / rpc).

From my Ignite server I can do an remsh to the new server without any problem and from the new server remsh works coming back.

swagentd and all rpc processes are running on both servers.

Both servers have several lan segments assigned to them, is it possible Ignite is trying to use the wrong lan segment that can't talk between the two servers ??

Any suggestions would be helpful to get this to work...
4 REPLIES 4
Steven E. Protter
Exalted Contributor

Re: Ignite-UX RPC exception: "Connection failure (dce / rpc)

inetd -l to get enhanced logging

tail -f /var/adm/syslog/syslog.log

on the server

Try the connect. Watch for error messages. This is probably a networking/permission issue.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
MikeL_4
Super Advisor

Re: Ignite-UX RPC exception: "Connection failure (dce / rpc)

syslog.log shows me coming into the server I am trying to setup through the correct lan segment from the Ignite server.

In what it appears to be trying to talk back to the Ignite server is is using a different lan port that is not allowed to talk to the Ignite server....
Alex Glennie
Honored Contributor
Solution

Re: Ignite-UX RPC exception: "Connection failure (dce / rpc)

if this is a DCE issue the following maybe of use ?

Restricting RPC Addresses
The runtime looks for a RPC_SUPPORTED_NETADDRS environment variable, which allows a user or administrator to restrict the network addresses that a DCE server will advertise in the name space/endpoint-map.

The RPC_SUPPORTED_NETADDRS environment variable is used to force the DCE/RPC service to bind to specific LAN cards in a multi-homed environment. If this environment variable is set, only addresses in the list are advertised in the endpoint map; addresses not found on the list are excluded from the server's list of available addresses. To restrict the servers to using only a specified set of IP addresses, set the RPC_SUPPORTED_NETADDRS environment variable before starting the servers. The syntax is:

RPC_SUPPORTED_NETADDRS=protocol:ip_address[,protocol:ip_address]

ie:

RPC_SUPPORTED_NETADDRS= ncadg_ip_udp:192.1.1.1

export RPC_SUPPORTED_NETADDRS

OR

RCP_SUPPORTED_NETADDRS=ncacn_ip_tcp:15.1.1.1,ncacn_ip_tcp:15.12.2.2

export RPC_SUPPORTED_NETADDRS

OR

export RPC_SUPPORTED_NETADDRS=ip:15.12.2.2

(Use ip only if you do not want to specify which protocol to use first)



Set the environment variable before starting dced/rpcd.

On HP-UX 10.20, add the environment variable to the files

/sbin/init.d/dce

/etc/opt/dce/dce_com_env

/etc/opt/dce/dce_config_env files

and /sbin/init.d/ncs.(HPUX 10.20) or /sbin/init.d/Rpcd (HPUX 11).

Then restart the system to make the IP address restriction take affect.
MikeL_4
Super Advisor

Re: Ignite-UX RPC exception: "Connection failure (dce / rpc)

Thanks