Typically by configuring your N800/770 with a valid IP address (which means just about any IP address out of a possible 4 trillion+ apart from the link-local range and local host, and possibly a handful of others).

You can assign an IP address either manually (Control Panel -> Connectivity and edit the connection in the Advanced section of the wizard, you'll also need to assign appropriate DNS entires) or through DHCP which needs to be running on the network you're trying to connect to.

When connecting to a third-party WiFi LAN your best bet is to rely on DHCP (ie. automatic address assignment) as you're unlikely to know what subnet (addresses) are in use and which addresses are available for use.

There's no need (or point) configuring anything on your home LAN when you're trying to connect to a third-party WiFi LAN - in terms of obtaining a local IP address your remote home LAN will be of no help to you whatsoever.

I get assigned a link local IP address when I'm unable to obtain a DHCP lease (that is, an IP address and other network settings from the access point/router). This is because there is no DHCP server or, in most cases, because my link quality is very poor. Even though I'm able to 'see' the network, massive packetloss prevents me from communicating (and thus obtaining a DHCP lease) from the AP.

In the worst cases I will not get a link local IP address, but a connection error instead.

If you get a link local IP address, just keep moving around - closer to the AP. Keep trying to associate, until you are close enough so a successful connection can be made.... That's how I find and join open networks Love doing it!

I've also seen some idiot wi-fi setups where there IS a DHCP "server" present to issue IP addresses but because the client isn't on the list of allowed MACs DHCP traffic is blocked.
Simple "hack" to get around that is to give it a 192.168.1.x IP address and you're in like Flynn since the MAC control doesn't block ALL traffic, just the DHCP reqs/acks.
Also seen some where DHCP is turned OFF and IP addresses are applied by hand.
Should be nothing more than cranking up Kismet on the N800/N770 to find them and get in.
Of course, these were most probably years-old early 802.11b wi-fi nets I was seeing.

Yea, ask the owner of the network what the settings are. Link-local is the same as a self assigned ip address. It's not seeing the access point, or the access point isn't talking to your nokia for some reason. Most likely mac authentication.

I don't think the router at my parents' house is playing nice with my 770. I checked all the DHCP settings on the router and they're just fine. I even gave myself a static IP to my 770's mac address. After that, I got rid of the local link message by setting my 770 to that static IP. I'm still getting no luck with internet though. I can see that my router "leased out" the IP to my mac address indefinitely and that my 770 is listed under devices that are connected, but one weird thing is that my 770's device name is not registering properly under the connected devices lists.

I do wish people would stop setting their DHCP server to lease IPs "indefinately" or for weeks at a time. That's silly and just winds up using all the IP space.
Set it for six hours or so, then about every three hours the client will check in and the lease time will jump out another six hours.
Applies to DHCP reservations as well.
You've probably got a boned router setting somewhere or a router/firmware that doesn't like the IT.

I just found this comment on Nokia's site:

http://nokia770.com/forum/viewtopic....3d29168292530a

and repeated here from May 2006:

"Maybe my experiences connecting to WiFi access points will help.

First attempt worked straightaway. Connection Manager detected my father's WEP-enabled network with 64-bit encryption, so entered the key (remember to select HEX under WEP key type), and no problem thereafter.

Second attempt also worked straightaway with an unsecured network at a bed-and-breakfast.

Then, got home to the UK from the US and no luck! Could connect to my neighbor's unsecured network, but could not download Web pages (got the "Network problem" message even though Connection Manager showed bytes being sent and received).

Couldn't connect to my own WEP-enabled network either; it was detected, but no WEP key entry was enabled. Solution was to set up the connection manually. In Connection Manager, select menu (with hard key) -> Tools -> Connectivity Settings. Click the Connections button and select the network and click Edit or add it with the New button. On the first page, enter network name (if necessary) and select WLAN as the Connection Type. On the next page, select Infrastructure as the Network mode (Ad hoc did not work for me) and WEP for Security mode (if appropriate). On the next page, enter the WEP keys (remember to select HEX for WEP key type). On the next page, click Advanced settings and go to the IP Addresses panel - I used 'Auto-retrieve IP address' and 'Auto-retrieve DNS' (others suggest static IP address, but DHCP works for me). Click Finish.

I was pretty frustrated after two painless connections to fail with my own home network, but a little patience paid off.

I love my 770, and ignore the reviews that complain about what it can't do. I bought it to lie in bed or sit on the bog (toilet) and surf. It's a pity some people seem to give up after not connecting instantly the first time, and many of the problems and questions are to do with WEP keys, which are not specific to this device. Oh well.

Good luck!

Jerry"

This is a little preliminary but I just tried it with a neighbors unsecured WAP which I was getting the usual errors with and it worked! I am using the 770 with the latest 2006 OS.