Networker Rpc Error Authentication Error
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 networker 8 authentication error why server rejected credential » Downloads » 日本語コミュニティ EMC Community Dell Community A AppSync Application Xtender networker unable to connect to server authentication error why = invalid client credential Atmos Avamar C Captiva Celerra Centera CLARiiON Cloud Tiering Appliance Connectrix D Data Domain Data Protection Advisor
Could Not Get Session Key From For Gss Authentication
Disk Library DiskXtender Documentum E ECS eRoom G Greenplum H Host Systems I InfoArchive Isilon ISIS Document Imaging L Leap N NetWorker P PowerPath Prosphere R RecoverPoint Replication RSA
Conflicting Nsr Peer Information Resources Detected For Host
S ScaleIO Secure Remote Smarts SourceOne & EmailXtender EMC Storage Analytics Symmetrix 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. 1 2 Previous Next 19 Replies networker update auth methods Latest reply: Oct 2, 2014 1:58 AM by baa Athentication error; why = Server rejected credential raffy Jul 11, 2013 8:03 PM Hi,Currently having some issue in adding clients in Networker backup solution.Unable to connect to server. Unable to authenticate with server "server name": Authentication error; why = Server rejected credential.Note: Client Networker agent has been re-install to isolate the issue but no luck. Same error occurred . 22088Views Tags: none (add) domain Content tagged with domain , data Content tagged with data 1. Re: Athentication error; why = Server rejected credential Tim Quan Jul 11, 2013 9:17 PM (in response to raffy) First verify the Hosts file. Add networker server entry to the Hosts file of the client and add the client entry to the Hosts of the networker server. (both short name and long name need to be added)If issue still exists, delete peer information:On the client:nsradmin -p nsrexecprint type: nsr peer information; name:
General Technology General thoughts Licensing Linux NetWorker Policies Quibbles Recovery Scripting Security Support VBA Windows Links Chuck's Blog LTO Consortium Micromanuals Penguin Punk's
Emc Support Login
Blog Reports Ronny Egner Storagebod StorageNerve StorageZilla About Nomenclature Contact Archives Why donations? Why the flag? Basics - Fixing "NSR peer information" errors Basics, NetWorker, Scripting Feb 232009 If you're using a modern NetWorker environment, the chances are that you'll periodically notice entries such as the following in the daemon.log / daemon.raw files https://community.emc.com/thread/177996?tstart=0 on the backup server: 39078 02/02/2009 09:45:13 PM 0 0 2 1152952640 5095 0 nox nsrexecd SYSTEM error: There is already a machine using the name: "faero". Either choose a different name for your machine, or delete the "NSR peer information" entry for "faero" on host: "nox" While this may look confronting, it's actually a http://nsrd.info/blog/2009/02/23/basics-fixing-nsr-peer-information-errors/ trivially easy error to fix that requires just a minute or so of your time with nsradmin. First, note the client that the error is about, and the client that the error is being recorded from. In this case, the error is about the client faero, while the error is being registered against the host nox. To fix, run up nsradmin against the client service on nox: # nsradmin -p nsrexec -s nox (alternatively, you can use: nsradmin -p 390113 -s nox) At the nsradmin> prompt, enter the command: delete type: NSR peer information; name: faero And answer yes when prompted to confirm. For example, the session might resemble the following: nsradmin> delete type: NSR peer information; name: faero type: NSR peer information; administrator: root, "user=root,host=nox"; name: faero; peer hostname: faero; Change certificate: ; certificate file to load: ; Delete? y deleted resource id 17.0.83.117.0.0.0.0.210.37.85.73.0.0.0.0.10.0.0.1(1) There, you've done it. Note that you should be periodica
known simply as Solaris, is a Unix-based operating system introduced by Sun Microsystems. The Solaris OS is now owned by Oracle. Search Forums http://www.unix.com/solaris/228033-rpcinfo-cant-contact-portmapper-rpc-authentication-error-why-failed-unspecified-error.html Show Threads Show Posts Tag Search Advanced Search Unanswered Threads Find http://www.tek-tips.com/viewthread.cfm?qid=255664 All Thanked Posts Go to Page... learn unix and linux commands Rpcinfo: can't contact portmapper: RPC: Authentication error; why = Failed (unspecified error) Solaris Thread Tools Search this Thread Display Modes #1 06-12-2013 christr Registered User Join authentication error Date: Sep 2011 Last Activity: 18 May 2014, 9:27 PM EDT Location: McKinney, TX Posts: 74 Thanks: 5 Thanked 6 Times in 6 Posts Rpcinfo: can't contact portmapper: RPC: Authentication error; why = Failed (unspecified error) I have two servers with a fresh install of Solaris 11, and having problems when doing rpcinfo between them. There is no firewall involved, authentication error why so everything should theoretically be getting through. Does anyone have any ideas? I did a lot of Google searches, and haven't found a working solution yet. Code: server1$ rpcinfo -p server2 rpcinfo: can't contact portmapper: RPC: Authentication error; why = Failed (unspecified error) Code: # svcs -a | grep rpc disabled May_20 svc:/network/rpc/keyserv:default disabled May_20 svc:/network/rpc/rstat:default disabled May_20 svc:/network/rpc/rex:default disabled May_20 svc:/network/rpc/wall:default disabled May_20 svc:/network/rpc/rusers:default disabled May_20 svc:/network/rpc/spray:default online May_20 svc:/network/rpc/bind:default online May_20 svc:/network/rpc/gss:default online May_20 svc:/network/rpc/smserver:default Remove advertisements Sponsored Links christr View Public Profile Find all posts by christr #2 06-13-2013 Peasant Registered User Join Date: Mar 2011 Last Activity: 21 October 2016, 12:22 AM EDT Posts: 991 Thanks: 26 Thanked 264 Times in 241 Posts Check output on host you are trying to get RPC info from (server1) : Code: svcprop network/rpc/bind:default | grep -i local If it returns config/local_only boolean true , then put it to false via svccfg. Code: svc:> select network/rpc/bind svc:/network/rpc/bind> setprop config/local_only=false svc:/network/rpc/bind> quit root@host:~# svcadm refresh /network/rpc/bind root@host:~# svcprop network/rpc/bind:default | grep
FORUMSFOR COMPUTER PROFESSIONALS Log In Come Join Us! Are you aComputer / IT professional?Join Tek-Tips Forums! Talk With Other Members Be Notified Of ResponsesTo Your Posts Keyword Search One-Click Access To YourFavorite Forums Automated SignaturesOn Your Posts Best Of All, It's Free! Join Us! *Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail. Posting Guidelines Promoting, selling, recruiting, coursework and thesis posting is forbidden.Tek-Tips Posting Policies Jobs Jobs from Indeed What: Where: jobs by Link To This Forum! Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.Just copy and paste the BBCode HTML Markdown MediaWiki reStructuredText code below into your site. Legato back-up solutions Forum at Tek-Tips HomeForumsServer RackBack-up SystemsLegato back-up solutions Forum RPC Error: Authentication Error thread480-255664 Forum Search FAQs Links MVPs RPC Error: Authentication Error RPC Error: Authentication Error jsargent (TechnicalUser) (OP) 19 Apr 02 12:26 I'm running 6.1.1 on Win2K SP2.I've got a couple of clients that used to be NT4 clients, but have recently been rebuilt on new hardware and Win2k server.They kept the same names.Here's what I'm getting:save: RPC Error: Authentication errorsave: Cannot open save session with chi2kmb01.xxx.comHas anyone seen this?Any help would be greatly appreciated!Thanks in advance!Josh RE: RPC Error: Authentication Error Zantor (MIS) 22 Apr 02 00:24 I had something similar happen. The error turned out to be a DNS problem. Networker uses a reverse lookup as part of its authentication.To diagnose the problem:From the client:Ping the client.Ping the server.nslookup the server.nslookup the client.From the server:ping the server.ping the client.nslookup the server.nslookup the client. Red Flag This Post Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework. Cancel Red Flag SubmittedThank you for helping keep Tek-Tips Forums free from inappropriate posts.The Tek-Tips staff will check this out and take appropriate action. Close Reply To This Thread Posting in the Tek-Tips forums is a member-only feature. Click Here to join Tek-Tips and talk with other members! Resources Join | Indeed Jobs | Advertise Copyright © 1998-2016 ENGINEERING.com, Inc. All rights reserved.Unauthorized reproduction or linking forbidden without expressed