connecting with local IP address

[Kym]

I installed OS 2006, set up my connection, but it's not connecting to the internet. I get this message with the connection:

Connected to xxxx with link - local IP address

and there's a red question mark over the little globe. Can anyone shed any light on this and help me solve this problem?

Thank you.

[johnf]

Looks to me like an IP address problem.
You should go to: Control panel > Connectivity > Connections
and edit the one you need to use, including the Advanced features, where you can choose an IP address. Good luck!

[Kym]

I tried assigning ip addresses, etc. That eliminated the question mark and the "link-to" message, however I still get "network problem" when attempting to go online.

Prior to OS 2006 I did not need to assign IP etc. Why should I have to do that now?

This is very frustrating. I'm not a complete dummy, however I need detailed, step by step "treat me like a kindergartener" troubleshooting instructions. The maemo site is no help. The Nokia site is no help. If there's someone out there that can talk me through this, I will even go so far as giving you my phone # if you can help.

Thanks for letting me vent.

[Kym]

Sometimes it's the simplest thing. And it can make you look foolish, too.

I'd entered the wrong WEP key. Once I got the right ones in - connection was made.

[bamse]

I got this message with my newly installed router.

[roadsterboy]

I got this message with a public unlocked Wifi access point. No WEP security.

[MikeL]

Since switching to OS 2006 I have been having real problems with "Local link-IP address" on my home Network which is set to provide a DHCP IP for the Nokia 770 etc. I logged my problem as a comment to an existing bug on Bugzilla, https://maemo.org/bugzilla/show_bug.cgi?id=596

Initial connection would be fine but almost whenever I re-connected after a dropped connection I would receive the Local link-IP address confirmation and the ? on the world symbol which is very helpful ;) I did NOT have this problem under OS 2005.

Last Night I noticed that checking and changing the following in connection parameters of a given Wi-Fi connection point seems to stop the "link-local IP address" issue occurring. (More testing required to be sure however)

On The Nokia 770.

Go-to, tools, connection manager and open connection manager.
Go-to, connection manager window, tools, connectivity settings.

In the connectivity window, select connections (at bottom of window) which will then list your saved connections. From here we can select and review a stored connections settings (Via a wizard) and edit specific connection parameters.

I have realised that for some reason under OS 2006 the "Network is Hidden" option is being selected for some saved connections? I know my network is NOT hidden and I never expressly asked the Nokia 770 to set this connection to "Network is hidden" ?

Since ensuring this option is switched off, the problem appears to have disappeared.

Note: I copied all my settings from OS 2005 to OS 2006, could this have introduce an anomaly perhaps?

[claudio]

Note: I copied all my settings from OS 2005 to OS 2006, could this have introduce an anomaly perhaps?

I noticed this also on my home wireless lan, and I can say that this is not related to settings copied from 2005 to 2006, since I started with a fresh 2006 image.

[shez]

Can anyone please please please help me here ... my 770 works fine at home, at work we have a free wireless network but the signals are weak - most of the time signals are just one or two bars. my nokia connects to the signal without any problems but always says using link-local IP address. I can see status as connected. Can anyone please tell me what can i do to fix it.

i have check all the settings and eveything looks normal. it works fine at home though.

thanks in adavce

[psj]

I had the same issue and found that by setting the wifi signal power mode from high to low (I know this seems counter intuative) I have been getting stable connections over the last week...

[shez]

Psj, thansk for your reply. I tried it but no luck. I found a spot at my work it works fine :-) its not perfect but at least i can sync my emails

regards

[emory]

Just to chime in; I think 2006 is broken in this way as well.

I can assign a static IP address to the device and attach to a WAP fine. I can get an address off ppp0 when connecting to EDGE/GPRS via Bluetooth to a Nokia N90 and using T-Mobile data service, but if I connect to any WAP and use dhcp I do not get an address and the dhcp client assigns the link-local address to $interface.

It seems really like a stupid bug to have, since a lot of people with the 770 will presumably be relying on dhcp to configure the device when they're at a hotspot, but whatever.

Short of waiting for an update, does anyone have any solutions? I haven't attempted to force dhclient to run, I am not entirely certain how GNU/Linux does dhcp these days.

[emory]

fwiw my home DHCP server is Mac OS X Server, my WAP is a Linksys 54g with Linksys firmware, and I have tried all manner of encryption/auth/on/off.

I haven't tried static DHCP yet. That wouldn't really solve my problem though.

[someone]

fwiw my home DHCP server is Mac OS X Server, my WAP is a Linksys 54g with Linksys firmware, and I have tried all manner of encryption/auth/on/off.

I haven't tried static DHCP yet. That wouldn't really solve my problem though.

I have the same issue. I find I get link-local connections about 50% of the places I try to connect. My home WLAN is using a Linksys 54g running Sveasoft. I have found that if I restart (unplug / replug) the problem is corrected for a few days. Not sure why this works. This solution doesn't help for access at public wireless locations. "I'll have an expresso, and would you mind rebooting your network so I can check my stock quotes?"

[abrinson]

I noticed that I started getting the "connected with local ip address" message after enabling the option to use the memory card as additional virtual memory. Once I disabled that option I haven't had any more problems connecting with local ip address except for the ocasional weak signal.
Anyone else notice this?

[pinky]

Every once in a while I also get the local link message. I have not used the virtual memory and also use dhcp to asign a IP address. When I get the error message I disconnect and connect again. At the latest after the second time I get a working internet connection. Hope that helps some of the others with this problem.

[echus]

