UNIX Cannot Run RCP or REXEC Against Windows NT

ID: Q102561


The information in this article applies to:
  • Microsoft Windows NT operating system version 3.1
  • Microsoft Windows NT Advanced Server
  • Microsoft Windows NT Workstation versions 3.5, 3.51, 4.0
  • Microsoft Windows NT Server versions 3.5, 3.51, 4.0
  • Microsoft Windows 2000 Professional
  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Advanced Server


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 nttcp NTSrvWkst
Version : :; WINDOWS:2000; winnt:3.5,3.51,4.0
Platform : WINDOWS winnt
Issue type :


Last Reviewed: January 20, 2000
© 2000 Microsoft Corporation. All rights reserved. Terms of Use.