Re: DNS/Active directory
- From: "Miha Pihler [MVP]" <mihap-news@xxxxxxxxxxx>
- Date: Tue, 22 Nov 2005 18:11:54 +0100
It is not a smart idea to have Active Directory in DMZ at all (if it needs
to talk to DC in LAN).
Personally I would consider putting Terminal Service in LAN as member of
domain and then open the ports from internet to LAN to allow users to get
access to TS. In this case you could consider use of two factor
authentication for logging on to TS (e.g. smart cards)...
--
Mike
Microsoft MVP - Windows Security
"tshad" <tfs@xxxxxxxxxxxxxx> wrote in message
news:uioGOvl7FHA.1032@xxxxxxxxxxxxxxxxxxxxxxx
>
> "tshad" <tfs@xxxxxxxxxxxxxx> wrote in message
> news:OHoSnCE7FHA.3752@xxxxxxxxxxxxxxxxxxxxxxx
>>
>> "Miha Pihler [MVP]" <mihap-news@xxxxxxxxxxx> wrote in message
>> news:uHbGFB86FHA.3172@xxxxxxxxxxxxxxxxxxxxxxx
>> > Hi,
>> >
>> > Server that is member of domain will need quite a few ports opened to
> talk
>> > to domain controller on the other side of firewall.
>> >
>> > Here is a short list protocols used...
>> >
>> > RPC endpoint mapper 135/tcp, 135/udp
>> > Network basic input/output system (NetBIOS) name service 137/tcp,
> 137/udp
>> > NetBIOS datagram service 138/udp
>> > NetBIOS session service 139/tcp
>> > RPC dynamic assignment 1024-65535/tcp
>> > Server message block (SMB) over IP (Microsoft-DS) 445/tcp, 445/udp
>> > Lightweight Directory Access Protocol (LDAP) 389/tcp
>> > LDAP over SSL 636/tcp
>> > Global catalog LDAP 3268/tcp
>> > Global catalog LDAP over SSL 3269/tcp
>> > Kerberos 88/tcp, 88/udp
>> > Domain Name Service (DNS) 53/tcp1, 53/udp
>> > Windows Internet Naming Service (WINS) resolution (if required)
> 1512/tcp,
>> > 1512/udp
>> > WINS replication (if required) 42/tcp, 42/udp
>> > and ICMP protocol.
>> >
>> > Service overview and network port requirements for the Windows Server
>> system
>> >
>>
> http://support.microsoft.com/default.aspx?scid=kb;en-us;832017&Product=winsvr2003
>> >
>> > Note: by placing server that is member of domain in DMZ you are not
> doing
>> > much for protecting your LAN where your domain controller is... If for
>> some
>> > reason I can gain access to your server in DMZ I have full access to
> your
>> > LAN...
>> >
>> I agree.
>>
>> This is why we are trying to get around that by not making it part of the
>> domain.
>>
>> This machine is going to have Terminal Server on it running one
> application.
>> The only port we are going to have open is the one to Sql Server with no
> Sql
>> Tools on it. And the user will only get access to the program we are
>> running with NO desktop.
>>
>> The problem we face is trying to set up groups that we can set different
>> policies on. We need one group to have NO desktop and another that will
>> have limited desktop and admin that will have full desktop. But we can't
>> find a way to do that without setting up Active Directory on the machine
>> which will need to have access to the Domain Controller.
>>
>
> I am looking at setting up Active Directory in the DMZ with just one
> server
> (the Terminal Server) - but I was told this was not a good idea - to have
> a
> TS as a DC. But that would mean getting a Computer to just be a DC -
> which
> is a little bit of overkill, I would think
>
> Tom
>> Thanks,
>>
>> Tom
>>
>>
>> > --
>> > Mike
>> > Microsoft MVP - Windows Security
>> >
>> > "tshad" <tscheiderich@xxxxxxxxxxxxxxx> wrote in message
>> > news:%23VM08366FHA.4012@xxxxxxxxxxxxxxxxxxxxxxx
>> > >I have a Server that is in a DMZ and is not pointing at the Active
>> > >Directory.
>> > >
>> > > To access Active Directory for Domain User authentication, I need to
>> open
>> > > a port on my firewall.
>> > >
>> > > Would this be the same port as DNS (53) or Does Active Directory use
>> > > a
>> > > different port?
>> > >
>> > > Thanks,
>> > >
>> > > Tom
>> > >
>> >
>> >
>>
>>
>
>
.
- References:
- DNS/Active directory
- From: tshad
- Re: DNS/Active directory
- From: Miha Pihler [MVP]
- Re: DNS/Active directory
- From: tshad
- Re: DNS/Active directory
- From: tshad
- DNS/Active directory
- Prev by Date: Mass storage driver for Server 2003 and Dell XPS 200
- Next by Date: Re: 2nd CPU not viewable/usable
- Previous by thread: Re: DNS/Active directory
- Next by thread: Re: Dirty shutdowns
- Index(es):
Relevant Pages
|