I upgraded from OS2005 to OS2006 almost immediately after getting my 770. I have had almost nothing but "local link" connections. It does not matter if I am near or far from the router. It happens with WEP on and off. I've tried different power settings, no luck. I've tried static addressing.

Every once in a while - not consistently - I can connect to a open router that my neighbour has kindly positioned in their back window right behind my house. Most of the time I get the "local link" message even with this router. I note that a Windows CE PDA and Windows XP can connect no problem, first try.

It sure seems like wireless is at least partially busted on the 770. It is a shame as everyone admires the screen. I think an important part of any future release would be to improve the diagnostics capability for the wireless.

[bac522]

I'm not a fan of WPA or WEP on these low end routers such as Linksys, Netgear, or D-Link. The problem is that most of these devices use software (firmware) encryption which hampers the performance of the device. I prefer to use to MAC authentication and with my SSID broadcast turned off. I've also seen in the past that WPA or WEP does cause problems with some devices regarding DHCP; could be Nokia's problem or the AP's problem.

Sure without WEP or WPA, someone could sniff my packets, but I'm not overly concerned with that. They are not going to easily be able to connect to my wi-fi and use it. Sure they could just change their MAC, but then I'll get MAC conflicts on my machines and will know something is up, too much of a headache for the wi-fi road warrior.

[rattis]

Sure without WEP or WPA, someone could sniff my packets, but I'm not overly concerned with that. They are not going to easily be able to connect to my wi-fi and use it. Sure they could just change their MAC, but then I'll get MAC conflicts on my machines and will know something is up, too much of a headache for the wi-fi road warrior.

What about the more mundain. Collect information from your wireless network and then use it to their personal gain. You know the simple things, credit card numbers, email addresses, site passwords, and the like.

[Neil McAllister]

Has there been any progress at all on the "link local" IP address issue? My 770 seems to be unable to get an address from DHCP anytime I'm in an area where lots of wireless networks are visible. If there's just one network (like my home network), it does fine. Take it to a public place, however, and it's useless.

The really frustrating thing is that I had this problem with the 770 when I first got it, but one of the updates to the 2005 OS fixed the problem. Then I upgraded to the 2006 OS and it's back again. Now it's almost the end of 2006 and, unless I'm mistaken, there have been ZERO updates to correct any of the problems with the 2006 OS, including this one. I must say I'm a little disappointed, but I would love to hear about if anyone has come up with a custom fix for the link local address problem.

[penguinbait]

I can connect to all kinds of networks and I am running 2006 OS, maybe try the nokia park wifi detector, see if you have any luck with that.

http://parkwifi.nokia.com/1,21,,,202.html

It will manage your wireless connections and automatically connect you to networks.

I have it installed but I usually only use the built in tool

good luck

[9a6or]

