- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: resmsh/telnet issue
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
Discussions
Discussions
Forums
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
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
тАО01-29-2010 01:37 AM
тАО01-29-2010 01:37 AM
I am trying to Boot a Client through Ignite. But Ignite canтАЩt connect to the client & couldnтАЩt start the ignition process. It suggests booting it manually but even that doesnтАЩt work.
(/opt/ignite/bin/bootsys -wv -R B.11.11 pandora: 192.168.137.222 2>/var/tmp/baaa28530)
When I check the Error Log File тАЬ/var/tmp/baaa28530тАЭ
Fatal error on "pandora": (remsh error: rcmd_af: connect: 192.168.137.222: Connection refused)
I can ssh & ping the system but couldnтАЩt Telnet to that system
# telnet 192.168.137.222
Trying...
telnet: Unable to connect to remote host: Connection refused
# telnet 0
Trying...
telnet: Unable to connect to remote host: Connection refused
I checked /etc/inetd.conf on the client but that has following entries (not hashed out)
login stream tcp6 nowait root /usr/lbin/rlogind rlogind
shell stream tcp6 nowait root /usr/lbin/remshd remshd
exec stream tcp6 nowait root /usr/lbin/rexecd rexecd
Then I checked $HOME/.rhosts file (logged in as root) which has following entry:
+ +
Also checked for /var/adm/inetd.sec & that has following entry
dtspc allow 127.0.0.1 loopback pandora
Checked /etc/services
exec 512/tcp # remote execution, passwd required
login 513/tcp # remote login
who 513/udp whod # remote who and uptime
shell 514/tcp cmd # remote command, no passwd used
& Finally Checked /var/admsyslogsyslog.log
Jan 29 10:48:15 inet30 inetd[7808]: Rereading configuration
Jan 29 10:48:15 inet30 inetd[7808]: telnet/tcp: socket: Protocol not supported
Jan 29 10:48:15 inet30 inetd[7808]: login/tcp: socket: Protocol not supported
Jan 29 10:48:15 inet30 inetd[7808]: shell/tcp: socket: Protocol not supported
Jan 29 10:48:15 inet30 inetd[7808]: exec/tcp: socket: Protocol not supported
Jan 29 10:48:15 inet30 inetd[7808]: daytime/tcp: socket: Protocol not supported
Jan 29 10:48:15 inet30 inetd[7808]: daytime/udp: socket: Protocol not supported
Jan 29 10:48:15 inet30 inetd[7808]: time/tcp: socket: Protocol not supported
Jan 29 10:48:15 inet30 inetd[7808]: echo/tcp: socket: Protocol not supported
Jan 29 10:48:15 inet30 inetd[7808]: echo/udp: socket: Protocol not supported
Jan 29 10:48:15 inet30 inetd[7808]: discard/tcp: socket: Protocol not supported
Jan 29 10:48:15 inet30 inetd[7808]: discard/udp: socket: Protocol not supported
Jan 29 10:48:15 inet30 inetd[7808]: chargen/tcp: socket: Protocol not supported
Jan 29 10:48:15 inet30 inetd[7808]: chargen/udp: socket: Protocol not supported
Jan 29 10:48:15 inet30 inetd[7808]: Thru with configuration
Jan 29 10:48:15 inet30 inetd[7808]: Configuration complete
I was trying to install an IPv6 Bundle on that client before reinstalling it.
But that installation failed while it was building kernel (at 24%)
The same bundle installed fine on my other 11.11 machine which was installed from the same depot server.
#netstat тАУin
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
* 0 192.168.136.0 192.168.137.222 0 0 4278190080 0 0
0 0.0.48.0 0.0.255.255 9523848 0 0 0 0
What else can be checked?
I would appreciate if you all can help me to boot this client from ignite.
Also please advise on why the netstat output looks like this?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-29-2010 07:18 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-29-2010 07:27 AM
тАО01-29-2010 07:27 AM
Re: resmsh/telnet issue
Are those the only entries you have in inetd.conf? If so then you are missing one for telnetd. You could make a copy of you existing inetd.conf file and then copy the /usr/newconfig/etc/inetd.conf file to /etc/inetd.conf. Run "inetd -c" and try your telnet, then your ignite.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-29-2010 11:26 AM
тАО01-29-2010 11:26 AM
Re: resmsh/telnet issue
You must have to re-read the /etc/inetd.conf file after any editing on this by inetd -c .
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-01-2010 01:13 AM
тАО02-01-2010 01:13 AM
Re: resmsh/telnet issue
The Issue is resolved now.
It was an issue with a corrupt IPv6 bundle.
That has caused the tcp/ip parameter values to change & hence the netstat -in o/p.
I have installled a new bundle now & things seem fine.
Thanks Again.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-01-2010 01:15 AM
тАО02-01-2010 01:15 AM