|
Home > Archive > Windows 2000 track general > January 2003 > SOHO domain??
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| Tech Ranger 2003-01-04, 9:39 pm |
| I have been building a small network for a friend. He has 3 PCs. The PCs are connected to Earthlink via a DSL hookup. We can either use WinPoet software running on each PC to connect to the ISP or we can go through a router. The DSL router has PPPOE built in, and can, therefore, authenticate to the ISP. I would like to install Active Directory, but I know that AD depends on DNS. Since Earthlink provides DHCP and DNS to the PCs, is it still possible to do a domain? I have a general notion of what I probably have to do, but I am not quite sure. | |
| chodan 2003-01-05, 12:54 pm |
| Sure its not a problem.
When you prepare for AD make sure to set up DNS as a standard primary first then do DCpromo. After the promo convert to AD integreted.
This way it will create the internet root hint file that lists the 13 dns root servers.
You can then put forwarders to the ISP dns servers in your dns config.
As for DHCP you will need only one address on the external router "depending on the router you use".
Use DHCP from the domain server enstead of the ISP or the router since you will want private addressing for your internal network.
Your outside router interface might have to be set as a DHCP client though.
Oh and set up nat on the router | |
| Patrickjb 2003-01-13, 10:16 pm |
| quote:
Originally posted by chodan
Sure its not a problem.
When you prepare for AD make sure to set up DNS as a standard primary first then do DCpromo. After the promo convert to AD integreted.
This way it will create the internet root hint file that lists the 13 dns root servers.
You can then put forwarders to the ISP dns servers in your dns config.
As for DHCP you will need only one address on the external router "depending on the router you use".
Use DHCP from the domain server enstead of the ISP or the router since you will want private addressing for your internal network.
Your outside router interface might have to be set as a DHCP client though.
Oh and set up nat on the router
I believe that the router will handle DHCP. All computers connecting to the router should be setup to receive IP address dynamically, unless you planning on having subnets. | |
| Tech Ranger 2003-01-14, 7:16 am |
| quote:
Originally posted by Patrickjb
I believe that the router will handle DHCP. All computers connecting to the router should be setup to receive IP address dynamically, unless you planning on having subnets.
Don't the DC and DNS servers need static addresses? | |
| chodan 2003-01-14, 1:47 pm |
| quote:
Originally posted by Patrickjb
I believe that the router will handle DHCP. All computers connecting to the router should be setup to receive IP address dynamically, unless you planning on having subnets.
I would use the DC for DHCP as it will make youre active directory easier to manage.
quote:
Originally posted by Tech Ranger [QUOTE][i]
Don't the DC and DNS servers need static addresses?[/B]
yes thats true. | |
| me? I dunno... 2003-01-15, 3:34 am |
| I tried this with NAT and a cable connection, if I configured for isp dhcp source, then I could surf from server, but nothing on internal network side of server. If I configured static ip on internet side of server, then I could browse the server from the lan, but no internet connectivity to isp.
I wrote down the ip address and made sure the static one was the same as had been issued by isp dhcp, and after changing back from static it still picked up the same isp issued address, but would not connect with static ip#. | |
| Patrickjb 2003-01-15, 6:08 pm |
| quote:
Originally posted by me? I dunno...
I tried this with NAT and a cable connection, if I configured for isp dhcp source, then I could surf from server, but nothing on internal network side of server. If I configured static ip on internet side of server, then I could browse the server from the lan, but no internet connectivity to isp.
I wrote down the ip address and made sure the static one was the same as had been issued by isp dhcp, and after changing back from static it still picked up the same isp issued address, but would not connect with static ip#.
If you are going to connect three computers to an ISP, there are several ways to do it.
At my house we have three computers that connect to the internet thru cable and ISP. We have one IP address that is Dynamic, which means it changes periodically. Our setup has the following:
1. One Cable modem (supplied by Cable Company)
2. One Router (Netgear, wireless-802.11B)
3. Three computers (one connects directly to the router, the other two computers have wireless receivers)
The router gets its ip address from the ISP (ex. 62.32.28.5 not the real ip address)
Our router has NAT capabilities (your router should either have NAT or PAT capabilities)
We have Nat enabled; also have DHCP on router enabled.
All three computers have Dynamic ip address enable.
The three computers and routers gateway IP addresses are:
1. Router (gateway) 192.168.0.1
2. Computer 1 connected directly to router: 192.168.0.2
3. Computer 2 Wireless: 192.168.0.3
4. Computer 3 Wireless: 192.168.0.4
The subnet mask is: 255.255.255.0 (handled by router)
The DHCP server: 192.168.0.1
The DNS server: 192.168.0.1
The Default Gateway: 192.168.0.1
Now if you want to do things a little different, say setup one computer as a Server with 2 clients, you would have to change this setup a little.
Here's how we do it where I work.
We have DSL which connects to a Router and then goes to Switches, the computers then attach to the Switches. This is how we break up out network.
Yes I know this is not the best configuration because it allows broadcasts to other networks. We have changed this just recently, but I won't go into that.
Here's one way you could setup your three computer network.
Your server connects to a Hub, Switch, or another Router which then connects to the Router which connects to the DSL modem and/or directly to ISP provider. The server would have: DHCP, DNS, AD installed.
ISP -> DSL modem and/or Router -> Hub, Switch, or Router -> Your Network (3 Computers)
The Router's external IP address would be Dynamic address given be you ISP. You would configure the private IP (internal network) address on the port connecting to the Hub, Switch or Router (ex. 192.168.1.0 with subnet mask of 255.255.255.0).
All the computers that you attach to this Hub, Switch or Router would be on the 192.168.1 network with 253 Host to use.
There are many way's to create your networks, but I think this may be one of the simplest. | |
| me? I dunno... 2003-01-21, 2:41 pm |
| Patrickjb, thanks and sorry for the delay, I was in the middle of reading another text for 70-217, forgot all about this post.
I'm trying this again, I have a domain set up with a single DC, 3 member servers, and 3 clients. The DC is multihomed but I have been thinking about what you said about the router and maybe I'll put another nic card in one of the member servers and make it a router. I guess the best way would be not to join it to the internal domain, but simply to use it for a switch? Then take another one of the member servers and configure it to be a NAT server, put it between the router and the private network DC? | |
| me? I dunno... 2003-01-21, 4:49 pm |
| Actually, I think I'll go to the 216 forum to proceed with this, thanks. |
|
|
|
|