Knowledge Base |

# UNIX Cannot Run RCP or REXEC Against Windows NT

Article ID: 102561

Article Last Modified on 2/20/2007

APPLIES TO

- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Professional Edition
- Microsoft Windows NT Advanced Server 3.1
- Microsoft Windows NT Workstation 3.1
- Microsoft Windows NT Advanced Server 3.1
- Microsoft Windows NT Workstation 3.5
- Microsoft Windows NT Workstation 3.51
- Microsoft Windows NT Workstation 4.0 Developer Edition
- Microsoft Windows NT Server 3.5
- Microsoft Windows NT Server 3.51
- Microsoft Windows NT Server 4.0 Standard Edition

This article was previously published under Q102561

## 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 KB102561