B&N Community

Reader

Posts: 1

Registered: 11-08-2011

updated to 1.1.0 now wireless will not connect

on 11-08-2011 03:48 PM

I updated my Nook and now am unable to connect Nook to wireless. It says its unsucessful. What can I do to correct this?

Answer

by on

I've been experiencing the same problem. This is what I posted in the main forum:

http://bookclubs.barnesandnoble.com/t5/NOOK-General-Discussion/My-NST-s-WiFi-doesn-t-work-with-1-1-U...

Hi all,

Maybe an hour after installing the 1.1 update, I noticed that my nook wasn't connected to my home WiFi network. What's more, when attempting to connect, it seems to pass authentication but then fail to get assigned an IP address, and WiFi status reverts to 'Unsuccessful' under the name of my network.

This is a serious flaw. It has nothing to do with my WiFi security settings; the same result occurs with WEP, WPA, WPA2, and running an open network.

If anybody else has experienced these issues, please say so.

-e

by on

I am using the stock Actiontec MI424WR router that comes with Verizon FiOS service, and my nook is refurbished.

by on

I had thought this was resolved on my ST after a restart, but I will confirm that when I get a chance.

I did notice this behavior (at one point last night, I wanted to do an erase and reset, and could not because I was not on-network. I looked, and I could see and hear the wifi, and the wifi log indicated that my client had connected, but nothing further happened.

However, I was doing a lot of different things last night since my ST is in an usual configuration. I'll look and confirm that I was able, ultimately, to connect.

My memory is that after I did the device reset and the software reinstalled, it was OK. So it might be worth trying to reinstall this.

One of the first steps in this update script is a reformat of /system.

by on

LastSilmaril wrote:
I am using the stock Actiontec MI424WR router that comes with Verizon FiOS service, and my nook is refurbished.

I have the exact same router and my N2E connected just fine. I don't think it's a router issue. Most likely some sort of settings glitch. Have you tried "forgetting" the router and reconnecting?

by on

AlanNJ wrote:
LastSilmaril wrote:
I am using the stock Actiontec MI424WR router that comes with Verizon FiOS service, and my nook is refurbished.
I have the exact same router and my N2E connected just fine. I don't think it's a router issue. Most likely some sort of settings glitch. Have you tried "forgetting" the router and reconnecting?

I entered the wrong passphrase on one of our nooks. The only way I could get the forget option to display was to first select another connection and then try the connection I wanted the nook to forget.

by on

Yeah, I have tried forgetting; that should have been clear by my having listed the various security protocols I used that didn't work. The one thing I didn't try was changing the SSID of my network, but honestly I would be very surprised if that would do it, and I don't want to have to change the settings on every wifi device in my house just for something stupid like that.

by on

LastSilmaril wrote:
Yeah, I have tried forgetting; that should have been clear by my having listed the various security protocols I used that didn't work. The one thing I didn't try was changing the SSID of my network, but honestly I would be very surprised if that would do it, and I don't want to have to change the settings on every wifi device in my house just for something stupid like that.

The same thing happened to me with one of the N1E updates, I think it was 1.5. Changing the name of the SSID was what worked for me then. Trust me, I tried every setting and that was the only thing that worked. When I had set up the router originally I was in a hurry to get my son's school computer up and running (it was right before school started) and had been too lazy to change the SSID from the default. It wsn't a problem with the 1.4 firmware, but 1.5 apparently had an issue. It connected right away when I changed it.

I haven't had any issues with wifi on this new update, though.

by on

I tried changing the SSID, still nuthin'.

I am afraid to do a factory reset, because the nook is unusable if not registered upon startup, which I obviously can't do without WiFi.

-e

by on

These are the steps I would try if trouble shooting your problem given that it used to connect;

Forget connection on nook and reconnect.
Reset router.
Check for firmware update for router (current for that router appears to be revision G).
Step router down to B\G mode only.
Temporarily disable the router's firewall.
Temporarily set the router to an open connection.
Waste time calling customer service at Verizon and then BN.
Jump up and down on nook until the pieces are small enough to be vacuumed up.

It is possible that the nook's modem failed during the update. That happened to me with a N1E after an update.

by on - last edited on

I found a copy of the 1.0.1 updater last night for someone who simply didn't like the update.

I'm seeing enough reports that the 1.1.0 firmware's making problems for folks that I wanted to share that link. (In my case, my problem was brief and entirely of my own making.)

I had hoped to set an updater that had one file brought in from 1.1.0 telling BN that people already had the update, but would otherwise roll you back to 1.0.1. I was not able to get that to work - the file was opened, vetoed and deleted the twice I tried it. (It seems this should be possible, if the manifest crypto signature of build.prop could be made to match the build.prop in the file, but I couldn't get it to work.)

Any rate, I would roll back to 1.0.1 if you're having trouble (power off; power on while holding in the left and right lower button pair to reset to the shipped /system; if that was 1.0.1, you're probably good. There is an 8 failed boots trick for the Touch as well, but from what I've seen, just wiping /system seems to be enough.)

If yours shipped with 1.0.0, you need to update to 1.0.1) and then keep wifi off most of the time to avoid getting the update pushed.

I really think it's too bad that this update is in trouble, because on my device it works very nicely and the screen is tons more responsive.

That said, here is a link to a 1.0.1 installer in case you don't have a copy available.

http://www.mediafire.com/?49cx3693cjtd0jk

by on

rustabout:

The fact of the matter is, when you do the L+R reset after doing a manual update, like I did, it seems to reset to 1.1.0, because I cannot connect to my wireless networks anymore after doing so (as I suspected). Back before I had decided to root (didn't go through with it but seemed to be prudent) I made an image of the system SD card, and dd'ing that back on gets me back to the shipped system, 1.0.0. Everything works fine with that back on.

Yes, it's a shame the update doesn't work.

gstone:

I appreciate your help but there have been no new firwares for my router. The revision you are referring to is a hardware revision, not a software revision. The fact of the matter is, disabling the firewall, disabling N mode, and going to an open connection are not long-term viable options anyway (though I did try that last one), and the Nook WiFi card isn't broken as it works perfectly upon returning to 1.0. Needles to say, forgetting the connection and restarting nook has not worked. I am going to try to connect to a different router today and then call or walk in to bn and see if they'll give me a replacement device for my trouble.

by on

And thanks, rustabout, for the 1.0.1 update; I'll keep it handy.

by on - last edited on

Ouch, I've just confirmed that the restore I thought worked does not restore you to what was shipped. I did an erase and deregister followed by power up plus hard button.

You absolutely have to do 8 failed boots, and I had not realized that. I've always found 8 failed boots very hard to accomplish, and on the e-ink screen, even harder.

Doing echo -n -e <bootcnt value of 8 - BN won't let me post the actual string> to BootCnt does trigger the firmware restore to 1.0.0 on my device, though.

I'm surprised, and I'd like to know how that can be forced to install short of 8 failed boots?

Because I have the noogie boot disk and linux around, it's so much simpler for me to do restores from dd than from the keypresses that I've only done a keypress restore once, and I thought that did roll me from 1.0.1 to 1.0.0. I think, though, that that was when I was first doing my partition hacks. I probably got something so munged that a firmware reset was triggered and I don't remember it.

Apologies. I'll keep reading around on this in hopes of a simpler way to do the reset.

by on

@LastSilmaril

They are not long term solutions or solutions at all. They help identify where the problem lies.

Hi Everyone!

I'm sorry for the inconvenience. To better assist you can all of you with issues connecting please PM with your account details(serial #, email) and router info. I'll get together with our devs and see what I can cook up.

Thanks!

- Alex

by on

Alex, can you ask the devs if there's an easier way to trigger the firmware restore than the 8 failed boots method? For the time being, to get folks back online, a firmware restore will work, but the power button on the ST has always been a challenge to me because the screen delay is fairly long.

by on

@gstone, yeah I should've realized that; sorry for jumping on you.

by on

Update:

I have just tried using a completely different router, and I can, indeed connect to it (asus with dd-wrt my friend set up) without issue.

It isn't connected to the internet - a fact which the nook successfully recognizes.

I'm using FiOS w/TV, so connecting this second router to the Interwebs will require doing some kind of complicated bridging operation, apparently - so keeping WiFi on is a bit useless right now, but I think we're making progress here. I'm going to send Alex some of my config.

-e

by on

More info:

When using the ASUS router WiFi when using WPA or WPA2 (AES) after inputting the password, but only after hitting the checkmark and shutting WiFi on and off; otherwise it'll just say 'Disconnected'.
One time, the N2E spontaneously shut WiFi on and off after connecting to the network.
Another time, a network that was set up as WPA was recognized as WEP, even though directly beforehand, I had it set up as an open network.
When I tried to connect to it in WEP mode, it connected faster than when I was using WPA or WPA2.
All times I connected, when I let it finish testing the connection, it would successfully recognize that the router has no Internet connection.
And, once again, absolutely no luck with my Verizon router. However, let me try reseting it. I am really loth to do so because it might result in having to call Verizon to reset my Optical Network Terminal (ONT) outside, but I'll find the time to do it later.

by on

Update:

Problem connecting to Actiontec persists under all circumstances after doing a Factory Reset back to 1.0.0 and then upgrading back to 1.1.0.

Reseting the router now.

-e

by on

I reset my Actiontec router, and using the *stock wireless settings* (WEP, weird SSID and default password) it still would not connect.

-e

by on

I've sent all this info to Alex; hopefully we'll get some results shortly.

-e

by on

Thank you for the idea, it was worth a try. It did not work for me.

by on

Don't do it unless you have easy access to WiFi at a Starbucks or Library or someplace like that. I did it and have lost so much time bothering with this. And it still doesn't work on my WiFi.

IMHO, wait untill they have a fix. If you want to download anything, either sideload it from your computer or go to an open WiFi at a cafe or someplace like that.

Good luck.

by on

I would like to pm you with my info. What is your email?

Thank you

by on

I'm sorry, are you talking me?

by on

LastSilmaril wrote:
I'm sorry, are you talking me?

I think he is addressing BN_AlexG not there is no telling.

By all appearnces the v1.1 update is not communicating with your router. Do you want to wait for BN to issue another update or get back to v1.0.1

by on

LOL, well I broke down and rooted it after all that, and lo and behold, it works just fine with my Actiontec now. Kinda screwy, frankly...

by on

Interesting, though. You might want to - very quickly - pull the device logs (so hopefully you still have

some from when you could not connect) and pass them on to BN.

by on

LastSilmaril wrote:
LOL, well I broke down and rooted it after all that, and lo and behold, it works just fine with my Actiontec now. Kinda screwy, frankly...

I think it was pretty much a foregone conclusion something changed in the update preventing you and a few others from connecting. Probably a reversal of whatever was done in v1.0.1 to improve connectivity.

by on

roustabout: so how do i do that, use logcat? I think it probably logged enough battery changes by now to overwrite what was going on before...

-e

by on - last edited on

---------------------------------------------

LastSilmaril wrote:

I'm sorry, are you talking me?

--------------------------------------------------

No, I apologize for the confusion, I'm looking for Alex's email address to give him the information about my S/N & Router information he requested in an earlier post. I am new to posting to these boards. Thank you for being patient with me

by on

fuzzyballerina wrote:
---------------------------------------------
LastSilmaril wrote:
I'm sorry, are you talking me?
--------------------------------------------------

No, I apologize for the confusion, I'm looking for Alex's email address to give him the information about my S/N & Router information he requested in an earlier post. I am new to posting to these boards. Thank you for being patient with me

When you click on a users name it brings up a listing of that users latest posts.

In the right hand pane of that window you should see a link like this;

Send this user a Private Message

When you click on that link a window opens that allows you to send the user a private message.

To view messages you have sent or received on this board click on the mail icon next to Help in the menu.

by on - last edited on

I am also having problems and tried various tricks. I also have a Verizon FIOS network, which supplies the DNS, but I am using a Cisco wireless router on it.

So, while it could be a DNS issue, it is not the FIOS wireless that is the problem.

Please let me know when there is a fix.

by on

Never, ever forget which direction you're trying dd in. I did a dd if=/device/in/bad/state of=my.old.backup.img earlier, and have just finished figuring out which step it was that I hadn't documented in my notes for getting my NST to let me install 1.1 without tearing out my partitioning. It would have been less time consuming, probably, to simply start from scratch.

logcat is a built in command that can be run from adb:

adb shell

logcat

This will dump whatever's around onto the screen.

More helpful would probably be

adb shell

logcat > /media/logcat.txt

Give it a few minutes, then break your ADB and take a look at the file.

Or do (on your computer)

adb shell command logcat

adb shell command logcat > logcat.txt

and save yourself the step where you have to get the output back off your device.

by on

I have had the same issue with my Nook no connecting with my home WiFi. It will connect to new WiFi but not at home. C/S has had me reboot twice without any success. They referred it to Software Development. I also love reading my Nook Books but doubt I will side load another upgrade as quickly.

by on

LOL, I'm sorry to hear that, roustabout, and thanks for the advice, but I've since moved on. Almost everything except market search is up.

by on - last edited on

Apparently market search will probably not work well for a bit on the NST, but what I want on the NST is a pretty limited constellation of apps anyhow - my preferred reader and sync tool, my preferred RSS reader, ADB wireless, busybox set up so I have the full set of unix commands.

The part of my NST that's heavily tweaked is the partition layout - I have 800 M of available storage, and my BN content lands on the visible partition, not deep inside Androidville. This is how I wind up preferring to reimage rather than do a full wipe, because linking the BN folder properly means I have to be awake.

One helpful thing I found partway through the process - I decided to try reediting my partitions a bit last night, and wound up deregistering the NST on the BN side but not successfully deregistering on the NST itself - is the location of the authentication flag.

When your device is registered, a database file gets your information added to it. If your Nook and BN disagree about that file, you can't use the shop.

On both the NST and the NC, the file is at

/data/system/accounts.db

It includes info on MANY registered accounts on your device - BN auth, Google auth, Youtube auth if you have it.

However, if it's deleted, it'll get rebuilt clean.

Very helpful if you find yourself with an NST that can not use the shop on the BN side, but still thinks it is registered on your side.

You can check if this applies to you by logging in at BN and going to My Nook. Manage My Nook.

If your device is NOT listed there, but when you are on your NST Settings... Device info .. About Your NC shows your email address is still tied to the device you will need to do something fairly hardcore to the device to fix it (I think that the power on + bottom left + bottom right would fix this, as I think that wipes out /data) - or boot from Noogie and delete the file, or if you have a file manage installed, use it to delete the file.

Reboot, and (on a rooted device) you can use the OOBE reg app to reregister. I do not know how to trigger that app from a stock NST.

by on

Thanks for the extremely helpful informatin, roustabout; saving it for posterity. (You should add it to the knowledge place at the usual place. Speaking of, I saw your post about messing with partitions. I'm good with an external sd for now, but may try it out at some pt (fully backed up and lovin' it!)

by on

Unfortunately I can't connect either

by on

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.

by on

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

by on

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

by on

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

by on

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.

by on

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.

by on

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.

by on

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

by on - last edited on

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.

by on

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.

by on

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

by on

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

by on

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.

by on - last edited on

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.)

by on

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. )

