edu_infra Posted January 17, 2014 Posted January 17, 2014 (edited) Hi guys, I would like to know if is possible to share de internet connection comming from a modem ADSL on a network using a wireless router, but using the DHCP of Windows Server 2008 that already have the DC/DNS/DHCP running instead of using the DHCP of wireless router? How could a make the setup to work internet on all machines? NOTE: I tryed to use the RRAS NAT role, but the internet keeps too slow on client machines, so, is important to use a hardware router. My environment: Thanks! Edited January 17, 2014 by edu_infra
Michael Posted January 17, 2014 Posted January 17, 2014 Yes it's really simple: Modem > Wireless Router > Network Switch Disable DHCP on your wireless router and Windows Server's DHCP will take care of the rest. Typically the IP address will be written on the base of your router. Login using the username/password provided and disable DHCP on the router. Once you've done this, you may need to change the IP address of the router itself to match that of your local network. By default it'll be a Class C, but many schools use Class A.
edu_infra Posted January 17, 2014 Author Posted January 17, 2014 Yes it's really simple: Modem > Wireless Router > Network Switch Disable DHCP on your wireless router and Windows Server's DHCP will take care of the rest. Typically the IP address will be written on the base of your router. Login using the username/password provided and disable DHCP on the router. Once you've done this, you may need to change the IP address of the router itself to match that of your local network. By default it'll be a Class C, but many schools use Class A. And where should I set on Windows Server for all internet requests to be routed to Wireless Router? Today the IP addressing is like follows: SERVER (With hosts DC/DHCP/DNS) IP: 192.168.1.1 MASK: 255.255.255.0 GTW: 192.168.1.1 DNS: 192.168.1.1 WINDOWS SERVER DHCP SCOPE OPTIONS: ROUTER: 192.168.1.1 DNS:192.168.1.1 DNS DOMAIN: company.com WIRELESS ROUTER: IP: 192.168.1.254 MASK: 255.255.255.0 The wireless router has 3 options about it internal DHCP: DISABLED, CLIENT, SERVER. Should I leave CLIENT or DISABLED?
Michael Posted January 17, 2014 Posted January 17, 2014 It should read like this: SERVER (With hosts DC/DHCP/DNS) IP: 192.168.1.1 MASK: 255.255.255.0 GTW: 192.168.1.254 DNS: 192.168.1.1 DNS: 8.8.8.8 WINDOWS SERVER DHCP SCOPE OPTIONS: ROUTER: 192.168.1.254 DNS:192.168.1.1, 8.8.8.8 DNS DOMAIN: company.com WIRELESS ROUTER: IP: 192.168.1.254 MASK: 255.255.255.0 The reason you need two DNS addresses is your own DNS server won't have all the answers. The 8.8.8.8 is an external Google DNS.
edu_infra Posted January 17, 2014 Author Posted January 17, 2014 (edited) It should read like this: SERVER (With hosts DC/DHCP/DNS) IP: 192.168.1.1 MASK: 255.255.255.0 GTW: 192.168.1.254 DNS: 192.168.1.1 DNS: 8.8.8.8 WINDOWS SERVER DHCP SCOPE OPTIONS: ROUTER: 192.168.1.254 DNS:192.168.1.1, 8.8.8.8 DNS DOMAIN: company.com WIRELESS ROUTER: IP: 192.168.1.254 MASK: 255.255.255.0 The reason you need two DNS addresses is your own DNS server won't have all the answers. The 8.8.8.8 is an external Google DNS. Michael, I noted on the Wireless Router there is a static IP on the WAN interface, and there are 2 ISP DNS there [200.204.0.10, 200.204.0.138]. I still have to put the DNS 8.8.8.8 on all machines? the wireless router shouldn't resolve the names with those DNS instead of using the google DNS? I am afraid of the traffic go crazy because will have 4 DNS servers across the network with the way that you told me: 192.168.1.1, 8.8.8.8, 200.204.0.10, 200.204.0.138. Or I am wrong? Edited January 17, 2014 by edu_infra
Michael Posted January 17, 2014 Posted January 17, 2014 (edited) OK specify settings as follows: SERVER (With hosts DC/DHCP/DNS) IP: 192.168.1.1 MASK: 255.255.255.0 GTW: 192.168.1.254 DNS: 192.168.1.1 WINDOWS SERVER DHCP SCOPE OPTIONS: ROUTER: 192.168.1.254 DNS:192.168.1.1 DNS DOMAIN: company.com WIRELESS ROUTER: IP: 192.168.1.254 MASK: 255.255.255.0 On your Windows Server, open DNS Server, right click your Servername and select Properties. Select the Forwarders tab and then enter: 200.204.0.10 200.204.0.138 8.8.8.8 Apply changes and that should be it The traffic won't go crazy. It just means requests can query 4 locations or 4 separate DNS servers to retrieve internet traffic. Edited January 17, 2014 by Michael
edu_infra Posted January 17, 2014 Author Posted January 17, 2014 Many thanks Michael, I will apply what you told me and I put a feedback here. Just for curiosity, what is the flow of the request of a client looking for i.e Google ? The computer will look to resolve the name using the 192.168.1.1 DNS, than the DNS on the server will pass to Forwarders, than for Root Hints, than the server will see the gateway 192.168.1.254, the wireless router gets the request and pass for the modem and the modem to internet? is that right?
Michael Posted January 17, 2014 Posted January 17, 2014 Google host their own DNS servers and generally speaking they're very reliable and up-to-date. When you want to visit a webpage - you're right, your workstation will query your local server first and if it doesn't know the answer, it'll query your ISP DNS servers and failing that, Google DNS.
edu_infra Posted January 20, 2014 Author Posted January 20, 2014 (edited) Michael, I made the settings like you said, but didn't work on the server that have the DC/DNS/DCHP 192.168.1.1. No internet conection on the server, but on the clients machines the internet is working good. What could be wrong on the server !? Edited January 20, 2014 by edu_infra
mac_shinobi Posted January 20, 2014 Posted January 20, 2014 @Michael - how come the forwarders are set to 200.204.0.10 200.204.0.138 Also where are these pointing to ?
Michael Posted January 21, 2014 Posted January 21, 2014 Michael, I made the settings like you said, but didn't work on the server that have the DC/DNS/DCHP 192.168.1.1. No internet conection on the server, but on the clients machines the internet is working good. What could be wrong on the server !? Good question You could try adding 200.204.0.10 and 200.204.0.138 to your server's static IP configuration and see if this makes any difference.
Michael Posted January 21, 2014 Posted January 21, 2014 @Michael - how come the forwarders are set to 200.204.0.10 200.204.0.138 Also where are these pointing to ? Those IPs are the DNS IP addresses for edu_infra's ISP.
edu_infra Posted January 22, 2014 Author Posted January 22, 2014 Good question You could try adding 200.204.0.10 and 200.204.0.138 to your server's static IP configuration and see if this makes any difference. Ok, I will make this change there and see if this works. One thing I made to avoid the problem at this moment, was turn on the second NIC and not fix an IP there, leaving the DHCP to assign and IP for that second NIC. And the internet is now working, but I won´t to leave with this way because I will use this second NIC for other purpose on a future.
Michael Posted January 22, 2014 Posted January 22, 2014 That's odd. I would compare configurations on both NICs (on your server). There has to be an issue somewhere in this area.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now