Pretty much everything the hackers want you to open and pretty much
everything you're never supposed to open. It'd be about the equivalent of
eliminating your firewall and letting your network sit "bare" out on the
Internet. The whole point of the firewall is to prevent what you asking to
do.
The closest to a "safe way" would be to establish a VPN between the machine
in the DMZ and your Internal System. Then do this "membership" through the
VPN. However if they get into the Member Server then they can just follow
the link in through the VPN from there and you are back in the same mess.
Using an Account for the VPN with no prviledge or rights other than to
establish a "dial-up" can help some but you are still at risk, particularly
if the Member server is "logged in" at the console giving them opportunities
with the "Currently logged on user". I don't believe there is any real
"safe" way to do this.
I've done this with one Server once using VPN, but I never made it a member
of the Domain. It is used so we can FTP to the box without the FTP sending
the username/password in clear-text over a publicly exposed link.
--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
"Dave Harry" <(E-Mail Removed)> wrote in
message news:%23$(E-Mail Removed)...
> Can anyone tell me what holes I need to open in my firewall DMZ to allow a
> server to be added as a Member Server?
> TIA
>
> --
> Dave Harry
>
>