by on - last edited on

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.

by on

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

by on

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.)

by on

'Tried forcing the router to accept the MAC address of the Nook, but that didn't seem to solve it.'

In other words, my quick-n-dirty fix did *not* work? Oy. Disappointing.

by on

LastSimaril.

This looks like DHCP client debug below..Can I ask you how you got this??

Is this from the nook itself?? or, is it debug from the router?

If I were to guess, I'd say it form the nook itself..

Thanks,

JFeole

by on

LastSilmaril wrote:

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!!!)

I actually LOVE my FiOS, but after the update to 1.1, I couldn't connect to our home Wifi.

I was able to download a few new purchases at work and didn't realize I was affected by this until today, when I tried to use my "Shop." I remembered having read that you'd solved this problem somewhat "simply" so I came looking for your instructions.

Less than a minute later, all is well. I got my book and now I'm going to go read it.

Thank you for taking the time to figure this out and for posting it for others. Thank you, Thank You, THANK YOU!

by on

MockDuck, did you try LastSilmaril's solution here? This procedure gives your Nook a static IP. It sounds like you tried MAC authentication.

by on - last edited on

jmf: the log is from my nook. I tried connecting to my ActionTec router, and then after that failed, connected my laptop and my nook to another router. Then, I did an adb connect to my nook, ran adb logcat > n2e_log.txt, found the relevant portion, blocked out my SSID and MAC Addresses, and posted it here.

by on

Ya_Ya: happy to help. Oh, and I also didn't mean to say that FiOS was bad - the speeds are some of the best in the country. It's just the router that's a pain to deal with

by on

I will try that when I get home tonight, thanks!

by on

What, you people don't need 253 IP addresses at home? Don't know what's wrong with you.

There's no reason not to dial down the list of available IPs, but it sounds like on this router, what you're actually doing is assigning the NC the same address each time via DHCP - not quite the same as a static IP address, which requires zero information from the router (this method requires that the DHCP request and offer work, it just fixes the value of the offer.) I don't know how to get Android devices to use static addresses, though, as I haven't needed to.

Am I reading you right that these Actiontecs don't have any ethernet handoffs on 'em?

If so, super annoying, as it means setting up a second access point is painful.

by on

Recieved replacement NST from B&N today. Fired it up and it has 1.0.1 on it. Now the question is, do I leave the wifi on and let it update to the new software??

by on

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!

This worked! Thank you for the excellent and detailed write-up on how to do this. I am still hoping that Barnes and Noble (and/or the Nook development team) do something to correct this, but I am now able to connect using my Nook, thanks to this writeup.

by on

LastSilmaril, thank you SO MUCH!!! I just about flipped when I came home to discover that my home wi-fi (Verizon ActionTec FIOS) did not work for my Nook Simple Touch! Your directions were scary at first glance, but once I overcame my fear and the weird nonsense phantom keystrokes that appeared in the password login field, it was all easy to follow. (I still don't know why several phantom dots showed up whenever I hit one key--but I logged in!).

I had tried all the other simple fixes earlier (forget, reboot, etc.), but nothing worked. I just recently got FIOS, and 1.0 had worked with it. Then I got the 1.1 update while at a Barnes and Noble store, and it stopped working. Thanks to your great info, I didn't even have to call tech support! SO GLAD I found this forum!

by on

Everyone,

I was also having the 1.1.0 firmware Wifi connection issue with my FIOS actiontec router (and another wireless router pointing to the Actiontec). After spending a few hours on the phone with BN tier 2 support they confirmed that they know about the issue, and are working on a fix. They are going to notify me when they find a fix. It would have been nice if they had notified me the last two times I talked to them.

by on

Very frustrating. I bought the nook SIMPLE because I didn't want to be wasting time programming the darn thing... I JUST WANT TO READ!! LOL!

I received the REPLACEMENT (a refurbished) NST yesterday. It has the OLDER 1.0.1 software...

My question is, what do I do when they push the 1.1.0 update and my unit doesn't talk to my wifi again?

What-ever....

by on

fuzzyballerina wrote:
Very frustrating. I bought the nook SIMPLE because I didn't want to be wasting time programming the darn thing... I JUST WANT TO READ!! LOL!

I received the REPLACEMENT (a refurbished) NST yesterday. It has the OLDER 1.0.1 software...
My question is, what do I do when they push the 1.1.0 update and my unit doesn't talk to my wifi again?
What-ever....

Don't leave your wifi on for long periods of time. Just connect to shop or download books you've purchased, then turn wifi off. If you start to see the message telling you that the update is downloading, turn off your wifi immediately. Then connect to a computer and delete the downloaded file (I'm actually not sure if this will work for the N2E - I don't know where the OTA downloads go to and if you'll be able to see it, but it's worth a try).

You won't have to avoid 1.1 forever - B&N will release an update to fix this issue eventually.

by on - last edited on

You won't have to avoid 1.1 forever - B&N will release an update to fix this issue eventually.

Keriflur: Thank you for the idea. Hopefully they will come out with a fix in the next week.

by on

Holy cow, that was a pain! I had to go through LiveChat to get to the router. Thank you LastSimaril (Tolkien fan

) for those steps. You're right, what a POS, or at least getting to it is a POS system rigamarole thingie. But enough of technical terms.

It's such a nice feeling to see the books I bought at the store (via my iPad) finally on my Nook Simple Touch. For a while there, I felt like the "simple" one.

by on

Thank you for the very clear instructions. I did everything as suggested and double checked the entries. Unfortunately, the problem remains. Even with a static IP address, the Nook will not connect.

I am now completely frustrated and, I must confess, just went out and bought a Kindle Touch. Message to B&N: Preventing a loyal customer from buying books and not responding as if it were a crisis, leads to very dissatisfied customers. Sad.

by on

I agree! B&N are u listening??

by on

roustabout wrote:
What, you people don't need 253 IP addresses at home? Don't know what's wrong with you. (--Indeed)

There's no reason not to dial down the list of available IPs, but it sounds like on this router, what you're actually doing is assigning the NC the same address each time via DHCP - not quite the same as a static IP address, which requires zero information from the router (this method requires that the DHCP request and offer work, it just fixes the value of the offer.) I don't know how to get Android devices to use static addresses, though, as I haven't needed to.

Am I reading you right that these Actiontecs don't have any ethernet handoffs on 'em?

If so, super annoying, as it means setting up a second access point is painful.

Eh I'm not sure what an Ethernet hand-off is but setting up access points, bridges &c isn't difficult? And obviously you're right, this isn't really static IP, but like you, I don't know how to get the NST to request the same IP each time. It's easy to do with Android phones, but the settings screen simply isn't there on the NST and I wasn't really sure how to approach hacking something together. I do hope that the dhcp weirdness gets fixed though...

And again, I'm glad the little guide I wrote is helping people here

by on - last edited on

(Though it doesn't seem to be at all a fool-proof solution; sorry if this didn't work for some of you)

by on

This is not solved for me. I've got a Netgear router, made sure all the settings were as specified here - nothing. Reserved an IP address and entered the MAC address of my Nook - connected! I thought all was well when hours passed and I was able to connect and shop, no problems. Then my computer said there was a conflict with a device's IP address on the network and shortly thereafter booted the Nook off the network. I'm done with troubleshooting and hope B&N releases the fix very, very soon. (I did send my info to BN Alex.)

by on

I spent over 2 hours on the phone with Verizon last night to try to get the Simple Touch up & running after the 1.1 update with the Actiontec router. It was to NO avail. The tech tried everything, including reading all the posts on this board. It just does not work. Fortunately, I am able to connect to my router in the office, but I will tell you that BN tech support's answer was to "take a ride over to a B&N store to get a book." I didn't say it, but, if I wanted to take a ride over to the store every time I wanted a book, I wouldn't have gotten an electronic reader over 2 years ago. Not a good answer. Whatever they did in this latest update, they need to fix, pronto.

by on

I'm sorry it didn't work Denise. Can you post the hardware revision of your router and firmware version? This can be found under the System Monitoring tab.

-e

by on - last edited on

OK everyone, I found an alternative solution for those of us who are rooted.

As roustabout pointed out, my method simply has the router assign the same IP to the nook each time; the nook is not requesting a Static IP. The upside to fixing the issue that way is you don't need to root or change the software on your nook in any way. The downside is that you need to know how to configure (and heck, have access to) every single router that has this weird DHCP issue.

If you're rooted, the fix is simple.

1) In the market (use Search Market app if market search doesn't work for you), search for the following program, called "WiFi Static"

https://market.android.com/details?id=com.farproc.wifi.statIc&feature=search_result#?t=W251bGwsMSwyL...

2) Open the program and click "Add Configuration".

