Look at the /usr/nsh/log/rscd.log on the agent server while you try to connect. That may show you the issue. Also, as a test, you can add the the following line to your /usr/lib/rsc/exports file:
That should map all incoming connections to root, regardless of user. Then test connectivity. If it works, then you know you have a permissions issue. If not, then I would open a support ticket.
before: 07/30/09 10:34:36.857 WARN rscd - 10.192.224.11 221294 59615/59615 (ENTERPRISE-LMF-Administrator:ME@LM.LMIG.COM): CM: Host not authorized
after adjusting exports: 07/30/09 10:37:46.396 WARN rscd - 10.192.224.11 221316 0/0 (ENTERPRISE-LMF-Administrator:ME@LM.LMIG.COM): CM: Bad command ("bladmin"). Probably wrong encryption type/key
And we go from not authorized to not licensed, so maybe my users file is out of whack... I'll push a standard copy of that and see what happens. Definately don't want exports hanging wide open like that.
Thanks for the help!
Ok, root problem, DNS name resolution in the exports file... Added the IPs for the app servers, and I'll be changing the default file to stop this in the future.
Most of the boxes with the problem are DR, which have a different DNS setup, so it makes sense.