Pier Paolo Frassino wrote:
> Davina,
> noooo ... too easy !!! the nsrexecd process is running on the phisical
> node where the "nwind" name resides. The Networker Remote exec service
> is started as well.
> 
> :-((

:-)  OK, but it's something closely related to this. Have you checked
the servers file on the client, and can the client correctly resolve all
relevant names for the server?

> 
> Pierpa
> 
> 
> Davina Treiber wrote:
>> Pierpa wrote:
>>   
>>> Hi all,
>>> for testing purposes I installed 2 systems:
>>>
>>> - a NW server W2K, named "piggy"
>>> - a W2K3 system named "rambo" acting as a cluster node with EMC AutoStart 
>>> v5.2
>>>
>>> On the cluster node "rambo" I configured a cluster service with an IP and 
>>> a disk. In the hosts file I defined this IP's name "nwind"
>>> On the Nw server "piggy" I setup the W2K3 node "rambo" and "nwind" as 
>>> client. If I run a backup from the W2K3 node "rambo" it obviously works, 
>>> being a simple "save -s piggy -c nwind E:" where E is the service's disk.
>>> The problem is that, If I run the savegrp command, I receive the error:
>>>
>>> nsrexec: nsrexecd on nwind is unavailable. Using rsh instead.
>>> nwind: connection refused.
>>> nsrexec: SYSTEM error: Connection refused.
>>>
>>> I put SYSTEM@rambo and Administrator@rambo in the "nwind" client's remote 
>>> folder and in the AutoStart Console I configured piggy's  SYSTEM user as a 
>>> Console user with Administrator role.
>>> But the error is still the same.
>>>
>>> Have I missed something ??
>>> Any help is really appreciated.
>>>     
>>
>> Take three steps back and re-examine the problem - look at the wood not
>> the trees. Forget clustering. Forget remote access lists. This error
>> means that the server is unable to connect to the NetWorker Remote
>> Access service (nsrexecd) on the client - probably because that service
>> is not running.
>>
>>   
> 
> 
> --
> This email has been verified as Virus free
> Virus Protection and more available at http://www.plus.net
> 
> 

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu 
if you have any problems
wit this list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER