Windows credentials failing to authenticate

Khanna Ji · ‎11-25-2018

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 · ‎11-27-2018

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

View solution in original post

DaveHertel · ‎12-03-2018

While you can try PING, it doesn't absolutely prove what you want. Ping can tell you if an ICMP request is getting thru between 2 IP addresses, but its not a reliable test because:

1. its often blocked, so just because PING doesn't reply, doesn't tell you much

2. Its not attempting any type of higher level IP connection (such as WMI would use). So PING doesn't help validate if WMI will work or not

3. Ping doesn't' reflect what is really going on between a MID and targets so its not that helpful...

Yes Ping is easy, but also leaves a lot of unanswered questions..... Hope that helps?

krishsenthil · ‎10-01-2019

Hi Dave Hertel,

I'm facing the similar issue . I'm able to connect target server from local machine not from the mid server . But i'm able do telnet port 135 from mid server .

RDP port 3389 is mandatory to discover windows server ?

Thanks,

Senthil