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 

[Fares1]

I've opened those ports both in the firewall settings of the Windows Server 2016 and Inbound settings on AWS, however there's still that error, I really don't see where there could be anything else to configure.

Thank you for your answers anyways.

[chuckm]

Did you first validate the credential successfully outside of ServiceNow from my earlier post (RDP from the MID server to the Windows Server 2016)?  Validating the credential outside of ServiceNow is important to help determine the next troubleshooting step to take.

[Fares1]

I managed to validate said credentials with the RDP from the MID Server to the Windows Server 2016. 

Then I opened the necessary ports.

[chuckm]

OK good.  Initiate ServiceNow discovery on the Windows Server 2016 (Discovery->Discovery Schedules and select Quick Discovery button at the top of the form).  Which phase does discovery stop at (in the ECC Queue tab)?

[Fares1]

There's a first error "Authentication failure with the local MID server service credential."

Then it tries to use a credential-less Discovery probe but can't because "the RPC Server is not available. HRESULT EXCEPTION : 0x800706BA)

Finally, it finishes by "Active, couldn't classify: No WMI connection, now finished"