The Win32 Version of RSH Reports "Option t Is Not Valid" to Rcp Clients (323719)
The information in this article applies to:
- Microsoft Windows Services for UNIX 2.0
- Microsoft Windows Services for UNIX 2.1 OEM Only
- Microsoft Windows Services for UNIX 2.2 OEM Only
- Microsoft Windows Services for UNIX 2.3 OEM Only
- Microsoft Windows Services for UNIX 3.0
This article was previously published under Q323719 SYMPTOMS When you run an rcp command from a UNIX/Linux client to the Windows Services for UNIX
RSH service, you may receive the following error message: Example: $ rcp testfile winsvr2k:/ Option t is not
valid.
CAUSE This problem occurs because of an incompatibility between
the UNIX rcp command and the Windows rcp.exe command. If the destination file is on a remote computer, the
UNIX rcp starts rcp -t on the remote computer and sends the file. The "-t" option tells
the remote rcp to start up in receive mode and wait for the incoming file.
Windows rcp.exe has a different method of transferring files between computers,
so it does not support the "-t" option. RESOLUTION The Interix version of rcp supports the "-t" option. To
cause that version to be invoked, you have to use the Interix version of rshd
daemon instead of the Windows Remote Shell service. The Interix rshd calls the Interix rcp, but the Windows Remote Shell service calls the Windows rcp.exe.
Modification Type: | Major | Last Reviewed: | 9/23/2003 |
---|
Keywords: | kbprb KB323719 |
---|
|