Problem with RSHELL

[Frank]

Hi,

what do I need to get RSHELL working? I'm not shure what

Note: Windows does not include the rshell service, so you will need to get one from a third-party and install it on the remote system before executing RSHELL

means. My target is a NetApp toaster with a unix-like os.

In XP it worked fine:

C:\Temp >ver /r

TCC LE  12,10,59   Windows XP [Version 5,1,2600]
TCC LE Build 59   Windows XP Build 2600  Service Pack 3

C:\Temp >which rsh
rsh ist ein externer : C:\WINDOWS\system32\rsh.exe

C:\Temp >rsh ber-nas01 version
NetApp Release 7.3.4P4: Fri Nov 19 14:20:42 PST 2010

C:\Temp >

In W7 rsh doens't exist anymore but RSHELL doesn't do what I expected:

C:\Temp >ver /r

TCC  13.00.26   Windows 7 [Version 6.1.7601]
TCC Build 26   Windows 7 Build 7601  Service Pack 1
Registered to ****************

C:\Temp >which rsh
rsh is an unknown command

C:\Temp >which rshell
rshell is an internal command

C:\Temp >rshell ber-nas01 version
TCC: (Sys) Der Zugriff auf einen Socket war aufgrund der Zugriffsrechte des Sockets unzulässig.
"version"

C:\Temp >

frank

 

[rconn]

> what do I need to get RSHELL working? I'm not shure what

It was never in the release version of Windows, though it used to be in the
resource kit. But since Vista it's been removed altogether.

You'll have to find a suitable rsh server (Google "Windows 7 rsh download").
There are a number to choose from.

Though you might be better off switching to a more secure (SSH?) connection.

 

[Frank]

But I want to connect to a machine which provides a rsh server.
Do I really need a rsh server on my W7 pc?

 

[rconn]

> But I want to connect to a machine which provides a rsh
> server. Do I really need a rsh server on my W7 pc?

No. The RSHELL command in TCC provides the local client; if you have an
existing rsh server you can connect to it with RSHELL without requiring any
additional software.

(Although as I said in my last message, you will have zero security, so if
the server is remote system you might want to think about using something
like PUTTY / SSH instead.)

 

[Frank]

ok, I'm glad that I'm not totally confused (yet ;-).
But that brings us to the origin. Under XP (windows rsh) it works,
but with the TCC rshell does not work.
This is an actual code snippet from my old XP pc:

>rsh ber-nas01 date
Tue Oct 25 15:18:23 CEST 2011

>rsh ber-nas01 "vol status"
         Volume State           Status            Options
            dod online          raid_dp, flex     create_ucode=on
             SP online          raid_dp, flex     create_ucode=on,
                                                  convert_ucode=on
           nfs0 online          raid_dp, flex     nosnap=on, create_ucode=on,
                                                  convert_ucode=on
            amd online          raid_dp, flex     create_ucode=on
        vollun0 online          raid_dp, flex     nosnap=on, create_ucode=on
        install online          raid_dp, flex     create_ucode=on
       regional online          raid_dp, flex     create_ucode=on
            lzm online          raid_dp, flex     create_ucode=on,
                                                  convert_ucode=on
     apps_projs online          raid_dp, flex     create_ucode=on

Under W7 / TCC rshell gives the abovementioned error.

frank

 

[rconn]

Under W7 / TCC rshell gives the abovementioned error.

Unfortunately, I don't speak German, so I have no idea what the above mentioned error means.

Your RSHELL command line will only work if your RSH server does not expect a username, firewall username and password, and/or remote port. (It seems unlikely that anyone would leave a server so exposed, but I suppose it's possible.) If your server *does* expect any of that information, you can specify it either on the RSHELL command line or in OPTION / Internet.

 

[Frank]

Hello Rex,

I really appreciate your patience and engagement with "your users"!

And I guess that you "speak" more computer languages than natural languages :-)
My english is not the best, too and perhaps sometimes my intention is not obvious at the first glance.

In this case both my pc and the NetApp machine are AD domain members and the permitted rsh-users are coded as a pair of "hostname" "username" in a etc/hosts.equiv file. In my opinion this configuration is safe enough for our environment.

... so I do not need to specify user/password. Simply "rsh hostname/ipaddr command" is working, as you can see in my last example from my XP pc.

If you can't translate the error message I will try to install an english W7 pc and reproduce the error in english. Or wouldn't it be ok to use an Server 2008 R2 (same kernel) ? What do you think of that idea?


Frank

 

[rconn]

In this case both my pc and the NetApp machine are AD domain members and the permitted rsh-users are coded as a pair of "hostname" "username" in a etc/hosts.equiv file. In my opinion this configuration is safe enough for our environment.

... so I do not need to specify user/password. Simply "rsh hostname/ipaddr command" is working, as you can see in my last example from my XP pc.

But your XP example wasn't using RSHELL, it was using another rsh client. The XP rsh may have been automatically supplying a username; the RSHELL in TCC definitely does not. So there's no way for your host to know who is trying to connect to it if you don't configure RSHELL in OPTION or supply the parameters on the command line.

 

[Frank]

ok, I'm with you. Perhaps I was mislead by

RSHELL

Usage:
RSHELL allows remote execution of commands on any system with the rshell service installed. Press Ctrl-C to disconnect from the other system.

If you don't specify a username, RSHELL will use the current username.

Today I tried rshell on 2 Windows Server 2008 R2 (SP1).
On one it is working! One the other it is not working:

>ver /r

TCC  13.00.26   Windows 2008R2 [Version 6.1.7601]
TCC Build 26   Windows 2008R2 Build 7601  Service Pack 1
Registered to ****************

>rshell ber-nas01 "ifstat vifm"

-- interface  vifm  (178 days, 12 hours, 11 minutes, 4 seconds) --

RECEIVE
 Total frames:      274m | Frames/second:     289  | Total bytes:      4520g
 Bytes/second:    70184  | Multi/broadcast:  7626k
TRANSMIT
 Total frames:     2299m | Frames/second:     277  | Total bytes:     10969g
 Bytes/second:    42339  | Multi/broadcast: 34600

[C:\Program Files (x86)\JPSoft\TCMD13]ver /r

TCC  13.00.26   Windows 2008R2 [Version 6.1.7601]
TCC Build 26   Windows 2008R2 Build 7601  Service Pack 1

[C:\Program Files (x86)\JPSoft\TCMD13]rshell ber-nas01 "ifstat vifm"
TCC: (Sys) An attempt was made to access a socket in a way forbidden by its access permissions.
 "ifstat vifm"

[C:\Program Files (x86)\JPSoft\TCMD13]

Now we have at least the english error message ;-)

Slowly but surely I become a little bit frustrated.
But I will dig deeper...


Frank

 

[rconn]

> [C:\Program Files (x86)\JPSoft\TCMD13]rshell ber-nas01 "ifstat vifm"
> TCC: (Sys) An attempt was made to access a socket in a way forbidden
> by its access permissions.

That's a Windows socket error (not a TCC error).

It usually means that somebody else (app, service, or driver) is bound to
the same address with exclusive access.