2a)If you already did the original router-based fix and your nook is connected to that router, then you can click "Yes" at the dialog box that shows up asking whether you want to base the config on your network. Then, disconnect from WiFi, and remove the Static IP assignment from your router. Turn WiFi back on on your nook, and it should connect fine. You'll get a little pop-up with your network's SSID and MAC Address from WiFi Static at the top, but this disappears quickly. YOU'RE DONE.

3) If not, then under "IP Configuration" you have to set the static IP you'd like the Nook to have, the Gateway (router's IP), the Netmask (typically 255.255.255.0) and the DNS servers (typically the same as the router's IP or you could use OpenDNS/Google's DNS).

4) Under "APs use this configuration", click "Add access point".

5) Enter your SSID in top field and Router MAC address in bottom field. This should be on the side of the router if you have the POS ActionTec, and many others besides. Click OK and save the configuration.

Now, try to connecting to WiFi as usual; hopefully it should work. Optionally, you can add more APs (access points, routers in this discussion) for the same config above, if you know that the Static IP you chose will be available on all the routers and they use the typical 192.168.1.1/255.255.255.0/192.168.1.1 settings for Gateway, Netmask and DNS.

by on

Thanks so much! This worked for me. Although I am really dissapointed in B&N technical support as I am clearly not the only person who suddenly could not connect to a home network after the Nook updated to 1.1. When I called they were mystified that I would have such a problem, and we spent a long time turning the nook on and off, forgetting the netowork, etc, all of which I had already tried. Clearly this is an issue in their software, as all of my other devices are connected and working beautifully.

So, just wanted to say thanks for being helpful and providing a solution where B&N was mystified beyond belief.

by on

rachellebkny wrote:
Thanks so much! This worked for me. Although I am really dissapointed in B&N technical support as I am clearly not the only person who suddenly could not connect to a home network after the Nook updated to 1.1. When I called they were mystified that I would have such a problem, and we spent a long time turning the nook on and off, forgetting the netowork, etc, all of which I had already tried. Clearly this is an issue in their software, as all of my other devices are connected and working beautifully.

So, just wanted to say thanks for being helpful and providing a solution where B&N was mystified beyond belief.

Curious rachel, which way did you use? The router way or the Wifi Static way? Glad it worked.

by on

LastSilmaril:

I have some questions on your instructions, please. Do we need to install the program on our computer? Or is there another way to open the program? When the gray box popped up I was unable to get beyond the "IP Config or AP's use this...." It kept switching back and forth between the two. I must not be doing something right and do not have many computer programming skills. I would appreciate any help you could give. Thank you.

by on - last edited on

LoveToRead51RW wrote:
LastSilmaril:
I have some questions on your instructions, please. Do we need to install the program on our computer? Or is there another way to open the program? When the gray box popped up I was unable to get beyond the "IP Config or AP's use this...." It kept switching back and forth between the two. I must not be doing something right and do not have many computer programming skills. I would appreciate any help you could give. Thank you.

I'm really not sure I'm following you here. You're not installing *anything* on your computer, only the WiFi Static app on your nook, which you can only do if your nook is rooted. I'm not sure what exactly is going on when you say "It kept switching back and forth between the two." Maybe you can clarify yourself or take a video or something?

by on

thank you!!! it works

by on

Sorry about the confusing message. I don't know what I don't know about the tech aspect of trying to fix the lack of WiFi connection but I will try again. While reading the blog on my computer, I clicked your link, the web page indicated the software to create static address but it was for android devices I believe. My connection is through my PC home network WiFi, so I thought perhaps it was necessary to download the software to my PC to create a static address for my NOOK to connect.

Thank you for your patience. I believe I am in over my head on this one. Not to worry. Appreciate all your blog advice. This blog has helped me to appreciate there are other ways to down load my books. Many thanks to you all.

by on

Where would I find the system monitoring tab?

by on

LastSilmaril wrote:
I'm sorry it didn't work Denise. Can you post the hardware revision of your router and firmware version? This can be found under the System Monitoring tab.
-e

Ok, I figured out what you were asking for. Here's the info.

Firmware Version:	20.19.8
Model Name:	MI424WR-GEN2
Hardware Version:	F

by on

DenisePW wrote:

LastSilmaril wrote:
I'm sorry it didn't work Denise. Can you post the hardware revision of your router and firmware version? This can be found under the System Monitoring tab.
-e

Ok, I figured out what you were asking for. Here's the info.

Firmware Version: 20.19.8
Model Name: MI424WR-GEN2
Hardware Version: F

Wow, exactly the same router and firmware as my own and it still does not work. That is depressing. BN_AlexG, methinks, should uncheck the 'solved!' box...

by on

Re: My NST's Netgear WGR614v6 WiFi doesn't work with 1.1 Update

Serial # 3012220046963008 ahc822@comcast.net

by on

ooops! sorry I goofed and did not expect the text to appear like that in a column.

by on

You can edit the text under options.

by on

With the Netgear WGR614v7, the only security that would work with the Nook was WPA-PSK [TKIP].

I tried WEP and WPA-PSK [AES], but those two didn't work. Try using WPA-PSK [TKIP] security.

by on

Add me to the list of those that have this issue.

I have tried every suggestion related in this forum. I have tried setting the nook's mac address in the wireless router to have a reserved ip address. I have tried removing ALL security from the wifi, still no go. I have tried removing all other devices from the wifi, still not working. The nook connects to the wifi then says it is getting an IP address then says it fails. I am able to connect the nook to any other wifi but this one that it has worked on for months. My wifi router is a Netgear WGR614 v5. I have half a dozen other devices that connect to the wifi without any problems.

B&N chat support directed me to do a hard reset of the nook. This I did following their instructions exactly. The factory reset did not solve the problem but it did give me the headache of reloading all of my books on the device with no wifi connection. Chat support now tells me to take it in to a B&N store and see if it will connect to the wifi there, which I know it probably will since I can connect to any other wifi but my own. My only idea is that my router, which is an older router and probably now incompatible with the nook since the 1.1.0 upgrade (downgrade).

If anyone at B&N is listening, PLEASE FIX THIS ISSUE OR I WILL BE REQUIRING A REPLACEMENT.

Thanks for listening to me complain

by on

Add me to the list. Wifi stopped working on my NST after updating to 1.1 firmware.

by on

tremorrs wrote:
If anyone at B&N is listening, PLEASE FIX THIS ISSUE OR I WILL BE REQUIRING A REPLACEMENT.

While we understand your frustration, this forum is merely a way for customers to communicate with each other. If you're trying to reach Tech Support, there are more direct ways to do it.

by on

ladybugAC wrote:
ooops! sorry I goofed and did not expect the text to appear like that in a column.

It was kind of funny though

by on

