Solved

rsh problem from redhat9 to solaris 2.6 - protocol failure

Posted on 2003-12-03
6
1,153 Views
Last Modified: 2013-12-19

  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
Comment
Question by:keles
6 Comments
 
LVL 18

Accepted Solution

by:
liddler earned 500 total points
ID: 9867057
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
 

Author Comment

by:keles
ID: 9867226

  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
 
LVL 61

Expert Comment

by:gheist
ID: 9871135
redhat asked if you want ipchains when installed, and you selected different answers...
0
Find Ransomware Secrets With All-Source Analysis

Ransomware has become a major concern for organizations; its prevalence has grown due to past successes achieved by threat actors. While each ransomware variant is different, we’ve seen some common tactics and trends used among the authors of the malware.

 

Author Comment

by:keles
ID: 9873889

  The problem was a hardware problem on ethernets. So it was solved.
0
 
LVL 61

Expert Comment

by:gheist
ID: 9874038
"connection refused" is firewall or routing problem as liddler pointed out, not ethernet.
0
 
LVL 24

Expert Comment

by:shivsa
ID: 9875360
0

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

Article by: IanTh
Hi Guys After a whole weekend getting wake on lan over the internet working, I thought I would share the experience. Your firewall has to have a port forward for port 9 udp to your local broadcast x.x.x.255 but if that doesnt work, do it to a …
Don’t let your business fall victim to the coming apocalypse – use our Survival Guide for the Fax Apocalypse to identify the risks and signs of zombie fax activities at your business.
Learn how to find files with the shell using the find and locate commands. Use locate to find a needle in a haystack.: With locate, check if the file still exists.: Use find to get the actual location of the file.:
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.

707 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

15 Experts available now in Live!

Get 1:1 Help Now