Exchange 2007 CAS having issues connecting to second CAS server

Hi,

I have a single forest domain with 6 Exchange servers on the same vlan, and have a newly installed Exchange 2007 environment.  2 HUB/CAS, 2 Mailbox and 2 Edge servers.
When logging onto one of the CAS servers, I navigate to Server configuration > Client access. I get the error below when clicking on the other CAS server listed in the window.   The same applies when I log on to the other CAS server and perform the same actions.  I was reading the web and came across some posts about opening RPC ports because of Windows firewall being enabled.

I just wanted to add that If I tuen off the Windows firewall, this resolves the problem.    But I do not believe this is the correct solution.

Get-OabVirtualDirectory
Error: The task was not able to connect to IIS on the server xxxx. Ensure that the server exists and is reachable from this computer: The RPC server is unavailable

Get-OWAVirtualDirectory
Error: The task was not able to connect to IIS on the server xxxx. Ensure that the server exists and is reachable from this computer: The RPC server is unavailable.

Thanks
dross333Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

adiloadiloCommented:
is exchane 2007 running on a windows 2008  ? if so which version ?
0
dross333Author Commented:
We are running Windows 2008 SP 2 on all servers.
0
adiloadiloCommented:
make sure that the network type on all servers is private . also enable folder and printer sharing on the servers .
0
dross333Author Commented:
Thanks for the suggestions.  I found the problem though.  During the installation of client access role, it would fail indicating that certain virtual directories could not be created because they already existed, even though I could not find them in IIS.  So I would just manually create these directories.  I could be wrong here, but there was more to the failure then just the virtual directories and certain windows firewall rules were not created as well.  To resolve this, I removed the virtual directories using the IIS Metabase Explorer tool.  Once I removed them from here, I was able to correctly install the client access role and all correct Windows firewall rules are now present.

Thank You
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.