Windows Server 2016 credentials validation failed
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-25-2019 07:01 AM
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
- Labels:
-
Discovery
-
Service Mapping
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-26-2019 07:30 AM
Even though you updated the local Windows firewall rules for Discovery, it would be helpful to completely eliminate any firewall issues on the Windows Server 2016. If this is a lab server, temporarily turn off the Windows Server 2016 firewall rules and re-discover the Windows Server 2016. The steps are as follows:
1) Open the Windows Firewall.
2) In the Firewall Actions panel select Properties.
3) On the Firewall state to off in 1) the Domain Profile tab, 2) the Private Profile tab, and 3) the Public Profile tab.
4) Save.
Re-discover the Windows Server 2016 and look in the ECC Que TAB. Open the WMI: Clasify (input) and determine if you are getting any errors. For example in this discovery I am getting the following error (HRESULT: 0x80070005 (E_ACCESSDENIED)):
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-26-2019 08:16 AM
I think the problem may be from the MID Server itself.
The WMI Probe keeps telling me that there's an issue from the RPC Server the error is in French (and my computer is in French so that's the only possibility here).
I'm gonna check on that, but thanks ALOT for your answers.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-09-2024 09:39 AM
Hi Folks
I'm really interested to this issue.... Any update on it? We are facing the same for Azure. The only thing I have to share is that the error "0x80070005" has this solution:
Windows server needs to be installed with latest patches
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1123774