UNIX Cannot Run RCP or REXEC Against Windows NT

 Last reviewed: March 25, 1997
Article ID: Q102561
The information in this article applies to:
  • Microsoft Windows NT operating system version 3.1
  • Microsoft Windows NT Advanced Server version 3.1
  • Microsoft Windows NT Workstation versions 3.5 and 3.51
  • Microsoft Windows NT Server versions 3.5 and 3.51
  • Microsoft Windows NT Server version 4.0
  • Microsoft Windows NT Workstation version 4.0

SYMPTOMS

When a UNIX system tries to Remote Copy (RCP) or Remote Execute (REXEC) with a Windows NT system, the connection is refused. If you run the command GUEST@OLYMPUS 7 :/USR/GUEST>RCP TEST INDURAIN:TEST from SCO UNIX, the following error message is generated: 

   rcmd: connect: indurain.microsoft.com: Connection refused
A similar error message is returned for REXEC. In addition, if you enter a local host name and a local user name using RCP (see example below), a similar error message appears. The local host name and the local user names are not required.

Example of RCP Command: 

   rcp <localhost>.<localuser>:<filename>
       <remotehost>.<remoteuser>:<filename>

   -or-

   rcp <remotehost>.<remoteuser>:<filename>
       <localhost>.<localuser>:<filename>

CAUSE

Windows NT does not have the server portion of the Remote Copy and Remote Execute commands (usually, rshd and rexecd, respectively); therefore, the connection is refused.

STATUS

This behavior is by design.

Additional query words: prodnt tcp/ip rcp rexec rshd rexecd
Keywords : kbnetwork NTSrvWkst nttcp
Version : 3.1 3.5 3.51 4.0
Platform : WinNT

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: March 25, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.