My Actiontec MI424-WR Rev F router (Verizon Fios) doesn't work with the Nook 1.1.0 update. Bahhh. It's frustrating. I think you could get books by making a direct connection to the computer, instead of using wifi. Am i wrong there? Still I have an Ipad, and want to easily be able to synch where I am (in a book I'm reading) in the Simple Nook, and the Nook app in the ipad. When the wifi doesn't work, it becomes a hige hassle. If B& N knows we could connect before the update, they ought to be able to fix this. I sure hope they can.

by on

lemby wrote:
My Actiontec MI424-WR Rev F router (Verizon Fios) doesn't work with the Nook 1.1.0 update. Bahhh. It's frustrating. I think you could get books by making a direct connection to the computer, instead of using wifi. Am i wrong there? Still I have an Ipad, and want to easily be able to synch where I am (in a book I'm reading) in the Simple Nook, and the Nook app in the ipad. When the wifi doesn't work, it becomes a hige hassle. If B& N knows we could connect before the update, they ought to be able to fix this. I sure hope they can.

There is a solution for your router. See reply 70 of this thread.

by on

LastSilmaril wrote:
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!

This worked for me too.

One additional tidbit of information that should provide everyone who may be behind the scenes trying to fix this issue. I noticed that when I tried to connect my NST (each time getting Unsuccessful) it would end up in the connected devices list on the router for a few minutes. While reading this thread I ran into the post by LastSilmaril with his router log (post 52) and went searching for the DCHP settings of the router. When I found this Connection List on my router I tried to connect again and the NST showed up, but instead of a status of Active, it was Expired. So, the thought that there must be some sort of caching going on in the DHCP portion of the router may have some teeth to it. Since my NST was there, I just clicked on Edit and selected the Static Lease Type, saved and tried to connect. BAM, it worked. I decided to uncheck the Static Lease Type to see if the pairing has an issue somehow with dynamic assignment of the IPs.

So, hopefully there's some information to help out with. Much simpler than restoring to a previous version but unfortunately more difficult for anyone who has little experience in networks.

by on

The purported solution is way too complicated. I'm not a tech person. If that's the best to fix it, it's beyond me. Every wifi device I have in my house works, and without any hassle. So why shouldn't the nook update?

by on

lemby wrote:
The purported solution is way too complicated. I'm not a tech person. If that's the best to fix it, it's beyond me. Every wifi device I have in my house works, and without any hassle. So why shouldn't the nook update?

Too complicated? You just have to follow the 10 steps, without having to do any thinking. Just do what the steps tell you. It will only take you about 5 to 10 minutes to change the router DHCP setting.

by on

I called verizon when I was having trouble with the login. They told me that I couldn't create a static address for the router without upgrading to a business account, and that that would cost money. If I did it on my own, I would make the router inoperative. So Verizon does not want me to follow the ten steps you have suggested. I'm just passing that along so those people who are having trouble with the Actiontec router understand what the issue is with Verizon, in terms of creating a static addresss. If these people already have a business account, they don't have to spend money upgrading. If like me, they don't have a business account, creating the static address is apparently an upgrade/ "money" issue.

by on

This worked!!!!!!!! Thanks so much I can now buy books at home since we don't have 3g on our nooks. Great help you should share this info with BN customer service.

by on - last edited on

lemby wrote:
I called verizon when I was having trouble with the login. They told me that I couldn't create a static address for the router without upgrading to a business account, and that that would cost money.

I couldn't help laughing out loud when I read this. The static address you'd be creating for your Nook is an address on your internal network (LAN). The static address they were talking about you paying for is on the exterior network (WAN). You router is the gateway between those two networks. The addresses your router gives to your local devices are never seen from the internet.

By the way, this "purported solution" has worked for nearly everyone, if not everyone, who has tried it. Thanks to ChuckHeston for reposting it.

by on

lemby wrote:
They told me that I couldn't create a static address for the router without upgrading to a business account, and that that would cost money. If I did it on my own, I would make the router inoperative. So Verizon does not want me to follow the ten steps you have suggested.

As a Verizon FiOS customer who doesn't have a business account, whose N2E quit connecting to the router in question after the update to v1.1, who followed those ten steps, whose N2E connects to her Wifi again, whose Wifi works for all of her other devices, too, I promise you you didn't understand the person on the phone, or perhaps s/he didn't understand you.

If you follow those steps above, exactly, it will (almost definitely) work, your NOOK will connect to your Wifi, your router will not be inoperable and it won't cost you any mooney.

I'm fine with wanting things to just work, but if a consumer doesn't understand the basics of the technology s/he buys, this is what happens. Even the simplest of fixes become baffling...

by on

lemby wrote:
I called verizon when I was having trouble with the login. They told me that I couldn't create a static address for the router without upgrading to a business account, and that that would cost money. If I did it on my own, I would make the router inoperative. So Verizon does not want me to follow the ten steps you have suggested. I'm just passing that along so those people who are having trouble with the Actiontec router understand what the issue is with Verizon, in terms of creating a static addresss. If these people already have a business account, they don't have to spend money upgrading. If like me, they don't have a business account, creating the static address is apparently an upgrade/ "money" issue.

The instructions don't say to create a static address for the router. Verizon is completely correct about that. The instructions say to create a static address for the Nook (device).

by on

I have tried just about everything in the forum at this point. Using a WGR614v7 router. Tried setting a static IP, tried changing security type (open, WEP, WPA, WPA2 both types). I can't seem to connect no matter what I do. Any help will be AWESOME at this point so long as I can get connected. Wife bought for me 2 months ago, and she's pretty furious at this point (already had to replace my first one).

by on

I have the exact same Router (REF F) with Verizon FIOS and my NST will no longer connect to my home WiFi once the Nook software upgraded. BN Tech support refused to acknowledge there was any problem with the new software, and did not acknowledge that others were having this problem. I have not tried the work around yet. How can we get to the right Tech Support (Tier 2?) or customer service to register our problem?

Has B&N made any official statements about this to acknowledge the problem and to say they are working on a fix?

Thanks,
Caroline

by on

As with the many on this thread, I'm experiencing the same wifi connection issues after manually upgrading my Nook Touch to 1.1.0. After mulling it over (reviewing the +/- of the upgrade), I reverted back to factory (1.0.0) and connectivity works perfectly with my home network (Netgear WGT624v3 router).

In addition, I have several other wireless devices on the same network/router (including a Nook Color and HTC Thunderbolt) that have no problems in connecting.

My question, does 1.1.0 not like Netgear routers? It seems that most of the issues are with Netgear from what I've seen on this and other forums. Just my two cents.

Otherwise, I love my NT!

Dwayne

by on

I have this same router and had the same problems after my software upgrade. B&N replaced with a refurbished unit but with software version 1.0.1. I am connected now! Thanks customer service.

by on

Well, I love my little nook reader as a convenient book reader. The only one I ever liked.

But this software glitch is the height of absurdity, and now I'm back to reading used paperbacks until someone ???? fixes my nook reader (and I don't think it should be me, as the thing is only 3 months old, the guy in the store hasn't a clue about this and it never said anything about reconfiguring my home network !).

I'm supposed to reconfigure my computer network every time B&N "upgrades" my nook? What about my wife's phone" her i-pod? her windows computer? my linux netbook? my guests tablet gizmos? . . . reconfigure the network every time someone wants to connect some new device to my home network ?

Yeh yeh . . . grumpy old man, that's me.

I understand that no one here is accountable for this, so please tag this as "crazy old man tries hi-tech book reading, flips out and goes back to paperbacks" and let's let it go at that.

by on - last edited on

scotta316 wrote:
tremorrs wrote:
If anyone at B&N is listening, PLEASE FIX THIS ISSUE OR I WILL BE REQUIRING A REPLACEMENT.

While we understand your frustration, this forum is merely a way for customers to communicate with each other. If you're trying to reach Tech Support, there are more direct ways to do it.

Yes there are more direct ways to contact tech support and they are completely useless. They finally told me to take it to a B&N store and the people there would definatelyhelp me out. Of course after a 20 mile drive to the nearest B&N, the guy behind the nook desk gave a frustrated sigh and said, "No there is nothing we can do to help you, tech support is wrong about that, we can't even replace your device in the store. You have to call customer service to get a replacement." Way to go B&N. Way to pass the buck, tech support.

by on

How do you revert to the old version?

My Nook also lost conectivity when I up-graded. I dont have the same router most of you do. I have a brand new Westell A90-???? with Centurylink.

I cant find where to ping a MAC address, but Ive tried all the other solutions with no success. Tech support said they would call me back with a fix, but that was 2 days ago.

by on

Ok, i followed the steps and I have a wifi connection. I hope it lasts. Thanks for the help. The biggest problem I had was logging into the router. There was some sort of security set up, so that the user name and password didn't work. I called Verizon, and had to reset the router to eliminate the security stuff, so I could get the log in. After that, evertying went ok. I did this as a last resort when i was getting no help from Barnes & Noble support. They offered to take back the Nook, and send me a new one, but I was going to have the same problem with the new one.

by on

I'm so glad it worked!

by on - last edited on

Ugh. Lots of people here complaining without actually reading the thread at all, or calling Verizon or BN tech support (both of them pretty bad) before attempting to understand what I wrote or asking any questions. My 10-step solution is actually more verbose than it needs to be in order to be idiot-proof - I encourage you all to try it!

The router-based solution:

http://bookclubs.barnesandnoble.com/t5/NOOK-Technical-Support/updated-to-1-1-0-now-wireless-will-not...

The Rooted-Nook-based solution (use arp -a or /usr/sbin/arp -a to find out router MAC address if auto-detection doesn't work and you've got a laptop handy.)

http://bookclubs.barnesandnoble.com/t5/NOOK-Technical-Support/updated-to-1-1-0-now-wireless-will-not...

ChuckHeston's possibly-much-easier solution:

http://bookclubs.barnesandnoble.com/t5/NOOK-Technical-Support/updated-to-1-1-0-now-wireless-will-not...

One note, Chuck: that log you read was from my Nook, not my router. The log in question, by the way, can be found here, though it will likely not convey much to anyone without a cursory background in networking:
http://bookclubs.barnesandnoble.com/t5/NOOK-Technical-Support/updated-to-1-1-0-now-wireless-will-not...

by on - last edited on

yrralbn wrote:
How do you revert to the old version?

My Nook also lost conectivity when I up-graded. I dont have the same router most of you do. I have a brand new Westell A90-???? with Centurylink.

I cant find where to ping a MAC address, but Ive tried all the other solutions with no success. Tech support said they would call me back with a fix, but that was 2 days ago.

What solution are you trying exactly. You never need to 'ping a MAC address' if you're trying the router-based solution; the only MAC address you need to care about is that of your Nook, which is easy to find.

by on

Ignitite wrote:
I have tried just about everything in the forum at this point. Using a WGR614v7 router. Tried setting a static IP, tried changing security type (open, WEP, WPA, WPA2 both types). I can't seem to connect no matter what I do. Any help will be AWESOME at this point so long as I can get connected. Wife bought for me 2 months ago, and she's pretty furious at this point (already had to replace my first one).

Hmm, I'm sorry this didn't work. You might wanna try the alternative, root-based solution. If you could provide more information/screenshots/the Nook log I guess we can try to figure out if you actually were assigning the same IP to the Nook every time via the router, but otherwise I don't think we'll be able to figure it out.

by on - last edited on

Also, for the record? The fact that we need to bookmark posts in order to access a permalink directly to them is stupid (unless I'm missing something). As is the placement of the 'Quote' button on the reply page. I like the quaint feel that the UI of this board has, but some of the quirks are grating in the year 2011.

by on

lemby wrote:
I called verizon when I was having trouble with the login. They told me that I couldn't create a static address for the router without upgrading to a business account, and that that would cost money. If I did it on my own, I would make the router inoperative. So Verizon does not want me to follow the ten steps you have suggested. I'm just passing that along so those people who are having trouble with the Actiontec router understand what the issue is with Verizon, in terms of creating a static addresss. If these people already have a business account, they don't have to spend money upgrading. If like me, they don't have a business account, creating the static address is apparently an upgrade/ "money" issue.

Somehow I missed this one earlier. Wow. Huge understanding fail. The static IP is for *the Nook*, not *your personal internet connection*. It *certainly* does not require ANY upgrade in service *whatsoever*.

And of COURSE Verizon doesn't want you to follow those ten steps: that would actually require (a) you to understand what those 10 steps did (b) them to know wtf they were talking about (c) you to know wtf they were talking about (d) them being interested in helping you *at all* instead of turping you off as some silly customer who is in over his/her head and really shouldn't be messing with router internals.

You will sometimes come across a genuinely knowledgeable and helpful network guy over there, if you manage to get bumped up a level or two, but otherwise? Pfft.

That is why I took the 10 mins to write out the guide in the first place: as usual, nobody is going to help but the community, until the network stack programmers at BN figure out what the heck is going on and releases firmware 1.1.1 or whatever they're gonna call it.

by on

LastSilmaril wrote:

ChuckHeston's possibly-much-easier solution:
http://bookclubs.barnesandnoble.com/t5/NOOK-Technical-Support/updated-to-1-1-0-now-wireless-will-not...

Actually, rereading his post, I think I already tried what ChuckHeston proposed before going through with my solution, and don't think it worked for me. But there is no harm in trying it out, since it should be doing essentially the same thing.

by on

I first of all want to thank you for your help so far - even though it isnt working for me.

I tried to do your 10 step solution, but I have a different router - Westell A90-7500 series gateway router. I cant find any way to asign a static IP to the Nook - or any other device thats connected like my two computers, wireless printer, or two smart phones. All of those devices work fine.

I was able to switch to a MAC address filtering table where I entered the MAC address of the Nook, but that didnt work either.

I was also unable to follow Chuch Hestons methode exactly but I was able to increase the lease time to 90 days - again with no success.

If you have any other ideas I would be very appreciative!

By the way, I found what I thought was the 1.0.1 firmware and tried to install that, but it doesnt seem to take. My nook still says its got 1.1.0.

by on

Picked up a new Nook Simple Touch for my wife for the holidays, and she was unable to register the Nook properly due to this issue (1.1.0 not being compatible with Actiontech routers from Verizon.) I got home after work to hear her talking with BN customer support, who was giving her the basic "try turning it off and on, forget and try to hook up to wireless again", etc. advice.

I told her to tell the phone support person that we are using an Actiontech router from Verizon, at which point the support person ended the help call by telling her, "The Nook doesn't support that router."

I guess that's one way to solve the problem! I had her follow the steps in this thread, and her Nook is now hooked up properly to our wireless. It was frustrating to see my wife get the runaround from BN support, and their approach to not help people because the router is "not supported" is pretty poor, in my opinion. Thankfully this thread has a great step-by-step guide to solving the problem, it's a post that has really made a difference on this issue. Hopefully BN can get their act together soon and fix this.

by on

I agree. I got it working thanks to the ten step approach, which really was pretty easy, once I was able to login to make the changes to my router configuration. That was hard because of the security set up on the router, but Verizon helped me do that. It seems unconsciounable that Barnes & Noble simply tells someone they don't support the router. And why not. Every other piece of wi fi, i have works with it.

by on

This is unaceptable. I guess I have no choice but to return this stupid thing.

I think everyone in this thread should get online where ever these are veing sold and start leaving negative reviews and let people who are considering buying a Nook that this problem exists.

Potential customers need to be warned about the lack of support and potential for frustration and ending up with a product that does not work.

Thats what I intend to do.

by on - last edited on

OK guys, poking around on the inside of my nook, it looks like the 1.1.0 update brought us a new version of WLAN driver, which can be found at:

/system/etc/wifi/tiwlan_drv.ko

I highly doubt that B&N's techs wrote this driver, unless they were using some extremely specialized chipset...which makes no friggin' sense. No configuration files - which were likely written by b&n...some cool tidbits in there, like the fact that the NST uses Google's DNS servers - were changed between the two releases, except that a minor config file here:

/system/etc/dhcpd/dhcpd-hooks/01-test

is no longer included in the 1.1.0 release. This file doesn't do anything except echo print a few things to a log file somewhere, so I'm gonna deem it irrelevant.

This means: we can yell at bn for not doing the obvious thing and releasing a stopgap 1.1.1 release post-haste that just has the old driver in it.

Luckily, I made myself a full backup of my nook running 1.0.0 (which is how I know the files were different - I diffed anything I thought might have caused the changed between the two), so I got the old driver out and copied it over.

It is then relatively easy to fix everything, for good, without having to run an extra app like Wifi Static or changing *anything* in any router anywhere IF you have root AND have a way to shell into your nook:

1. Download the old file from here.

2. Fire up a terminal and adb shell into your nook.

2a. I'm assuming that you're smart and have already added the adb command to your path. If not, then modify your commands accordingly.

3. Run the following command to make your /system partition writable:

mount -o remount,rw /dev/block/mmcblk0p5 /system

4. Exit the Nook's shell, and then copy the current WiFi driver from your nook to your computer:

adb pull /system/etc/wifi/tiwlan_drv.ko tiwlan_drv_1.1.ko

5. Push the old 1.0 WiFi driver to your Nook (assuming you're already in the directory where the driver downloaded in step 1 is):

adb push tiwlan_drv_1.0.ko /system/etc/wifi/tiwlan_drv_1.0.ko

6. Shell back into your nook, do some removing and renaming, and reboot your nook.

adb shell
cd /system/etc/wifi
rm tiwlan_drv.ko
mv tiwlan_drv_1.0.ko tiwlan_drv.ko
reboot

Upon rebooting, your Nook should be able to connect to your router without issue. But this isn't enough of a test. I rebooted my router, shut off wifi on my nook, and removed any configuration from WiFi Static...and it still works! There ya have it folks.

by on

Lastsilmaril - once again thank you for your help. Unfortnately, I have no clue about "rooting". It sounds like your NOT talking about using explorer to look in the root dir on the Nook, so Im long lost. Im sure 99.9% of Nook owners will be be in the same boat Im in.

By the way, I managed to hook up with the CHAT tech support on the Bn site. After explaining the problem, the tech suggested I make the nook 'forget' my connection, turn off the nook and re-try - even though I had told her I already did that at least 30 times. Then she wanted me to turn off my router and turn it back on - been there done that too.

So then she wanted to do a replacement on my Nook - BUT - I had to give a CC# incase they decided it was something I had done or if I failed to maiil the old one back in.

I asked why she thought it was a hardware problem when it connected fine before the software change? She said they want mine back to see why it wasnt connecting.

I declined. I then returned my Nook to Best Buy and got an exchange unit with no hassle at all. It connects fine. The customer service person at Best Buy said these were coming back like crazy for connection issues - so we are not alone!

I wont do the up-date until they get this fixed.

I also left negative feedback on this site and on the Best Buy site explaining the problem.

by on

If the fix is that simple, why the heck dont they issue a fix?????????????????????????????

by on

Yes yrralbn, the post wasn't really written for laymen. In order to connect to your nook and really see and be able to manipulate *everything* on it (*real* root access) you need to have the development kits for both Java and Android installed and follow one of the guides at xda. There are several, and I'm not sure which one is the best at this point - I've had almost 100% success doing everything manually - but in any case they can be found here:

http://forum.xda-developers.com/forumdisplay.php?f=1201

And thanks for the anecdote from Best Buy about many people returning Nooks due to connectivity issues. Maybe that'll wake'm up...

by on

"rooting" is beyond my skill level. Thanks for the link, but I would sure to screw it up,

One other note - if you decide to return your Nook, you should UN-register it and erase it. otherwise, your name and e-mail, BN password etc will be there for someone to possibly get ahold of.

However - you cannot do that if you dont have wifi access!!!!

Fortunately, the customer service person at Best Buy offered to log my return Nook onto their network long enough to erase it before I returned it.

You could probably do that at many hot spots before returning it. id recomend you do that.

by on

Everyone: I was a bit too harsh with b&n just now, it seems. I just rooted my brother's Nook and adb'd the old WiFi driver onto it (over usb - at no point after updating to 1.1.0 did the Nook ever have a working WiFi conection), and the 'Unsuccesful' problem persisted. So there is clearly something else at work here that I'm missing (not being a true expert at internals; I'm really just dipping my toe in here.

I fully expect my nook to eventually stop connecting to the router soon enough.

by on

The WLAN driver *did* change, however - that much is plain.

by on

Great job LastSilmaril!! that's engineering.

by on - last edited on

This is not engineering; this is flying blind I would never insult engineers by claiming to be one, and in any case, still have not found a real fix.

Anyway, using the old wifi driver doesn't work. It was only working because uninstalling WiFi Static doesn't disable static ips on the nook. In order to do that, you've got to

adb pull /data/data/com.android.providers.settings/databases/settings.db
sqlite3 settings.db
update system
set value="0"
where name="wifi_use_static_ip";
.q
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
adb reboot

And then, WiFi will cease to work with the problem routers. I have finally set up adb over usb, so this isn't a problem for me, and the old fix, setting 'static' ip on the router side, still works once you reset your router.

Oh, and there are several other things that can be cleared in this db related to static ips, but it's not necessary to:

wifi_static_ip
wifi_static_gateway
wifi_static_netmask
wifi_static_dns1
wifi_static_dns2

by on

Super. My Simple Touch no longer connects to Wifi. Yes, I have FiOS. That router is truly a POS. My Roku had a difficult time connecting to it too. Though that issue prompted me to change from WEP to WPA2.

Since then I've added a Linksys router hanging off of the FiOS router and the setup is very delicate. I don't want to have to adjust things that worked FINE before B&N released an impropery tested update. Ridiculous. It's not incumbent on me or any of us to "fix" our broken Nooks.

B&N needs to fix this.

And they dam well ought to be monitoring this thread since it's 7 pages of people complaining about their product being broken. By them.

by on

Thank you for your post. We have Verizon FiOS and a Actiontec router. I have never tried to change an IP address and I was worried I would mess something up. However I followed you directions and it worked. I bought a NST in September and it worked fine until I tried to download books in November. I could not connect to the internet. I followed the directions on B & N's site and from customer support. After doing everything again with customer support on the line they said it was a faulty NST and to send it back. The only thing I did not do was try to connect to a different wireless router. I assumed it had to be the NST because everything else in the house worked with the internet-computers, nook color, IPod touch, daughter's IPhone, and a Kindle. They sent me a preowned unit. In less than two weeks the preowned unit would not connect to the internet. That is when I saw your reply to some one else's cry for help on the message boards. Now I am upset that I have a preowned unit when there was nothing wrong with my originl unit. If B & N is aware there is a problem why doesn't their support service tell people to try your solution first rather than send the NST back and get a replacement? Next time I have a problem I will look @ the message board first then call customer support.

by on

I'm sorry to hear that you went through the trouble of getting a pre-owned unit when you didn't need to, but am glad it worked out.

by on

Technologirl wrote:
Super. My Simple Touch no longer connects to Wifi. Yes, I have FiOS. That router is truly a POS. My Roku had a difficult time connecting to it too. Though that issue prompted me to change from WEP to WPA2.

Since then I've added a Linksys router hanging off of the FiOS router and the setup is very delicate. I don't want to have to adjust things that worked FINE before B&N released an impropery tested update. Ridiculous. It's not incumbent on me or any of us to "fix" our broken Nooks.

B&N needs to fix this.

And they dam well ought to be monitoring this thread since it's 7 pages of people complaining about their product being broken. By them.

Hey, I think BN should be flogged for this, too - as well as for a shelving system that (a) doesn't persistently keep sideloaded books on SD cards in the shelves you assign them to (b) doesn't let you sort on books that are unshelved or have an easy way to know which books are on *multiple* shelves.

Did my solution not work for you then? I would at least try it out - it's a good stopgap measure and doesn't require you to have another router set up specially for the Nook or to have your Nook rooted.

by on - last edited on

I hated to do it because I really liked the form factor of the NST, but I ended up returning my nook due to the connectivity issue. I have a Linksys router. My husband set it up this past summer. I really don't know anything about router's and my husband was too busy to play around with it for me to get my nook to connect. I bought the limited edition nook on black Friday and returned it this past Saturday.

I still have my 1st Gen Nook which I love. I'll wait and see what happens with NST and how quickly B&N comes up with a fix before I purchase again. I'm afraid I'm just not tech savvy enough to attempt any of the work arounds and I"m afraid I'll mess up our router connections or compromise the security/functionality of our other devices which would not lead to wedded bliss!

by on

luvbooksCM wrote:
I hated to do it because I really liked the form factor of the NST, but I ended up returning my nook due to the connectivity issue. I have a Linksys router. My husband set it up this past summer. I really don't know anything about router's and my husband was too busy to play around with it for me to get my nook to connect. I bought the limited edition nook on black Friday and returned it this past Saturday.

I still have my 1st Gen Nook which I love. I'll wait and see what happens with NST and how quickly B&N comes up with a fix before I purchase again. I'm afraid I'm just not tech savvy enough to attempt any of the work arounds and I"m afraid I'll mess up our router connections or compromise the security/functionality of our other devices which would not lead to wedded bliss!

I think the key, and a rule I did not enforce this time that I usually do, is to keep Wifi turned off and don't let any device update its own software for at least 6 weeks post release date. I keep my NC wifi off as weel as my first gen Nook wifi. Why I left this on, I don't know. Inattention I guess.

I hope they do fix the problem.

LastSilmaril, I just don't know which router to make these adjustments on. I'm not kidding, this setup literally took hours and hours to get working. I use 2 routers, the FiOS is my moca bridge and DHCP server but wireless is turned off. My Linksys is connected via Ethernet and serves up the wireless. I am just not willing to mess with the setup. It poses the potential to mess up too much.

I can live without the wifi connection for a few weeks, but then, I'm returning the device. The first reports of problems go back a month now. No reason they couldn't fix the problem in that time if they chose to.

by on

There is no incentive for B&N to fix this problem. They are relying on the nook community to come up with a workaround that keeps most people happy or at least learn to live with the problem, after having loaded X books onto the thing.

They days of product (& software) quality control are long gone. You (we) are the quality testers (and problem solvers).

by on - last edited on

Technologirl wrote:
luvbooksCM wrote:
I hated to do it because I really liked the form factor of the NST, but I ended up returning my nook due to the connectivity issue. I have a Linksys router. My husband set it up this past summer. I really don't know anything about router's and my husband was too busy to play around with it for me to get my nook to connect. I bought the limited edition nook on black Friday and returned it this past Saturday.

I still have my 1st Gen Nook which I love. I'll wait and see what happens with NST and how quickly B&N comes up with a fix before I purchase again. I'm afraid I'm just not tech savvy enough to attempt any of the work arounds and I"m afraid I'll mess up our router connections or compromise the security/functionality of our other devices which would not lead to wedded bliss!
I think the key, and a rule I did not enforce this time that I usually do, is to keep Wifi turned off and don't let any device update its own software for at least 6 weeks post release date. I keep my NC wifi off as weel as my first gen Nook wifi. Why I left this on, I don't know. Inattention I guess.

I hope they do fix the problem.

LastSilmaril, I just don't know which router to make these adjustments on. I'm not kidding, this setup literally took hours and hours to get working. I use 2 routers, the FiOS is my moca bridge and DHCP server but wireless is turned off. My Linksys is connected via Ethernet and serves up the wireless. I am just not willing to mess with the setup. It poses the potential to mess up too much.

I can live without the wifi connection for a few weeks, but then, I'm returning the device. The first reports of problems go back a month now. No reason they couldn't fix the problem in that time if they chose to.

Hmm...what you're describing to me doesn't sound like too complicated a setup, but I understand your trepidation. All you did is shut off WiFi on your router and added an AP in bridge mode, right?

If your Linksys is only serving as an AP, and the ActionTec is your DHCP server - you should see your wireless devices come up under 'my network' - then by all means you should backup your settings and then go through the process I detailed here. It should not impact this bridge you've got set up in the slightest.

But, to make sure, why don't you post a link to the exact bridging process you used, in case I misunderstood?

by on - last edited on

In any case, everybody, I think I've isolated the issue here to one file, /system/lib/libnetutils.so, which is easy to replace if you're rooted. It's almost 100% perfect - only failed to reconnect to wifi from sleep once, out of maybe 10-20 wake-from-sleep events - and just clicking wifi on/off fixes this. This is such a small tradeoff to make for working WiFi in general that it is almost certainly worth trying.

Here's the link to my thread at xda with instructions. I need people to try this out to make sure that this is a valid fix!

http://forum.xda-developers.com/showthread.php?t=1372239

by on

I'm considering buying the Nook Simple Touch for my husband for Xmas. We have Verizon Fios. The router we have is Actiontec M1424WR Rev D. I have heard Rev F mentioned. Does anyone know if people with Rev D are experiencing this wifi problem?

by on

Please HELP!!!!! I have called BN tech support, NetGear tech support and Comcast with no results!!! I, like everyone else on here cannot get a wireless connection. Comcast wanted to charge me $75 for their help!! Someone has to have the same problem as I do??? I need step by step if anyone has a NetGear router, PLEASE!!! I don't have a problem with any of my other wireless devices except the Nook Color.

by on

I have the 1.3.0 updated version for Nook Color.

by on

I have a Linksys router and this solution worked for me. I changed the "Wireless Network Mode" to "G-Only" then clicked "Save Settings." (The default setting was "Mixed," meaning a combination of B, G, etc.) I then powered off my Nook, turned it back on, and all is working fine.

The Linksys setting above can be found under the "Wireless," then "Basic Wireless Settings" menus.

Good luck!!

by on

LastSilmaril - After saying that Rooting was beyond me, I decided to try it. It took me 3 days of cussing and sweating and many failed attempts, but I finally managed to get my replacement Nook rooted and working great - on 1.0.1.

Then it died. Im getting a new one today from Best Buy. It will likely come with 1.0.1, so I will make a back up of that one before trying any changes.

I read your thread above with great interest, BUT I cannot follow much of your newest fix. I did get ADB installed finally and I thiink it was even working, but Ive never used it before.

Could you possibly add to your instructions a bit to make them more verbose for noobs like me?

Id like to be able to get rooted on 1.1.0, but dont think I can do it as is.

Thanks again so much for all your efforts so far!!!!

by on

Reed1 - I will give your methode a try with my Westell router when I get my new Nook.

This is my second one by the way.

I bought mine from best Buy. I returned the first one hoping a replacement would connect ok on 1.1.0 - didnt work.

Then, yesterday, the replacement decided to refuse to power on, so its going back today.

Im really close to changing over to a Kindle......

By the way - I got an e-mail back from customer service finally. They said they were working on a solution and hoped to have it any time now. They must only have one software guy who only works on alternate good fridays.

by on

yrralbn wrote:
They must only have one software guy who only works on alternate good fridays.

Yes, and who doesn't read XDA-Developers.

by on

Can't swear it, but I'm likely Rev. D, since I have the original Actiontec FiOS router.

ljk

Beach57 wrote:
I'm considering buying the Nook Simple Touch for my husband for Xmas. We have Verizon Fios. The router we have is Actiontec M1424WR Rev D. I have heard Rev F mentioned. Does anyone know if people with Rev D are experiencing this wifi problem?

by on

LastSilmaril wrote:
Technologirl wrote:
luvbooksCM wrote:
I hated to do it because I really liked the form factor of the NST, but I ended up returning my nook due to the connectivity issue. I have a Linksys router. My husband set it up this past summer. I really don't know anything about router's and my husband was too busy to play around with it for me to get my nook to connect. I bought the limited edition nook on black Friday and returned it this past Saturday.

I still have my 1st Gen Nook which I love. I'll wait and see what happens with NST and how quickly B&N comes up with a fix before I purchase again. I'm afraid I'm just not tech savvy enough to attempt any of the work arounds and I"m afraid I'll mess up our router connections or compromise the security/functionality of our other devices which would not lead to wedded bliss!
I think the key, and a rule I did not enforce this time that I usually do, is to keep Wifi turned off and don't let any device update its own software for at least 6 weeks post release date. I keep my NC wifi off as weel as my first gen Nook wifi. Why I left this on, I don't know. Inattention I guess.

I hope they do fix the problem.

LastSilmaril, I just don't know which router to make these adjustments on. I'm not kidding, this setup literally took hours and hours to get working. I use 2 routers, the FiOS is my moca bridge and DHCP server but wireless is turned off. My Linksys is connected via Ethernet and serves up the wireless. I am just not willing to mess with the setup. It poses the potential to mess up too much.

I can live without the wifi connection for a few weeks, but then, I'm returning the device. The first reports of problems go back a month now. No reason they couldn't fix the problem in that time if they chose to.
Hmm...what you're describing to me doesn't sound like too complicated a setup, but I understand your trepidation. All you did is shut off WiFi on your router and added an AP in bridge mode, right?
If your Linksys is only serving as an AP, and the ActionTec is your DHCP server - you should see your wireless devices come up under 'my network' - then by all means you should backup your settings and then go through the process I detailed here. It should not impact this bridge you've got set up in the slightest.
But, to make sure, why don't you post a link to the exact bridging process you used, in case I misunderstood?

I'll see if I can find the instructions ... I think it was from the DSL Reports web site. I'll post back if I can locate the setup.

by on

Adding my +1 to a NST that won't connect via a Verizon Fios router.

If B&N is cool with not fixing this, I'll continue to buy my books from Google. The longer they ignore this problem, the more money I'll give their competitors.

by on

I just found that I was having a problem connecting with my FIOS router with my Nook plugged into my PC's USB port. When I unplugged the usb cable and tried again it connected right away to my wifi. Not sure if this will help anyone else but I figured I'd throw it out there...

by on

There was a notification message on my NST today saying it upgraded itself to firmware 1.1 version.... like everyone else here, wifi fails to connect.

I guess it won't be able to upgrade itself ever again =)

by on

I got my NST V1.1.0 working with wifi and internet access by configuring the router for static IP addressing. It literally took three minutes. I normally do assign static IP leases to all my devices to help segregate their functionality - PCs,Servers, VOIP adapter etc. So far, the router static IP address method is a viable working around. Not perfect but it works.

I also got my old Linksys WAP54G access point to work behind my router. You can buy this G speed AP on e-bay for $15-$20. Not difficult to configure, but you got to be tech savy.

by on - last edited on

I had a similar situation but returning the NST would have been my last choice. Hardware wifi failure are possible, but unlikely since most wifi chips are robust and reliable. After doing an initial registration with BN using V1.0.0, I knew my NST wifi and my wifi access point were fine. I did a manual update to V1.1.0, but I didn't test the NST wifi until I tried it on my sister's wifi router. My wifi didn't connect and my sisters V1.1.0 NST also had similar results. Two NST with hardware issues are possible but very unlikely. So it was either the V1.1.0 or my sister netfgear router wifi connection. Back home, i tried my linksys access point and the NST, still no wifi connection. T wo different routers with similar wifi problems, difficult to accept that is a router issue. The only thing that changed was the firmware. Now it is time to read the forum. After 15 minutes, sorting through the non-technical issues ( ie personal NST stories ), the static IP address solution became apparent. In three minutes, I admin into my buffalo DD-WRT router, entered an IP outside of the DHCP range, etc. And as expected it worked. (tech note: I have a router and a separate access point. The fix goes in the router, since it forwards the assigned IP address to the attached access point.) I have completed integration testing on the same router but with a different access point linksys WAP54G and it looks good so far.

When I spoke, to the BN tech support, she was frustated too, and asked if her Linksys WRT54 router supported static IP lease cpabilities. I am not sure, I am reading very conflciing info on the linksys forums. Someone posted the following: "DHCP reservation is a pain in the WRT54G. It is located under Management on the Administration page about halfway down."

I have linksys routers but no longer have linksys firmware. So I cannot verify which models & versions support static IP leases.

Bottom - line, the work-around is a static ip address lease.

by on - last edited on

yrralbn wrote:
LastSilmaril - After saying that Rooting was beyond me, I decided to try it. It took me 3 days of cussing and sweating and many failed attempts, but I finally managed to get my replacement Nook rooted and working great - on 1.0.1.

Then it died. Im getting a new one today from Best Buy. It will likely come with 1.0.1, so I will make a back up of that one before trying any changes.

I read your thread above with great interest, BUT I cannot follow much of your newest fix. I did get ADB installed finally and I thiink it was even working, but Ive never used it before.

Could you possibly add to your instructions a bit to make them more verbose for noobs like me?

Id like to be able to get rooted on 1.1.0, but dont think I can do it as is.

Thanks again so much for all your efforts so far!!!!

Well I'm not going to completely restate everything that's out there, and there's a great thread on this at xda already, but I'm gonna add some minor points. Note that I am not responsible in the slightest if your Nook ends up becoming uh, a very light brick

Also, this guide is for firmware 1.1.0. Do NOT follow it unless you have already updated.

This is assuming you have already installed the Android SDK for 2.1 and have adb and the adb usb driver package. (The usb drivers are an optional part of the Android SDK installation, just look around a bit in the list.) You might want to add adb to your path; if you don't know how to do that, here's how:

http://geekswithblogs.net/renso/archive/2009/10/21/how-to-set-the-windows-path-in-windows-7.aspx

OK, ready?

1) Download this:

http://www.multiupload.com/OFI609MP8V

2) burn the image you downloaded from the link above to a microSD card using this software:

https://launchpad.net/win32-image-writer/+download

Make sure you select the right drive letter, or you will regret it.

3) shut off your nook, pop your microSD card in it, and start it back up.

4) BACKUP.

