What happened to rsh.exe

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Did this app get retired from Vista or is there an option I'm missing to have
it installed? I installed the Telnet client from the add/remove windows
programs menu, but I don't see anything else that might give me rsh if it's
available.
 
Yes, I concur.

Not only rsh, but rcp as well.. both useful tools in a windows/unix network.

Vista RC1 5600 seems to be lacking these two executables. And yes, I found
how to turn on telnet as well, but seems nothing for rsh/rcp.
 
Looks like if you enable the 'unix utilities and SDK' (control panel ->
Programs and Features|Turn features on/off), and go through that whole
process you will end up with rsh.exe and rcp.exe binaries.

Unfortunately this brings in a /lot/ of unwanted stuff, including an
apparently broken version of ping that complains with "socket: Operation not
permitted", and a bunch of unix tools that don't understand drive letters or
unc paths:

ls -la c:
ls: c:: No such file or directory <-- what??

ls -la //meade/net
ls: //meade/net: No such file or directory <-- no unc's either??

dir \\meade\net <-- works fine
[normal directory listing]

Those first two ls commands /should/ work. I understand cygwin likes this
other path naming scheme with /dev/fs or whatever, but come on. The commands
should understand the underlying file system's naming conventions too.
*throws hands in air*
 
ls -la c:
ls: c:: No such file or directory <-- what??

ls -la //meade/net
ls: //meade/net: No such file or directory <-- no unc's either??
Click to expand...

OK, somehow magically the above ls commands are now working fine.. not sure
what changed. Possibly an old DOS window was open from before installing the
Unix tools that didn't have the SUA environment variables? Not sure.

I've also been installing the VS Express compiler today.. maybe one of the
DLLs made this work now? Not sure.
Unfortunately this brings in a /lot/ of unwanted stuff, including an
apparently broken version of ping that complains with
"socket: Operation not permitted"
Click to expand...

I poked at this a little more.

The ping that comes with the unix tools works OK in a DOS window running as
the real "Administrator" user (eg. 'runas /user:administrator cmd').


--- snip -- DOS Window running as Administrator
C:\Windows\SUA\bin>.\ping on
PING ontario.erco.x (192.168.1.9): 56 data bytes
64 bytes from 192.168.1.9: icmp_seq=0 ttl=63 time=1.953 ms
64 bytes from 192.168.1.9: icmp_seq=1 ttl=63 time=0.977 ms
^C
--- snip

But if I run the same binary from one of my other DOS windows running as the
default user, I get the 'socket: Operation not permitted' error:

--- snip -- DOS Window running as regular user created during install:
C:\Windows\SUA\bin>.\ping on
ping: socket: Operation not permitted
--- snip ---

So that's "interesting"..
 
Back
Top