• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

remote adminclient failing

 
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I'm trying to run adminclient from a remote system. It's failing trying to connect. The debug output shows:
ADGU1045E: Caught exception while getting initial context:"javax.naming.CommunicationException: Caught CORBA.COMM_FAILURE when resolving initial reference=WsnNameService [Root exception is org.omg.CORBA.COMM_FAILURE: minor code: 3 completed: No]
There is no firewall between my systems. I've tried running the adminclinet from both a NT and Linux systems with the same result.
The adminclient runs fine locally. The local system is RedHat Linux 8.0 with WAS 4.04.
I can telnet, ftp, ping and otherwise connect to the box running WebSphere.
Anyone have any suggestions?
Thank you.
 
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,
Are you giving complete command like "adminclient.sh remotehostname bootstrapport" while invoking admin client from remote machine ?
 
Jim Grecni
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Yes, I used the complete command
adminclient.sh hostname 900
I also tried defaulting the host number, same result. I also tried running the command on the local machine, specifically puting in the hostname and port number. It works from the local command.
I also tried connecting to port 900 using telnet, just to ensure the communications are working. I get connected.
I admit, I'm confused as to what's wrong.
 
author
Posts: 3892
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I suspect a TCP (probably DNS) problem. Try adding the name of the remote host to your etc/hosts file on the client and then try with the fully qualified shell script (e.g. specifying the name and port).
Kyle
 
Ranch Hand
Posts: 179
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
How many network cards in the machine? WebSphere needs to be bound to one network card via the admin.config.
e.g
com.ibm.CORBA.LocalHost=192.168.200.111
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic