JEA discovery set up (Timed out & Authentication failed) issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-12-2025 08:16 AM
Hi Team,
I have implemented the JEA discovery on few servers, but 2 servers are discovered successfully using with JEA credential and other servers are not discovered, I did the same configuration on all the servers but still its not working
When i test the credential validation am getting timed out issue. even successful discovery servers also when i test credential validation getting timed out issue, sometime validation successful and some times am getting timed out issue on successful discovery servers
But am able to login the same credential using RDC from source MidServers to target server, Also have checked with Firewall team and they told there is no firewall blocking the access from source to destination then open the Hi ticket but no resolution yet, Still ServiceNow(Engineer) suspecting some communication blocking or dropping from source to destination
When i check the port numbers 5985/5986 from source to destination connectivity established and there is no issue
Our windows admin added the JEA user id into the "Remote Desktop User " group on the target machine, So please let me know is this correct ? or is there any specific Non-admin group to add the JEA discovery user id?
I am facing the issue from last 1 month but no luck yet, If any one have an idea or resolution please share with me it could be appreciated.
For JEA set up and configuration I have met all the prerequisites and PowerShell commands are executed properly, source Midserver and target servers are the same domain , but not sure why am getting timed out issue for credential validation and discovery getting error message as "Active, couldn't classify No WMI connection", So please check and provide your thoughts.
Regards,
Maruthi
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-27-2025 01:30 AM
Have you created and deployed the code signing certificates ? are you still facing the same issue ?
Regards,
Anuj Bathvi