Nsradmin Rpc Error Unknown Host
Contents |
Management Converged Platforms Data Protection Infrastructure Management Platform Solutions Security Storage Dell Products for Work Network Servers Education Partners Programs Highlighted Communities Support » Connect » Developers » Partners » Downloads » 日本語コミュニティ EMC Community conflicting nsr peer information resources detected for host Dell Community A AppSync Application Xtender Atmos Avamar C Captiva Celerra Centera CLARiiON emc networker authentication error why = server rejected credential Cloud Tiering Appliance Connectrix D Data Domain Data Protection Advisor Disk Library DiskXtender Documentum E ECS eRoom G Greenplum authentication error; why = invalid client credential H Host Systems I InfoArchive Isilon ISIS Document Imaging L Leap N NetWorker P PowerPath Prosphere R RecoverPoint Replication RSA S ScaleIO Secure Remote Smarts SourceOne & EmailXtender EMC Storage Analytics Symmetrix to correct the error it may be necessary to delete the nsrla database U Unity V ViPR Controller Product Communities > NetWorker > Discussions Please enter a title. You can not post a blank message. Please type your message and try again. 4 Replies Latest reply: Jul 10, 2009 7:06 AM by DavidHampson RPC error: Unknown host aaisupport Jul 26, 2006 12:30 AM Hi, I am
To Correct The Error, It May Be Necessary To Delete The %s Database
having one Windows 2003 server (name: srvr1) which is Networker Client. When I am taking the backup of the above through a Solaris storage node, I am getting an error (RPC error: Unknown Host). But when I am taking the backup of another server (name: srvr2), which is of the sane configuration of the above, it is working fine. The Networker service is confirmed to be running on srvr1 and I am able to ping to the client from the backup server. Pls help me to solve this issue.Regards,Shreejesh. 1000Views Tags: none (add) support Content tagged with support 1. Re: RPC error: Unknown host Hrvoje Crvelin Jul 26, 2006 1:49 AM (in response to aaisupport) Unknown hosts usually hints toward name resolution. Report Abuse Like Show 0 Likes (0) 2. Re: RPC error: Unknown host jherlihy Jul 30, 2006 10:33 PM (in response to aaisupport) Hi Shreejesh,Hrvoje's right - this sounds like a name resolution issue. You say that you can ping the client from the server, but try these extra steps (in each step test with both the hostname and IP address):1 - do an nslookup of your server
returned: (111) Connection refused http://nsrd.info/blog/2009/02/23/basics-fixing-nsr-peer-information-errors/ The remote host or network may be down. Please try the request again. Your cache administrator is webmaster. Generated Thu, 20 Oct 2016 13:03:01 GMT by s_ac4 (squid/3.5.20)
directed recover From: "VERHAEGHE Koen (BMB)"
signal, RPC, RPC TCP time, rpcinfo, TCP RPC error: RPC send operation failed; errno = An existing connection was forcibly closed by the remote host. 74209:save: Quit signalreceived. March 19, 2012 RPC error: RPC send operation failed; errno = An existing connection was forcibly closed by the remote host. 74209:save: Quit signal received. This error message mainly either Firewall issue or TCP timeout problem, you will need to test the connectivity from the backup server to the client and vice versa using the following command: Note: in each command use the FQDN and the Short Name of the machine. And you will use those commands in two ways communications ( Server > client and client > Server) 1- Ping 2- nslookup 3- rpcinfo -p MACHINENAME 4- nsradmin -v1 -s CLIENTNAME -p390113 ( This is from backup server to client machine) If communication is good, check the ability to telnet your client from the backup server using 7937 and 7938 ports respectively. If all of these checks work correctly, and you still receiving that RPC error message, so it is TCP timeout issue. To avoid any TCP timeout issue, I would suggest the following: 1- Change the group properties, and set "Client Inactivity Timeout" to "0" 2- Setting Keepalives to Prevent Timeouts: https://solutions.emc.com/emcsolutionview.asp?id=esg91994 If you are using Windows operating systems for the Backup server and client, use the following recommendations as well: 1- Disable TCP Chimney on Server and Client https://solutions.emc.com/emcsolutionview.asp?id=esg118437 2- Set TCP/IP keep alive settings at OS level. https://solutions.emc.com/emcsolutionview.asp?id=esg60759 Also there are some recommendations by Microsoft TCP/IP tuning to avoid any TCP timeout issue. You need to ap