I have had the some problem after upgrading to another router. I had to change the WEP code (on the router's back) and then ended up with the link-local IP address. A restart of the N770 seems to have fixed the problem though... fingers crossed.

[9a6or]

I have some interesting findings, now that I am using a 700, an N800 and a desktop PC with wireless connection on the same wireless router. When the Desktop is connected then both Nokias can connect with only link-local IP. If I put the Desktop to sleep then the Nokias connect normally. If I wake the Desktop once the Nokias are connected then it connects fine. The Desktop uses a D-Link DWL-510 PCI wireless card.

It seems that the Desktop has some priority over the Nokias... Reading back this thread some of the situations might be explained by this.

I don't know enough about wireless networks, if anyone can help then please do so.

[csoldfield]

N800 testing 'in the field' (around town) has resulted in quite a lot of 'link-local ip address' with the question mark instead of the lollypop on the connection icon. I have not had a single instance at home, with a Trendnet router and about 6 devices connected to it (4 PCs, PAP2, N800).
When connected 'link-local' when in town, viewing the IP Address details on the N800 show:-
ip address: 169.254.63.223
netmask: 255.255.0.0
default router/Primary/Secondary DNS = none
I also struggle with sometimes getting a browser going OK, but cannot send email. My SMTP settings are set to my ISP, which works perfectly from home. Just not when I connect to a free hotspot!

[csoldfield]

Reading back this thread there appears to be numerous similarities between N770/OS2006 issues and N800/OS2007 issues that I am having. I did not see any resolution of issues seen on the 770/OS2006 (OS2005 appears to have had a fix) with:-
Numerous hotspots visible
Virtual memory enabled

Next time I encounter the 'link-local ip address' on my N800 I will try disable Virtual Memory (currently 128MB).

[csoldfield]

Further results. Sat outside OfficeDepot and tried to connect to their free WiFi hotspot. Always got the 'link-local ip address' and the ip address claims to be 169.254.63.223 (nowhere near what it should be). At that time there were three other open AP, plus two other 'locked'. Same results connecting to the other two open AP (coffee shop and 'KiteNetFree') - no success, could not browse.
Later outside BestBuy, tried to connect to KiteNetFree again and it worked normally. Browse/email send/receive OK. Tried to connect to BestBuy and it failed (despite being open). Only two APs were visible at that moment - BestBuy and KiteNetFree.
So it appears that the results indicate the more APs visible, the harder it is to get an IP address, even though it 'Connects' fine and the signal is good (2 out of 4 bars). Anyone else with similar experiences on the N800? Remember at home it works flawlessley to my WEP-enabled router, never having failed to connect EVER (even though I can see 4 open APs, 3 locked APs)

This has to be a bug in the N800! It should not be this difficult to connect to free WiFi hotspots, and IMHO makes the N800 useless, at best unreliable.

[Mara]

Might be also that some 2.4GHz wireless phones interferes with the WiFi connection. I have one Vtech phone and every time it rings both my desktop and N800 gets disconnected from the AP. Needless to say that I'm no longer using that phone... Too bad you can no longer find those 900MHz phones that have no issues. Another alternative are those 5.8GHz phones but I'm afraid the RF signal is less capable to penetrate walls etc...

I suspect some of my neighbours have similar 2.4GHz phones since sometimes I get frequent disconnects without any good reason. If I try to reconnect most time I get the same error message than you. Then on other times the connection stays rock solid?

However, the N800 seem more sensitive to this than my desktop? It could be that the Transmit power level of the N800 is lower or the N800 antenna is less optimal.

[9a6or]

Link-local addresses (from Wikipedia): If a network address cannot be obtained via DHCP, an address from 169.254.1.0 to 169.254.254.255 is assigned randomly.

This means that my two Nokias cannot get their IP addresses from the DHCP when my Desktop is connected. Should I use manual IP addresses? That would bypass the need for DHCP, wouldn't it? But then any new device would have to be added manually... Why can the Nokias not access the DHCP??

I tried BT's (as in British Telecom) online help guys but they don't know the answer.

[9a6or]

I have assigned IP addresses, DNS server and gateway addresses manually and now the three devices can connect fine in any order. I used the addresses the DHCP server sends to them (when it works) and so the settings on the router didn't need changing. Problem solved, but it still concerns me that the DNS server on my router (?) does not send addresses to the Nokias when the Desktop is connected. Any gurus know why this is?

[cstross]

I had the same problem, hooking up to my airport network (128-bit WEP). Fixed it by re-entering my WEP hex key repeatedly until I got it right.

It is (IS ANYONE AT NOKIA LISTENING?) really, *REALLY* annoying to try entering a 26-digit hexadecimal number in a text entry box that (a) replaces every character you enter with an asterisk after a fraction of a second, and (b) doesn't let you paste in a string you typed into another application. It took me about five to eight tries to get it right!

An option to switch off automatic hiding of passwords would be really useful. Let the user decide if they need extra privacy, right?

[csoldfield]

So it looks like DHCP problems at home can be fixed using static ip addresses. This is no solution for trying to connect to free WiFi hot spots when out of the house, right?

[thebeck]

...and (b) doesn't let you paste in a string you typed into another application.

I was able to paste into the wep key box w/o any problems. I did not test to see if it works as my ap is open. I am using a N800 btw.

PS: Hello everyone! I got my N800 the day after Macworld and this site is awesome. I have already learned so much here. Thanks! :D

[Cerebus]

I'm having the same problem now with my N800 on all WEP networks, despite it having worked earlier *today* on those same networks. WTF?

-- C

[TA-t3]

As was said by another poster: If you get the 169.xxx IP then it means that you didn't get any from the DHCP server. If this depends whether or not the desktop pc is connected then it sounds like the server is set up to serve a limited number of connections, in other words it should be possible to fix this in the server (the router setup, or whatever is your server).

[Cerebus]

Not in this case. My sniffs on the network show a working DHCP server (I can watch other stations discover and request successfully); it just doesn't respond to the DHCP Discover packets sent from the N800. That makes me think that the discover packets are malformed since this happens on multiple networks with multiple different DHCP servers. But when I examine the N800 discover packets, they look good to me (at least they decode properly in ethereal).

[TA-t3]

That's an interesting find. Wish I had some time to look into that myself, but it won't be this week. But it sounds like you're on the right track.

[csoldfield]

Anyone else been brave enough to take the N800 out of the house yet (I realize the case sucks!). Almost *always* I get the "link-local IP address" = 169.* when away from my own router. Coffee shops, etc. Everyone else is happily surfing and all I can do is Disconnect/Reconnect whilst my coffee gets cold! This has to be a bug in the Nokia's DHCP code.
[Operating in Denver, CO, USA. Made in Korea, 51-6 firware]

[TA-t3]

It's worked fine for me in all coffee shops so far.. and in the library.. and any other intermittent open networks I've found while idling on the bus and so on. I used it extensively in such places every day last week. FWIW, I'm in Europe, I have a 'made in Finland' N800, and that latest 51-6 software version.

[9a6or]

As was said by another poster: If you get the 169.xxx IP then it means that you didn't get any from the DHCP server. If this depends whether or not the desktop pc is connected then it sounds like the server is set up to serve a limited number of connections, in other words it should be possible to fix this in the server (the router setup, or whatever is your server).

I can get addresses for all devices from the DHCP server if I conect them in a specific order, so you're on a wrong track.

[iFrank]

At home, with all the other networks around, I can always connect to my wireless network (WPA2) without any problems, regardless of presence of other connected devices (e.g. laptop) or normal interference.
While, in downtown, I get a lot of "local IP" messages when trying to connect to open networks. So, to me, it seems the problem is related to quality of signal than merely order of connection.

[aflegg]

Or also networks that appear open are using MAC filtering or similar to restrict what they'll give DHCP addresses to.

...or they could even be networks with no DHCP server and just static IPs (although it sounds like csoldfield's had problems at coffee shops etc. too)

[frenzon]

FWIW, using my two-day-old N800, I can *sometimes* connect to the campus-wide public wireless network at my workplace. When I can connect, I can disconnect and reconnect repeatedly successfully. However, after some time, I get disconnected and then only get the local-link problems. During this time both my PPC6700 and Laptop can connect to and use the wireless network without issue.

It may be chance, but three times now I have success connecting to the public wifi immediately after attempting to connect to our private wifi network (only attempting - I don't think the N800 has everything needed to connect to it).

[9a6or]

.... So, to me, it seems the problem is related to quality of signal than merely order of connection.My Nokias are half a metre from the router when they get the local-link IP, while the Desktop reports 'excellent' signal downstairs. When the N's connect first they get in from the furthest corner of the house (too cold to test in the garden now but that used to be fine too), and the Desktop gets excellent signal again. It is weird...

[frenzon]

To followup, the behavior described above is repeatable:

1. Use N800 on open wifi for a while.
2. Eventually link stops working (grr)
3. Attempts to reconnect, gets link-local IP (grr)
4. Repeat (3) endlessly to the same result
5. Manually attempt to connect to private wifi, which then gives me an unable to authenticate error as I haven't set it up properly.
6. An attempt to connect to the open wifi then works.

It would be interesting to replace (5) with an attempt to connect to a different open wifi network and see if that works, but there aren't any here.

[niceisnice]

I am having this problem too: at home, I can only connect using my anonymous neighbour open connection. When I configure my router (a Belkin G) with no encryption, I always get a local link. I'm of course 1 foot away from my own router and signal is excellent for every other device.
Frenzon "method" doesn't work for me.
Anyone has a workaround?

[Mara]

I just realized yesterday when trying connect to my hotel AP it worked first and then it just got disconnected. Retries to get back access gave always the Link local IP address...

But, it looks in my case that the N800 Bluetooth is giving this problem: It only occurs if Bluetooth is turned on on N800. I noticed this because when I browsed the web I had no problems... not even after long surfing period. But after I opened MaemoMapper, which turns on the Bluetooth automatically, the connection dropped right away. I was not able to get connected or stay connected with MaemoMapper running. Once I closed it and Bluetooth, the WiFi started working again without any issues!

So, could it be that the Bluetooth and the selected channel on the AP is at the same (or too close?) frequency band? They both are at 2.4GHz... but I assume they should not be exactly at the same frequency band?

[Mara]

I made some more experiments and when I changed the WiFi AP channel from 11 to 1 the connection improved. No more disconnects, but I think it still did slow down the connecion, and occasionally caused it to pause downloading. Therefore I'm pretty sure the Bluetooth and WiFi do interfere with each others...

Also both of them are exactly at the same frequency band: 2.40-2.48GHz. Bluetooth should be hopping between the whole band, while WiFi is more constant at the set frequency band.

Anybody seen this behavior in your N800 or 770? If you turn on your bluetooth radio does it degrage your WiFi connection?

[Texrat]

I didn't think of that Mara! When I was doing troubleshooting I also changed the channel from 11 to 1. But later I realized there were other problems and figured that after I did get things working again the channel change was moot. But now you have me wondering...

[TA-t3]

Interesting. BT and WiFi can interfere for sure.
On the other hand, right now I'm streaming music through wi-fi with BT on (I just scanned it from my laptop), and there are no problems. I'm almost 100% certain the wi-fi is on channel 11, unless it was changed recently -- I'll update this posting if so.

[Texrat]

I think some routers are just more tolerant. I know my Netgear router had no issues with my 770 (until it crapped out) but my Linksys has (and as noted, other than interference or configuration problems, rebooting the router resolves my recent connection woes). The interference issues seem to have been resolved by the antenna I just added to the router.

[Mara]

I don't think it is only router related? I never noticed this problem (or it wasn't severe enough) prior to my purchase of N800. With 770 I *think* I had some mysterious WiFi disconnects or network slowdowns before, but it never got as bad as with the N800. Now it is very consistent that *any* WiFi connection seem to suffer if Bluetooth is turned on. It is just more sensitive with higher channels like 11. However, my desktop or laptop do not seem to be disturbed about the BT at all. (I have external BT dongle on my desktop and I use BT mouse with my laptop when working without docking station.)

Based on my knowledge (which may be wrong...) the N800 as well as 770 use the same antenna for both BT and WiFi. Therefore the "interference" signal for each other will be significantly stronger than if the antennas were separate.

[TA-t3]

I think some routers are just more tolerant. [...]The interference issues seem to have been resolved by the antenna I just added to the router.
Ah, interesting. I was looking at the active BT dongle on my laptop sitting just inches from my N800, but if the problem is more likely to appear at the wi-fi router end then there's a good reason I don't see any problem -- I'm located fairly far away from the router, the BT signal wouldn't be at all detectable there. If so, the problem could possibly be reduced by moving away from the router.. I seem to recall several postings pointing out that they had a problem with wi-fi even though the wi-fi router was up close. Obviously the simplest thing to test first is to just switch off BT..

[TA-t3]

Based on my knowledge (which may be wrong...) the N800 as well as 770 use the same antenna for both BT and WiFi. Therefore the "interference" signal for each other will be significantly stronger than if the antennas were separate.
They use the same antenna, but the signal is multiplexed -- that is, it doesn't transmit both at the same time. wi-fi/BT/wi-fi/BT.. (this is from what I could gather from those FCC papers that made us aware of the upcoming new N800).

[Texrat]

I don't think it is only router related? I never noticed this problem (or it wasn't severe enough) prior to my purchase of N800. With 770 I *think* I had some mysterious WiFi disconnects or network slowdowns before, but it never got as bad as with the N800. Now it is very consistent that *any* WiFi connection seem to suffer if Bluetooth is turned on. It is just more sensitive with higher channels like 11. However, my desktop or laptop do not seem to be disturbed about the BT at all. (I have external BT dongle on my desktop and I use BT mouse with my laptop when working without docking station.)

Based on my knowledge (which may be wrong...) the N800 as well as 770 use the same antenna for both BT and WiFi. Therefore the "interference" signal for each other will be significantly stronger than if the antennas were separate.

I'm not saying it's ALL router-- but we're troubleshooting so every factor needs to be examined. I'm just tossing out my own experiences in case it triggers an idea in someone. In my case, if I have trouble with one wifi device in my house I have trouble with them all (1 laptop, 1 770 and 3 N800s). I realize my situation doesn't necessarily translate to everyone, but IMO every angle needs to be examined. tA-t3's point about the possibility of being too close is worthy of exploration I think.

[Mara]

I played with this thing little bit more tonight at hotel. What I can say that with my N800 the WiFi and Bluetooth are absolutely NO-NO to use at the same time. :eek:

I'm starting to wonder if my N800 is somehow defective? Anyone has similar symptoms that with Bluetooth on (such as MaemoMapper running and searching GPS receiver, actual GPS receiver was not powered on) your WiFi connection gets very erratic?

The hotel AP seem to be on channel 6... so this does not seem to be related to channel 11 as I previously though.

[XeQtoR]

Maybe it doesn't work with BT enabled... but it doesn't even work with BT disabled.

I love my N800 at home works like a charm... But I have never - ever been able to access the internet through a open wifi on the road. Tried several places, ... even at my parents place (where i know how the wifi router is configured) ... no go.

This bug ,or what should I call it, really makes the N800 worthless out of the house. I'm practically sorry i bought it. Because that was the main reason i got it.

Hope Nokia diggs in to this because it doesn't do the main thing it's build for!!!
What use is a Internet Tablet (for the road) that doesn't connect to the internet. Sorry but this is something that must be fixed asap otherwise I can't see any future in the internet tablet device.

[TA-t3]

Maybe we should start listing what type access points we're using. I know it's going to be difficult to figure out this for public hotspots, but..
The one I'm currently using is a D-Link Airplus extremeG, works like a charm. Roaming too. (I had local IP problems in the past but it was resolved when we figured out one of them hadn't been updated when we changed essid). I'll be able to test a couple more types at least (later).

