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.
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.
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 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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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
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;
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.
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
or
adb shell command logcat > logcat.txt
and save yourself the step where you have to get the output back off your device.
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.
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.
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!)
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.
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..
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.
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.
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.
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
byleoda11-13-201108:07 AM - edited 11-13-201108:10 AM
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.
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:
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.
byscotta31611-13-201110:48 AM - edited 11-13-201111:07 AM
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.)
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. )
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.
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.)
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!
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.
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
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.
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??
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.
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!
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.
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.
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.
Keriflur: Thank you for the idea. Hopefully they will come out with a fix in the next week.
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.
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.
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
byLastSilmaril11-18-201102:23 AM - edited 11-18-201103:08 AM
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.)
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.
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.
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"
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.
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.
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.
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 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?
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.
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.
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...
Re: My NST's Netgear WGR614v6 WiFi doesn't work with 1.1 Update
After Nook Simple Touch updated to 1.1.0 on 11/12/11 on my home wifi, NST will not connect to home wifi but works in B&N store. NST worked for the prior two months on home wifi before update. Now connecting to Netgear WGR614v6 router using WPA/WPA2 PSK security, the response is “obtaining IP address … unsuccessful”. Have already tried changing security, MAC address after B&N telephone chat and 2 store visits. HELP!
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.
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.
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.
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.
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.
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?
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.
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.
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.
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.
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...
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).
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).
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?
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.
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.
