updated to 1.1.0 now wireless will not connect

[Starearedkid]

Unfortunately I can't connect either  

[bklvr896]

---

Starearedkid wrote:

Unfortunately I can't connect either  

---

Did PM the board moderator Alex with the information he requested?  Account details, serial number and router information like brand, model number, security settings.  Since not everyone is experiencing a problem, he asked for this information so they can see if there's any type of pattern as to the router, settings etc.

[jmf56]

Ok..I haven't been able to connect all week AFTER installing the 1.1.0 update.  

Earlier in week I tried forgetting all remembered networks, resetting nook, re-enterting my wpa key..nuthing..

Tonite, I hand reset the whole network, powered down/up.  Still nuthing..So, i then logged into my Actiontec router(Verizon FIOS router) and looked at the connections under My Network, and found the Nook's MAC address, and tried to ping it from the router.  Now heres the funny part..It now works..

Its kinda weird that the power down reset didn't fix it though..I am suspecting that after I ran the update, its almost as if it hung that DHCP client connection, and the action of my attempting to ping(connect) to it from the router freed up that TCPIP port..The router must have some sorta caching mechanism built into its firmware..

Anyways, hope this helps someone..

JFeole

[jmf56]

Also,  i used Roustabout's excellent debugging overview on page 2 of this thread to go over the possibilities of where the issue may be..

JFeole

[jmf56]

User Roustabout's earlier post is here, this is what I jus referred to :

http://bookclubs.barnesandnoble.com/t5/NOOK-General-Discussion/Wi-Fi-not-working/m-p/1198592/message...

JFeole

[roustabout]

I'm glad that starting there helped, but pinging by MAC address is a very clever addition and entirely your own.  It's one I'll put in the list for next time and if I get around to updating the blog this weekend. 

[scotta316]

It's something I'll definitely remember, since I also have the Actiontech router from Verizon (now Frontier). I've decided to wait until my NST downloads the update on its own, but that will be the first thing I try if there are problems.

I've had trouble connecting new devices to this router before, like when family members brought their laptops with them, it would usually make the connection, but the throughput was either very slow or non-existent. Usually power cycling the router fixed it.

Thanks for the tip.

[sygram]

I just manually updated to ver 1.1 and have a Verizon Actiontech router.  When the update was complete I was still connected to my home WiFi.  I updated my library and purchased another book with no issues.

I manually updated after reading this thread and seeing that others with my router had a problem.  I figured I'd update while I had some time to play with it if there were problems.

[LastSilmaril]

Bah, the problem has returned, without any warning! The N2E's MAC address does show up in the client list on my router, but is listed as 'inactive', and the Nook simply displays 'unsuccessful'. Reverting to a backup image I made yesterday (when it was working) changed absolutely nothing. Will try to adb connect through my other router later and do a logcat to a text file. In the meantime, screw it, I bought this thing to read! And that's just what I'm gonna do

[leoda]

For the record, add me to the list of users who can no longer connect to home wireless after the 1.1 "upgrade".

Verizon Fios / Actiontec M1424WR_RevF router (WEP), worked fine until I upgraded.

I tried the tricks suggested above . . .  nothing worked.

Store clerk had no idea what to do. (Connected fine in the store.)

I'll spare you my opinion on buggy, incomplete, untested software releases.

P.S. . . .  I absolutely LOVE this device as a reader.

[geertm]

---

leoda wrote:

I'll spare you my opinion on buggy, incomplete, untested software releases.

P.S. . . .  I absolutely LOVE this device as a reader.

---

As has been said before: B&N cannot test compatibility with every router in the word.

For every Wifi device (even the Kindle!) you will find complaints that people have connection problems with certain combinations of router/device.

Only a small number of users has the Wif connection problem. Otherwise we would have seen a lot more complaints.

So the problem is probably related to some very specific cause: a specific router chipset, a specific combination of settings, specific router models.There is no way for B&N to test this.

I am sure that as soon as B&N has found the cause, they will release a firmware update to fix the problem.

[LastSilmaril]

Everybody here:

There are a few people having problems with the ActionTec FiOS router, but nobody has posted their hardware revision. Mine doesn't work, and I'm using Rev. F. The revision can be easily found on the barcode on the side of your router.

