Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
Hi there,
There is an issue with role permissions that is being worked on at the moment.
If you are having trouble with access or permissions on regional forums please post here to get access: https://www.boards.ie/discussion/2058365403/you-do-not-have-permission-for-that#latest

ipad 2 wifi issue

  • 08-09-2011 12:53pm
    #1
    Closed Accounts Posts: 17,661 ✭✭✭✭


    hi guys,

    i bought the missus an ipad 2 there last week and it's been having a few issues. just wanted to run it by some of the heads on here to see if it was something i can do something about or if we should bring it back to the store

    basically, it seems to have a lot of trouble with the wifi side of things. when we turn it on, itll initially connect to our wifi network with a 169.x.x.x address. we're on a 192.168.1.x pool, so that's not ideal. putting in a static ip address of 192.168.1.x works fine initially, and everything is ticketyboo

    however, it sporadically drops the connection and needs to have the lease renewed continually for it to regain connectivity. obviously this is a pain in the arse. ive assigned it a static ip address via our router, which is 192.168.1.84, but that hasn't made any difference at all. it still drops regularly

    it's not a network problem, since we've got a desktop, 3 laptops, a mac, 2 iphones, an android phone, 3 xbox 360s, 1 ps3, 1 psp, 1 ds, and a skype phone that never suffer from drops

    to my eye it would appear to be a hardware problem, but im not too well up on ipads, so im wondering if this is a common issue that can be resolved by myself, of if you recommend bringing it back and getting a new device?

    cheers