[Texrat]

Maybe it doesn't work with BT enabled... but it doesn't even work with BT disabled.

I love my N800 at home works like a charm... But I have never - ever been able to access the internet through a open wifi on the road. Tried several places, ... even at my parents place (where i know how the wifi router is configured) ... no go.

This bug ,or what should I call it, really makes the N800 worthless out of the house. I'm practically sorry i bought it. Because that was the main reason i got it.

Hope Nokia diggs in to this because it doesn't do the main thing it's build for!!!
What use is a Internet Tablet (for the road) that doesn't connect to the internet. Sorry but this is something that must be fixed asap otherwise I can't see any future in the internet tablet device.

I realize I may take heat for doing this again but... I don't know how pervasive your experience is. I *am* able to get on other networks outside my house-- unless I don't have the security key.

It's normal for a person to think their unique experience translates to the general populace, but until I see data supporting such a case, I'm going to keep assuming this is either router issues (including interference) or a hardware problem unique to your N800. In the latter case, I'd return it and try again.

Oh, and to TA-t3's suggestion: I've successfully used Linksys WRT54GC and Netgear WNR854BT. Netgear was more stable. Linksys occasionally needs rebooting.

[XeQtoR]

Hi,

My (linux) experience isn't that great, I myself would say I'm a linux newb. Besides some ubuntu experiments. :)
But it would be great if you didn't need to be computer expert to use the N800.

