vktonk
9th June 2006, 09:14
we are installing SSA ERP package on Linux server. And this installation is being done through remote window(2000 server) machine. REXEC protocol is being used to communicate. when we give IP address of linux server, it's giving message "logging from REXEC". after this nothing happens. when we press ok it returns to the login screen (for remote login)

Now when we manually try to start rexec on windows
machine it is not giving any error nor its responding
Please help me out.

thanks.......

dave_23
9th June 2006, 13:32
Most likely Firewall

Dave

vktonk
9th June 2006, 13:43
could u please elaborate more.... is firewall hindering REXEC service?

dave_23
9th June 2006, 14:02
Oh, sorry. it's early here, i read that wrong.

In linux you have to enable the rexec service via YAST it's off by default.

Dave

dave_23
9th June 2006, 14:07
installation is being done through remote window(2000 server) machine.

What do you mean by a remote windows 2000 machine?

You're not using Remote Desktop are you? If so - it will not work
you have to use PC-Anywere/Citrix/VNC instead.

Dave

patvdv
9th June 2006, 14:16
we are installing SSA ERP package on Linux server. And this installation is being done through remote window(2000 server) machine. REXEC protocol is being used to communicate. when we give IP address of linux server, it's giving message "logging from REXEC". after this nothing happens. when we press ok it returns to the login screen (for remote login)

Now when we manually try to start rexec on windows
machine it is not giving any error nor its responding
Please help me out.

thanks.......

1. First check that the rexecd service is running on your linux box:

# telnet localhost 512

If not, then you probably either have to install it and/or add it to the inetd configuration.

2. Then check that the rexecd is reachable from your windows server. For that, open a DOS window and do a telnet to your linux server also on port 512:

DOS> telnet linux-server 512

If that does not work, then a firewall is probably blocking access for you.

3. Check that rexec works from your windows server:

DOS> rexec <linux-server> -l <user> hostname

This should show you the name of your linux server

vktonk
12th June 2006, 06:44
hi patvdv.........

here are the details what i am getting while running these commands.

telnet localhost 512
telnet: localhost: Temporary failure in name resolution
localhost: Host name lookup failure

on DOS prompt...........
telnet linux-server 512

connection to host lost

on DOS prompt.......
rexec <linux-server> -l <user> hostname

No response

patvdv
12th June 2006, 10:51
vktonk,

Make sure "localhost" has an entry in your /etc/hosts file. It looks like rexec is not enabled on your linux server. How to do this depends on your Linux flavour but if you are using SuSE then this can be done through Yast (Network Services > inetd). Look for the exec service.

vktonk
12th June 2006, 11:06
i think rexec is on as the output of following command shows

[root@c-3176 etc]# chkconfig --list | grep rexec
rexec: on

i am using REDHAT Advanced Application server 2. What do you mean by localhost. i had found that /etc/hosts file but that was empty.
also i am not able to locate exec service when i try service exec start it says unrecognised service..

patvdv
12th June 2006, 11:28
You should have at least following entries in your /etc/hosts file:


127.0.0.1 localhost.localdomain localhost
<ip of your server> <name of your server>


Make sure the file has '644' permission set so that it is world-readable.

Then try the rexec tests again. You may also have to change some other security settings as well (securetty, PAM).

vktonk
12th June 2006, 12:13
hi patrick.....
now that issue has been resolved but we are getting a new message.. it tells that "An error occured while login to host" ..
the snap shot of that is attached... this message comes when previously REXEC message was coming....

patvdv
12th June 2006, 13:54
hi patrick.....
now that issue has been resolved but we are getting a new message.. it tells that "An error occured while login to host" ..
the snap shot of that is attached... this message comes when previously REXEC message was coming....

You obviously forgot the attachment. Does a telnet to port 512 work now?

jetendra
8th February 2019, 08:08
Hi,

I have a similar situation, but problem with my REXEC is it cannot authenticate passwords more than 16 characters and fails wherein Baanlogin can authenticate. Can someone please help