03-10-2014 05:07 PM
Hi All,
I have a greenfields EV install version 10.0.4, with 2 servers working ok, I have just added a further 2 and am getting an RPC error when attempting to manage them from the Directory server.
When attempting to right-click Properties on the new server the error is;
"Failed to get auditing information from computer xxxx0004, Reason: The RPC server is unavailable
Check that the admin service is running on xxxx0004."
Clicking ok shows the properties screen but with the auditing tab empty aside from another error;
Unable to obtain Auditing data from computer xxxx0004, Check that the auditing registry keys have been setup correctly and that Admin service is running.
Any attempt to make any other changes on the other tabs result in an RPC error.
You can manage the server Directory server from the new server. All servers are on the same sub-net and are resolvable both by server name and alias name.
Any ideas would be gratefully received.
Thanks
Solved! Go to Solution.
03-10-2014 07:46 PM
I would be tempted to disable the firewall to see if that allowed it to work.
Also, double check your firewall settings with this:
Article:HOWTO75003 | | | Created: 2012-03-31 | | | Updated: 2013-07-12 | | | Article URL http://www.symantec.com/docs/HOWTO75003 |
03-10-2014 05:32 PM
Can you do a dtrace of the MMC and recreate the issue?
03-10-2014 05:58 PM
Hi Tony,
I've done that now, unfortunately I am at a site where I can't just paste the results so bear with me while I summarise it;
Successfully communicated with the directory service on the local machine
CAuditingHelper:: GetAdminAuditInterface () hr = The RPC server is unavailable.
CAuditingHelper:: SetAuditRegistryArray () Admin Server: xxxx0004
CAuditingHelper:: GetAdminAuditInterface () Admin Service: xxxx0004
CAuditingHelper::
{VaultCoCreateInsatnceEX} Attempt [1] to create COM object failed CLSID [{03ee.....}] Server Name [xxxx0004] Result [The RPC server is unavailable. (0x800706ba)]
This is repeated a few times for each attempt at opening the properties.
Thanks
03-10-2014 06:32 PM
Did the Deployment Scanner come up clean? Is the firewall disabled on the new servers?
03-10-2014 07:20 PM
Deployment scanner was ok, a few cautions but no red. The firewall is on but 135 is excluded.
03-10-2014 07:46 PM
I would be tempted to disable the firewall to see if that allowed it to work.
Also, double check your firewall settings with this:
Article:HOWTO75003 | | | Created: 2012-03-31 | | | Updated: 2013-07-12 | | | Article URL http://www.symantec.com/docs/HOWTO75003 |
03-10-2014 08:02 PM
Thanks Tony, found the offending ports 49153-49453 and required editing of the default protocols under component services.
Details here;
http://www.symantec.com/business/support/index?page=content&id=TECH124260
Thanks for your help.