This content has been marked as final. Show 1 reply
First of all, I dont know if you even done the proper fault elimination
No route to host is indicative of a network problem that could be based on several different faults.
Simplest way to check, log in to the system running your IdM.
first check if your nameservice is working
nslookup <your fully qualified hostname for the AD gateway>
if you get the right response there
idmmgr@unix103a:$ nslookup idm-gw.company.com Server: 126.96.36.199 Address: 188.8.131.52#53 idm-gw.company.com canonical name = win050a.company.com. Name: win050a.company.com Address: 184.108.40.206
try pinging the returned address
If you have a routing problem it will probably show above...
idmmgr@unix103a:$ ping 220.127.116.11 18.104.22.168 is alive
if the route to the gateway works, it might be the gateway that cant talk to the AD
Just follow the track manually and if it stops working from one point, go past that point (if you can) and see if it works beyond it.
Either way, whatever resource is pointed out in the connectinfo in the pertinent adaptor or connector should work from the prompt of the system running it, if not, then you can start unraveling it from there.