Back to the topic:

Is it possible to connect to open non secure WIFI networks?

I was able to connect to multiple WEP secured WIFI networks (that I installed for some friends)

But open non secure networks don't seem to work for me... Am I doing something wrong?

[TA-t3]

Is it possible to connect to open non secure WIFI networks?

Sure. Public access points are always open, even the ones where you have to pay - that part is taken care of by redirecting you to an https: page the first time you try to set your browser to some web page.


I was able to connect to multiple WEP secured WIFI networks (that I installed for some friends)

Good, then it works.


But open non secure networks don't seem to work for me... Am I doing something wrong?
Are you sure these are open, public networks? If they are merely without WEP or WPA protection, they could still have MAC filtering on. Try in some airport, hotel or Starbucks - you should at least get a valid IP address.

[typicalmacuser]

Let me tell you after spending hours yesterday with out being able to make a connection to my Router (every configuration you can imagine) I woke up this morning and changed the wireless router from Channel 11 to Channel 6 and everything work. I hope this helps someone . That's on an N800 by the way

[revwillie]

I thought I was going nutz. I also have this problem on open public hot spots.

A lot of times, the hot spot provider wants you to click on a button to agree to a usage policy and there's this catch 22. You can't see the policy page until you get a connection, but you can't get a real ip address until you agree to the policy. I had some success by editing the advanced properties to allow for a proxy server and make it auto-config. That way, I can open a browser first and try to go to google.com. Then, the proxy redirects the browser to the policy agreement page. I cannot connect to my email pop server when I have the connection set up for a proxy server, though. I'm still fiddling with it...

[XeQtoR]

Let me tell you after spending hours yesterday with out being able to make a connection to my Router (every configuration you can imagine) I woke up this morning and changed the wireless router from Channel 11 to Channel 6 and everything work. I hope this helps someone . That's on an N800 by the way

Could you tell me how to do that? I have no idea where to change channels on the N800.

[TA-t3]

@XeQtoR: You can't change channel on the N800, it's at he router (access point) that the channel is set.

@revwillie: It sounds a bit strange to me.. to see the policy/login/pay-me-by-credit-card page there must be an IP address already.. if you could explain further it would be great. For those kind of hotspots the first thing to do is always to use a browser, only after that will other things (like pop, vpn etc.) work.

