Hi,

I think the firewall settings works fine, because a rpcinfo -p from the nsr server to the client and back give us a range of port information.

The backup and recovery process works also fine.

Have anyone an idea to debug the nsrpush command?

Regards, Bernd

Hello

was ping (by IP & by Name) from (client to server) & (server to client )  ok

from server , rpcinfo -p  client check on client ports

from client , rpcinfo -p server  check on server ports

Hi Bernd,

    As I understand your networker server is a Unix machine and the clients are windows. In this case the repository has to be on a windows file system. If not you may receive error.

Arun

Hello esnbesch

The error "RPC receive operation failed. A network connection could not be established with the host." suggest communication issues and may not be related to the nsrpush process.

The following KB articles addresses communication issues within the NetWorker environment, and in particular the error you are recieving.

http://solutions.emc.com/emcsolutionview.asp?id=esg77265

http://solutions.emc.com/emcsolutionview.asp?id=esg70774

Further to the above, the following KB article provides detailed information regarding NetWorker's operational port ranges. Please review and ensure that the proper and adquate ports are available.

http://solutions.emc.com/emcsolutionview.asp?id=esg66059

Also as an aside, please check the NIC configuration in your environment. I have seen in previous cases where a dual NIC environment (not proeprly configured for NetWorker)  can result in the error you have stated, however this is usually during backups.

Thanks.

Check for the Firewall settings..

HI Bernd,

Check out the NetWorker Administration Guide for your NetWorker version:

7.5 Admin Guide- http://powerlink.emc.com/km/live1/en_US/Offering_Technical/Technical_Documentation/300-008-471.pdf?
7.6 Admin Guiee - http://powerlink.emc.com/km/live1/en_US/Offering_Technical/Technical_Documentation/300-009-443.pdf?

The chapter on 'Firewall Support' is the best source of information on what exactly needs to be open on your firewall for
nsrpush and everything else.

-Bobby

Hi Bernd,

You can use the dbgcommand to raise the debug level of nsrcpd to debug 9 - although I wouldn't be too confident that that will give you much more useful information ( dbgcommand -p [pid-of-nsrcpd] "Debug=9"). If I were you, I'd start by opening more ports just to rule that out as an issue here.  nsrpush does use an extra port so it is possible that backup and restore get through but that the nsrpush doesn't.  Also, you should check that you are not running into one of the known limitations of the nsrpush command:

-Cannot perform a fresh install of the NetWorker software on a client machine.
NetWorker release 7.3 must already be installed on the client machine.

-Cannot upgrade clustered clients. This is automatically prevented.

-Cannot upgrade clients with PowerSnap packages installed. This is automatically prevented.

-Cannot upgrade hosts with NetWorker Server, License Manager or NetWorker Console packages installed (automatically prevented).

-Cannot upgrade the NetWorker software on clients where a module is installed unless both the NetWorker and module software is upgraded simultaneously on AIX. Modules can be upgraded independently.

-Cannot upgrade the NetWorker software if the NetWorker software is not installed on the same drive for the Windows operating system.

-Cannot install language packages as part of the upgrade process from NetWorker release 7.3 to release 7.4. English is installed by default.

-Bobby

Hollo ,

Have you tried to use host file on both end and what happense? I would advise to.

Alexey.