Failed to validate the Domain User and Password

[Oscar Antonio Becerril Lopez]

After a new install of the PVS Server, tried to create the applayering connector but can't pass the credentails test, even tho those are the credentials for that user and that's the correct admin user, Agent and snapins are insalled and PSRemoting is enabled

 

[Rob Zylowski]

You have to reregister powershell whenever you upgrade PVS versions.

[Oscar Antonio Becerril Lopez]

12 minutes ago, Rob Zylowski1709158051 said:

You have to reregister powershell whenever you upgrade PVS versions.

Already registerd PS, and this was not an upgrade it was a new PVS server

 

 

[Rob Zylowski]

Did you set the execution policy within powershell to remote-signed  or unrestricted?  I assume the account is also a PVS admin?

[Oscar Antonio Becerril Lopez]

10 minutes ago, Rob Zylowski1709158051 said:

Did you set the execution policy within powershell to remote-signed  or unrestricted?  I assume the account is also a PVS admin?

yes is set to remote, and yes this is also a PVS admin

[Rob Zylowski]

After that we would normally think of firewalls in the way or a problem routing by name or maybe dns resolution for the short name.

What OS is PVS on?

[Oscar Antonio Becerril Lopez]

14 minutes ago, Rob Zylowski1709158051 said:

After that we would normally think of firewalls in the way or a problem routing by name or maybe dns resolution for the short name.

What OS is PVS on?

Windows server 2012 r2, firewalls are down, ELM is resolving for the name of the PVS (long and short)

 

Edited January 24, 2018 by becerr59
typo correction

[Oscar Antonio Becerril Lopez]

It might be possible that a previous PVS server configuration is causing the problem, it seems that the value and UUID are stored in a MySQL DB, is there any way to delete the previous configuration from the ELM?

 

We have been trying to create a new PVS connector using a newly created PVS server with the same name and ip as the old one, after that failed we tried with an another name, on the ELM it shows the old PVS config even tho this server has been deleted, and the new one is not shown in the available PVS list.

 

Edited January 25, 2018 by becerr59
spelling and info missing

[Daniel Weszligling]

Have you tried to reboot the ELM appliance? Had a similar problem, after the reboot of the appliance it worked for me.

 

Regards,

Daniel

[Rob Zylowski]

Daniels idea is worth trying.  If you change the IP address of the ELM then a reboot is required for the ELM to fully know about it.  I would think though that that would only matter when you get to transferring files to the PVS server because we actually pull them using the BITs service so the ELM tells the agent what its IP address is so the file can be pulled by the BITS service.

 

I would say try the reboot then put in a ticket at this point because it looks like you have done everything right.

 

Rob

[Oscar Antonio Becerril Lopez]

Daniel yes we have tried several reboots but without success

 

Finally worked, well kinda, The check credentials works, now it on the vDisk settings the test fails

 

 

[Rob Zylowski]

What did you change to make it accept the credentials?

What does the agent log file say when you tried to upload the vDIsk?

Do you have the BITS service enabled?

[Levi Hunter]

I ran into this issue today...after a fair amount of troubleshooting I found that a new Group Policy setting was applied to my PVS servers (both 2012r2 and 2019).

Upon inspection of that policy I noticed that "Allow Remote Shell Access" was Disabled.

Re-enabling "Allow Remote Shell Access" resolved the problem.

 

Policy location:-

Computer Configuration - Administrative Templates - Windows Components - Windows Remote Shell

Allow Remote Shell Access