[slaguru]

Using a new N800 with a Netgear router. It was all in the WEP key for me. I entered it wrong at the start and it screwed me from there. I was fooled by the fact that I looked like I had a connection BUT I did not. Removed the connection, and did it from scratch and Bingo.. it worked.

[enbrewer]

I've been using both a 770 and an N800 at home (Linksys 1st generation AP and Netgear 54g) and at work (many different Cisco AP's scattered through several buildings) and have never had a problem. All are open AP's, though the Netgear is set up with MAC filtering. I usually have Bluetooth disabled. I don't doubt that others are having problems, but I suspect it's more subtle than what everyone is suggesting.

Maybe some particular combination of things, even the software you've been most recently using on the Nokia, is causing a deeply-buried bug in the WAP drivers to surface? Just throwing that out, not that there's any evidence to support it...

[TA-t3]

Trying to make a list..

1) - Wrong WEP key, the error symptoms aren't obvious so may look like network problem
2) - MAC filtering, the network isn't truly open
3) - Bluetooth interference, needs channel change on AP
4) - Access points interference, i.e. some other network nearby, needs channel change on AP
5) - Configuration problem inside roaming network, e.g. one AP has incorrect ESSID - works occasionally but isn't stable. AP must be reconfigured
6) - Occasional problem inside the AP, this is the nature of cheap APs - need to restart AP (yank the power cable for a few seconds)
7) - Some early 802.11g routers are slightly outside spec, they work with some equipment but not with others. If it works ok in 802.11b mode this is it. Be wary of "108Mbit" APs.
8) - Since the N800 is so sensitive it may see an AP but the AP doesn't see the N800. Move closer to get a stronger signal.
9) - Some unrecognized/non-understood 770/N800 problem.

Of the above I've experienced 5 and 6, others have reported the rest with the possible exception of 7 - I think so, but I'm not certain. However, I've seen this with other (non-tablet) equipment. 9 is speculative at this point, but cannot be dismissed yet.

Did I forget anything?

[slaguru]

Got to work this morning and tried the 800 on a Apple Airport connection. Same problems as yesterday. The link seemed up, but network problems. Removed my initial WEP key, scrubbed the setup and started again. VERY pricise entering the new WEP key and it all worked fine.

Convinced that some kind of error key should be involved in the setup of secure networks. Thats hours I have lost because I have been under the illusion of a connected network when I'm not.

[Mara]

Looks like the latest OS fixed this local link IP address issue (when Bluetooth radio is on) for me? (If not sure what I mean browse through some of my previous posts in this thread.) :)

[XeQtoR]

Oké it's been months now...

