remote system error networker Holly Hill South Carolina

Address 2731 Cleveland St, Elloree, SC 29047
Phone (803) 897-1051
Website Link
Hours

remote system error networker Holly Hill, South Carolina

Close Box Join Tek-Tips Today! Has anyone seen similar problems? But I haven't checked that as of yet. shortname) and any other names (e.g FQDN) as aliases.

This is from the group output. Right now, the backup is via Ethernet. No packets are being dropped.- Able to telnet to NDMP port#10000 on the celerra DM server.Thanks RE: rpcinfo problem tremblyj (TechnicalUser) 1 Feb 05 12:33 Hi,I got this message on my One scenario that MIGHT be the cause, as far as I can tell, is if Legato somehow starts to use ports that are beyond the specs in the networker administrators guide

will it have any impact on the client if I start the backup now ? Confirm and manage identities. Registration on or use of this site constitutes acceptance of our Privacy Policy. Re: unable to connect to server: Remote system error - connection refused Hrvoje Crvelin Oct 31, 2011 7:06 AM (in response to Sabarna Deb) Sabarna_Deb wrote:rpcinfo: can't contact portmapper: RPC: Remote

Thanks & RegardsPanwar Report Abuse Like Show 0 Likes (0) 10. These clients always reach a point when they fail after a few days/weeks. Oh, the servers are all Windows 2003 servers with client 7.1.1 and the server is running 7.1.2 on Solaris. When i fixed the device/pools problem, the error was gone.

The clients are on ESX cluster and have shared storage on the clariion too. You must create remote devices on the storage nodes attached mapping to local paths on the storage node. Documentation Nomenclature Categories Architecture Aside Avamar Backup theory Basics Best Practice Cloud Data Domain Data loss Databases EMC Ethics General Technology General thoughts Licensing Linux NetWorker Policies Quibbles Recovery Scripting Security Comments?

Preston de Guise said: [blog] NetWorker 7.6 SP1 firewall configuration on Windows 2008 R2. You can not post a blank message. John Tremblymailto:[email protected] RE: rpcinfo problem 605 (Instructor) 1 Feb 05 13:14 Is the listener nsrexecd running at the client? - It provides portmapper functionality. I also added it to my RC file.I'm now getting the other message "rpcinfo: can't contact lgtomapper: Remote system error - connection refused" on a Caldera Linux box but the portmapper

was this it ?? RE: rpcinfo problem AndersTrolle (ISP) 14 Apr 03 07:39 Make sure that the neccesary ports are open across your network. To make it simple, in a firewall enviornment it is best to open the required number of ports, rather than opening the entire port range. (opening the entire port range beats Update the HOSTS file with the correct IP Address and Host Name.

Windows XP/SP1? There is no name resolution issue either, since the hosts file is used in both ends. Confirm and manage identities. Yes, that's a lot of ports .

This can be because the client is down, the network is slow, reverse lookup isn't working, the RPC service is down on the client. 0 Kudos Reply skt_skt Honored Contributor [Founder] Re: unable to connect to server: Remote system error - connection refused Hrvoje Crvelin Nov 1, 2011 2:42 AM (in response to Sabarna Deb) In that case 2 things are happening:- mnisadmin says: March 8, 2011 at 11:13 am Hi Preston, I created a new folder on the disk and then selected Browse storage file system instead of device path > entered All rights reserved.Unauthorized reproduction or linking forbidden without expressed written permission.

Here's Why Members Love Tek-Tips Forums: Talk To Other Members Notification Of Responses To Questions Favorite Forums One Click Access Keyword Search Of All Posts, And More... PXE is working great as i was about to pull an inventory of a machine and from a debug mode i was able to ping back and forth between the fog Ultimately, prevent IP theft, fraud, and cybercrime.Explore products and solutions from RSA.Visit RSA.comOverviewEnterprise Network HardwareSwitchesRouters and Wireless NetworkingOverviewDocumentumLEAPInfoArchiveOverviewDell LaptopsDell DesktopsDell Thin Clients and VDI ProductsNo results foundNo results foundMODERN DATA CENTERGet According to the legato knowledge base, this might be the cause: Solution Title: Error: 'savefs: RPC error: Remote system error' Solution ID: legato12891 Here is the solution: Schedule the backups for

Close this window and log in. Default ports are 7937 -> 7939 and 10000 -> 30000. The name/IP address could also be one of the server's as seen by the client. Report Abuse Like Show 0 Likes (0) 7.

K kr1spy last edited by Hello, This is my first attempt at Linux for about five years and i could use all the help i can get. Restarting the networker server also solves the problem, which further indicates that this is not network related. Solution suggestions? :) //Oscar -- Note: To sign off this list, send a "signoff networker" command via email should be sent to stan < at > temple.edu Note: To sign off Join UsClose Navigation FOG Project Register Login Recent Unsolved Tags Popular Users Groups Search Your browser does not seem to support JavaScript.

Incoming Links ¿Cómo se soluciona el error "Conexión rechazada"? Ideas? Confirm and manage identities. this is what we have.

Typically you'd be looking at dedicated storage nodes, fibre-channel mapped/zoned to see tape drives, or VTLs, etc., backing up their own data to SAN-connected backup storage. The error message is more informative than just a "RPC error: Remote system error" (which is all I'm getting). It is telling you that, upon backup, Networker did a reverse and/or forward lookup of some name or IP address of the client/or server and did not like it..ie. Ultimately, prevent IP theft, fraud, and cybercrime.Explore products and solutions from RSA.Visit RSA.comOverviewEnterprise Network HardwareSwitchesRouters and Wireless NetworkingOverviewDocumentumLEAPInfoArchiveOverviewDell LaptopsDell DesktopsDell Thin Clients and VDI ProductsNo results foundNo results foundMODERN DATA CENTERGet

This was not specified in the networker documentation. IPCONFIG /flushdns - Purge the DNS Resolver cache. Then installed NW 7.6.1.3.Build.446 64bit. Locate partners—or learn about becoming one.Find EMC PartnersEMC Business Partner ProgramBecome an EMC ResellerPartner CommunityPartner PortalRSA PartnersDell PartnerDirectContact UsPartner with EMC today.Live ChatContact SalesCall 1-866-438-3622Call 1-866-438-3622Company InformationKeep up with the news,

Apparently, inbound TCP port 111 needs to be open as well. Oh, the servers are all Windows 2003 servers with client 7.1.1 and the server is running 7.1.2 on Solaris.