NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
EX6200 Acting as a DNS server
Purchased a EX6200, upgraded to latest firmware. Connected to a business network and configured as an access point. Issue I am having is that two PC's on the business network which is on a 160.0.1.x range suddenly lost internet connection. When an ipconfig check the DNS setting was 192.168.1.250 which is the default IP address of the EX6200. Normally the DNS server is 160.0.1.7. Obviously the ex6200 is acting as a DNS server and communicing with devices on the network telling them so. Is this a design feature? or a serious bug in the device firmware. In essence any PC on the network that does not have a hard set DNS setting will lost internet connectivity if this device is connected to a business/home network.
10 Replies
Did you configure your EX6200 to use a static IP address? If so, you should have assigned an address in the 160.0.1.x range to the EX6200 and set the DNS server to 160.0.1.7.
If the EX6200 is configured to get its IP address dynamically, then it still should have picked up an address in the 160.0.1.x range from the DHCP server. By no means should it be using 192.168.1.250 in your business network.
Precisely what I am saying. It should NOT be acting as a DNS server, but it most certainly is.
Chicken/egg. To set the unit up as access point you need to connect to your network so it can find the router otherwise cannot setup. Do this and any PC that does not have a fixed DNS in network settings potentially will get 192.168.1.250 set as its DNS. So you need to connect to your network and then go as quick;y as possible to fix the IP settings for the unit before it knocks out every PC that does not have a fixed DNS.
Bear in mind that the two PC's affected had been on all day with internet access, plugged in the ex6200 and the PC's lost internet connection, yellow exclamation mark and ipconfig showed 192.168.1.250 as DNS. I have seen units affected on reboot but not while booted up.
Units going back.
I don't think see the chicken and egg situation. When you first set it up, it should have connected to the existing network and created two new Wi-Fi SSIDs by concatenating _2GEXT and _5GEXT to the existing SSID. At this point, there's no way any other PC would have connected to the EX6200 since the new SSIDs were different. When the EX6200 connected to the router, it should have picked up a new IP address in the 160.0.1.X subnet as well as the proper DNS server address, 160.0.1.7. You could have confirmed this by connecting a PC to the EX6200 and checked the DNS server address. It it was still wrong, you could have changed it in the EX6200 settings.
From that point onwards, any PC that connected to the new SSIDs should have picked up the correct DNS server.
Anyway, if you haven't already sent the unit back, give it another try.
