Comments for DavidPierron.Com/Net/Org

Comment on Verizon Sucks by Samara Cummins

Samara Cummins — Wed, 14 Dec 2011 14:38:29 +0000

My 82 year old mother cannot get coverage at her home in FL where she lives half the year. Verizon doesn’t care. They won’t let her out of her contract. She lives alone and pays for a phone but has none. Amazing. Nonsense.

Comment on Verizon Sucks by brad

brad — Tue, 29 Nov 2011 22:57:50 +0000

I am a loyal verizon customer never a late payment would like to upgrade new phone. Verizon will not honer my unlimited package they want to down grade service and raise my price. I know I am a small fish in Verizons pond but I want to be treated like family I’m pissed and don’t know what to do HELP

Comment on Mac Self Assigned IP Address by Philip

Philip — Mon, 12 Sep 2011 19:05:28 +0000

Success! So far, anyway. I’m sure I’ll be back should it fail again, but in the meantime, thank you!

Comment on Mac Self Assigned IP Address by Jesse Williams

Jesse Williams — Mon, 15 Aug 2011 20:18:27 +0000

David,
Serious problem. I have tried everything you have listed, still nothing. Even worse is that my wife’s MacBook Pro is having no issuse with our router (Apple Airport, Time Capsule). Continue to receive “Airport has the self-assigned IP address 169.254.9.140 and will not be able to ….” Configuration is DHCP, while the version of OS is 10.6.8

Anything you offer would be greatly appreciated.

Thanks, Jesse

Comment on Mac Self Assigned IP Address by WifiHell

WifiHell — Mon, 28 Mar 2011 23:49:45 +0000

I’ve tried all these “fixes”, and none of them seem to help my Macbook connect through my NetGear WNR2000 when WPA2 security is set. When the network is open or when WEP security is set, there’s no problem.

Comment on Problems Update by David Pierron

David Pierron — Sun, 20 Mar 2011 17:52:42 +0000

@Anne Nolan: In a later post you will see that the same router I found a solution with also failed me. A different Revision of the firmware made the difference … I wonder why us Mac people don’t just buy the Airport?

Comment on Problems Update by Anne Nolan

Anne Nolan — Sun, 20 Mar 2011 05:35:32 +0000

David,

Thanks for your continuing efforts to solve the self-assigned IP issue and share solutions.

Here is a new wrinkle for you to consider. I have a MacBook from 2007 that’s running 10.4.11. and can dual-boot into Windows XP via Boot Camp. I routinely decline most software updates because I have some pretty old Windows applications that work with my current setup and I’m concerned updating anything might mess ‘em up. So pretty much all my software is circa 2007, and my Linksys router was even older than that. Yet it all played nicely together. I never, ever had any problem with the self-assigned IP issue.

But the Linksys finally died and we replaced it with a Netgear, and now I get intermittently dropped and sometimes frozen out with a self-assigned IP almost every day.

When I configured the Netgear, I followed its setup wizard’s recommendation that I set it up with WPA2 security, and I am beginning to suspect it was the move to WPA2 that caused this trouble. When I get a chance I’m going to switch to WPA and see if that solves it.

But not tonight. It’s after midnight here and I don’t attempt tasks like that after midnight.

Anyway, just wanted to give you an example of where older hardware worked but newer hardware has problems.

Thanks again for tackling this issue.

Comment on Mac Self Assigned IP Address by Kent Tunks

Kent Tunks — Thu, 03 Mar 2011 21:46:37 +0000

I should have said 812.11b and 812.11n. I am a retired audio engineer, not a computer guy
at all!

Comment on Mac Self Assigned IP Address by Kent Tunks

Kent Tunks — Thu, 03 Mar 2011 21:10:46 +0000

Hello everybody,

I had the same problem everyone else did, but with the help of Isaiah at C. Crane the problem was solved. A list of my gear: MacBook Pro model A1211
OS 10.4.11
D-Link DIR 655 Router
C Crane Super USB Wi FI Antenna 3
Wild Blue Satellite Internet service

