Windows Server 2016 credentials validation failed

[Fares1]

Hey fellow ServiceNowers,

I have a Windows Server 2016 instance on an Amazon EC2 and I can't seem to validate the credentials. 

The MID Server is running and doing fine and I'm using the Admin account as a local one (.\Administrator).

I've allowed inbound rules concerning port 135 and WMI protocols : 

I've even created rules for these port ranges:  49152 – 65535 (I used this answer but it didn't work for me: https://community.servicenow.com/community?id=community_question&sys_id=2e490e3cdb43a700afc902d5ca9619b7&view_source=searchResult ) 

I really don't see why it's so complicated compared to Linux systems? For Linux credentials as long as you have the right IP Address and the right login/password, it would work, the Windows authentification system isn't very clear.

Anyways, if you have any other advice about this types of credentials, I would really need it! 

Thanks in advance,

Fares K 

[robertgeen]

Can you post the error message you are getting if you run a horizontal discovery on it? I have run into issues with cloud environments in the past where the lack of DNS reverse lookup and netbios capabilities have caused windows discovery to fail.

[Fares1]

It's not during the horizontal Discovery that there's the problem.

It's during the "test credentials" phase in the Credentials module.

The error is just "Authentication failed".

[chuckm]

Validate your credential outside of ServiceNow discovery.  The Authentication failed error message you are getting might have nothing to do with the Credential but could be WMI or Firewall issues.  The steps to validate the credential are as follows: 

1) Log into the server where the MID Server Service is installed.

2) RDP from the MID Server to the Windows Server 2016.  There are several ways to launch RDP from the MID Server:

-From the command line, type mstsc and select enter…or

-In the Windows search box on the taskbar, enter Remote Desktop Connection and select enter... or

-Select the Windows+R keys and input mstsc and hit OK.

3) In the Remote Desktop Connection dialog box, fill in the Computer (IP address of Windows Server 2016) and Username.  Select the connect button.

4) Enter the credential in the next dialog box and select the OK button.

5) If you get the "The identity of the remote cannot be verified.  Do you want to connect anyway? select Yes.

If you successfully connect, then you know you have a valid credential - and you can move on to other troubleshooting steps.

[chuckm]

If you successfully test your credential outside of ServiceNow Discovery using RDP, then the next troubleshooting step would be to check the AWS Security Group between the MID Server and the Windows Server 2016.  For Windows, both port 135 and the high ports (49152 – 65535) need to be open in the AWS Security Group: