remsh

[suamb]

when i issue the following command it connects to the specified server

remsh DRSERVER


but if issue any command with remsh, it fails

# remsh DRSERVER ls
remshd: connect: Connection timed out

can you help to know, what could be possible reason of failure.

[Prashanth Waugh]

Hi,
Paste the output of below command
#grep remsh /etc/inetd.conf
Regards
Prashnat

[Suraj K Sankari]

Hi,

Please go through this below link.

http://www.docs.hp.com/en/32650-90897/ch06s03.html

Suraj

[Torsten.]

I would start with some very basic commands:

# nslookup DRSERVER
# ping DRSERVER

(sure about the capital letters?)

[Frank de Vries]

Hmm,
Seems like you are dropping packets.
remsh hostname cmd will require 514 port

Can you do a diagnostic:
telnet DRSERVER 514
Look for the words: connected to
synema:/tmp/# telnet DRSERVER 514
Trying 10.214.16.131...
Connected to DRSERVER.
Escape character is '^]'.
Connection closed by foreign host.

and do a

ping DRSERVER -c130 -w 2 -i 0.01
This is a burst, how many timeouts or drops do you get ? Are all okay , if yes,
then it is not a connection problem, but something else.

Try to restart the remshd deamon on the remote host.

Then try to diagnose dns
nslookup with and without suffix domain name, bot forward and reverse lookup.
Do the same from the target host.

What do the symptons tell you ?

[suamb]

There is no connection issue

nslookup is ok
ping ok
telnet DRSERVER 514 is OK
and as I mentioned remsh also works fine, but when i pass and unix command it fails, though it should not fail. it works on other servers.


prashant, following is the output of
# grep remsh /etc/inetd.conf
shell stream tcp6 nowait root /usr/lbin/remshd remshd
# The standard remshd and rlogind do not include the Kerberized
kshell stream tcp nowait root /usr/lbin/remshd remshd -K


Would there be any permissions/security issues, that cause the failure.

Please suggest,

Thanks

[T G Manikandan]

i would suggest you to check the syslog.log file for remshd errors.

you can do a tcpdump to find what is causing the issue.

you need to check the route between the source and destination servers.
netstat -nr

also check /var/adm/inetd.sec to see if you have anything defined there.