Comments

  • Registered Users, Registered Users 2 Posts: 4,147 ✭✭✭CathalDublin


    2 things you should try before going back to the shop

    1.Hold in the home and Power button for 30seconds till the device reboots.
    2.Goto settings - General - Reset - Reset Network Settings.

    You'd be surprised the number of problems the 2 above things can solve


  • Closed Accounts Posts: 17,661 ✭✭✭✭Helix


    i did try the network settings reset, but i wasnt aware of the home button trick. cheers, will definitely give this a go and see if it improves anything


  • Registered Users, Registered Users 2 Posts: 230 ✭✭collier


    Helix wrote: »
    i did try the network settings reset, but i wasnt aware of the home button trick. cheers, will definitely give this a go and see if it improves anything

    If this fails try update the iOS or restore it should be a last resort though but do update frequently.


  • Posts: 0 [Deleted User]


    Helix wrote: »
    when we turn it on, itll initially connect to our wifi network with a 169.x.x.x address. we're on a 192.168.1.x pool, so that's not ideal. putting in a static ip address of 192.168.1.x works fine initially, and everything is ticketyboo


    I would start looking at your router. Is there an adequate DHCP range to support your devices.

    The 169.xxx.xxx.xxx tells us that the next device upstream isn't providing a DHCP response.

    I'm not familiar with IOS, I'm typing this on a macbook pro, I know you can release a DHCP in OSX by going to > Network Preferences > Advanced > TCP/IP, maybe there is a similar approach in IOS.


  • Registered Users, Registered Users 2 Posts: 25,622 ✭✭✭✭coylemj


    2.Goto settings - General - Reset - Reset Network Settings.

    You'd be surprised the number of problems the 2 above things can solve

    And some people would be equally surprised that doing a network reset loses all your stored Wi-Fi passwords.

    Please post a health warning when dishing out this type of advice.


  • Advertisement
  • Registered Users, Registered Users 2 Posts: 4,147 ✭✭✭CathalDublin


    coylemj wrote: »
    And some people would be equally surprised that doing a network reset loses all your stored Wi-Fi passwords.

    Please post a health warning when dishing out this type of advice.
    LOL thought that was kinda obvious by the name 'reset - reset network settings'
    sorry


  • Registered Users, Registered Users 2 Posts: 230 ✭✭collier


    coylemj wrote: »
    And some people would be equally surprised that doing a network reset loses all your stored Wi-Fi passwords.

    Please post a health warning when dishing out this type of advice.

    A better solution is to go to general settings -> wi fi, click on your connection then click forget this network and re-add.


  • Closed Accounts Posts: 17,661 ✭✭✭✭Helix


    NoDrama wrote: »
    I would start looking at your router. Is there an adequate DHCP range to support your devices.

    The 169.xxx.xxx.xxx tells us that the next device upstream isn't providing a DHCP response.

    I'm not familiar with IOS, I'm typing this on a macbook pro, I know you can release a DHCP in OSX by going to > Network Preferences > Advanced > TCP/IP, maybe there is a similar approach in IOS.


    yeah theres a 100 address dhcp range, ive got everything assigned static ip addresses though, so dhcp shouldnt come into it. im concerned with the fact that the ipad, once connected, frequently loses the network and then dhcps to a 169 address rather than doing what it's told and taking the preassigned static ip address


  • Posts: 0 [Deleted User]


    Helix wrote: »
    yeah theres a 100 address dhcp range, ive got everything assigned static ip addresses though, so dhcp shouldnt come into it. im concerned with the fact that the ipad, once connected, frequently loses the network and then dhcps to a 169 address rather than doing what it's told and taking the preassigned static ip address

    Are you given the static address outside of the DHCP range?


  • Closed Accounts Posts: 17,661 ✭✭✭✭Helix


    nope, its within it

    dhcp range is 192.168.1.50 to 192.168.1.150 iirc

    i read something about creating a subnet using my imac, which would then serve dhcp to devices. im not sure how to go about this though, is it straighforward?


  • Advertisement
  • Posts: 0 [Deleted User]


    I would put a static address outside the DHCP range.


  • Closed Accounts Posts: 17,661 ✭✭✭✭Helix


    Does that make much of a difference? Ill give it a go and let you know if it works. Cheers!


  • Closed Accounts Posts: 17,661 ✭✭✭✭Helix


    had no issues so far after trying the reset


  • Registered Users, Registered Users 2 Posts: 5,213 ✭✭✭culabula


    Helix wrote: »
    hi guys,

    i bought the missus an ipad 2 there last week and it's been having a few issues. just wanted to run it by some of the heads on here to see if it was something i can do something about or if we should bring it back to the store

    basically, it seems to have a lot of trouble with the wifi side of things. when we turn it on, itll initially connect to our wifi network with a 169.x.x.x address. we're on a 192.168.1.x pool, so that's not ideal. putting in a static ip address of 192.168.1.x works fine initially, and everything is ticketyboo

    however, it sporadically drops the connection and needs to have the lease renewed continually for it to regain connectivity. obviously this is a pain in the arse. ive assigned it a static ip address via our router, which is 192.168.1.84, but that hasn't made any difference at all. it still drops regularly

    it's not a network problem, since we've got a desktop, 3 laptops, a mac, 2 iphones, an android phone, 3 xbox 360s, 1 ps3, 1 psp, 1 ds, and a skype phone that never suffer from drops

    to my eye it would appear to be a hardware problem, but im not too well up on ipads, so im wondering if this is a common issue that can be resolved by myself, of if you recommend bringing it back and getting a new device?

    cheers

    A 169 address is a self-assigned IP and is a frequent problem where multiple peripherals/multiple iOS devices are all adding to the router's workload, especially when the latter are frequently leaving/returning to the premises.

    Instead of rebooting the iPad, it is much better to reboot the router, then add each peripheral back onto the net, one by one.

    In addition, I have found that this is often caused by the type of passkey. It is best that WPA/WPA2 is used. That cured this issue permanently for me.


  • Closed Accounts Posts: 17,661 ✭✭✭✭Helix


    im on wpa/wpa2 at the minute

    might reboot and add everything one by one again though if its likely to improve things, but i havent had an issue since i reset the ipad so finger crossed


  • Registered Users, Registered Users 2 Posts: 8,034 ✭✭✭mad muffin


    culabula wrote: »
    A 169 address is a self-assigned IP and is a frequent problem where multiple peripherals/multiple iOS devices are all adding to the router's workload, especially when the latter are frequently leaving/returning to the premises.

    Instead of rebooting the iPad, it is much better to reboot the router, then add each peripheral back onto the net, one by one.

    In addition, I have found that this is often caused by the type of passkey. It is best that WPA/WPA2 is used. That cured this issue permanently for me.

    Was going to suggest this as it worked for me.

    Helix, do you have an iPhone 4 in the house? I have various wifi enabled devices plus the iPhone 4 and the 3G. Everything was fine until I got the iPad 2.

    The iPhone 4 would lose wifi and the iPad 2 would lose it or just be extremely slow. Every other device was fine, including the 3G.

    Turned off all wifi, reset the router, then turned on wifi on my iPad 2 first then iPhone 4 and so on.

    Has been fine ever since. Unless I reset the router, then I have to go through it again.


  • Closed Accounts Posts: 17,661 ✭✭✭✭Helix


    i have indeed got an iphone 4, it had a bit of an issue a few weeks ago, but i was having network issues anyway and decided to reinstall the firmware on my router which fixed that right up. ill do a controlled reboot and get everything back online in a predetermined order later tonight though

    cheers lads!


Advertisement