Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1165
  • Last Modified:

rsh problem from redhat9 to solaris 2.6 - protocol failure


  When I tried to connect with rsh to solaris 2.6 machine from my redhat 9.0 machine I had a problem.
  For example a simple command :
     [operator@ldw1 tmp]$ rsh scmssrv1 "ls"
     poll: protocol failure in circuit setup

   When I tried exactly the same thing from a redhat 8 machine there is no problem. The unix machine same and rlogin works for both redhats.
   I tried to install and use the same rsh and rsh-server packages on the redhat machines but there was no change.
   Thanks for your help.
0
keles
Asked:
keles
1 Solution
 
liddlerCommented:
try doing
rsh 127.0.0.1 "ls"
to make sure rsh works OK on the machine, if it does, the problem may be firewall or network speed / duplex related.
Do you have a firewall?  Does it log? Can you see any drops?
Can you confirm all NICs / switches / Hubs are set to the same speed & duplex?
0
 
kelesAuthor Commented:

  I had the following answer and I think it seem that rsh is running as a client. I didn't configure the Redhat9.0 machine as a rsh server.
  [operator@ldw1 tmp]$ rsh 127.0.0.1 "ls"
  ldw1: Connection refused

   There is no firewall. Only a soft linux router with some little firewall configuration and as I said rlogin is working on the machine properly.
   Both redhat machines are on the same swith and same network. The network configuration for both machines ( Two redhats = 1 woks the other not) are exactly same.
0
 
gheistCommented:
redhat asked if you want ipchains when installed, and you selected different answers...
0
NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

 
kelesAuthor Commented:

  The problem was a hardware problem on ethernets. So it was solved.
0
 
gheistCommented:
"connection refused" is firewall or routing problem as liddler pointed out, not ethernet.
0

Featured Post

Ask an Anonymous Question!

Don't feel intimidated by what you don't know. Ask your question anonymously. It's easy! Learn more and upgrade.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now