Welcome! » Log In » Create A New Profile

Cant add new client; server rejected credential

Posted by Michael Leone 
Michael Leone
Cant add new client; server rejected credential
November 08, 2017 08:03AM
So I am confused about this. I need to set up a new MS SQL Cluster server,
re-using an older server that had been a Networker client already.
So I re-formatted everything, installed new OS (Win 2012 R2), made it into
a cluster, then installed SQL Server 2012 R2 as a cluster, and installed
the Networker client 8.2.4, and the Networker client for MS Applications
8.2.3. I've done this a half dozen times before.

However, I can't add the SQL Cluster name as a client. Every time I try,
it is rejected with "Unable to connect to server: Unable to authenticate
with server pssql2-1: Authentication error: why = Server rejected
credential".

Now, this is a brand new SQL cluster, and has never been a Networker
client before.So there is no peer certificate to delete, which is usually
the first thing I check when I can't add a client (that, and DNS).
I did rename the nsrladb folder on the NMC client, and did delete the peer
certificate for the Windows host, both on the NMC and the NW server (I saw
earlier log messages in the NMC about how the peer information provided
did not match the one stored by the NMC, and recommended to delete the
peer certificate for the Windows host)

Am I missing something simple? Forward and reverse DNS exist for the SQL
cluster name. Windows firewall has the proper ports opened by the client
installation. I have simple ping connectivity between the server and the
SQL client.

I have no peer certificate for the new SQL client name, either on the NMC
or the server. All I see

--
Michael Leone
Network Administrator, ISM
Philadelphia Housing Authority
1800 South 32nd Street
Phila, PA 19145
Tel: 215-684-4180
Cell: 215-252-0143
<mailto:michael.leone@pha.phila.gov>




--
This list is hosted as a public service at Temple University by Stan Horwitz
If you wish to sign off this list or adjust your subscription settings, please do so via http://listserv.temple.edu/archives/emc-dataprotection-l.html
If you have any questions regarding management of this list, please send email to owner-emc-dataprotection-l@listserv.temple.edu
This message was imported via the External PhorumMail Module
akshay bhumkar
Re: Cant add new client; server rejected credential
November 08, 2017 08:04AM
Michael,

I think the error "Unable to connect to server: Unable to authenticate with
server pssql2-1: Authentication error: why = Server rejected credential"
may also point to different auth methods being used on NW server and the
client.

Can you check the auth methods?


Thanks & Regards

Akshay Bhumkar
516-262-2104

On Wed, Nov 8, 2017 at 10:45 AM, Michael Leone <Michael.Leone@pha.phila.gov>
wrote:

> So I am confused about this. I need to set up a new MS SQL Cluster server,
> re-using an older server that had been a Networker client already.
> So I re-formatted everything, installed new OS (Win 2012 R2), made it into
> a cluster, then installed SQL Server 2012 R2 as a cluster, and installed
> the Networker client 8.2.4, and the Networker client for MS Applications
> 8.2.3. I've done this a half dozen times before.
>
> However, I can't add the SQL Cluster name as a client. Every time I try,
> it is rejected with "Unable to connect to server: Unable to authenticate
> with server pssql2-1: Authentication error: why = Server rejected
> credential".
>
> Now, this is a brand new SQL cluster, and has never been a Networker
> client before.So there is no peer certificate to delete, which is usually
> the first thing I check when I can't add a client (that, and DNS).
> I did rename the nsrladb folder on the NMC client, and did delete the peer
> certificate for the Windows host, both on the NMC and the NW server (I saw
> earlier log messages in the NMC about how the peer information provided did
> not match the one stored by the NMC, and recommended to delete the peer
> certificate for the Windows host)
>
> Am I missing something simple? Forward and reverse DNS exist for the SQL
> cluster name. Windows firewall has the proper ports opened by the client
> installation. I have simple ping connectivity between the server and the
> SQL client.
>
> I have no peer certificate for the new SQL client name, either on the NMC
> or the server. All I see
>
> --
> Michael Leone
> Network Administrator, ISM
> Philadelphia Housing Authority
> 1800 South 32nd Street
> https://maps.google.com/?q=1800+South+32nd+Street+%0D+Phila,+PA+19145&entry=gmail&source=g
> Phila, PA 19145
> Tel: 215-684-4180 <0215%20684%204180>
> Cell: 215-252-0143 <0215%20252%200143>
> <mailto:michael.leone@pha.phila.gov <michael.leone@pha.phila.gov>>
>
>
> -- This list is hosted as a public service at Temple University by Stan
> Horwitz If you wish to sign off this list or adjust your subscription
> settings, please do so via http://listserv.temple.edu/
> archives/emc-dataprotection-l.html If you have any questions regarding
> management of this list, please send email to owner-emc-dataprotection-l@
> listserv.temple.edu
>


