The 169 Problem

Peter Rukavina

Often I find that when I’m trying to access hotel WiFi, I get assigned a TCP/IP address that starts with 169. The Apple network setup complains that this is a “self-assigned” address, and it don’t get any Internet access in any case.

The universal solution to this problem appears to be simply to power the WiFi access point off and on. Sometimes this is easy to do yourself (hint: often the access point is hidden under the desk in the hotel room); other times you have to ask the hotel staff.

I just had to do this at Club Quarters in New York: there’s a little SMC access point on the desk in the lounge; I unplugged the power, plugged it back in and, presto, working WiFi.

Comments

Submitted by Big B on

Permalink

I have the same problem. Our network is encrypted (WEP) but my keys are correct. I have full connection but won’t receive any IP adress.

I have tried for days to connect. But it seem to be impossible. My winsock is correct. I have no firewall. No antivirus and no spywares.

My wireless lan is working perfect when using it at hotels.

Add new comment

Plain text

  • Allowed HTML tags: <b> <i> <em> <strong> <blockquote> <code> <ul> <ol> <li>
  • Lines and paragraphs break automatically.

About This Blog

Photo of Peter RukavinaI am . I am a writer, letterpress printer, and a curious person.

To learn more about me, read my /nowlook at my bio, listen to audio I’ve posted, read presentations and speeches I’ve written, or get in touch (peter@rukavina.net is the quickest way). 

You can subscribe to an RSS feed of posts, an RSS feed of comments, or a podcast RSS feed that just contains audio posts. You can also receive a daily digests of posts by email.

Search