Share internet on a network using Server's DC+DHCP with wireless router, possible?

[edu_infra]

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]

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]

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]

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]

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]

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]

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]

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]

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]

@Michael - how come the forwarders are set to

 

200.204.0.10

200.204.0.138

 

Also where are these pointing to ?

[Michael]

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]

@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]

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]

That's odd. I would compare configurations on both NICs (on your server). There has to be an issue somewhere in this area.