http://forum.xda-developers.com/showpost.php?p=15115162&postcount=2

Make sure the resulting file is around 2GB, or more precisely, around 1958 or 1962 MB. This file can then be compressed considerably using your favorite compression scheme (I use lzma/7zip) if you're worried about diskspace.

5) Download this: http://www.multiupload.com/RLU6A9B6Y2 If you are not using firmware 1.1.0, then this file will NOT work for you. You have been warned.

Your computer should see a small fat32 partition called boot. If not, assign it a drive letter with MiniTool (one of the programs you downloaded in part 4) or diskmgmt.msc. Then, copy the file you downloaded just now straight into the root of the drive.

6) Disconnect your nook, remove the microSD card, and reboot your nook. Might take a little bit of holding the power button for it to respond (sometimes 10 secs or so), but it eventually will.

7) Hopefully, your nook is rebooted and everything works (you won't notice anything different). Now, you'll want to modify the ADB USB drivers so that your nook will get recognized per this post:

http://forum.xda-developers.com/showpost.php?p=19342931&postcount=12

8) Connect your nook, open up the command line, and type "adb shell". If all goes well, you now have console access to your nook internals!

9) But you don't have 'root' per se, and can't really do that much, until you follow the instructions in this post:

http://forum.xda-developers.com/showpost.php?p=20069222&postcount=3

