- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Ignite-UX RPC exception: "Connection failure (dce...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-09-2005 05:51 AM
05-09-2005 05:51 AM
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...
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-09-2005 05:54 AM
05-09-2005 05:54 AM
Re: Ignite-UX RPC exception: "Connection failure (dce / rpc)
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
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-09-2005 06:28 AM
05-09-2005 06:28 AM
Re: Ignite-UX RPC exception: "Connection failure (dce / rpc)
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....
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-09-2005 07:55 AM
05-09-2005 07:55 AM
SolutionRestricting 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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-11-2005 06:40 AM
05-11-2005 06:40 AM