Credentials test fails authentification for 2012 R2 Standard Windows server inside of a DMZ

mpelyanskiy · ‎07-28-2017

Hello, community

I have a following problem - I'm trying to run Discovery for a 2012 R2 Standard Windows server inside of a DMZ. Server is located in a WorkGroup, not in a Domain.

I made sure, that both DMZ and local firewalls include exception for MID server, 443 port is enabled, remote UAC and local UAC are disabled, local admin account is being used for connection.

I've set up a MID server directely on the discovered server, validated it in my ServiceNow instance. Then, I've created a record in Credentials menu to store server access credentials. When I try to Test credentials - I get Authentification fail message. I've tried all possible combinations of credentials:

workgroup\username;

workgroup.\username;

computername\username;

computername.\username;

.\username;

\username;

username;

Trying to ping server IP address attempts from command promt works fine, and connecting to the server through Telnet is successfull.

Neither of options work to test credentials.

But the most odd thing is that when I run Quick Discovery using server's IP address - discovery process runs successfully.

Question: What am I doing wrong with credentials test? Why do I get Authentification error, but am still able to perform server's discovery?

Thank you.

geethunannapane · ‎07-31-2017

Hi Michael,

We had the same issue. We were able to resolve this. When testing credentials, ensure the user is a member of the local admin group on the target host and the target host can't be same as the host where the MID server installed. If it is the same you will get failures, which will seem like the user doesn't have access, when it, in fact, does.

Please mark as helpful or correct based on impact.

View solution in original post

naren_cis · ‎03-14-2018

Hi @geethunannapaneni,

I am currently facing same issue, could you please help me out here.

I have used different windows server for MID server & Active directory.

But when i am testing windows credentials it is getting failed.

for testing i am using below details with credentials of AD host machine with domain admin rights

1) Target: Public IP address of AD host machine

2) Port: 135

3) MID server: mid server installed on another host

Please suggest me what else need to be done. Please respond as it is some urgent thing i require

Thank you very much

naren_cis · ‎03-14-2018

Hi,

Could you please elaborate the steps that need to be configure to test the windows credentials for AD orchestration?.

1) which user credentials we should use Mid server host machine or target host machine?

2) is it necessary to open port 135? is there any other port can we use to test credentials?

3) what should be target? is it ip address of AD or Mid serverhost.