4 Replies Latest reply on Aug 24, 2012 10:34 PM by DeanGibson

    Connected, but no internet

      I just thought I would throw in my experience with the old "Connected, but no internet " issue which is still hanging around from the Nook Color era. I found that the issue in my case was that I had a not-so-common subnet mask in my DHCP settings in my router,  Once I changed it to the more standard 255.255.255.0 mask, my connection issues went away. I was able to recreate the issue many times by changing the mask back and forth. Having subnet masks other than the above listed mask is not entirely uncommon. Perhaps they should fix this limitation so that these devices will on other than the simplest of networks.

        • Re: Connected, but no internet

          I think you may have something there. Good work!

          • Re: Connected, but no internet
            THANK YOU!! I've been going berserk!
              • Re: Connected, but no internet

                Two things I've found with my Cisco router

                 

                1) If you choose one of the highest speeds from the Router (instead of using the Default setting or All Speeds setting), then it doesn't work.

                 

                2) Sometimes, you have to change the speed and that fixes the issue.

                 

                I have no idea why this would happen.

                 

                Finally, if you have a b/g/n router, the Nooks don't work if you use n.

                  • Re: Connected, but no internet
                    DeanGibson

                    5ivedom wrote:

                     

                    Finally, if you have a b/g/n router, the Nooks don't work if you use n.


                    Depends upon the router.  My Nooks (1stED/3G, Touch, Glow, and Tablet) work just fine with my Netgear b/g/n routers.  Note that the "n" wireless protocol is available on two UHF bands (2.4GHz and 5GHz), and the Nooks only use the 2.4GHz band.

                     

                    Also, they work just fine in my class B (netmask 255.255.0.0) network.

                     

                    Correct configuration of the router is essential.  For routers that provide a DHCP server, if the router internal address is not in the same subnet (as defined by the netmask) as the addresses provided to the devices by the DHCP server, then the devices don't know how to contact the router as a gateway.