Error Adsd
Contents |
Console error; SP; Console Technote (troubleshooting) Problem(Abstract) Users may find that they are unable to log in to their SiteProtector Console due to a "no server" error. Symptom The following error emc networker authentication error why = server rejected credential is displayed when attempting to start and log in to the SiteProtector Console: There is authentication error; why = invalid client credential no server at the machine address / port entered. Cause The primary reason for this issue is the SiteProtector Application Server is
Could Not Get Session Key From For Gss Authentication
not able to accept the connection from the SiteProtector Console. However, this primary issue can be caused be several different underlying problems. Resolving the problem YouTube Video Siteprotector Console Login Errors (2:02) This video describes how
Gss Authentication Server Rejected Credential
to resolve the login error: There is no server at machine address. Watch the video on YouTube (2:02) Verify that the SiteProtector Application Server is running The SiteProtector Console establishes its connection to the SiteProtector Application Server, so the first item to check is that the Application Server is running. Open Windows Services on the SiteProtector server. Check the SiteProtector Application Server Service and ensure that it is running. If it is not running, conflicting nsr peer information resources detected for host attempt to start it. If it is already running, restart the service. Verify that the SiteProtector Database is running and listening for connections In order for the Application Server to start successfully, it must be able to establish communication with the SiteProtector Database. With this in mind, the second item to check is that SQL is running and listening for incoming connections. Open Windows Services on the database server. Ensure that the SQL Server service is running. If the SQL Server service is running, ensure that it is listening for new connections by opening a command prompt on the database server and entering: netstat -an | find "1433" There should be at least one result like the following: TCP 0.0.0.0:1433 0.0.0.0:0 LISTENING Note: If you have configured SQL to listen on a port other than the default (1433), you will need to run the command against the custom port that you configured. If you are in this situation, you should ensure that you have configured the SiteProtector Application Server to connect over that custom port using the information in Technote 1619136: Changing SQL Server port to a non-standard port in SiteProtector. Verify that the SiteProtector Application Server can communicate with the SiteProtector Database If your Application Server and Database are on different servers, you should verify that communica
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 Dell Community
Networker Update Auth Methods
A AppSync Application Xtender Atmos Avamar C Captiva Celerra Centera CLARiiON Cloud Tiering Appliance Connectrix D Data Domain Data Protection Advisor 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 S ScaleIO Secure Remote Smarts SourceOne & EmailXtender EMC Storage Analytics Symmetrix U Unity V ViPR http://www-01.ibm.com/support/docview.wss?uid=swg21689502 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 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 https://community.emc.com/thread/177996?tstart=0 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 . 21768Views 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:
• Delete all board cookies • All times are UTC - 8 hours Powered by phpBB Forum Software © phpBB Group
be down. Please try the request again. Your cache administrator is webmaster. Generated Mon, 10 Oct 2016 10:09:07 GMT by s_wx1094 (squid/3.5.20)