Re: Active Directory server: WMI cannot be accessed
- From: "Lincoln De Kalb" <lincoln.dekalb@xxxxxxxxxx>
- Date: Wed, 9 Aug 2006 09:38:48 +1000
I'm not an Exchange expert (yet) but I think what you are looking for is a
frontend / backend solution with a RPC over HTTPS between the two. You
haven't menitoned what the actual problem is but from my readin I think this
is the solution to the Swiss Cheesed Firewall approach of RPC.
<dhemond@xxxxxxxxx> wrote in message
news:1155045583.877662.286580@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
For the first time ever, I can build a MS Exchange server without a
huge time constraint. So, I decided to solve all the issues raised by
the Microsoft Exchange Server Brest Practices Analyzer Tool. However,
I can't seem to solve this one.
The network that I run on is extremly hostle. So, I have to keep all
servers heavily locked down (firewalls.. etc). So, my AD servers have
very few ports open. All the research I have put into this point to
RPC ports on the AD servers. But, they are only referenced as just
open RPC ports. Then I find that RPC ports are random ports from
1024-65***. I cannot just open up all those ports. Also, when I find
the ports that need to be open, they have to be locked to a single IP
(the exchange server/other AD servers).
I know it's only a firewall issue, because I can turn off the firewall
on an AD server and everything works just fine. So, what do I need to
open up?
.
- Follow-Ups:
- Re: Active Directory server: WMI cannot be accessed
- From: dhemond
- Re: Active Directory server: WMI cannot be accessed
- References:
- Active Directory server: WMI cannot be accessed
- From: dhemond
- Active Directory server: WMI cannot be accessed
- Prev by Date: Re: Direct Push - Requires certificate
- Next by Date: owa issue
- Previous by thread: Active Directory server: WMI cannot be accessed
- Next by thread: Re: Active Directory server: WMI cannot be accessed
- Index(es):
Relevant Pages
|