It should be obvious by now that something is screwy with Dhcp (since connecting only fails once the Nook tries to obtain an IP address from the ActionTec). But in case it wasn't, here's the relevant part of my log file:

I/wpa_supplicant( 2539): CTRL-EVENT-SCAN-RESULTS Ready

I/wpa_supplicant( 2539): Trying to associate with FIOS_ROUTER_MAC_ADDRESS (SSID='MYSSID' freq=2462 MHz)

I/wpa_supplicant( 2539): CTRL-EVENT-STATE-CHANGE id=-1 state=3

V/WifiMonitor( 805): Event [Trying to associate with FIOS_ROUTER_MAC_ADDRESS (SSID='MYSSID' freq=2462 MHz)]

V/WifiMonitor( 805): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=3]

V/WifiStateTracker( 805): Changing supplicant state: DISCONNECTED ==> ASSOCIATING

D/NetworkStateTracker( 805): setDetailed state, old =DISCONNECTED and new state=CONNECTING

D/ConnectivityService( 805): ConnectivityChange for WIFI: CONNECTING/CONNECTING

I/wpa_supplicant( 2539): CTRL-EVENT-STATE-CHANGE id=2 state=4

I/wpa_supplicant( 2539): Associated with FIOS_ROUTER_MAC_ADDRESS

I/wpa_supplicant( 2539): CTRL-EVENT-STATE-CHANGE id=2 state=5

V/WifiMonitor( 805): Event [CTRL-EVENT-STATE-CHANGE id=2 state=4]

V/WifiStateTracker( 805): Changing supplicant state: ASSOCIATING ==> ASSOCIATED

D/NetworkStateTracker( 805): setDetailed state, old =CONNECTING and new state=CONNECTING

V/WifiMonitor( 805): Event [Associated with FIOS_ROUTER_MAC_ADDRESS]

V/WifiMonitor( 805): Event [CTRL-EVENT-STATE-CHANGE id=2 state=5]

I/wpa_supplicant( 2539): CTRL-EVENT-STATE-CHANGE id=2 state=5

I/wpa_supplicant( 2539): CTRL-EVENT-STATE-CHANGE id=2 state=6

I/wpa_supplicant( 2539): WPA: Key negotiation completed with FIOS_ROUTER_MAC_ADDRESS [PTK=CCMP GTK=CCMP]

I/wpa_supplicant( 2539): CTRL-EVENT-STATE-CHANGE id=2 state=7

I/wpa_supplicant( 2539): CTRL-EVENT-CONNECTED - Connection to FIOS_ROUTER_MAC_ADDRESS completed (auth) [id=2 id_str=]

V/WifiStateTracker( 805): Changing supplicant state: ASSOCIATED ==> FOUR_WAY_HANDSHAKE

D/NetworkStateTracker( 805): setDetailed state, old =CONNECTING and new state=AUTHENTICATING

D/ConnectivityService( 805): ConnectivityChange for WIFI: CONNECTING/AUTHENTICATING

V/WifiMonitor( 805): Event [CTRL-EVENT-STATE-CHANGE id=2 state=5]

V/WifiStateTracker( 805): Changing supplicant state: FOUR_WAY_HANDSHAKE ==> FOUR_WAY_HANDSHAKE

V/WifiMonitor( 805): Event [CTRL-EVENT-STATE-CHANGE id=2 state=6]

V/WifiStateTracker( 805): Changing supplicant state: FOUR_WAY_HANDSHAKE ==> GROUP_HANDSHAKE

D/NetworkStateTracker( 805): setDetailed state, old =AUTHENTICATING and new state=AUTHENTICATING

V/WifiMonitor( 805): Event [WPA: Key negotiation completed with FIOS_ROUTER_MAC_ADDRESS [PTK=CCMP GTK=CCMP]]

V/WifiMonitor( 805): Event [CTRL-EVENT-STATE-CHANGE id=2 state=7]

V/WifiStateTracker( 805): Changing supplicant state: GROUP_HANDSHAKE ==> COMPLETED

V/WifiMonitor( 805): Event [CTRL-EVENT-CONNECTED - Connection to FIOS_ROUTER_MAC_ADDRESS completed (auth) [id=2 id_str=]]

