X-Spam-Check-By: sourceware.org From: Li_Adrian AT emc DOT com Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: Re: Using RSH on Windows 2003 server? Date: Thu, 26 Jul 2007 16:03:08 -0400 Message-ID: <7E9C5D9E5FB9BE4A8616D0AEC0E8FD690CC632@CORPUSMX60B.corp.emc.com> To: Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id l6QK3q3w008670 I realize that ssh is safer, but my boss said that he wants rsh because that is what the rest of our computers are running, or something along those lines. I even got ssh to work, and he still said that he wanted rsh. Believe me, I was pushing for ssh. I now get a different answer, however, when I run rsh commands ("Permission denied.") Is anyone willing to help? Thanks, Adrian * (Thu, 26 Jul 2007 11:05:17 -0400) > I'm trying to rsh into a computer that is running Windows 2003 server, > but I get the error "No Remote Directory." I can, however, ftp and > telnet into that same box, and when I ping it, the test comes back as > successful. Anyone have any ideas? rsh is an inherently unsecure protocol. Don't use it. Don't use the excuse that this is on a local corporate network only. You have no idea who's sniffing on your network. Better use a secure protocol instead, like ssh. All services provided by the OBSOLETE rsh/rlogin/telnet interfaces are provided in a much more secure way by ssh. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/