You now have root f'real!

Now, if you all you want to do is fix WiFi, you should follow the instructions I made here:

http://forum.xda-developers.com/showpost.php?p=19897624&postcount=1

by on

Oh, and, of course, all credit to those at xda and nookdevs who made all this possible.

by on

Does anyone know if the NookST will connect to a Netgear WGT624 v3? I tried the static IP fix and it does not seem to be working. I was planning on replacing my router soon with a D-Link. Everything else in the house connects fine including my rooted Nook Color.

by on - last edited on

FWIW, I have a Netgear WNR2000 v3, and I haven't had a speck of trouble getting my NST to connect, neither on 1.01 nor on 1.1. My network security is configured as WPA2, and all devices other than my network printer use dynamic address assignment.

Of course, your Netgear is a different model and may have different software.

by on

Add me to the list of frustrated Nook owners. I am going to try the work around of assigning my Nook a static IP Address, but this certainly explains why my Nook won't work at home, but works at the office (Cox), B&N store and even connected to my friend's FiOs router ... she lives about 2 hours away from me so she must have a different Rev. or whatever.

by on

Thanks! Your solution worked great for me...excellent instructions.

by on

Our Nook also stopped connecting. Went to a B&N store and was told to contact Verizon and/or Nook Tech. Had a 20-30 minute conversation with NOOK Tech but could not resolve problem. Finally was directed to take NOOK back to B&N store and would receive new one in mail.