V/WifiStateTracker( 805): New network state is CONNECTED

W/BluetoothHeadset( 805): Proxy not attached to service

D/WifiStateTracker( 805): DhcpHandler: DHCP request started

D/NetworkStateTracker( 805): setDetailed state, old =AUTHENTICATING and new state=OBTAINING_IPADDR

D/dhcpcd ( 2546): dhcpcd 4.0.15 starting

D/dhcpcd ( 2546): hardware address = NOOK_MAC_ADDRESS

D/dhcpcd ( 2546): executing `/system/etc/dhcpcd/dhcpcd-run-hooks', reason PREINIT

D/WsprService( 862): Received android.net.wifi.STATE_CHANGE action.

D/SettingsWifiEnabler( 862): Received network state changed to NetworkInfo: type: WIFI[], state: CONNECTING/OBTAINING_IPADDR, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: true

D/dhcpcd ( 2546): host does not support a monotonic clock - timing can skew

D/dhcpcd ( 2546): broadcasting for a lease

D/dhcpcd ( 2546): sending DHCP_DISCOVER with xid 0x834efe68, next in 2.52 seconds

D/ConnectivityService( 805): ConnectivityChange for WIFI: CONNECTING/OBTAINING_IPADDR

D/SurfaceFlinger( 805): Frame buffer posted; elapsed time = 15 msecs

D/SurfaceFlinger( 805): Frame buffer posted; elapsed time = 18 msecs

D/dhcpcd ( 2546): sending DHCP_DISCOVER with xid 0x834efe68, next in 3.12 seconds

I/WifiStateTracker( 805): DhcpHandler: DHCP request failed: Timed out waiting for DHCP to finish

I/wpa_supplicant( 2539): CTRL-EVENT-STATE-CHANGE id=2 state=8

V/WifiMonitor( 805): Event [CTRL-EVENT-STATE-CHANGE id=2 state=8]

V/WifiStateTracker( 805): Changing supplicant state: COMPLETED ==> DORMANT

D/WifiStateTracker( 805): Deconfiguring interface and stopping DHCP

D/dhcpcd ( 2546): received SIGTERM, stopping

I/wpa_supplicant( 2539): CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys

I/wpa_supplicant( 2539): CTRL-EVENT-STATE-CHANGE id=-1 state=8

V/WifiMonitor( 805): Event [CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys]

V/WifiMonitor( 805): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=8]

D/NetworkStateTracker( 805): setDetailed state, old =OBTAINING_IPADDR and new state=FAILED

I/wpa_supplicant( 2539): succeeded in stopping the last periodical scan

E/wpa_supplicant( 2539): Start periodical(connection) scan.

D/NookWifiManager( 1045): Cannot connect to pre-configured networks

D/DeviceManagerBroadcastReceiver( 1097): action (com.nook.intent.action.OOBE_WIFI_ENABLE_RESPONSE)

D/NookWifiManager( 1097): Cannot connect to pre-configured networks

D/NookWifiManager( 1116): Cannot connect to pre-configured networks

V/WfDownloader( 1116): +WifiManagerObserver: Wifi status: FAILURE__FAILED_TO_ASSOCIATE

V/WfDownloader( 1116): -WifiManagerObserver

V/WifiStateTracker( 805): New network state is DISCONNECTED

V/WifiStateTracker( 805): Changing supplicant state: DORMANT ==> DORMANT

D/ConnectivityService( 805): ConnectivityChange for WIFI: DISCONNECTED/FAILED

V/ConnectivityService( 805): Attempt to connect to WIFI failed.

D/WsprService( 862): Received android.net.wifi.STATE_CHANGE action.

D/SettingsWifiEnabler( 862): Received network state changed to NetworkInfo: type: WIFI[], state: DISCONNECTED/FAILED, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: true

[LastSilmaril]

So the question is, in the meantime, is there any way to eschew dhcp and set a static ip manually on the nook itself?

[scotta316]

LastSilmaril, you and I were thinking along the same lines. While I was looking all over the configuration in my ActionTec FIOS router for info that might help, you posted that. I will say that mine is a MI424-WR Hardware version C, and so far I haven't had any problems. (My Nook updated over wifi this morning, about an hour ago.)

I haven't looked over your log very much yet, but I'll see if anything stands out. I suppose I could post mine also, but I don't really want to pollute this thread if it's not welcome.

[scotta316]

As for the static IP, on my FIOS router, that setting is under Firewall settings. I haven't played with this myself, but if it's like anything else on this router, it won't be as easy as it should be.

I'd also be glad to compare settings if that would be helpful. I wonder if there could simply be a different default setting between hardware versions, like MAC authentication being turned on, for example. (Mine is off, by the way.)

[LastSilmaril · Accepted solution]

Yep, I absolutely detest this router. Since FiOS doesn't have the tennis channel anymore, we might switch to satellite, and then I'll be able to use any router I want after they run CAT5 for us.

Fortunately however, after some googling, I've found out how to assign a static IP to the nook in the Actointec, and this fixes it! (I hope for good this time!!!)

1. Log in to your POS ActionTec router. (For Verizon, at least, the default username is admin and the default pwd is password1, but I suggest you change these post-haste.)

2. Click the 'Advanced' tab, and then click 'Yes' to get through that stupid warning.

3. In the lower-right box labeled 'IP' in the Advanced panel, click on 'IP Address Distribution'.

4. Now, you should see a table labeled (wouldn'tchaknowit) 'IP Address Distribution', with one item in it, 'Network (Home/Office)', with an IP range of 192.168.1.2-192.168.254. This is a comically large range for a home router, and allows for no static IPs that don't cause conflicts. However, when I decided to reduce the range and assign the Nook an IP outside of it, it would not work (of course). So we're not gonna bother messing around with this, but it's probably a good idea to lower the range to a smaller number. Roustabout, other network ppl, care to chime in? 

5. Now, below the table, click 'Connection List'. Now what should pop up is a list of all of your clients, which right now are all dynamic IPs assigned by DHCP.

6. Click the 'New Static Connection' link at the last line of the Connection List table. You'll be at a new page labeled Connection List settings, that'll ask you for a Host Name, IP Address, and MAC Address.

7. Enter whatever you'd like for the hostname, and an IP address that starts with '192.168.1', as long as it's outside the range 100-150 (reserved for set-top boxes).

8. Enter your nook's MAC address. If you don't already know it, go to Settings >> Device Info >> About Your Nook, and it'll be on the last row.

9. Click apply.

10. Turn wireless on on your Nook, and enter any security information required to connect to your network. If you're lucky, you should be done!

[Wendynat]

I have the same issue - same Actiontec Verizon FIOS router as the others. I've PM'ed all my information to the BN_ user that requested it on this thread. There are other people with the issue, per the other messageboards and the nook facebook page. I'm imagining they all have the same FIOS router. 

Just wanted to say thanks to everyone on this board who have been testing, etc, and posting their results. I've avoided wiping my nook to factory settings by reading this, since it seems it would revert to the same problem once the OS automatic download completes again. For now, I'll keep my hours of shelving organization and book loading intact until we hear there's a patch of some sort .

(I didn't notice the wifi problem until yesterday since I don't tend to download a lot of books. Most of mine end up side-loaded from the public library. )

[scotta316]

Thanks for the step-by-step, LastSilmaril. I had already changed the dhcp range on my router to 192.168.1.21 - 192.168.1.40 so that I could use the lower numbers for static IPs on my devices that don't move around. My NST currently has the ...22 address. Who knows, maybe that has something to do with it not messing up.

By the way, on my Advanced tab, the IP box is in the lower right.

[LastSilmaril]

LOL, right you are, I always confuse right and left, which as you might imagine, gets me in heaps of trouble...

[Mockduck]

Really bummed. My Nook Simple Touch updated to 1.1.0 over the weekend, and I was immediately no longer able to connect to my wireless router on the Nook. It had been working fine for months, and I really loved it!

Yup, have a Verizon Actiontech router, which overall has been very nice. Too bad it's not working well with the Nook. Tried forcing the router to accept the MAC address of the Nook, but that didn't seem to solve it.

Here's hoping that there are enough of us having this issue to spur the Nook dev team to do a bug fix (if it's something they can fix; if not, hopefully a solution can be found.)