I still don't see any answers to this problem. In all that time I haven't been able a single time to connect to an open wifi. (I mean non WEP password secured wifi's out of the house)

So this makes the nokia the perfect device for home. And i mean it, i truely love it at home. To me it's better than having a laptop. But out of the house it isn't worth anything for me. And that is after all the reason i bought it.

So if anyone is intrested in a N800... it's out for sale.

(PS: don't blame anyone of the user community for still having this problem. But it's a shame Nokia doesn't seem to care a bit on this issue)

[metallimake]

XeQtoR: Just curious, what was the SSID of the free public wifi you were trying to connect?

[XeQtoR]

The SSID is "TELENETHOTSPOT" Without the quotes of coarse. But I guess you'll already figured that out :)

That is what's my provider say's it should be... and I see it like that on the N800 aswell.

But I already tried several other open wifi's aswell. None with succes.

[luketoh]

XeQtoR,

Do you know what channel the Wifi is using? Also, have you tried connecting to those very routers using a laptop successfully?

[richie]

I've had this a couple of times with the N800. I found it happens when the signal is weak, I'm too far away. It seems the wifi can connect, but not enough to properly to get the ip addresses, gateway and DNS.

Rich

[therblack]

For what it is worth, I have noticed the same thing...I get the local IP address when I am getting a weak signal. Note that I csn usually connect with my laptop...guess it has a ?more sensitive? card.

[Texrat]

Interestingly enough, in the hospital this week I had the opposite problem: my IBM T43 (which usually connects fine) had a devil of a time with their patient room wifi, but the N800 connected fine most of the time.

[Texrat]

Oké it's been months now...

I still don't see any answers to this problem. In all that time I haven't been able a single time to connect to an open wifi. (I mean non WEP password secured wifi's out of the house)

So this makes the nokia the perfect device for home. And i mean it, i truely love it at home. To me it's better than having a laptop. But out of the house it isn't worth anything for me. And that is after all the reason i bought it.

So if anyone is intrested in a N800... it's out for sale.

(PS: don't blame anyone of the user community for still having this problem. But it's a shame Nokia doesn't seem to care a bit on this issue)

Not to be insensitive, but to say there are no answers is a bit broad. TA-t3 listed a whole host of possibilities (mine tended to be #6 on my Linksys). If you've exhausted the ones you can effect, then you either have a severe incompatibility issue (which would be odd with multiple nodes) or a unique device problem. If it's the latter, return it to Nokia for repair or replacement.

Again, it's common for a user to think the problem he's experiencing is universal, but enough troubleshooting tends to rule this out.

[mdanehart]

I don't understand how my X51V can connect to a local unsecured point, but when I fire up the N800 the unit finds the connection with 3 bars of signal strength but gives a "network connection failure". Better carry the Dell when I go to my office location!

[YoDude]

I don't understand how my X51V can connect to a local unsecured point, but when I fire up the N800 the unit finds the connection with 3 bars of signal strength but gives a "network connection failure". Better carry the Dell when I go to my office location!


There in is the issue^...

Chances are your Dell may not even recognize the network the N800 see's.

I found this to be true while using the free EarthLink service in downtown Philadelphia.

The N800 will sniff the service where others don't even register it. It will show bars in colors other than green (brownish) when this is the case.
When that happens all I can do is connect with a local IP but no TCP/IP. Interestingly though, the feed reader can update sometimes. (maybe it uses a different protocol or port)

I was frustrated with my first day's attempts in Philly. Then I realized that I would attempt to connect as soon as I found signal. (after parking the car, etc.) I was about to bag it and even had a post ready claiming it was another BS attempt by Nokia, blah, blah.

Later that week I gave it a second try and I'm glad I did. This time I only attempted to establish a network connection where I saw other users connected. I got green bars and the connection configuration punched through with all available protocols.

As a bonus I found that the N800 would hold on to the connection longer than the other devices while we walked around. I'm guessing this made hand offs to other EarthLink transmitters easier. Other devices would drop the connection entirely than have to reconnect.

In summary the N800 seems to be very sensitive to available signal but it doesn't give you a lot of info regarding connection quality. Now I use the connection manager to locate signal prospects then I walk around to find the green bar "sweet spot" before attempting my initial connection.

[heavyt]

There in is the issue^...

Chances are your Dell may not even recognize the network the N800 see's.

I found this to be true while using the free EarthLink service in downtown Philadelphia.

The N800 will sniff the service where others don't even register it. It will show bars in colors other than green (brownish) when this is the case.
When that happens all I can do is connect with a local IP but no TCP/IP. Interestingly though, the feed reader can update sometimes. (maybe it uses a different protocol or port)

I was frustrated with my first day's attempts in Philly. Then I realized that I would attempt to connect as soon as I found signal. (after parking the car, etc.) I was about to bag it and even had a post ready claiming it was another BS attempt by Nokia, blah, blah.

Later that week I gave it a second try and I'm glad I did. This time I only attempted to establish a network connection where I saw other users connected. I got green bars and the connection configuration punched through with all available protocols.

As a bonus I found that the N800 would hold on to the connection longer than the other devices while we walked around. I'm guessing this made hand offs to other EarthLink transmitters easier. Other devices would drop the connection entirely than have to reconnect.

In summary the N800 seems to be very sensitive to available signal but it doesn't give you a lot of info regarding connection quality. Now I use the connection manager to locate signal prospects then I walk around to find the green bar "sweet spot" before attempting my initial connection.

I read your post but I don't understand what you did different (if you did do something) to make connections with a network showing brown bars instead of green bars. :confused:

[mdanehart]

YoDude: Thanks for the reply. Just returned from that site with both units and both the Dell and Nokia recognized the same unprotected Netgear signal ranging from 2/3 s/units.

The Dell locked on and I surfed the net for what time I had but no go with the Nokia. The Nokia reflected the same signal strength and showed a stationary antenna (or connected) but when I tried to hit a webpage I got a warning of network failiure.

Checked all settings and surrendered.:confused:

[YoDude]

A lot of times a network will show brown bars on the N800 because of signal strength and not signal quality. Moving closer to the transmitter or getting in it's line of site will change the bars to green.

In other words, my first attemps were while trying to configure the connection in a fringe area. I brought my iPAQ with me the second time for my wife to use. (She could care less BTW but will do most anything if it means she can shop for shoes on Rittenhouse Square... A real trooper. Sort of a mercenary geek if you will. :))

We found that:
1. Where the N800 picked up fringe signal it didn't register at all on the iPAQ.
... and
2. When ever the iPAQ did recognize signal it connected flawlessly... but so did the N800.

[YoDude]

YoDude: Thanks for the reply. Just returned from that site with both units and both the Dell and Nokia recognized the same unprotected Netgear signal ranging from 2/3 s/units.

The Dell locked on and I surfed the net for what time I had but no go with the Nokia. The Nokia reflected the same signal strength and showed a stationary antenna (or connected) but when I tried to hit a webpage I got a warning of network failiure.

Checked all settings and surrendered.:confused:

Well then... there is something else at play here.
... I got no clue.

[YoDude]

Well then...

... I got no clue.

After spending the w/e on the Penn campus I think I can shed some more lite on the "connected to local IP" issue.

My wife spent her time at various alum functions and I chilled in the background with the N800. (great babysitter BTW :D )

Philadelphia has WiFi in many flavors everywhere I went including Earthlink (major suckage BTW). Our Hotel, the Inn @ Penn had one and I could remain connected down the block to the café by the bookstore. The café had one too and from the tables outside I could connect to it as well as Penn's student mesh and a plethora of independent student routers located in the surrounding , Hi-Rise dorms.

What I found was that a connection that reported a "Local IP" message usually required you to register at that IP in order to control traffic. That local IP is the gatekeeper, if you will.
Once your registration is accepted, (name + room number, student ID, or PIN) a cookie is left on the device that will allow an instant connection for as long as the server will allow it. (3 to 48 hours in most cases).

Now here is the problem and solution.

Opera does not automatically go to the local IP when the connection is established like IE does. If the browser is open already, you are not redirected.

... So, if you open the browser first by using a bookmark to a site (other than the local IP) and then the device connects, you will get the "Network Problem" error as Opera tries to open your site.

The work around is to select the connection, wait for the "connected to Local IP http://yadda.yadda.yadda" and then only open Opera using the "Open new browser window" menu item.
Now when Opera opens it will go to that Local IP addy where you can register for access.

[therblack]

... when I open a new window from opera it tries to open my home page and gives a network error. Am I missing something?

(I am trying to access the London free wifi network)

[luketoh]

Therblack, see last part of YoDude's post above yours. Maybe you need to get to some login page first?

[therblack]

... I guess that is the bit I don't get. YoDude's email says opera will 'goto the local IP' when I select open new window, but all I get is the error.

thanks for your help on this...

[Bill F.]

Using my 770, I just ran into the link-local IP problem at home for the first time yesterday. Switching the wireless channel on my Linksys router from 6 to 1 seemed to solve it.

[XeQtoR]

that has been proposed by some before.

Unfortunally that is not an option when i'm on the road and want to access a Wifi Hotspot of my internet provider. :(

That's why my N800 stay's at home. To bad it could have been such a great device on the road... now all he does is eating dust...

[paulh]

Using my 770, I just ran into the link-local IP problem at home for the first time yesterday. Switching the wireless channel on my Linksys router from 6 to 1 seemed to solve it.

I got it for the first time today, too. Rebooting didn't help, switching to a non DHCP setup fixed it. But I've been using DHCP for a while.

The one thing that HAS changed is that yesterday I was experimenting with setting up a bluetooth PAN based on this page:

http://maemo.org/community/wiki/HOWTO-BluetoothNetworking

But I don't see why the reboot didn't help, unless the bluetooth IP address was written to disk and used for the next wireless connection.

[stevenmao]

I am having this problem too: at home, I can only connect using my anonymous neighbour open connection. When I configure my router with no encryption, I always get a local link. I'm of course 1 foot away from my own router and signal is excellent for every other device.
Well. when I assigned the IP, gateway and DNS munually , the connect to my router is ok and I can visit the configure page for the router by 770. But incredible thing happened, I still can not browse the web.....rightly, the router works normally and my other wireless device can get the web smoothly.
Drive me crazy.....My neighbor would close his wireless AP every 10pm...

[billdoze]

I recently got a 770 on WOOT and love it.
This thread has been very helpful, but my problem seems the opposite of most of the posts.
I have no problem at all with public wi-fi. At home on my Mac Mini I cannot get online via Airport. I would like to do this to load software, etc.

I have no problem getting a "local IP" connection which seems to be useless.
I tried the suggestion of manually typing in an IP and DNS address. Again, I get a connection but opening a browser gives a network error.
Two issues may be relevant. 1-My mouse and keyboard are wireless so I cannot turn off bluetooth. 2- My DSL connection is shared via a d-link hub.

I wonder if I am not using the correct IP and DNS info.
Any suggestions on things I can check? I have tried most of the channel choices in Airport setup, as well as auto.
I"m unix illiterate but I can follow directions. :-/

[Texrat]

Did you enable SSL2 in the web browser settings? I had the same problem with my home router until I corrected that.

[sapporobaby]

I am having this problem too: at home, I can only connect using my anonymous neighbour open connection. When I configure my router with no encryption, I always get a local link. I'm of course 1 foot away from my own router and signal is excellent for every other device.
Well. when I assigned the IP, gateway and DNS munually , the connect to my router is ok and I can visit the configure page for the router by 770. But incredible thing happened, I still can not browse the web.....rightly, the router works normally and my other wireless device can get the web smoothly.
Drive me crazy.....My neighbor would close his wireless AP every 10pm...


Just to be clear here. Are you looking for advice on how to steal something?

[zanglang]

Just wanted to contribute my 2 cents worth of experience while trying to get my N800 connect to my Linksys WRT54g router running DD-WRT. I've been having this link local problem ever since, but have been really puzzled why it simply wouldn't work. So experimenting with various wifi settings on the router, I noticed that if I used simply "TKIP" for my WPA2 instead of "TKIP+AES" it works perfectly!

[barry99705]

I am having this problem too: at home, I can only connect using my anonymous neighbour open connection. When I configure my router with no encryption, I always get a local link. I'm of course 1 foot away from my own router and signal is excellent for every other device.
Well. when I assigned the IP, gateway and DNS munually , the connect to my router is ok and I can visit the configure page for the router by 770. But incredible thing happened, I still can not browse the web.....rightly, the router works normally and my other wireless device can get the web smoothly.
Drive me crazy.....My neighbor would close his wireless AP every 10pm...

You're probably overloading the radio sitting that close to the radio. As for connecting to your neighbors networks, I'm not even going to go into how many laws you're breaking.

[TheRealBubba]

After many months of the occasional "connected with link-local IP" on my home network with my N800, all of a sudden I cannot get the @$$##$#@! thing to connect properly. I've rebooted everything involved a couple of times and I'm totally stumped. I hanv't installed or upgraded anything in days...

[bunanson]

After many months of the occasional "connected with link-local IP" on my home network with my N800, all of a sudden I cannot get the @$$##$#@! thing to connect properly. I've rebooted everything involved a couple of times and I'm totally stumped. I hanv't installed or upgraded anything in days...

Have you also reboot the router as somebody mentioned before? Some router may require reset for a reboot, taking the power off and put it back may not be enough, just a thought.


bun

[apogig143]

can any one tell me how can i connect to wirless g router with nokia n800
3 mounts ago it was working good when i tried to connect to gps after that does't connect to the router? any one please help
thanks

[Kolyan]

I'm having the same problem, i try to connect to a university WiFi network so i cant really rest the router and everything i've tried with my N800 does not help

[barry99705]

I'm having the same problem, i try to connect to a university WiFi network so i cant really rest the router and everything i've tried with my N800 does not help

Talk to the uni network guys. Usually they're techno-geeks like us and will think the nit is cool, and try to figure out why it won't talk. As far as I can remember, I've never had a problem with wireless network connections.