Answer
Distinguished Correspondent
LastSilmaril
Posts: 129
Registered: ‎07-30-2010
Accepted Solution
My NST's WiFi doesn't work with 1.1 Update

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 LastSilmaril ‎11-08-2011 07:20 PM - edited ‎11-08-2011 07:20 PM

My nook is a refurb, but I don't think that's at all relevant...

by ‎11-08-2011 07:22 PM - edited ‎11-08-2011 07:23 PM

LastSilmaril wrote:

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

 


Nope mine is working just fine after I installed the update yesterday.  

 

Now, my mom's does that a lot and it's been doing that since she got it, I was kind of hoping the 1.1 update would help it. But I won't know until I get to her house in December, because that's probably the earliest she's going to get the update unless she goes to a store, because it won't connect to her home WiFi 99% of the time.

 

Edit:  Mine is refurbished also.  Mom's was new.

 

by LastSilmaril on ‎11-08-2011 07:25 PM

Aha. 

Probably the WiFi driver or something got modified and is now somehow not compatible with my home router. I've seen that nonsense happen before but I'm disappointed that it happened with the nook.

Anyway there's a thread about this in the support forum, so I'm gonna head over there and repost this.

-e

 

by fuzzyballerina ‎11-08-2011 09:26 PM - edited ‎11-08-2011 09:36 PM

Mine doesn't work either. This is NOT a refurb...:smileysad: 

by fuzzyballerina on ‎11-08-2011 09:27 PM

Mine doesn't work either!!!

by LastSilmaril on ‎11-08-2011 11:10 PM

That makes a total of three of us so far, between this thread and the one in the technical forum. Uh-oh...

by lindajm22 on ‎11-09-2011 11:37 AM

Mine was not working initially as well but I got it working by "forgetting" the network and then reconnecting.  Now mine works fine.

by Administrator BN_AlexG on ‎11-09-2011 11:41 AM

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 LoveToRead51RW on ‎11-10-2011 08:31 AM

Mine doesn't work either.  I have Windows XP and Netgear wireless router.

 

by Starearedkid on ‎11-11-2011 09:39 PM

Mine doesn't work either! I have a MacBook Air and a Verizon Fios router. :smileysad: 

by on ‎11-11-2011 10:05 PM

You should PM Alex with your information, including the model number of your router.  To PM someone, click on the user's name (Alex has a message a couple of posts above yours, and over on the right, look for send this person a personal message.

 

I believe they are trying to collect information on what routers people seem to be having troubles with, since this problem doesn't appear to be affecting everyone.

by on ‎11-12-2011 04:14 AM

There's a very interesting report that at least one person with this problem after the update was able to resolve it by logging into the router, getting to the network administrative panel (it's called different things on different routers) and pinging the NST via its MAC address. 

 

Different routers need different ways of putting in MAC addresses.  Most use the address in the form XXXX:XXXX:XXXX:XXXX but some omit the colons between the character groups.  Try to ping a working computer by MAC address to be sure you're using the right way of inputting the MAC, then try pinging your NST. 

 

I'd love to konw if this fix works for a range of folks. 

 

My theory on why it worked is that the table the router keeps that tells it what MAC address can be found on which switch port can be corrupted by some very subtle difference in the new NST network stack. 

by jt4521 on ‎11-13-2011 07:52 PM

Who do these nimrods think buy these things? Under 30 IT professionals?.I live near St. Louis and went into the store in person today. "Why they've never heard of such thing." Really? Get on the boards and look; you'll find dozens of people just like us. So a nice lady clerk who knew NOTHING regardless of the fact she was assigned to the Nook corral called the the "store tech support." He knew nothing; his suggestions were (1) turn it on & off; (2) do a reset to its original factory settings; (3) call my ISP provider as if it were THEIR fault. None of those worked. The "original factory reset" by the way did NOTHING. It was still set at v 1.1.0 AND my all books were still there.  This was after I spent 45 minutes on Saturday on "chat now" with "Mandy" and "Paul" who were useless.

 

When I finish the books I have loaded, this sucker will go to Goodwill or be listed on e-bay for $35 (approx. what I spent on the cover). This is a glitch . BN is too stupid or too arrogant to fix or at least acknowledge. I retired so I didn't have to have idiots in my life; I will not now pay to invite them in. Amazon will be fine for me.

by on ‎11-13-2011 10:37 PM

jt4521 wrote:

Who do these nimrods think buy these things? Under 30 IT professionals?.I live near St. Louis and went into the store in person today. "Why they've never heard of such thing." Really? Get on the boards and look; you'll find dozens of people just like us. So a nice lady clerk who knew NOTHING regardless of the fact she was assigned to the Nook corral called the the "store tech support." He knew nothing; his suggestions were (1) turn it on & off; (2) do a reset to its original factory settings; (3) call my ISP provider as if it were THEIR fault. None of those worked. The "original factory reset" by the way did NOTHING. It was still set at v 1.1.0 AND my all books were still there.  This was after I spent 45 minutes on Saturday on "chat now" with "Mandy" and "Paul" who were useless.

 

When I finish the books I have loaded, this sucker will go to Goodwill or be listed on e-bay for $35 (approx. what I spent on the cover). This is a glitch . BN is too stupid or too arrogant to fix or at least acknowledge. I retired so I didn't have to have idiots in my life; I will not now pay to invite them in. Amazon will be fine for me.


I agree they need to fix this, but fixing a problem that doesn't affect everyone can be extremely difficult.  You have to narrow down the cause, why do some people have the problem and others don't (I haven't had any difficulties) and then determine a fix that doesn't break the ones that are working.  We run into this at work, we pretty much have identical computers, we can't load any software on our own, and yet we get computers that won't do something everyone else's will do.  The moderator here on the board asked people who are having problems to PM him with the information, including the router make, model, etc.  That's the only way their going to figure it out, is to get the information from the users and find the common denominator, because they can't test the update against every router and configuration being used today.  When the update to the N1E broke it and it wouldn't read SD cards right, there were hundreds, if not thousands of posts from people having problems.  So far, there aren't hundreds of posts about the WiFi issue.

 

You can go to Amazon, that's fine, there's room in the eReader world for both companies, but I don't understand why folks seem to think if they move over to Amazon, they're never going to run into any problems.

by DouglasGPerry on ‎11-13-2011 10:38 PM

I have exactly the same problem, which began right after the update. My NST can no longer connect with my home WiFi router. My NST works fine at B&N, but not at home. All of my other devices at home work fine with the router.

by Ya_Ya on ‎11-13-2011 10:39 PM

Try assigning the N2E a static IP address.

 

It has worked for everyone who has reported trying it, except one.

by cactusminer on ‎11-16-2011 07:04 PM

I'm also suffering the wifi malfunction after the 1.1 update.  My home router (netgear wgr614) continued to work but the older netgear router I also connected to stop working. (can't find the model # at the moment, it looks the same as the 614)

 

I deleted the remembered network but still could not reconnect. Tried a power cycle, no luck.

 

When can I expect update 1.1.1 or 1.2? Some of these workaround, which may work, are quite frankly ludicrous to ask non-technical users to perform. I work in IT so it's a breeze for me but come on B&N...

by jeepreader on ‎11-17-2011 10:00 AM

Alex,

 

Hello, my nook just updated itself and now I can't hook up to my wireless network. It was working fine for the last month, but now it says it is unsuccessful when it tries to hook up. I have not changed anything on my network and all my other devices are working fine. Here is my information

 

Owner: Brian Kokesh

Account: brian.kokesh@hotmail.com

Software version: 1.1.0

Model Number: BNRV300

Serial Number: 3013410059413004

Wi-Fi Mac address: 58:67:1a:7e:0b:f0

 

I hope you can help me

 

Thanks

Brian

by Brendon on ‎11-17-2011 01:43 PM

I found a fix from another site.

 

Basically you'll need to go into your wireless router settings . You need to setup a static IP address for your NOOK based on it's  MAC address which you can get from Settings, Device Info.

 

If you have Verizon FIOS the detailed steps are below, otherwise you may need to find someone who understands your Wireless router if you don't and set a static IP address for the NOOK. 

 

This is an issue from the 1.1 update obviously since it worked fine before the update, but Barnes and Noble refuses to acknowledge this from the many support personnel I've spoken with. I did get mine working on my home wifi again by the instructions below . (For Verizon Fios Actiontec routers)

 

 

 

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.

 

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!

by ajeff on ‎11-17-2011 02:00 PM

Alex

I am having a similar problem to those who have had problems since the 1.1 update.  I have the actiontec m1424-wr router using verizon fios.  I am particularly frustrated for the following reasons: 1- made a special trip to my closest b&n store looking for some help.  No one there had a clue.  2- I spent an hour with your telephone tech support in the Philippines who also had no clue that there was a problem.  Instead she had me do a hard reboot.  Now I have a completely frozen NST and can't even read my content. 3- I have now spent an hour searching for an answer online only to find that there are a bunch of us in this basket and b&n is falling flat.  A bad week for this considering the amazon touch readers are out this week.  This is suppose to be a seamless, simple device, not a grief inducer.  What am I suppose to do?! 

 

Thanks

Alan

by Ya_Ya on ‎11-17-2011 04:29 PM

ajeff wrote:

This is suppose to be a seamless, simple device, not a grief inducer.  What am I suppose to do?! 

 


You are supposed to assign it a static IP in your router.  Then it will work.

by ladybugAC on ‎11-22-2011 01:30 PM

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!

Serial # 3012220046963008  ahc822@comcast.net

 

by geertm on ‎11-22-2011 01:41 PM

Someone at the Mobileread forum was told by B&N that there would be an update to fix the Wifi problem at the end of this week.  Lets hope that is true.

by tomservocrow on ‎11-25-2011 09:40 PM

I am also having problems with connecting to wi-fi since the 1.1 update. It always just says "unsuccessful". I was looking to see if I could remove the software update since I didn't notice any difference with it anyway, but it seems that that can't be done, at least so far as I can figure out....

by Ya_Ya ‎11-28-2011 08:11 AM - edited ‎11-28-2011 08:12 AM

Wrong thread.  :smileysurprised:  Sorry.

by dhyamato on ‎11-28-2011 12:02 PM

(This is a duplicate post I posted on another thread.)

 

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 scotta316 on ‎11-28-2011 12:17 PM

dhyamato wrote:

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.


My best guess is that the 1.1.0 update standardized something in the wifi implementation, but that some Netgear and Actiontec routers (and possibly others) do something that is not standard. I experienced a similar problem when I helped someone set up a Netgear router, and then we had to update the wifi driver on his laptop before it would connect.

 

Just a guess.

by jeepreader on ‎11-29-2011 11:11 AM

How do you revert back to 1.0. I think that is probably the best fix. Could you please post the steps to accomplish this

 

by dhyamato on ‎11-29-2011 11:27 AM

Here's the link to the site I used to revert back to 1.0.

 

http://blog.the-ebook-reader.com/2011/11/07/how-to-unroot-nook-touch-to-restore-it-to-original-firmw...

 

As a note, this 3-step method can be used for either a rooted or non-rooted NT as stated on the site.

 

Good luck.

by kchai007 on ‎11-29-2011 09:32 PM

 

I experienced same problem. I have Cisco e2000 running DD-WRT firmware. All other wifi devices in my home work. NST failed after the 1.1 update.

 

Thanks for the link to revert back to 1.0; I will try it out and post my result.

by KincaidNook on ‎12-03-2011 06:20 PM

I don't understand B&N. I walked into a store, and the Nook Customer Service rep had NEVER heard of this problem either. Of course the WIFI worked in-store.

 

That an update is causing this much grief is plain silly - I tried asking if there was a way to roll back this stupid update, but nada. I'm pretty techie, and that assigning a static IP thing up top doesn't make a whole lot of sense to me. I rarely mess with my router, and see no need to, since clearly, this is something B&N needs to fix on their end. It worked fine, before.

 

Jeez, how many people have to complain about this for them to pay attention??? Yes, it may be difficult to fix something that only applies to a subset of users, but then, just put a freaking patch out there that affected users can download!! This is such bull. If I wanted to read stuff I downloaded on my laptop, I wouldn't have bought an e-reader in the first place! And of course I can't find the stupid cable. Seriously, Barnes & Noble, DO SOMETHING!!!!!!

by LastSilmaril ‎12-03-2011 07:12 PM - edited ‎12-03-2011 07:22 PM

The fact of the matter is, people, is that B&N is not a huge tech company that has got the kind of resources to throw around to fix this kind of thing quickly. Unfortunate. This is something that I didn't really care too much about until the WiFi issue came up - and it's cropping up, now I hear, not just for Verizon/ActionTec people like myself, or people with old Netgear or Linksys routers lying around, but to people running solid router software like dd-wrt and tomato on newish stuff! It's really an unfortunate situation, and having customer support pretend like it doesn't exist is going to do them no favors. It really is a good thing that the NST is a compelling piece of hardware, despite the shortcomings of the people backing it and some of the dumber quirks and restrictions on the device.


scotta316 wrote:

dhyamato wrote:

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.


My best guess is that the 1.1.0 update standardized something in the wifi implementation, but that some Netgear and Actiontec routers (and possibly others) do something that is not standard. I experienced a similar problem when I helped someone set up a Netgear router, and then we had to update the wifi driver on his laptop before it would connect.

 

Just a guess.


The fact of the matter is, though, scott, I haven't been able to figure out just what the heck they changed! I extracted the old wlan driver, the old wpa_supplicant, and the old dhcpcd from the recovery image, copied them over and fixed permissions - to no avail. Outside of that, the configuration files for wifi and lan, unless I am very mistaken, or diff doesn't work, have not changed! It's a maddening situation. It's possible they change something in the kernel; I really have no idea. And I'm not so ready as you to simply say that the change was BN trying to be proactive in terms of standardizing their wifi drivers/implementation - not at this late stage, where a month late they still have not made a public comment on this matter or released a 1.1.1. If it were a matter of something simple like that, why haven't they got their acts together then? And what of this guy above, who reports that he had problems connecting to a dd-wrt based router? I have never had a problem getting dhcp from any dd-wrt router I've ever come across. Other probalos? Maybe. But not something so basic as dhcp.

 

Meh, sorry for the rant, not trying to create enemies here.

 

by LastSilmaril ‎12-03-2011 07:16 PM - edited ‎12-03-2011 07:19 PM

kchai007 wrote:

 

I experienced same problem. I have Cisco e2000 running DD-WRT firmware. All other wifi devices in my home work. NST failed after the 1.1 update.

 

Thanks for the link to revert back to 1.0; I will try it out and post my result.


NO! You have a REAL router my friend! You don't even need my slightly convoluted instructions for the Verizon POS Actiontec - try setting up a Static DHCP lease FIRST before trying to backup/restore (unless you'd like to have a working 1.0.0 image lying around - then, by all means.)

 

