I am also having issues with Remote Procudure Call (RPC). My ISA 2006 SE (running on 2003 R2 SP2) is a member server. I recently uninstalled SP2, installed ADAM SP1, then reinstalled SP2. My ISA is also my Routing and Remote Access for the Domain, for which i use as my default router.
The issue i get is when i add domain members to a local group on my ISA and receive, "The Remote Procedure Called Failed" I know there is something Wack going on because it resolves the Domain Members Full name without typing it all in? I also set up a connectivity test between the ISA and Domain Controller for Group Type Active Directory, Method TCP testing RPC. Now i could be way way off here by using this test, but its seems like the thing to do, that is test??? (For which it works!) On a side note, should the DC be able to use AD to manage the ISA?
I would just like at add that when i go into my ISA's computer management. Under the Administrators GROUP, my domain\Domain Admins is displayed as it should be, but also the SID follows??? This is something that for me raises alarm bells, am i correct or way of base?
Would someone pleae throw me a bone! (figuratively speaking)
I did see this article, and even before reinstalling ISA 2006 SE after reinstalling SP2, I went ahead and made the registry change as suggested by Microsoft. And of course to no avail it didn't make a dam thing change!
So if you are running windows 2003 SP2 and can't get RPC to it's Probably because you're having issues with RSS.
(If you have a HP server you can disable RSS in the HP Network Configuration Utility)
Thanks!!! You just made my day - I was starting to contemplate a new install of my ISA box, but it turns out your solution had my system running again smoothly in no time at all, without even restarting it (used the HP Network utility, not the reg hack).
I opened a case with Microsoft 2 weeks ago regarding this matter and it still isnít resolved.
Microsoft admitted to me that there SP2 stuffed up my ISA 2006 server. I have been going around in circles with registry fixes and Microsoft patches with no luck to date. (Disabled RSS, Updated NIC drivers and about a million other ideas!)
I admit that I am using a "glorified workstation" as my ISA server but this shouldnít be the reason. (Even though I got that impression from Microsoft)
I am now replacing my ISA Server with a NEW piece of hardware that is infinitely better than what I have been using. I have a very strong feeling that once I import my settings into the new server that it will probably fail.
For the time being I had to disable the RPC filter and setup a special access rule from the ISA server to my Domain controller to keep things running until a fix is found. This setup was suggested by Microsoft themselves.
When and if I found the solution I will post it here. Until then anyone else that is having RPC issues with ISA I suggest the above mentioned suggestion if your desperate.
The PC is a dedicated ISA server with 1 external, 2 internal nics. It wasn't due to its "wimpyness" it was "implied" by Microsoft that since it had generic parts e.g. Family Ethernet Nic, that these parts hadnít been tested in a ISA environment and therefore should be changed.
And yes, since I disabled the RPC filter and created a rule to allow all outbound traffic specifically from the ISA server to the DC, I havenít had "THE" issues. But obviously this is not a good solution...