Went home and googled the NOOK connection problem and found "LastSilmaril" fix. My geek son followed the directions and within a few minutes our NOOK was working fine. Had recently switched from COX to Verizon.

Following day received email from B&N quering about quality of Tech support. Advised the agent was most professional and tried hard but was unsuccessful. Advised would never purchase another NOOK because B&N does not support it. Why it does not know what 'LastSilmaril" knows is beyond me. Advised can you imagine the complaints B&N will have in the Washington area when all the Christmas NOOKS will not connect to Verizon!!!!

by on

! have been without WiFi connectivity for my NST for 45 days -- I just got around to checking for a solution to what I thought was a "one off" problem. I was amazed to see how widespread this issue is. I was amazed because I had been down the B&N support path....that leads to a dead end. I applied the workaround found here -- assign a static IP -- and I was up and running on WiFi again. Many thanks for all your help! How is it that B&N can continue to be so obtuse on this issue, given how many people it seems to effect? How about a "heads up" B&N? Sheese.

by on - last edited on

Well, I am one of those masses who purchased a couple of NST's on Black Friday and have now discovered the incompatibility with the Actiontec routers. I'm not tech savy enough to reconfigure my router (tried but apparently the tech who installed it changed the username and password from the default, and I'm not willing to completely risk every other connection with the router by resetting to factory defaults and consequently losing SSID and WEP codes to fix a B&N software bug). So, I've sent a note to B&N tech support asking when version 1.1.1 will be released fixing this bug. If it's not before the return deadline for my NST's (I bought two, one for me and one for my son as Christmas gifts), then they're both going to be returned with regrets. I love the device and its features, but if this is the type of tech support they're going to receive then I'd not want to invest in purchase of lots of books on a device that could stop working at any time.

by on - last edited on

Can someone tell me why I have to go through all this just to fix a problem that should just work? I'm done with Barnes & Noble and their terrible customer service and their terrible products. I got the Nook Simple Touch for Christmas and this is the second Nook I've owned in terms of form factor but I went through 4 of the original Nook tablets and had to deal with that terrible thing that they termed a touch screen and now I get the new Nook Simple Touch that has a wonderful interface and I can't read a book on it? This is ridiculous. I love how this thread has nine pages of people helping other people who bought Nooks but can I recommend to everyone to just get a Kindle quite blaming it on the router I've had no other problems with my other devices connecting to the router its the POS Nook not the router people. Barnes & Noble doesn't care about any of you they just want your money so that their brick and mortar store doesn't go out of business but if they keep providing support like this then I hope they go out of business much sooner rather then later.

by on

Herffinator wrote:
Can someone tell me why I have to go through all this just to fix a problem that should just work? I'm done with Barnes & Noble and their terrible customer service and their terrible products. I got the Nook Simple Touch for Christmas and this is the second Nook I've owned in terms of form factor but I went through 4 of the original Nook tablets and had to deal with that terrible thing that they termed a touch screen and now I get the new Nook Simple Touch that has a wonderful interface and I can't read a book on it? This is ridiculous. I love how this thread has nine pages of people helping other people who bought Nooks but can I recommend to everyone to just get a Kindle quite blaming it on the router I've had no other problems with my other devices connecting to the router its the POS Nook not the router people. Barnes & Noble doesn't care about any of you they just want your money so that their brick and mortar store doesn't go out of business but if they keep providing support like this then I hope they go out of business much sooner rather then later.

Perhaps you should first read all the posts about Wifi problems in the Amazon Kindle forum before recommending a Kindle. There is no Wifi device that works with all Wifi routers, settings and configurations.

by on

A salient point here would be that THIS tablet worked with pretty much all makes of routers until they issued 1.1.0.

Why defend B&N ... they released poorly tested software. People need to be accountable for screw-ups ... otherwise they become Borders.

by on

Technologirl wrote:
A salient point here would be that THIS tablet worked with pretty much all makes of routers until they issued 1.1.0.

And it works with most of those "pretty much all" now; a single setting needed to be changed in most cases. A single setting.

by on

Thanks so much for your information. I was trying to connect to our Actiontec fios router for hours. When I did a search, I came upon your thread and was able to get my daughter's new Simple Touch connected. I didn't have this problem with my or my other daughter's Nook 1st editions, or any other devices in our household. I am so appreciative to you. Thanks again. We're now up and running.

by on

Ya_Ya wrote:
Technologirl wrote:
A salient point here would be that THIS tablet worked with pretty much all makes of routers until they issued 1.1.0.

And it works with most of those "pretty much all" now; a single setting needed to be changed in most cases. A single setting.

Well, I had the opposite problem with my mom's NST. Her's would not connect to her Netgear router. I finally got to her house to update her to 1.1.0 and amazingly, it now connects to the router without any issues. Mine also connects without a problem to her Netgear router without a problem and my Linksys router without issue. In fact, with the exception of my mom's problem, I've never run into a wifi connection problem with any of my Nooks.

by on

Same problem. I PM'ed my info to BN_alexG. ActionTec Verizon FiOs router. WiFi wouldn't work after version 1.1.0 was downloaded. I reset the Nook back to the previous version, but then it downloaded 1.1.0 again and the same problem occurred. I called Tech Support and they couldn't fix it. Live chat tried to blame it on me not knowing the WEP key. It's been over a month since I had this problem but it looks like there's still no fix from B&N?

by on

How do I even log onto the router in the first place? I can't find it under Control Panel, any of the Verizon folders or programs, and there's no ActionTec folder or program anywhere.

I tried to go to the website where you have to go in the first place to configure the router during setup ( http://192.168.1.1 ), and that looks like where you say to use admin and password 1, but I tried that and it doesn't work. And if the password or username was ever changed, the person in my family who would've changed it didn't write it down and can't think what it would be. Great.

by on

The browser typically has an IP address of 192.168.1.1 or 198.168.0.1.. Just type one of those into your browser where you usually type your URL. Most likely your router has a password that you need to know to access it after that.

by on

Oops- Above should say the router has an I.P. address of 192.168.1.1 or 192.168.0.1. Sorry about that.

by on

azeri wrote:
Same problem. I PM'ed my info to BN_alexG. ActionTec Verizon FiOs router. WiFi wouldn't work after version 1.1.0 was downloaded. I reset the Nook back to the previous version, but then it downloaded 1.1.0 again and the same problem occurred. I called Tech Support and they couldn't fix it. Live chat tried to blame it on me not knowing the WEP key. It's been over a month since I had this problem but it looks like there's still no fix from B&N?

If you leave wifi turned on in the NST, then it will download any updates automatically. Considering how often B&N breaks readers with their poorly tested updates, I don't recommend leaving wifi turned on. If you purchase books, turn it on until those books download, then turn wifi off.

Let other people beta test their software, or go through workarounds.

by on - last edited on

LastSilmaril,

Thank you very much for your detailed instructions! That did the trick for me.

The only hiccup I had (due to my own stupidity ) was I didn't assign the address for the Nook outside of the DHCP range the first time. Once I did that, it worked right away.

If anyone else is looking for LastSilmaril's directions, they are on page 3 of this topic.

by on

I'm another user who couldn't connect after the update.

I tried all the given advice but it wouldn't work. I have a Netgear WPN824v2 router which is pretty old. Setting a reserved IP address for the nook didn't work, updating the firmware of the router didn't work, I can't even remember what all else I tried.

For anyone else who has a similar router, the only fix I finally found was to use WPA not WPA2. It doesn't work if you use both either. Which is a shame because I would prefer to use the more secure WPA2.

The good thing about this adventure I've been on today, I found someone leaching wifi from me. How? I have no clue. But I'm glad to have kicked them off my router

by on

Yeah, that sounds like my best plan for now. I'll reset it again then turn it off.

by on

I'm using a Netgear WGR614v7 router running the newest firmware (V2.0.30_2.0.30NA). I just bought two nook simple touch readers today. The first one connected to my wifi network just long enough to register it. The second one can't connect at all so is about as useful as a brick (less useful actually since you can build things with bricks). Both now fail in obtaining an IP address.

I've tried pretty much every suggested fix except the completely idiotic ones like turning off your security (seriously??). I'm using WPA2-PSK [AES] on a B/G network channel 11. I have a kindle, an ipod touch, 2 desktop computers, 2 laptops, an ipod touch, a droid bionic and a samsung galaxy all connected fine to the router so I don't think there is anything wrong with how it's setup.

I've tried restarting the Nook, setting a static IP address for it on the router, changing security from WPA2 to WPA and then back to no avail. As much as I enjoyed using the Nook at the store, I'm not really in the mood to root a brand new product to get it to work. I think I will be returning both nooks and the cases and asking for a refund on the books I purchased in the 5 minute window that the the device was working.

by on - last edited on

sarus wrote:
I'm using a Netgear WGR614v7 router running the newest firmware (V2.0.30_2.0.30NA). I just bought two nook simple touch readers today. The first one connected to my wifi network just long enough to register it. The second one can't connect at all so is about as useful as a brick (less useful actually since you can build things with bricks). Both now fail in obtaining an IP address.

I've tried pretty much every suggested fix except the completely idiotic ones like turning off your security (seriously??). I'm using WPA2-PSK [AES] on a B/G network channel 11. I have a kindle, an ipod touch, 2 desktop computers, 2 laptops, an ipod touch, a droid bionic and a samsung galaxy all connected fine to the router so I don't think there is anything wrong with how it's setup.

I've tried restarting the Nook, setting a static IP address for it on the router, changing security from WPA2 to WPA and then back to no avail. As much as I enjoyed using the Nook at the store, I'm not really in the mood to root a brand new product to get it to work. I think I will be returning both nooks and the cases and asking for a refund on the books I purchased in the 5 minute window that the the device was working.

See reply 97 from this thread:

http://bookclubs.barnesandnoble.com/t5/NOOK-Simple-Touch-Support/updated-to-1-1-0-now-wireless-will-...

According to this post with your router Nook will not connect when using AES, but only when using TKIP.

by on

Strongly consider the return/refund option. I bought one on December 15, charged it, created an account and put it under the Xmas tree for my daughter. The Simple Touch ugraded on its own on the evening of the 29th, I called BN on the 30th. My first round of troubleshooting/escalation on that Nook resulted in BN tier 2 support telling me that the patch was 2-3 days away and could I be patient. he would call me back in 2-3 days to make sure everything was resolved. Needless to say, no call. I called back last week, and after more troubleshooting/escalation to Tier 2's supervisor, no solution offered except to call "corporate" and complain. I asked for a refund and was told that I was out of the 14 day window.

Run, don't walk, to get a refund. This software update is not ready.

by on

Followed your directions step by step and thoroughly and THEY WORKED! I have the pain the arse Actiontec router and it connects to other WIFI with no issues but for this one the manual IP static conncection set up worked flawlessly! I used 192.168.1.150 for my Nooks IP address and, boy, have you relieved a lot of stress and annoyance that I definitely do not need at the moment.

Thank you so much to you and to everyone for their attempts and fixes for the Nook community. We'd be up sh*ts creek with no paddle if it weren't for all of you!

by on

I too can confirm this issue. I am using an Apple Airport Extreme and an Apple Airport Express in extended mode. After the 1.1.0 update, my NST would read "Connected, but no internet". None of the troubleshooting steps fixed the issue. I currently have to reboot my Airport evertime I want to use the Nook's wifi. Setting a dhcp reservation did not solve the problem. I would prefer not to root my nook to fix this problem. Currently I am leaning towards returning it.

by on

Thank you LastSilmaril...your steps worked perfectly just when I was about ready to throw the Nook out the window

by on

Add me to the list of people having this problem. My router is

Netgear WGR614v6 54 Mbps Wireless Router

I didn't know the problem was caused by the upgrade to 1.1 so at the Barnes and Noble store they graciously gave me a refurbished Nook which I took home and it worked!! ... until it upgraded today to 1.1.0 and stopped working.

by on

Callimachus wrote:
Add me to the list of people having this problem. My router is
Netgear WGR614v6 54 Mbps Wireless Router

I didn't know the problem was caused by the upgrade to 1.1 so at the Barnes and Noble store they graciously gave me a refurbished Nook which I took home and it worked!! ... until it upgraded today to 1.1.0 and stopped working.

http://bookclubs.barnesandnoble.com/t5/forums/forumtopicprintpage/board-id/STReader/message-id/1527/...

by on

Thanks Technologirl. I will give that a try. I talked to BN support yesterday and they said they were working on a fix. I have a Nook Color and a Nook original so I can cope. After I buy a book on my Nook Color I can go to work and use their wi-fi to get my book on my Nook Touch but it is irksome.

Hi, I have the same router and same experience. It sounds like your Nook Color works with the Netgear Router, is that true?

Iconn

by - last edited

Dear

LastSilmaril

I bought the nooks for my two daughters at x-mas. Had problems with one of them two weeks later. Called Verizon and B&N and after trying everything they told me B&N asked me to return it as "faulty" and they sent me a new one!

A month later, it is again not connecting! I happened upon your post followed the steps and.....baaam!!! I am in!

Thank you so very very very much!!!!

Updated to version 1.1.2 on 3/12/2012.

Version 1.1 did NOT work on my Home router (Westell 7500)

Version 1.1.2 (the update) works on the 7500.

-Jack

I just got the 1.1.2 update and finally FINALLY I can connect to my wi-fi router at home!

It works ! !

Thanks, at last !

Well, I'm glad that it seems like B&N finally fixed this issue. As I have root, I'm gonna see if I could install the update without mucking up my setup

-e

I just picked up my new Nook Touch GlowLight and was sooo excited until I got it home and it would not connect to my network. I have been able to connect every other device (Nook, WI, a TV, IPod) with no problems. IT online chat guy told me it was a provider problem after a hard reboot and phone IT guy agreed. Since I have Comcast (eewww) I refused to call and wait on hold forever to be told there was nothing wrong so I went back to B & N and registered my device there. They also said it must be my provider...NOT! Did some looking around online and found your post, and all the praise!! I have a Linksys router but I followed your directions (page 3) and low and behold, the nook was immediately recognized by my network and connected itself I have never posted or replied to a post before but I wanted to say THANK YOU! You saved my family a little bit of crazy!

You must be a registered user to add a comment here. If you've already registered, please log in. If you haven't registered yet, please register and log in.

Post a Comment

Accepted Solution

Inspired Correspondent

Posts: 126

Registered: 07-30-2010

Answered

[ Edited ]

on 11-13-2011 11:45 AM - last edited on 11-13-2011 12:33 PM

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!

You must be a registered user to add a comment here. If you've already registered, please log in. If you haven't registered yet, please register and log in.

Post a Comment

Subject	Laurels
Re: updated to 1.1.0 now wireless will not connect	10
Re: Tech idiot can't obtain address	5
Re: updated to 1.1.0 now wireless will not connect	3
Re: Frustration in setting wallpaper	3
Re: Tech idiot can't obtain address	3

B&N Community

updated to 1.1.0 now wireless will not connect

Answered

Re: updated to 1.1.0 now wireless will not connect

Re: Tech idiot can't obtain address

Re: updated to 1.1.0 now wireless will not connect

Re: Frustration in setting wallpaper

Re: Tech idiot can't obtain address