http://www.dd-wrt.com/wiki/index.php/Static_DHCP

 

But thanks for letting us hopeless NSTers of your issues.

 

by LastSilmaril ‎12-03-2011 07:18 PM - edited ‎12-03-2011 07:20 PM

Also, the fact that you're having this problem with a router using open-source firmware may be able to clue us in into what the heck is *actually* going wrong here, thanks to system logs that actually tell us things that are useful. Can you dump the logs after attempting to connect and failing???

 

might be a li'l more tricky to set up; not sure, haven't configured a dd-wrt router in a while.

http://www.dd-wrt.com/wiki/index.php/Logging_with_DD-WRT

by Starearedkid on ‎12-03-2011 08:45 PM

Ugh. I am SO frustrated. I have visited B&N once, been on the phone with them 3 times, and once with Verizon--and nothing works. They told me to try a hard reset, but it freezes mid way through (and won't actually work.) And because the device won't do a hard reset, they can't exchange it for me. 

 

I am in the mindset that it should just work. I don't have the time or energy to be on the phone with tech support every day of the week. 

 

by Technologirl on ‎12-04-2011 12:19 PM

Ya_Ya wrote:

ajeff wrote:

This is suppose to be a seamless, simple device, not a grief inducer.  What am I suppose to do?! 

 


You are supposed to assign it a static IP in your router.  Then it will work.


Sorry, no. That's not what we're supposed to do.

 

It worked with 1.0 software. I didn't have to assign an IP address. I don't know how to. I don't want to spend any part of my life fixing what they broke.

 

What I'm supposed to do, is hear how they've fixed what they broke and install it.

 

It's been over 3 weeks and it should be happening soon.

by on ‎12-04-2011 12:38 PM

Technologirl wrote:

Ya_Ya wrote:

ajeff wrote:

This is suppose to be a seamless, simple device, not a grief inducer.  What am I suppose to do?! 

 


You are supposed to assign it a static IP in your router.  Then it will work.


Sorry, no. That's not what we're supposed to do.

 

It worked with 1.0 software. I didn't have to assign an IP address. I don't know how to. I don't want to spend any part of my life fixing what they broke.

 

What I'm supposed to do, is hear how they've fixed what they broke and install it.

 

It's been over 3 weeks and it should be happening soon.


As a TEMPORARY fix it should work just fine though.  Luckily my router still connects with my N2E although it tries to connect about 2 or 3 times before it actually does.

by Ya_Ya on ‎12-04-2011 12:57 PM

Technologirl wrote:

It worked with 1.0 software. I didn't have to assign an IP address. I don't know how to. I don't want to spend any part of my life fixing what they broke.


I'd rather spend five minutes of my life doing "something I'm not supposed to" than whine about something not working - when there's a simple (any idiot could do it) fix available.  That's apparently just me, though.

by Technologirl on ‎12-04-2011 01:09 PM

Ya_Ya wrote:

Technologirl wrote:

It worked with 1.0 software. I didn't have to assign an IP address. I don't know how to. I don't want to spend any part of my life fixing what they broke.


I'd rather spend five minutes of my life doing "something I'm not supposed to" than whine about something not working - when there's a simple (any idiot could do it) fix available.  That's apparently just me, though.


I honestly don't consider it whining when they broke the NST and I'm voicing displeasure over it. Really, you do? 

 

I've been through a lot in life, including a major disease that nearly killed me. I ration my time as if it's precious, and I don't consider fixing their mistake to be a good use of it. 

 

Are you having the problem yourself, or just here harassing people who do, who chose not to fix B&N's f-up?

 

by Ya_Ya ‎12-04-2011 01:31 PM - edited ‎12-04-2011 01:33 PM

Technologirl wrote:

 Are you having the problem yourself, or just here harassing people who do, who chose not to fix B&N's f-up?


My N2E quit connecting to my Verizon FiOs, but I didn't notice it immediately because I had been syncing at the office for several weeks rather than at home.  

 

When I realized it, I followed LastSilmaril's procedure, which literally took five minutes - three of which were booting up my laptop.  (I suspect you know that, though, because you posted in that same thread.  So, does that mean you're just here to harrass those of us who think a user has some responsibility in keeping their toys working?)

 

