Re: Flag for public AD integrated zones

"Herb Martin" wrote:
> Your are really going at this the hard way -- and
> very insecure to be exposing a DC on the Internet.

What is hard (difficult) about it? I don't see exposing port 53 as being
insecure at all. To make any changes to the server (DC), the RPC ports must
be available. Since they are not, security is not an issue. However, I know
thousands of companies that have port 80 of their Exchange Servers exposed to
the Internet. That is a security risk and has lead to several corporate LANs
being hacked.
.

Relevant Pages

  • Re: Flag for public AD integrated zones
    ... >> very insecure to be exposing a DC on the Internet. ... I don't see exposing port 53 as being ...
    (microsoft.public.windows.server.dns)
  • Re: Internet Security Warning!
    ... If you are currently using internet, chances are that your IP address ... You can know your IP address and Port here. ... My *port* is insecure! ...
    (sci.crypt)
  • Re: Internet Security Warning!
    ... If you are currently using internet, chances are that your IP address ... You can know your IP address and Port here. ... My *port* is insecure! ...
    (sci.crypt)
  • Re: Internet Security Warning!
    ... If you are currently using internet, chances are that your IP address ... You can know your IP address and Port here. ... My *port* is insecure! ...
    (sci.crypt)
  • Re: Linux als Router
    ... # Enter all trusted network interfaces here. ... # which should be available to the internet and set FW_ROUTE to yes. ... space separated list of ports, ... # Packets to silently reject without log message. ...
    (de.comp.os.unix.linux.misc)