• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1164
  • Last Modified:

Separate Wi-Fi clients from the domain DHCP server allocation?

My client (a small college) has a Windows SBS server running dns, dhcp, etc. There are approx. 50 desktops used by college staff and students.

Additionally, students are allowed to connect to the college's Wi-Fi using their iPhones, iPads, etc. in order to browse the internet.

There is a Netgear DSL modem, a Sonicwall Firewall and 5 CISCO wireless access points throughout the building.

Windows SBS DHCP server is configured to allocate IP Addresses from 192.168.0.50 - 192.168.0.200. Everything else is reserved for printers, ip phones and networking equipment above.

The problem I have is that students using Wi-Fi from their phones/tablets, get allocated an IP Address by the DHCP server and soon after the DHCP server runs out of IP addresses to allocate.

These Wi-Fi clients dont need access to the college's network. They only need internet access.

How can I resolve this issue?
0
cgruber
Asked:
cgruber
  • 5
  • 3
  • 2
  • +1
1 Solution
 
edster9999Commented:
You could
1.
expand the network to allow more IPs in the same range.
so instead of 192.168.0.1 - 192.168.0.255
you could use 192.168.0.1 - 192.168.1.255
Giving 510 usable address instead of 253.

You do this by changing the subnetwork to 255.255.254.0 (instead of 255.255.255.0)

or 2.
You could have two subnets.  So you keep 192.168.0.X for what you have today
and then put 192.168.1.X just for wireless.
Both networks would have the 255.255.255.0 subnet
and the router / dhcp would have to be setup to route and assign the addresses.
0
 
amclaughlin01Commented:
Does anyone connect through the wireless that would have the need to connect to the college's network?

Is there a controller in play or are these APs standalone devices?  Usually, there is is a setting to allow for guest connections through the APs that would be on their own IP addresses and only have access to the Internet not the internal network.

Other option would be to setup a second IP address subnet with it's own DHCP pool of addresses that could be used just for the wireless network.  This would entail creating a separate VLAN and assigning the ports on the switches that the APs are patched into.  Then when a DHCP request from the wireless came through, it would recognize that it was coming through on the VLAN and assign an appropriate IP address.

What make/model are your switches?  Are they Cisco also?

If they are Cisco, here is some information on configuring VLANs on them:

http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/configuration/guide/cli/VLANs.html
0
 
Mandeep KhalsaCommented:
To separate your WiFi with your physical network you should use Sonicwall. Configure a port say X4 on the Sonicwall to be part of the WLAN zone and turn on the DHCP Server for that zone. Connect all your Cisco AP's to that port (X4) using a switch. Then update your firewall rules to deny traffic flow from WLAN to LAN.
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
cgruberAuthor Commented:
Yes, some wi-fi clients (such as staff with laptops) will still need access to the college's network.

switches arent cisco.

I dont want to expand the current network to allow more Ips, I want to keep the hotspot users away form the network.
0
 
cgruberAuthor Commented:
KhalsaComputer - That sounds interesting. I will try that on the Sonicwall with just one WAP and see if it works
0
 
Mandeep KhalsaCommented:
Just so you know doing it with the Sonicwall will stop your staff members with laptops from accessing the network unless you put in specific firewall rules.
0
 
cgruberAuthor Commented:
I could simply setup a separate WAP in the staff office which would bypass the Sonicwall and have its own SSID and passcode !?
0
 
Mandeep KhalsaCommented:
Yes a separate WAP that is placed on your LAN will continue to give you the same results that you are achieving currently, the only difference being the SSID and password will be restricted to staff only.
0
 
amclaughlin01Commented:
I am not absolutely positive on the Sonicwall, but most WAPs will allow for multiple SSIDs.

You might be able to configure all your Sonicwalls with one SSID for staff and another SSID for guests, which would eliminate having to add additional WAPs
0
 
Mandeep KhalsaCommented:
From my understanding the newer models of Sonicwall are capable of having multiple SSID's however in this case, if we are going to block the whole WLAN zone from accessing the network multiple SSID's will accomplish nothing.
0
 
Mandeep KhalsaCommented:
Just remembered that Sonicwall by default only allows SonicPoints to pass traffic on the WLAN so you will have to do one more step for this to work. Go to Network -> Zone -> WLAN and under wireless tab, uncheck the box for "sonicpoints" only (should be at the bottom).
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 5
  • 3
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now