The fix Last Silmaril found is literally so easy to follow that anyone who can read can follow it.  (Note, I said following the fix is that easy.   Finding it definitely was above and beyond my technical chops, and I've admitted that multiple times.  And thanked him/her for finding it and shared it with others. )

 

And yes, I do consider it whining when one takes (several times) more time to complain about a problem than to follow an extremely simple procedure to fix said problem.

 

I also don't totally consider this "their f-up."  They've made a change and now default settings for some routers are no longer supported.  I have multiple Wifi devices.  Several of them require specific settings to work - they're not all broken or f'ed up, IMO.  They just have specific requirements in order to connect.  That's just part of having tech toys, as far as I'm concerned...

by psucutie on ‎12-04-2011 03:27 PM

this fix worked for me, thanks.

 

by Technologirl ‎12-04-2011 06:58 PM - edited ‎12-04-2011 07:03 PM

Ya_Ya wrote:

Technologirl wrote:

 Are you having the problem yourself, or just here harassing people who do, who chose not to fix B&N's f-up?


My N2E quit connecting to my Verizon FiOs, but I didn't notice it immediately because I had been syncing at the office for several weeks rather than at home.  

 

When I realized it, I followed LastSilmaril's procedure, which literally took five minutes - three of which were booting up my laptop.  (I suspect you know that, though, because you posted in that same thread.  So, does that mean you're just here to harrass those of us who think a user has some responsibility in keeping their toys working?)

 

