Active Topics

 


Reply
Thread Tools
Posts: 60 | Thanked: 0 times | Joined on Jan 2007
#31
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?
 
Posts: 34 | Thanked: 0 times | Joined on Jan 2007
#32
Originally Posted by cstross View Post
...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!
 
Posts: 26 | Thanked: 0 times | Joined on Nov 2006
#33
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
 
Posts: 3,841 | Thanked: 1,079 times | Joined on Nov 2006
#34
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).
 
Posts: 26 | Thanked: 0 times | Joined on Nov 2006
#35
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).
 
Posts: 3,841 | Thanked: 1,079 times | Joined on Nov 2006
#36
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.
 
Posts: 60 | Thanked: 0 times | Joined on Jan 2007
#37
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]

Last edited by csoldfield; 2007-01-24 at 18:46.
 
Posts: 3,841 | Thanked: 1,079 times | Joined on Nov 2006
#38
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.
 
Posts: 177 | Thanked: 4 times | Joined on Apr 2006 @ Wirral, UK
#39
Originally Posted by TA-t3 View Post
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.
 
Posts: 88 | Thanked: 0 times | Joined on Dec 2006
#40
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.
 
Reply


 
Forum Jump


All times are GMT. The time now is 14:24.