NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
WG102 AP and iOS 6
I seem to be having DNS issues with any devices running iOS 6 when connecting to a WG102 AP. The router's (Draytek Vigor2830n) wireless works fine, however when connecting a device to the WG102 th...
I have tried searching a lot :(. This was sort of my last resort lol. Most of the results I get are from 2012 which is when the massive issue with netgear and ios6 was around that was 'supposedly' fixed with ios 6.1.
I'm pretty confident that the problem is now ios 6 + netgear + WPA or WPA2. What I don't get is why I can connect just fine, browse LAN, use direct IP address but anything that involves DNS doesn't work - yet it will at 'some point'. Its really weird. Also after a reboot of the AP it will work just fine, but as soon as I disconnect the device from the wifi and reconnect the problem is there. I tried loads of times,
1st time connecting: works fine.
2nd time connecting: works fine.
And ALWAYS
3rd time connecting: DNS issue
Beyond the 3rd time is a hit and miss, sometimes it works sometimes it doesn't. Meanwhile no encryption works 100% of the time.
Rebooting the AP wouldn't be so bad if ios devices could connect to the webpage, but they can't due to the certificates >.<
I'm pretty confident that the problem is now ios 6 + netgear + WPA or WPA2. What I don't get is why I can connect just fine, browse LAN, use direct IP address but anything that involves DNS doesn't work - yet it will at 'some point'. Its really weird. Also after a reboot of the AP it will work just fine, but as soon as I disconnect the device from the wifi and reconnect the problem is there. I tried loads of times,
1st time connecting: works fine.
2nd time connecting: works fine.
And ALWAYS
3rd time connecting: DNS issue
Beyond the 3rd time is a hit and miss, sometimes it works sometimes it doesn't. Meanwhile no encryption works 100% of the time.
Rebooting the AP wouldn't be so bad if ios devices could connect to the webpage, but they can't due to the certificates >.<