--
This list is hosted as a public service at Temple University by Stan Horwitz
If you wish to sign off this list or adjust your subscription settings, please do so via http://listserv.temple.edu/archives/emc-dataprotection-l.html
If you have any questions regarding management of this list, please send email to owner-emc-dataprotection-l@listserv.temple.edu
This message was imported via the External PhorumMail Module
Michael Leone
Re: Cant add new client; server rejected credential
November 08, 2017 08:59AM
> Michael,
>
> I think the error "Unable to connect to server: Unable to
> authenticate with server pssql2-1: Authentication error: why =
> Server rejected credential" may also point to different auth methods
> being used on NW server and the client.


I got it (with the help of Support). I had to delete the peer information
for the NMC and NW server on the actual client itself. Then I could add
it. I needed to do a manual command to register the client as being SQL,
but once I did that, I could add it.

So that's odd, yet resolved ...

On to other things! LOL


--
This list is hosted as a public service at Temple University by Stan Horwitz
If you wish to sign off this list or adjust your subscription settings, please do so via http://listserv.temple.edu/archives/emc-dataprotection-l.html
If you have any questions regarding management of this list, please send email to owner-emc-dataprotection-l@listserv.temple.edu
This message was imported via the External PhorumMail Module
Anonymous User
Re: Cant add new client; server rejected credential
November 09, 2017 04:59AM
I can't tell you the number of times that the solution is:

1. Delete client res folder

2. Clear server peer info.



Particularly when a VM template with NetWorker pre-installed was in use…



Dave



Date: Wed, 8 Nov 2017 11:47:13 -0500

From: Michael Leone <Michael.Leone@PHA.PHILA.GOV>

Subject: Re: Can't add new client; server rejected credential



> Michael,

>

> I think the error "Unable to connect to server: Unable to

> authenticate with server pssql2-1: Authentication error: why =

> Server rejected credential" may also point to different auth methods

> being used on NW server and the client.





I got it (with the help of Support). I had to delete the peer information

for the NMC and NW server on the actual client itself. Then I could add

it. I needed to do a manual command to register the client as being SQL,

but once I did that, I could add it.



So that's odd, yet resolved ...



On to other things! LOL


--
This list is hosted as a public service at Temple University by Stan Horwitz
If you wish to sign off this list or adjust your subscription settings, please do so via http://listserv.temple.edu/archives/emc-dataprotection-l.html
If you have any questions regarding management of this list, please send email to owner-emc-dataprotection-l@listserv.temple.edu
This message was imported via the External PhorumMail Module
Michael Leone
Re: Cant add new client; server rejected credential
November 14, 2017 05:59AM
> I can't tell you the number of times that the solution is:
> 1. Delete client res folder
> 2. Clear server peer info.

I tried doing deleting peer info, on the NW server and on the NMC server.
Where I *didn't* do it from was the client ...

> Particularly when a VM template with NetWorker pre-installed was in use…


I never pre-install Networker in my VMware templates, it just causes
aggravations. But in this case, the client was a physical host that was
completely re-formatted from scratch, with a OS upgrade, and Networker/NMM
upgrade. The host kept the same name, but the virtual SQL cluster node did
not ...

It's all working now. Or was, when I left on Wed (been off for a few
days).



--
This list is hosted as a public service at Temple University by Stan Horwitz
If you wish to sign off this list or adjust your subscription settings, please do so via http://listserv.temple.edu/archives/emc-dataprotection-l.html
If you have any questions regarding management of this list, please send email to owner-emc-dataprotection-l@listserv.temple.edu
This message was imported via the External PhorumMail Module
Sorry, only registered users may post in this forum.

Click here to login