I was trying to get the USB antenna working and I had the same problems of a 169….. ip adress
that everyone else has been having. I found out that I had been using the wrong password but even
so it showed that the antenna was connected with the dreaded 169 address. When I finally started
using the correct password I could get on the internet sometimes but not every time.I went through
restarting, repluging the antenna , etc. but nothing seemed to work consistently. My router was set to
use only the 812.b standard and I was using WPA2 Personal security with AES Cipher type. I got rid of the WPA2 and set the the router to have no security. To be “open”, in other words. I could connect
every time with the “Open” setting. Next, I set the router to the 812.n standard only and went back to
the same security setting I had before. So far, it has connected every time. I have my fingers crossed! I had tried everything in David’s original post, but nothing worked for me.
I am thinking that perhaps Stef and Crut et. al. have a pretty good theory in their above posts.
Maybe the Mac does not wait long enough for a ip address.I am certainly no computer expert, but it does make sense that it would take some time for a Mac get an address if it had to wait to get through whatever security that was being used to get an address. Also, I would imagine that some transmission standards would be faster than others. Anyhow that is what happened to me.. I would be very interested in what everyone else would have to say about my experience.

Comment on Mac Self Assigned IP Address by David Pierron

David Pierron — Wed, 09 Feb 2011 22:23:24 +0000

@crut – Frustrating … this is how I see it, especially since I bought the same router and had the same problem. Even if you followed my success and bought the same router, you still could have had this problem. There is no way to check the Revision of the firmware when you’re buying a router, is there? =) … I don’t think “Lion” would fix anything, this problem has existed for a long while going back several felines. The only thing I haven’t tried is buying a true Apple product in the Airport base station. I’d assume there would be no problems if you used that device rather than a third party router. But that defeats the purpose of protocols and standards. By the way, I think you meant to say “Static IP” rather than “DHCP with fixed IP” … That “D” is for Dynamic, nothing fixed about it. You may also be referring to running DHCP on the router as well as having a fixed range of IPs available for your static assignments. But the machine’s network interface itself can only run static or DHCP, not both.

Comment on Problems Update by David Pierron

David Pierron — Wed, 09 Feb 2011 22:09:45 +0000

@Julie – when any Mac sleeps it loses its network connections. If you want to access it at any time, you will have to turn the sleep function off. If you have an Airport, why use the DLink at all?

Comment on Problems Update by Julie

Julie — Sat, 05 Feb 2011 23:17:53 +0000

OK this is weird. I have a DLINK 1005d connected to my Satellite modem and then to Airport.
I have an ethernet connect from DLINk to IMAC.
I can connect using Airport but not using ethernet. I get the self-assigned IP error!.
I want the ethernet connect so that I can access my IMAC remotely and when it sleeps it drops the airport wireless connection.
I want the wireless for my mac book and Tivo.

I have tried EVERYTHING on all the forums but so far no luck. I am running Snow Leopard 10.6.6

Comment on Mac Self Assigned IP Address by crut

crut — Thu, 30 Dec 2010 00:53:34 +0000

Stef & others, in my opinion, have the answer.
I believe the Networking concept of Mac is flawed.
As others have said a PC laptop will function 100% in DHCP mode because it waits indefinitely for the DHCP assigned address, as does my old IBM T23.
Mac OS.XXX doesn’t, it seems to wait only 20 to 30 seconds then self-assigns? Even a ‘Script-Kiddie’ would know better?
There seems no point in designing such a flawed networking mode as this that I can see?
On my wife’s MacBook (10.6.2) I use a fixed IP and WPA2 using a Thompson-Alcatel 585 router. It connects and holds permanently. Using DHCP the problem arises.
On my iMac 27″, i5, (10.6.5) I normally use Ethernet, but when testing WiFi the same problem arises if I use DHCP, so I use DHCP with fixed IP. It then works.
Maybe ‘Lion’ will fix things?

Comment on Mac Self Assigned IP Address by stef

stef — Fri, 24 Dec 2010 21:51:06 +0000

I think it’s some sort of timeout. I think the Mac wants a quick answer but the older wireless routers aren’t as fast. Windows will wait forever for an answer so maybe that’s why my laptop works. It does take a while for the network to become active while on a Mac it’s ready almost immediately … So, I’m guessing a timeout and a newer router gives a faster response, and possibly the permission problem aids the Mac in not needing to wait for an answer or something and the Mac gets the connection a little later without issue.

This seems the root of the solution.

Comment on Mac Self Assigned IP Address by David Pierron

David Pierron — Thu, 18 Nov 2010 08:50:43 +0000

@mark: Uhm … okay.

Again, my solution was a new router, nothing internal to my MacBook Pro … Also I’ve found that my Belkin Rev 1000 works, but the newer Rev 2000 doesn’t … If I had to do over again, I’d buy an Apple wireless router and avoid all these problems, yes?