Can your client resolve the hostname of the appserver?
Are you using a vip?
There are a couple ‘validate..’ settings in blasadmin you can set to false and restart the appserver to clear this.
I dirctly login to ap server and facing this issue.
Please tell me the setting in blasadmin also I came to know it's pointing to some old BL server and if your credentials are cached then it works.
Can you run a ‘blasadmin show auth all’ and post the result (if you have a separate config instance you might need to do blasadmin –s instanceName show auth all)
C:\Documents and Settings\pkwebopspcg.PCG>blasadmin show auth al To change future application servers, blasadmin must be run against the _templat e deployment. blasadmin now running against deployment: default [AuthServer] ActiveDirectoryLdapUrl: ActiveDirectorySearchBase: AppServiceURLs: AuthSvcKrb5Config:blappserv_krb5.conf AuthSvcKrb5LoginConfig:blappserv_login.conf AuthSvcPort:9840 AuthSvcSocketTimeout:75 AuthSvcSocketsBindAddress:all IsADKAuthEnabled:true IsActiveDirectoryLdapCheckEnabled: IsDomainAuthEnabled:true IsLdapAuthEnabled: IsSRPAuthEnabled:true IsSSOCredRefreshEnabled:true IsSecurIdAuthEnabled: IsSsoRefreshHostnameCheckEnabled: LdapUserDnTemplate: LdapUserValidationFilter: MaxAuthSvcContexts:20 MaxAuthSvcThreads:3 MaximumSessionCredentialLifetime: ProxyServiceURLs: ReportServiceURLs: SessionCredentialLifetime:525600
Actually issue is that it's trying to connect another bl appserver and editing
host file at c:\windows\system32\etc\host fixes it after restarting the service