W2K Server 2b Domain behind Cable Modem?

  • Thread starter Thread starter Laura Mae
  • Start date Start date
L

Laura Mae

My question:
I want to promote my current Win2K Server
to a Domain but I have not yet conf DNS or Active
Directory because I'm not sure if I can w/o
conflicts with my ISP.

My current SetUp:
I have Broadband via my Cable company rented
cable modem.
I have a D-Link Router connected to the cable modem.
I have 5 machines connected to the router.

One of the machines is the Win2K Server that
I really want to create a Domain so I can
manage all the User's logins and their machines...
2 machines are Win98
1 machine is Win CE
1 machine is XP

Here's my dilema....
The Cable company I get my internet connection from
has DNS....ofcourse....

If I install DNS and Active Directory on my Server
do I do it as the only Domain on "My network"
(as in behind the D-Link Router is supposidly
invisable to the ISP...they just see the IP address
the Router has and what ever IP's the Router leases
is it's own Private Network and is idependant of the
ISP????)

Or do I install it as a Child Domain, a 2nd Domain,
a Tree in a Forest...
(but it wouldn't replicate with the ISP DNS servers)

My fear is that promoting it to a Domain will permantly
disable its network connection because the ISP will be
able to see that its a Domain and there will be a
perminant conflict...

Please advise if I should redirect this ? to the
Windows Server Newsgroup?

Sincerely,
Laura Mae Brown
206.235.4165
..
 
In
Laura Mae said:
My question:
I want to promote my current Win2K Server
to a Domain but I have not yet conf DNS or Active
Directory because I'm not sure if I can w/o
conflicts with my ISP.

My current SetUp:
I have Broadband via my Cable company rented
cable modem.
I have a D-Link Router connected to the cable modem.
I have 5 machines connected to the router.

One of the machines is the Win2K Server that
I really want to create a Domain so I can
manage all the User's logins and their machines...
2 machines are Win98
1 machine is Win CE
1 machine is XP

Here's my dilema....
The Cable company I get my internet connection from
has DNS....ofcourse....

If I install DNS and Active Directory on my Server
do I do it as the only Domain on "My network"
(as in behind the D-Link Router is supposidly
invisable to the ISP...they just see the IP address
the Router has and what ever IP's the Router leases
is it's own Private Network and is idependant of the
ISP????)

Or do I install it as a Child Domain, a 2nd Domain,
a Tree in a Forest...
(but it wouldn't replicate with the ISP DNS servers)

My fear is that promoting it to a Domain will permantly
disable its network connection because the ISP will be
able to see that its a Domain and there will be a
perminant conflict...

Please advise if I should redirect this ? to the
Windows Server Newsgroup?

Sincerely,
Laura Mae Brown
206.235.4165
.

Best bet is to use only your internal DNS server (which is recommended), for
all your clients, and is what AD needs anyway. If you use their DNS server
in any machines' IP properties, all kinds of things go out of whack in an AD
infrastructure, no matter how small. Don't even bother using the router as
DNS either.

Once you setup your internal DNS, change the settings on all the machines to
only use this guy. Then setup a forwarder on your DNS server to the cable
company's DNS server. This will "forward" out resolution for Internet names
for your internal machines. If not sure how to create a forwarder, check
this article out (step 3):
http://support.microsoft.com/?id=300202

Then create the zone for the AD name you chose (make sure it's in the form
of domain.com and not just "domain"). Set updates to YES. Then run DCPROMO.
Select new domain in a new tree in a new forest.

Remember, no matter what the cable company says, do not put their DNS
addresses in your machines.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Back
Top