Error In Rsh Connection, poll:protocol failure in circuit set
Red HatThis forum is for the discussion of Red Hat Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Error In Rsh Connection, poll:protocol failure in circuit set
I wanted to setup the rsh service. But there is some problem.
the host name with rsh service is "netking",and the client name is "xxx"
When I input the command "rsh netking ls" in the netking which surpport the service,the work went well . however while I input the same command in the client ,the terminator showed the tips like :
rsh netking ls
pollrotocol failure in circuit set
Now I list the hosts and hosts.equiv in /etc
hosts:
127.0.0.1 netking
211.111.12.63 xxx
hosts.equiv:
netking
xxx
What's wrong with my system?
By the way ,my system is redhat9.0.
thanks a lot to the upstairs in advance!
I've read the link you introduced to me and done by fitterhappier's method.
but it doesn't work.
In rsh's work,there's something I still not sure!
Firstly , is there neccesary to add a same username in both the server and the client .
Secondly, when i input the comannd "rsh netking" in the client,the terminator showed the tips saying "passwd",then i try the server's root and a normal user's passwd ,but they didn't work, and the third time,the terminator ask me to input a username ,and i
have just done follow that ,finally the connection does work. In one word ,i can't rsh the server directely.It need input passwd. Is there something inproper with the server's
firewall or other things? If is firewall, how can i modify the firewall's setup?
Firstly , is there neccesary to add a same username in both the server and the client .
No it's not. The -l <username> option can be used. Take a look at the manpage for more details.
If you omit the -l <username> part, rsh uses the name of the user executing the rsh command to execute the command on the other side. If that user does not excists, an error will occur. In this case you have to use the -l <username> option.
Quote:
Secondly, when i input the comannd "rsh netking" in the client,the terminator showed the tips saying "passwd",then i try the server's root and a normal user's passwd ,but they didn't work, and the third time,the terminator ask me to input a username ,and i have just done follow that ,finally the connection does work. In one word ,i can't rsh the server directely.It need input passwd. Is there something inproper with the server's firewall or other things? If is firewall, how can i modify the firewall's setup?
Before the command is remotely executed you need to give the appropriate password (the one for the remote user). This is normal behaviour. However, there are ways to automate this (I'm not going into that atm).
I'm don't think that the firewall is causing this.
Originally posted by druuna No it's not. The -l <username> option can be used. Take a look at the manpage for more details.
If you omit the -l <username> part, rsh uses the name of the user executing the rsh command to execute the command on the other side. If that user does not excists, an error will occur. In this case you have to use the -l <username> option.
I thinke you're right .But when i created a same username in the client and input the command "rsh netking pwd",it shouted at me the same tips.After that used "rsh netking"(of course i had used the same username to get in the client on the client side),and the same
situation appeared.
Quote:
Originally posted by druuna
Before the command is remotely executed you need to give the appropriate password (the one for the remote user). This is normal behaviour. However, there are ways to automate this (I'm not going into that atm).
I'm don't think that the firewall is causing this.
Sorry for my poor english, i can't understand your words "(I'm not going into that atm)".
And i wanted to take a try in this way.But i couldn't make it work by "setup" on the terminator.when i changed the firewall's setup , the next time i got in, everything was recoveried.In fact,i am setting the MPI's enviorament.From the http://www-unix.mcs.anl.gov/mpi/mpich/docs/faq.htm
i got the idea of shutting down my firewall.
but till now ,i can't shut down it yet.
i feel really hopeless.
Any way, thanks a lot of you. Druuna!
Sorry for my poor english, i can't understand your words "(I'm not going into that atm)".
Sorry for the abbreviation. atm = at the moment.
I'm was just saying that it's a bit much to explain what you need to do to set it up without a password. You first need to get this running the way it should
Quote:
And i wanted to take a try in this way.But i couldn't make it work by "setup" on the terminator.when i changed the firewall's setup , the next time i got in, everything was recoveried.In fact,i am setting the MPI's enviorament.From the http://www-unix.mcs.anl.gov/mpi/mpich/docs/faq.htm i got the idea of shutting down my firewall.but till now ,i can't shut down it yet. i feel really hopeless.
I'm not familiar with MPI(CH), so I cannot help you with that.
It would be a good idea to shut down thw firewall and see if rsh is working. If it does, you know that the firewall is the cause of your problem.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.