1 of 1 people found this helpful
There's a 'socketsbindaddress' that should bind the appserver ports to that ip.
but the above looks like some kind of name resolution issue where the appserver can't resolve itself.
Applied this change but now I just receive connection refused when i attempt to run nsh commands against hosts.
where is the error coming from - the proxy or the target ? if the target, what's in the agent log when it happens ?
the connection refused is only shown on the appserver, the rscd log on the target doesn't log that connection attempt. though i can now prove the connection is going over the proper adapter, now i'm back to troubleshooting the error from this post (using non fully qualified username to contact agent vice fully qualified --the profile i get the credential with is domain authentication): https://communities.bmc.com/thread/65837