Configuring Internet for the DC with DHCP

65 pts.
Tags:
DHCP
Domain Controller
Network connectivity
Routers
ok, im a semi newb when it comes to domain controllers and networks. since we dont have an IT person on staff full time, i have to fill that role. we moved locations and i brought over all the computer equipment (server, switches, etc) and reinstalled them exactly how we had them at the other office. this is how the network was setup. modem/router----firewall----switch----domain controller all the workstations are connected to the switch. so how do i get internet to all the workstations and domain controller? it was working fine at our old location. the main thing that needs to be configured is a new router since our new isp's modem is not a router/modem. ive been doing searches all over google. here is a possible solution that i found while researching... the new router should broadcast an IP such as 10.0.0.1. then the router section in the DHCP setup on the DC should be set to 10.0.0.1 ...? is that a start? please help :P thanks

Answer Wiki

Thanks. We'll let you know when a new response is added.

You will want to setup the network kind of like this.

<pre>Router 10.0.0.1
Server 10.0.0.2

DHCP Range 10.0.0.50-10.0.0.200
Subnet Mask 255.255.255.0
Default Gateway 10.0.0.1
DNS Server 10.0.0.2</pre>

Do not setup a backup DNS Server.

Discuss This Question: 13  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Joshik
    so ... Router 10.0.0.1 - so i need to change the router (linksys router) to an IP address of 10.0.0.1? Server - server already has an address of 10.0.0.100 DHCP range is currently at: 10.0.0.30 - 10.0.0.200 subnet mask - where do i set this? in the actual NIC tcp/ip properties? Defautl Gateway - is this setup in the actual NIC tcp/ip properties? DNS Server - is this setup in the actual NIC tcp/ip propertie? what about the DNS Server setting in the DHCP configuration screen? do i put the ip of the server? thanks! j
    65 pointsBadges:
    report
  • CosmoC
    Since your network setting were working fine at your old location (on Server and Workstations), setting the LAN IP of the new router to match the previous settings makes the most sense. This way you don't have to change any of your internal networking DHCP settings (unless you have to for other reasons). For example, if your previous (old) location router IP was 10.0.0.1, setting the new Linksys router IP to 10.0.0.1 will make everthing work (assuming the WAN IP on the router was setup properly). The router LAN IP is your networks gateway address (for all devices which will have Internet access). In the NIC TCP/IP properties on the Server: IP = 10.0.0.100 Subnet = 255.255.255.0 Gateway = 10.0.0.1 Preferred DNS = 127.0.0.1 [if local DNS runs from another Server, use that IP] Alt DNS = [leave blank] You didn't mention what model the new Linksys router is, but it probably has a DHCP server built in, you will NEED to disable it. You can only have one DHCP server running on your network (subnet). It's also a good idea to exclude the Server IP (10.0.0.100) from the DHCP range, along with any other static IP's (Printers, WAP's, Network Scanners, etc.). If you need to change DHCP settings, you will do it from the Server. In your DHCP Scope Options, "003 - Router" is the gateway your workstations will use (for example 10.0.0.1). "006 - DNS Servers" is the IP your workstations will use for DNS lookups (for example 10.0.0.100). Just to clairify... Q: Router 10.0.0.1 - so i need to change the router (linksys router) to an IP address of 10.0.0.1? A: Yes, if that's what your old router was using. Q: Server - server already has an address of 10.0.0.100 A: It's fine to use that IP. Most of us pick a lower number so it's not included in the DHCP Scope Q: DHCP range is currently at: 10.0.0.30 - 10.0.0.200 A: That's fine. if you don't have a lot of devices connecting, you can lower that range a bit. Q: subnet mask - where do i set this? in the actual NIC tcp/ip properties? A: On the Server, YES. The Workstations will get it from your DHCP settings. Q: Defautl Gateway - is this setup in the actual NIC tcp/ip properties? A: On the Server, YES. The Workstations will get it from your DHCP settings. Q: DNS Server - is this setup in the actual NIC tcp/ip propertie? A: On the Server, YES. The Workstations will get it from your DHCP settings. Q: What about the DNS Server setting in the DHCP configuration screen? do i put the ip of the server? A: Yes, you would use the Server IP 10.0.0.100, assuming that DNS is actually running on it. Hope that helps. :-)
    280 pointsBadges:
    report
  • Joshik
    thanks COSMOC. that is a GREAT help! i will test it out tomorow morning before work begins. thanks for the detailed instructions. just to clarify for the DHCP settings on the server: 006 DNS SERVER: it currently has the 10.0.0.100 (servier ip address) in there but it also has 64.60.0.18 & 64.60.0.17. what would those have been for? i remember when i would setup a workstation with a static ip address i would have to enter the 64.60.0.17&18 dns address. thanks again for all your help!!!
    65 pointsBadges:
    report
  • Dwiebesick
    Your DHCP should only give your DNS server's IP address. Your DNS server should then use forwarders to forward any request for internet to some public DNS ( i suggest using OpenDns.com you can do many restrictions there). YOU do not want your workstations/servers using a public DNS IP as the PUBLIC DNS cannot resolve request for intranet resources such as domain controllers, global catalog etc. So on you DHCP 006 DNS the only listing should be your DNS server and you should remove the 64.60.0.18 & 64.60.0.17 good luck dmw
    2,235 pointsBadges:
    report
  • Joshik
    Thanks Dwiebesick i setup everything and everything seems to be working great. EXCEPT the actual server cannot access the internet. would this be because the TCP/IP config in the server NIC is incorrect? This is what is in the Server NIC: IP info: 10.0.0.100 255.255.255.0 10.0.0.1 dns: 10.0.0.10 blank about opendns. i like this service. im trying to implement it. i registered a free account. so basically i need to configure my DNS server fowarders to OPENDNS dns numbers which they provide. then i need to setup a network in the network setup section and have it approved by opendns then i just customize my settings? thanks everyone!
    65 pointsBadges:
    report
  • Dwiebesick
    You server's DNS settings should point to your DNS server. If you only have one server then it should point to itself. That way when the server request a page from the internet, it will sent the request to itself, and since it does not own that name space, it will send the request to its configured forwarder DNS setting. So, if your replay is not a type, I suspect the DNS setting should read 10.0.0.100 and not a dot 10. best of luck dwiebesick
    2,235 pointsBadges:
    report
  • CosmoC
    In your last response you listed "10.0.0.10" as your Server DNS address. Is that a typo? It should be either "127.0.0.1" or "10.0.0.100". Don't use both... pick one as the primary DNS IP and leave the Alt DNS blank. That should fix it. :-)
    280 pointsBadges:
    report
  • Joshik
    yeh, that was a typo. it is 10.0.0.100 (pointing to itself.) server still cant access the web. :P in the DHCP settings under 006 DNS SERVERS i had 10.0.0.100 and nothing else in it but certain workstations were losing internet connection. (o btw, the workstaiions are not connected to the domain yet. they are just connected to the switch as workstations with different workgroups.) so i put back in the DNS from the ISP and the 10.0.0.100 and everyone seems to be able to get online ok again.
    65 pointsBadges:
    report
  • Joshik
    oh also, the internet goes down every nite. it seems that the router bugs out. i cant access the router so i have to power cycle the router and everything is ok again. it is a linksys WRT160N which acts as the router and wireless accesspoint. i was planning on buying a router dedicated to route the internet to the server and have the WRT160N dedicated as a wireless accesspoint. any ideas on what would cause this?
    65 pointsBadges:
    report
  • Dwiebesick
    It appears that your DNS settings on your server are incorrect. Here is a link to troubleshooting from Microsoft http://tinyurl.com/2puwfk short for[http://technet2.microsoft.com/windowsserver/en/library/e42d510a-443d-4c31-96da-f66a67a89d861033.mspx?mfr=true] Are you getting any error messages in the event logs that give clues to your DNS problems? Do you know how to go to the Forwarders tab on your DNS server? [Start | Run | dnsmgmt.msc] If so, check that you have this entry in the box labeled DNS Domain: All other DNS domains There is a place to add the IP addresses for public DNS. [To add a forwarder, select a DNS domain, type the forwarder’s IP address below, and then click Add.] You can use either your ISP’s DNS settings or OpenDNS which is 208.67.222.222 and 208.67.220.220 I also would check the box Do not use recursion for this domain. Remember to flush you DNS cache with ipconfig /flushdns and then ipconfig /registerdns to see if that helps. Let us know if you have more questions dmw
    2,235 pointsBadges:
    report
  • CosmoC
      Did the Server have Internet access before the move? Are you able to view external websites (from the Server) via IP address? Do you have multiple IP's assigned to the Server NIC? Try entering 127.0.0.1 as the Server NIC DNS. Does it work after (ipconfig /flushdns)?
    If your workstations started working after you added an external DNS server address from your ISP, then your DNS Forwarders are not setup properly (as Dwiebesick mentioned). You probably have your DNS setup as a root server. Go into your Forward Lookup Zone and remove the "." zone (if it's there). Restart the DNS Service and let us know if it works. :-)
    280 pointsBadges:
    report
  • Joshik
    man, this site is the bomb and so are the contributers (you). i really appreciate everything you've helped me with. im a quick study and never got into this aspect of networking. Dwiebesick, the "all other dns domains" was in there but no public dns was there so i added the ISP dns for now until i get the opendns.com configured. so now, i should be able to take out the ISP DNS from the DHCP: 006 DNS SERVER section right? i did everything else you mentioned and now the server has web access. :) CosmoC, yeh the server had webaccess before. No, there is only one IP assigned to the server nic. i flushed and registered the dns and it seems to be working now. again, you guys are a great help! now i have to begin configuring active directory. im going to buy the active directory for dummies book. haha. im sure i'll post more too when i start that. for now, i think everything will be ok. i just want to implement the opendns.com soon.
    65 pointsBadges:
    report
  • Joshik
    [...] for dummies, 2nd edition « aku cinta kamu ... Free download: windows server 2008 for dummies Configuring internet for the dc with dhcp Buku-buku seri for dummy, huruf awal a - kaskus - the largest ... Free download: windows server [...]
    0 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following