The fix Last Silmaril found is literally so easy to follow that anyone who can read can follow it.  (Note, I said following the fix is that easy.   Finding it definitely was above and beyond my technical chops, and I've admitted that multiple times.  And thanked him/her for finding it and shared it with others. )

 

And yes, I do consider it whining when one takes (several times) more time to complain about a problem than to follow an extremely simple procedure to fix said problem.

 

I also don't totally consider this "their f-up."  They've made a change and now default settings for some routers are no longer supported.  I have multiple Wifi devices.  Several of them require specific settings to work - they're not all broken or f'ed up, IMO.  They just have specific requirements in order to connect.  That's just part of having tech toys, as far as I'm concerned...


a. I scanned a few pages of the other thread. I didn't know you had posted there, regardless of what you "suspect." lol Think much of yourself?

 

Yes, I'm sure everyone who reads anything I've ever posted on any thread remembers it. (that's sarcasm).

 

b. It's interesting that you think because you were able to fix your situation in 5 minutes, therefore everyone should be able to. If you had read my post in the other thread, you might have noticed (I guess only the rest of us are supposed to memorize your posts) that my setup is complex and that is one reason I am very unwilling to mess with anything. It took many hours over a period of days to get it working. The 20 or so devices I have connected are fine connecting to it. Only the NST stopped working, right after the 1.1 update. If you don't consider that a f-up, then you must not expect much of companies whose products you buy. I expect mine not to get broken by a poorly tested software update.

 

c. Anyone who releases a product update and doesn't verify that it hasn't broken their product with one of the largest regional ISPs in the country has f'ed up. Seriously. Thank god they just sell books and ereaders, not medical devices. (Gee Mrs. Smith, sorry about your late husband's pacemaker that stopped working after our software update.) Calling it a toy doesn't diminsh their responsibility to test the update before they release it.

 

We obviously have a philosophical difference here. I don't expect you to be able to understand my point of view, and I don't care that much about yours. Sounds like a great reason to ignore each other. I'll start.

 

by Ya_Ya ‎12-04-2011 10:50 PM - edited ‎12-04-2011 10:57 PM

Technologirl wrote:
b. It's interesting that you think because you were able to fix your situation in 5 minutes, therefore everyone should be able to. If you had read my post in the other thread, you might have noticed (I guess only the rest of us are supposed to memorize your posts) that my setup is complex and that is one reason I am very unwilling to mess with anything. It took many hours over a period of days to get it working. The 20 or so devices I have connected are fine connecting to it. Only the NST stopped working, right after the 1.1 update. If you don't consider that a f-up, then you must not expect much of companies whose products you buy. I expect mine not to get broken by a poorly tested software update. 

I did read your post in the other thread.  You have your FiOS router (which doesn't work with other devices, so you had to buy another, a Linksys) connected to a Linksys so that your Roku works.  So Roku doesn't have to work, but your NOOK does?  Hmmm, inconsistent.

 

It was implied, but clearly not apparent that I believe that if you have the technical chops to come up with that, you absolutely have the technical chops to follow a simple procedure, and the technical chops to revert if said procedure "breaks" something else.  You're a lot smarter than you're playing and we both know it.  

 

Enjoy being angry.   I'll enjoy syncing books to my NOOK.  :smileywink:

 

[EDIT:  Broken was when N1E v1.7 v1.6 caused them all to not recognize SD cards larger than 2G.  A software update causing a minority of users to make a single adjustment to their router setups doesn't constitute broken in my book.  Stupid?  Poorly beta tested?  Nuisance?  Annoying?  All of that, but not quite broken.]

by scotta316 on ‎12-05-2011 05:10 AM

Come on, ladies. You're both pretty.  :smileywink:

 

Seriously, I agree with both of you. On the one hand, something that was working fine has stopped working due to a firmware update. I don't believe in the ridiculous logic that "they can't test it with every possible hardware combination," because it worked fine before.

 

On the other hand, this isn't the first time a software update has broken something. If you have the good fortune to find a solution to your problem, and the desire to use the work-around, then knock yourself out. It's not your obligation, but it's certainly your right.

 

Just my two cents.

by Technologirl on ‎12-05-2011 01:06 PM

scotta316 wrote:

Come on, ladies. You're both pretty.  :smileywink:

 

Seriously, I agree with both of you. On the one hand, something that was working fine has stopped working due to a firmware update. I don't believe in the ridiculous logic that "they can't test it with every possible hardware combination," because it worked fine before.

 

On the other hand, this isn't the first time a software update has broken something. If you have the good fortune to find a solution to your problem, and the desire to use the work-around, then knock yourself out. It's not your obligation, but it's certainly your right.

 

Just my two cents.


I don't know, I'm done reading her posts. This goes back a while, according to some vague recollection that at some point months ago, something I said must have annoyed this person. Life's too short. That's what Ignore buttons are for.

by Radikalriky on ‎12-06-2011 01:31 PM

My Nook Simple Touch BNRV300 lost WiFi connectivity after software upgrade from 1.0.0 to 1.1.0.

 

My home WiFi device is a [CenturyLink provided] Westell DSL Gateway-Router Model A90-750022-07.

 

I can no longer connect to my home WiF no matter what steps and this is already a "Factory Pre-Owned" (used) replacement for the new one i sent back for the same reason.

No amount of fiddling with the Nook nor my router seems to make a difference. I'm not technical enough to get inside my Nook's interal workes as some are able to using "abd / shell" stuff.

A frustrating time now with two readers and not fix date yet set.

by LastSilmaril on ‎12-07-2011 01:25 PM

scotta316 wrote:

Come on, ladies. You're both pretty.  :smileywink:

 

Seriously, I agree with both of you. On the one hand, something that was working fine has stopped working due to a firmware update. I don't believe in the ridiculous logic that "they can't test it with every possible hardware combination," because it worked fine before.

 

On the other hand, this isn't the first time a software update has broken something. If you have the good fortune to find a solution to your problem, and the desire to use the work-around, then knock yourself out. It's not your obligation, but it's certainly your right.

 

Just my two cents.


Yup. BN doesn't get a pass on this...even with the crappy ActionTec router. Especially considering that the company's flagship store is in New York City, and a significant portion of their customers are going to be stuck using this turd of a router! I have had connectivity issues with the router all of two times before, and upgrading wifi drivers on my clients fixed it both times. 


Anyway, I've actually managed to isolate the dhcp problem to - wouldntchaknowit! - the dhcp "dll" file, /system/lib/libnetutils.so. Except for one time where I had to turn wireless on and off on the nook to reconnect after waking up from the screensaver, replacing it with the version from 1.0 works like a charm. I don't know what they changed, and I don't know much about decompiling, but it's something I'm gonna look into later. In the meantime, here are instructions (which I also posted in the old thread):

 

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

 

The fact of the matter is, there are some people here that could benefit from rooting and dropping this file in, without adding a launcher or apps. That way you can even connect to routers that have this issue even if you don't know what the router's MAC Address is and do not have admin access to the router in question: that's why I did it! If there is demand for such a process I could probably spell it out; it's really not that hard.


by LastSilmaril on ‎12-07-2011 02:14 PM

Radikalriky wrote:

My Nook Simple Touch BNRV300 lost WiFi connectivity after software upgrade from 1.0.0 to 1.1.0.

 

My home WiFi device is a [CenturyLink provided] Westell DSL Gateway-Router Model A90-750022-07.

 

I can no longer connect to my home WiF no matter what steps and this is already a "Factory Pre-Owned" (used) replacement for the new one i sent back for the same reason.

No amount of fiddling with the Nook nor my router seems to make a difference. I'm not technical enough to get inside my Nook's interal workes as some are able to using "abd / shell" stuff.

A frustrating time now with two readers and not fix date yet set.


I'm assuming that the "A90-750022-07" is the Westell 7500 Gateway, rev 22.

It looks like the Verizon version of this router uses basically the same interface as the hated ActionTec, but not the CenturyLink. But really, there should be a way for you to assign static IPs through DHCP in there. Every router I've ever owned has allowed me to do so.

by LastSilmaril on ‎12-07-2011 03:17 PM

I would suggest you go to the CenturyLink forums at DSLreports and ask them how to have your router assign a static IP to a given client (your Nook).

 

http://www.dslreports.com/forum/centurylink

by scotta316 ‎12-11-2011 02:20 PM - edited ‎12-11-2011 02:21 PM

LastSilmaril wrote:

I'm assuming that the "A90-750022-07" is the Westell 7500 Gateway, rev 22.

It looks like the Verizon version of this router uses basically the same interface as the hated ActionTec, but not the CenturyLink. But really, there should be a way for you to assign static IPs through DHCP in there. Every router I've ever owned has allowed me to do so.


 

Actually I had a Westell router five years ago before I got FIOS, and as I recall, I couldn't find a way to assign a static IP through DHCP either. I remember thinking it was a neat feature when I started poking around in my new FIOS router.

 


by Rereader on ‎12-28-2011 03:52 PM

What is the status of 1.1.1 with wifi fix?

 

I just got a new Nook at 1.0.1 and am afraid to turn on wifi for fear of this issue.  Our home router is standard-issue Actiontec, one of the routers in the threads that appears to be having the issue.  Surely with millions opening their Xmas gift NSTs you have a fix pending?  Otherwise you face millions of returns.

by Shagger on ‎12-29-2011 03:58 PM

I'm with you man. Mine "updated" this morning. I got the WiFi bug AND my touch screen got a bug that only went away on one of several reboots. You couldn't type. You couldn't tell it to power down, it would select "cancel" no matter where you poked. Typing anywhere on the right side of the keyboard would acivate the center key as well.

 

I did the eight boot trick to revert to the factory 1.0.1 and everything works fine.

 

Come on B&N. I can understand and forgive some of this sort of thing. But until this issue is addresed I have to be very carefull with my WiFi so as not to have to deal with this update bomb. It seem some folks are getting USB issues from this as well.

 

Do they really want us all to root these things? Are they trying to chip away at our patience?

by guanagirl on ‎01-01-2012 07:06 PM

I have a modem/router Westell Model 7500 (through Century Link) and also lost wifi with updated software.  After many phone calls and finally reaching a couple of people who acknowledged that it was their fault, they sent me a new Nook Simple.  I cannot register it because it won't recognize my home wifi connection.  I can, of course, register it at a local McDonalds, but probably won't be able to use it in my home if I could not register it on my home wifi system/.  You can, however, download books from BN on line and can get the instructions from a customer support person.  Don't know why they haven' fixed the problem quickly, since many people don't know how to download using the USB cable connection.  Haven't decided whether I will try to use the new Nook or not........probably has the updated software also.  I do know that two friends of mine with new Xmas Nooks have the old software.  Does it mean that they are not offering the new software on newly manufactured Nooks???? 

by Radikalriky on ‎01-13-2012 01:39 PM

My Westell 7500 [Model A90-7500-22] is now owned by Netgear and is the "VersaLink 7500" DSL Gateway provided by CenturyLink Phone/Internet Company.

I'm now on my 4th Nook Simple Touch. The last 3 were factory pre-owned and came with software 1.1.0, which would not connedt to my home WiFi. Now, B&N sent me a new Nook Simple Touch claiming it  would be specially equipped with software 1.0.1 that worked fine on my original Nook. They said to "side-load" all content for the next few months unilt they fixed the software bug.

 

However, the new Nook ST they sent was equipped with what must be software 1.1.0 because I cannot even register it.

 

I don't know how to mess around in my router (even when I log into it) without the threat of messing up every other WiFi connected computer and printer in the house. Asigning IPs is out of my understanding.

I don't think B&N is hot on this fix. I would mess with my router if it was a simple "do 1, then 2, then 3 and you're done" without mesing up everything else.

by camarossrs on ‎01-19-2012 08:06 PM

Same router, same problem, same conclusions.:smileymad:

by Technologirl on ‎01-20-2012 12:18 PM

They're sure bustin their arses to get that fix out, too.

 

Not.


camarossrs wrote:

Same router, same problem, same conclusions.:smileymad:


 

by newguy2012 on ‎01-24-2012 02:08 AM

Thanks the fix worked: like a charm.

by tammy1986d on ‎01-25-2012 12:04 AM

I did a hard set on mine got it back to the old software and yes it worked again but just as soon as it went to sleep it reset to 1.1 and the would not connect. I Did a hard set again and it worked until it went to sleep and then it reset to the new update. Now just doing the reset the support peps walk me through wont get the thing back to the old version.

 

My point is why not give us the option personally I can't see that the update inproved anything so greatly that I would be missing anything using the old software. This would at least give those of us a working device untill the wifi conection issue is fixed.

 

 


by tammy1986d on ‎01-25-2012 12:26 AM

I did a hard set on mine got it back to the old software and yes it worked again but just as soon as it went to sleep it reset to 1.1 and the would not connect. I Did a hard set again and it worked until it went to sleep and then it reset to the new update. Now just doing the reset the support peps walk me through wont get the thing back to the old version.

 

My point is why not give us the option personally I can't see that the update inproved anything so greatly that I would be missing anything using the old software. This would at least give those of us a working device untill the wifi conection issue is fixed.

 

by Technologirl on ‎01-26-2012 12:49 PM

tammy1986d wrote:

I did a hard set on mine got it back to the old software and yes it worked again but just as soon as it went to sleep it reset to 1.1 and the would not connect. I Did a hard set again and it worked until it went to sleep and then it reset to the new update. Now just doing the reset the support peps walk me through wont get the thing back to the old version.

 

My point is why not give us the option personally I can't see that the update inproved anything so greatly that I would be missing anything using the old software. This would at least give those of us a working device untill the wifi conection issue is fixed.

 


If you leave Wifi turned on, it will always load any updates it finds.

 

Personally, I leave Wifi turned off unless I am downloading a recent purchase. As soon as I have the new book(s), I turn Wifi off. The device doesn't have enough time to download a software update in the short time it has to download a book.

 

by tammy1986d on ‎03-18-2012 09:41 AM

I just updated mine with the new 1.1.2 update, I am happy to say it fixed the wifi problem that 1.1.1 was giving me.

by kmoody83 on ‎04-14-2012 03:47 PM

I had the same problem at first. I deleted my wifi "remember" on it and then restarted it. I was then able to see the wifi network and connect.

by kmoody83 on ‎04-14-2012 03:50 PM

Oops! Forgot to say I also had to do a hard reset on my wireless router after I made it forget it and before I rebooted my nook.

Accepted Solution
Distinguished Correspondent
LastSilmaril
Posts: 129
Registered: ‎07-30-2010
Answered

It seems to work if you assign your Nook a static IP in your router; see my instructions on how to do this for POS ActionTec router here (page 3, post 57):

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

Other Answers: 0