-D enables socket debugging on the TCP sockets used for communication with the remote host. This option also displays the locuser and remuser being sent to rshd.
Note: Because rsh -D is looking at the world from the client machine's point of view (as opposed to the host machine's point of view), the name displayed as local_user is actually the one sent as remuser and the name displayed as remote_user is actually locuser.
Your host name will not be mapped to the 192.168.xxx.xxx numbers
If you are receiving a "permission denied" error, it could be for one of the following reasons:
There is no entry for the remuser on the remote host in either the global hosts.equiv file or the locuser's .rhosts file. Check these files to ensure that an entry exists for remuser on the machine you are connecting from. You can use rsh -D to determine the names being sent as locuser and remuser.
Note: UNIX systems may not always know your Windows machine by the same name that other Windows machines do. You can attempt to find out the name by which a UNIX system knows your machine by using the rlogin command to connect to that UNIX system and typing
/bin/who am i
This should display the name of your machine in parentheses at the end of the information line. If you cannot find the machine name using this method, consult the UNIX system's administrator.
fluidyn
4 Posts
0
May 28th, 2009 06:00
Hello my local user name is fluidyn and my system name is NASSAU.
I have the following entry in /etc/hosts.equiv file
NASSAU fluidyn
and the same entry in
home/fluidyn/.rhosts file
The command rsh -D is not working. I am getting segmentation fault error
when I type the command whoami under user I get the answer fluidyn & under root I get output root
but the name of the machine is not displayed
the command /bin/who am i does not work
thanks
speedstep
9 Legend
•
47K Posts
0
May 28th, 2009 06:00
192.168.1.XXX is a non routeable number aka an RFC 1918 number and is not unique.
http://www.isi.edu/in-notes/rfc1918.txt
The Internet Assigned Numbers Authority (IANA) has reserved the
following three blocks of the IP address space for private internets:
10.0.0.0 - 10.255.255.255 (10/8 prefix)
172.16.0.0 - 172.31.255.255 (172.16/12 prefix)
192.168.0.0 - 192.168.255.255 (192.168/16 prefix)
rsh executes command on the specified hostname
rsh otherhost -l mydomain/myname pwd
rsh otherhost -l mydomain\\myname pwd
rsh mydomain/myname@otherhost pwd
rsh mydomain\\myname@otherhost pwd
Options
-D
enables socket debugging on the TCP sockets used for communication with the remote host.
This option also displays the locuser and remuser being sent to rshd.
Note:
Because rsh -D is looking at the world from the client machine's point of view
(as opposed to the host machine's point of view), the name displayed as local_user
is actually the one sent as remuser and the name displayed as remote_user is actually locuser.
Your host name will not be mapped to the 192.168.xxx.xxx numbers
If you are receiving a "permission denied" error, it could be for one of the following reasons:
There is no entry for the remuser on the remote host in either the global hosts.equiv file
or the locuser's .rhosts file. Check these files to ensure that an entry exists for
remuser on the machine you are connecting from. You can use rsh -D to determine the
names being sent as locuser and remuser.
Note:
UNIX systems may not always know your Windows machine by the same name that other
Windows machines do. You can attempt to find out the name by which a UNIX system
knows your machine by using the rlogin command to connect to that UNIX system and typing
/bin/who am i
This should display the name of your machine in parentheses at the end of the information line.
If you cannot find the machine name using this method, consult the UNIX system's administrator.
speedstep
9 Legend
•
47K Posts
0
May 28th, 2009 07:00
Welcome to /etc/rc.d/rc.synsinit: line 70: 35 Segmentation fault
LC_ALL=C grep -q "Red Hat" /etc/redhat-release Red Hat Linux
Press 'I' to enter interactive startup.
Mounting proc filesystem: [failed]
Segmentation faults can also be hardware failures
such as RAM Failure.
The segmentation problem also happens when the tools inside /bin get corrupted.
This may happen when someone hacks your server.
The only way to solve this problem is by refornat and re-installing the OS.
fluidyn
4 Posts
0
May 28th, 2009 07:00
Hello
I rebooted with interactive startup.
I did not get the error message : mounting proc filesystem : failed
This system came with redhat linux preinstalled by DELL and I find it hard to believe that someone can hack the server. We have
a firewall on our routeur provided by France telecome and besides the firewall on the system is enabled.
as for the tools, I do not find many common tools like chkconfig ... in bin folders
Is this normal ?
I also have a Redhat CD supplied by DELL. Should I use this to reinstall ? I have not yet opened the CD
thanks