Hi Robert

> filer->traceroute admin-host
>
> Nor does "rsh filer version" work from the admin host, I'm getting the
> following on the filer's messages file:
>
> Mon Feb 11 19:24:58 GMT [rshd_0:info]: couldn't connect second port on
> admin-host@domain.com
>
> I'm thinking networks didn't open *all* ports between filer subnet and
> admin hosts subnet. I'm verifying with them now.

For the traceroute issue it does indeed sound as if the router is dropping ICMP ECHO packets.
The way RShell works is that the filer has to create a connection from any random port back to the client. In networks where NAT is in use or firewalling this can often pose a problem. It may be that the network admin needs to allow connections from the filer.

> I did configure ssh keys on the admin host (solaris 10) and am getting
> this upon ssh'ing into the filer:
>
> Mon Feb 11 19:43:16 GMT [openssh.invalid.channel.req:warning]: SSH
> client (SSH-2.0-Sun_SSH_1.1) from {admin-host ip supressed} sent
> unsupported channel request (10, env)

I have seen this error too on occasion, but because it has always worked I never paid too much attention to it. I believe this happens when an X-client requests to tunnel X traffic, a service which the filer does not run; but maybe others can confirm this.

Kind regards
Kenneth Heal
Databasement BV
The Netherlands

Express yourself instantly with MSN Messenger! MSN Messenger