Windows credentials failing to authenticate

[Khanna Ji]

Hello Team,

I am trying to add credentials in Orchestration -> Credentials & Connections -> Credentials for windows machine but it's is throwing authentication error when running Test Credentials.

Using a port as 135 and target as IP address and default mid server.

Credentials are working fine when I am trying RDC (Remote Desktop Connection).

[DaveHertel]

Be sure firewalls, ACLs, security rules, etc. are not blocking port 135 between the MID's IP and the target IP.

If you are testing RDP from your own machine (which may not be the MID???) then this doesn't validate what you need.  Ensure the MID-to-target IP on port 135 are indeed open. From what you describe, it seems something is blocking that communication...

Hope this helps?

[Khanna Ji]

How can I tell my network n windows team about the issue? I need some logs or a proof supporting my statement. They are saying it's a service now problem

[DaveHertel · Accepted solution]

Well, a fairly easy test is to: 1) login to your MID server (or remote control into it, if its not physically located where you are); 2) While on the MID, attempt to RDP (remote desktop protocol) into the target machine.  OR test from the MID that you can NET USE to the target windows machine.  

You want to Validate that from the perspective of the MID server (not your own desktop) that the MID can communicate with the target windows box.  RDP, NET USE, etc. are often adequate to see if IP communication is open between MID and target machine.

If the MID cannot talk to the target, but your personal desktop can talk to the target, you have some data to work with... implying there seems to be some network/security/ACL type of issue

[Khanna Ji]

Can we try ping commands from mid server to target host? Any other ways to prove the connection?