ServiceNow to SolarWinds Connector Test failed
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-17-2018 09:43 PM
Hi all,
I am trying to configure SolarWinds connector from my ServiceNow.
Have filled in all the details, but when I perform a test, the results returned "Timed out for connector instance".
What does this error means?
I can confirm the credentials supplied is working though.
I am also able to telnet to the SolarWinds server on the default port 17778.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-17-2023 07:46 AM
Even I am having the same issue at the moment, please share the solution if you have been found the solution by now.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-18-2023 08:13 AM
Did u test telnet from your MID server to Solarwinds server on port 17778?
u mentioned both servers are in same network but is there any local firewall in place with specific settings? It may be blocking as i have seen this several times due to group policies.
Are u able to ping bothways?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-25-2024 12:14 AM
Hello folks.....
We solved this issue in our case.
We have two SolarWinds connector instances, 17774 and 17778.
For 17774, it works properly and generates events. However, for 17778, the error is displayed below.
So we changed 17778 to 17774 for both the instance .And now it works properly and generates an event as well.
Please mark the answer if it was helpful.
Thank you.