0

Our office has around 250 users and DHCP server (192.168.1.1 /24) and primary DNS server(192.168.1.2 /24) installed at office. I just configured linksys Wireless router(192.168.2.1 /24) for mobile phone users. But nowadays i realize that some PC and laptop users gets the ip address from wireless router and ip conflict/bad address shown on DHCP server so the user need to restart pc in order to get ip from DHCP server. How do i solve this issue? Thanks.

  • As far as I understand, you do not need to access 192.168.2.0 network from 192.168.1.0 network as there are only mobile phones there. So, you can just remove routing from first network gateway. – Hardoman Dec 15 '15 at 13:10
  • Mobile users need to access local FTP server and work related servers. Please correct me if I am wrong with the setup, Wifi router's WAN Port is connected to office network switch? – Vic Dec 15 '15 at 13:25
0

Sounds like you have one of the LAN ports on the wireless router connected to the 192.168.1.1 network. I would disable the DHCP server on the wireless router, and if you have the option to set a DHCP relay on the wifi router configure it to point at the DHCP server on the 192.168.1.1 network. If you need more IP addresses, configure the 192.168.1.1 network to use a /23 (255.255.254.0) subnet which will give you a total of 510 usable ip addresses ranging from 192.168.0.1 to 192.168.1.254.

The other option would be depending on if you needed to segment the network traffic so wireless users were not able to communicate with the desktops and other hard wired machines on the first network. If that is the case, edit your question and say a requirement is to have wireless and wired connections to not be able to communicate.

I think it would be unwise if I did not mention the fact that if you change subnets on any network, you should do this after business hours when you will affect the smallest number of people at your workplace and also so you don't end up looking like an idiot when suddenly the network stops working. I would suggest turning off any and all computers that are easily accessible in your environment and are non essential. I would provide static DHCP leases (or manually entered static ip addresses) for all servers, networked storage devices, network UPS. This will vary depending on your environment and the type of gear you have in it. Some smaller companies are fine with managing a few static IP address updates, but other environments where you have 1000 devices across several racks I would be looking into static DHCP leases for any device that needs to be reachable at some IP address. After you shut down all of the computers, make the changes to the DHCP scope and subnet mask on whatever device is handing out DHCP to your LAN. Afterwards just start with one computer. Turn the machine on, boot up into whatever OS and make sure that the first machine is getting the new subnet mask info and is being assigned a IP address within the expected range. Check both LAN gateway connectivity and your connection to the outside world via ping and/or going to google and searching for some term you know won't be cached in the browser to be sure you have full connectivity. If all is good, start bringing up machines, 5 at a time and check that they also have full LAN gateway and internet connectivity. If all is good, power up the rest of the machines, but you can probably get away with just testing a few vital machines (CEOs and VPs are not going to be happy if they come in and can't connect to the network because you didn't test to ensure their connection was working as expected).

  • Good idea. I will change network to /23 on watchguard firewall so i can use 192.168.0.0 /23 for mobile users and 192.168.1.0 /23 for pc/laptop users. And i will disable DHCP on wireless router. Do i need to create a new DHCP scope for mobile users because currently using 192.168.1.10 to 192.168.1.250 ? Mobile phone users still need to access office first network and some worksite servers sitting at 192.168.1.0 /23. – Vic Dec 15 '15 at 13:35
  • That's up to you. I am not too familiar with watch guard products so I don't know if you can specify network zones (LAN, WAN, WLAN) and then specify DHCP scopes for each. If that is an option, then do it. And yes your wifi routers wan port should be connected to the switch or directly into an interface on your primary router even. As long as you turn off DHCP server on your wireless router, turn on DHCP relay on your wireless router, point it to the 192.168.1.1 DHCP server. – Richie086 Dec 15 '15 at 16:25
  • And real quick since you are new here, if someone properly answers a question that you ask, you should mark it as being the correct answer so that if someone comes to this forum with a similar issue they can see what worked for someone previously. There should be a check mark next to my answer that you need to check in order for that to work. Thanks – Richie086 Dec 15 '15 at 16:27
  • Vic, did my solution work for you? Did you encounter any issues? Welcome to super user btw! – Richie086 Dec 16 '15 at 2:16

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.