10.5.5 Self Assigned IP OR no connection at all

Okay, I'll try to condense this as much as possible. I have an imac, MBP, cell phone, and a couple gaming systems which connect to my network via wifi. All has been well for ages with this setup. 10.5.5 comes along and I didn't install it for a bit. Thursday I finally do it, and now my iMac cannot stay connected to the network. It also many times will not connect at all, simply saying connection failed
The other devices all connect with no problem what so ever. I turned off my network security and same problem. I unplugged modem + router for 10 mins, problem persisted. I then fully reset my router and left it at default, same result. My iMac either gets no IP address, fails to connect at all, or does a self assigned IP which doesn't do anything because I still cannot get online. I also updated my router firmware with no effect (i tend not to do this unless I need to, it usually ends up causing more trouble than it fixes).
My router is a netgear wgt624 v3. This first occurred when playing WoW. This had me checking the WoW forums for solutions. Over the past week, the problem has happened enough times without WoW being on for me to rule it out as a cause.
My router is in the same room as the iMac, so this is not a range issue. The other devices connect fine, so it is not a shot router. I am at a loss for what to do. I am going to take the computer to another network in a couple of days when i have the time (school/work.. too busy) but I am unsure if that will help me much. If it works there I'll be further perplexed, and if it doesn't I guess it's time to consider a faulty airport card? I am under warranty still.
Anyone know of a possible cause to this? Or how to further investigate. Aside from trying on another network I feel I have exercised all options.

Very similar problem. Since upgrading to 5.5, my internet connection has been spotty. Now it seems to be gone for good. The very weird thing is I can ping my router, I can ping the DNS's (which are outside my network at my ISP) listed. I can ping anything, just can't get to the web or my email. None of my browsers can reach outside (Safari, Opera, Firefox, even ancient IE). I can't get my mail (Entourage). Up until now I've been more than happy with my new(ish) iMac.
I have a hard-wired connection, with a fixed address, so I tried the Airport. No dice, same thing. Reset my hard connection, same thing. Turned everything off then on then off then on again.
Any other computer in the house has no problems, just my newly upgraded Leopard iMac.
I was about to go bonkers when I checked my properties on my old XP machine. Somehow the aforementioned DNS addresses had been changed. This is very mysterious, none of my other computers had the DNS addresses as my iMac and I had not changed them since buying the computer. I entered my correct DNS addresses and voila, connection again.
Bottom line? Check your DNS addresses and see if they've mysteriously been altered. And if anyone else has had this odd problem Apple should know about it.
Another oddity is that when I originally opened my network panel the "Firewire" connection was highlighted. I have never used that one.
Very strange.

Similar Messages

Self-assigned IP, no internet connection status with FIOS?

a friend just had FIOS installed at her house and after it was set up she was able to connect to the internet. i came over later in the day to join her airport express to this WiFi network by using airport utility (she wanted to have her printer available on the network). after i tried setting it up using her macbook (it failed because the WEP key used by verizon is 64 bit and apple only supports 128 bit) and rejoined the FIOS router network we lost the internet connection. in network preferences it showed a self--assigned IP address but no internet connection status. i've tried deleting this network from the joined network list, deleted the password from keychain and then rejoining the network, putting in the password when prompted. still the same "no internet connection" status. any ideas?
thanks!

Eh la Pastenague! Je savais que tu était léthale pour l'homme mais ce sont pluôt les machines à pommes qui devraient te craindre. Merci! Solved.
For future reference.
My TC is a 3rd gen.
I actually had to reset to standard defaults not only once but twice. The first time I simply returned to my old profile but that only led to the same message error on the network settings (i.e. IP by default, cannot connect to the internet). Therefore the second time around I kept my profile as backup and re-created a new one plus a guest one.
The airport utility then signaled to issues remaining:
1) Internet access was cut - this I solved by simply reseting the cable modem
2) There were no DNS Servers - I simply copied the ones I had from the previous setup and it worked
I did have AppleCare....
I'm online again and I hope for good.
Thanks a lot
PS. a small tip - I made captures of all my settings in Network settings, Airport Utility and Network utility using Grab in case of ... if anything it is just handy to get back settings that your are missing when setting up a new configuration

"Airport has a self assigned IP address & cannot connect to internet"

Hi, I'd appreciate any insight at all on this...
Apologies in advance for this vast post...!
(but I guess I may as well mention everything I've already tried...)
BACKGROUND:
I was recently trying to add an Airport Express Base Station to an existing ethernet and wireless network, which has been working flawlessly for 3 years.
(Network consists of an ethernet-connected G4 Dual 1.42 desktop running OS X.3.3, and two wireless-connected iBooks- one a 12" running OS X.3.5, the other a 14" on OS X.4.2).
For various reasons, I've now given up with the Airport Express, but ...
PROBLEM:
On the wireless 12" iBook- "Safari can't open the page "xxx" because it can't find the server "xxx"- ie, the internet connection is now wonky.(The problem is the same in Firefox, IE, and Camino too).
The fault must be with configuration on this laptop, as the other two machines on this network are still running and connecting normally with no problems at all.
What is the cause of this problem? (IP addresses? DNS server?)
WHAT I'VE TRIED SO FAR:
1. First looked at System Preferences --> Network --> Network Status, where I see this;
"Airport is connected to the network "Fritz!Box SL WLAN". Airport has a self-assigned IP address and may not be able to connect to the Internet."
Alongside it an amber button (which is usually green).
Then according to JohnHuber1's suggestion in Discussions on May 3rd 2006;
"Go to System Preferences --> Network and double click on Airport to open its preferences. Click on theTCP/IP tab and select Configure IvP4: "Using DHCP" and click on Apply Changes to save it."
I tried toggling this (it was already set this way), and then Restarted, but it hasn't helped.
I also tried clicking the 'Renew DHCP lease' button. Also hasn't helped.
2. Repaired permissions. It hasn't helped.
3. Read Apple KB article No:106798- 'Troubleshooting "Server could not be found" messages'.
From this article, it seems that
a) The problem cannot be caused by "an actual loss of internet connection", as the other 2 machines are still connecting fine.
b) Typing http://17.254.0.91 instead of http://www.apple.com makes no difference, therefore it doesn't APPEAR to be a DNS server problem. (?)
4. Tried to reconfigure the Airport settings using Network SetUp Assistant.
This allows me to select Airport as my connection method, select the network from the list; but once I've entered the network password and pressed 'continue', it then gives me a dialogue box, saying
"Unable to establish a network connection. Your computer could not connect to the internet. Click OK to go back and change your network settings and try again".
Returning to Network Prefs, I now see a box saying "Your Network Settings have been changed by another application".
I can't seem to get out of that vicious circle.
5. Opened a fresh Test Account, behaviour is the same here as in the regular user account.
6. Opened Network Utility, tried to 'Ping' on 17.254.0.91 (Apple site). Then tried to Ping my network router (192.168.178.1), and then also the other 2 computers on the network. Result in each case was "10 packets transmitted, 0 packets received, 100% packet loss".
What can I do to fix this problem? I suspect it's some small configuration checkbox in Network preferences which I've inadvertently altered.
But have I got any idea what I've done...?
Sorry for the epic post. But you get the idea...!
Thanks for your thoughts...
G4 Dual 1.42, FW800, 2GB RAM, (OSX.3.3), iBook G4 (1.2ghz, 1GB RAM, OSX.3.5) Mac OS X (10.3.3) 3 int.HDs, 3 Lacie ext.HDs, Logic Pro 6.4, RME Fireface 800.

Hi Grant, thanks for jumping in...
Have you removed the troublesome Airport Express?
Certainly have, that was Step 1 several days ago!
Are you using encryption?
Yes, I have to enter a password every time I've tried to use Network Set Up Assistant. I'm pretty sure I've got it right- it won't accept anything else.
Have you limited your network to only certain M.A.C. Addresses?
Not as far as I'm aware. Could I have done it inadvertently?
Is the Wireless Router set to allow the connection of slower 802.11b devices like the iBook?
Guess it must be... it worked fine before, and is still ok with the other 14" iBook.
Are you connecting to a Wireless Router and not to another Macintosh computer?
Hmm... I ASSUMED I was connecting to the WLAN router. The G4 desktop has no wireless capability itself, could I still be connecting to that regardless?
Internet access has never been affected in the past by that machine being on or off...
You will not be able to get anywhere until you have an IP address in the same subnet as your Router
(generally high octets the same, last octet different). Can you think of any reason why your Router
should not give you an IP address in this range?
Err... now I'm lost, sorry! What's an octet?
I really appreciate you taking the time to help me out Grant... sorry I'm not really up to speed!
Cheers, Andy.

Airport self assigned IP not able connect to Internet

I'm trying to connect my Mac Pro WiFi for the first time and have Airport turned on. Status says Airport hasna self-assigned IP adress and will not be able tonconnect to the Internet.
Anyone know how to get Airport to connect?
Thanks,
Steven

Thanks Linc, after clicking AirPort, Status is On and the correct network is showing in Network Name. when I click Advanced under AirPort tab the network shows in Preferred Networks the network I want to use.
In the TCP/IP tab Configuration IPv4 "Using DHCP" pulldown is selected and the IPv4 Address is the same as the previous screen where it says AirPort has the self assigned IP address and won't be able to connect to the Internet. Hmmm.
What I don't understand is that use this same network without any issues on my iPad and iPhone. Just Mac Pro AirPort is having a problem.
Thanks,
Steven

Hi, I have a MacBook Pro and a PC both connected to a TC who in turn is connected to a cable modem. I have no wifi accessfrom my MacBook pro (self assigned IP - no internet connection msg) while I do on PC through ethernet? can anyone help?

I was working yesterday afternoon when the wifi suddenly went cold. Initially on the MacBookPro and on the ethernet connected PC. I reinitialized modem and TC through the mac and then the ethernet on the PC worked again and has since.
I've reinitialized both the modem and TC many times, as well as checked the cables. Moreover, I've tried to renew the DHCP lease, provide the DNS servers manually, erased all networks in Network preferences and in KeyChain etc. but nothing seems to work.
One strange thing also happened. I had two networks created, one for me and one I created for guests. The latter one just vanished, dissapeared without a trace.
I've tried from the café down the street and the Wifi worked perfectly well though a little slow, but that could be their connection not the Airport. Therefore, my I deduct that there is either something wrong in the TC or something went wrong in the network settings in the Mac. But that doesn't help to move forward and fix the darn thing.
The only thing I haven't done is completely reset the TC, but after reading a couple of help threads on different forums I'm confused as to how to proceed to get it back to worrk? Has anyone had the same or similar issue and found a solution?
Thanks

Eh la Pastenague! Je savais que tu était léthale pour l'homme mais ce sont pluôt les machines à pommes qui devraient te craindre. Merci! Solved.
For future reference.
My TC is a 3rd gen.
I actually had to reset to standard defaults not only once but twice. The first time I simply returned to my old profile but that only led to the same message error on the network settings (i.e. IP by default, cannot connect to the internet). Therefore the second time around I kept my profile as backup and re-created a new one plus a guest one.
The airport utility then signaled to issues remaining:
1) Internet access was cut - this I solved by simply reseting the cable modem
2) There were no DNS Servers - I simply copied the ones I had from the previous setup and it worked
I did have AppleCare....
I'm online again and I hope for good.
Thanks a lot
PS. a small tip - I made captures of all my settings in Network settings, Airport Utility and Network utility using Grab in case of ... if anything it is just handy to get back settings that your are missing when setting up a new configuration

Self-assigned IP !!! Can't connect via Ethernet

Hi all,
This is my problem:
- Now every time I connect my MBP (running 10.6.4) to my hall's network (staying on campus, in uni) it appears as "Self-assigned IP" and cannot connect to the internet for the Ethernet. It suddenly happened a few days ago and I have no clue what caused that
- Airport's working well
- Using Windows on Parallels and can still connect to the Internet despite that the Mac OS X does not at the same time, my friends' laptops have no problems as well
- Tried taking the IP, subnet mask, router( I suppose in Windows it is called Gateway ) details and typing in manually for the Ethernet settings on OSX but still cannot connect to the Internet. The status is Connected and "Ethernet is currently active and has the IP address 137.xxx.xx.xx."
- When I bring my laptop to a different place and connect via Ethernet, it works well, too, I just leave the setting to be "Using DHCP"
I've seen that lots of people have met this issue, also loads of advices have been given:
- reset the router ... --> I'm connecting to the hall's network, so that's impossible for me to do
- sudo ipfw list , sudo ipfw flush .. --> nothing changed afterwards
- someone suggested uninstalling any VMware --> tried uninstalling parallels desktop and the problem's still there
- untick the "Use Passive FTP Mode" for ethernet --> no difference
- Security settings ,Firewall --> firewall was even off when the issue 1st appeared
So ANY SUGGESTIONS PLEAAASSSSSSSSSEE !!!! I'm sick of having to turn to Windows just to access the internet
Thanks in advance

fr1d4y13 wrote:
Apart from this one "*4) In the folder /Library/Preferences (not <yourhomefolder>/Library/Preferences), move the folder SystemConfiguration onto the Desktop, then restart your computer. See if you can now make your AirPort connection work.* " , I've tried all the other ways suggested but didn't work.
I'm wondering what it means by "move" here :? Is that "copying and then delete the original" :??
A "move" operation is normally considered equivalent to (although more efficient) than "copying and delete the original". Just drag the folder out of its original folder and onto the Desktop, which will make it be no longer in its original folder.
I've seen others post advice about moving out specific files in that folder. That probably works just as well if not better (as it leaves in place other files not involved in networking), but I haven't spent the time to determine just which files should be moved.

Self-assigned ip address -- can't connect to Airport

I have a 2006 MacBook Pro which recently started exhibiting the exact same behaviour as reported by another poster in 2011:
For some reason the computer has started self-asigning its IP address and Network Preferences says that, because of the self-assigned IP, i cannot connect to the network.
I have two other Macs connecting to the same Air Port with no issues and I've tried to duplicate those settings on the MacBook Pro but still get the "self-assigned ip" message
Tried re-setting SMC and PRAM, no change.
The only change to my wireless setup was the change from a Verizon-owned modem to an owned Motorola unit (but the MacBook Pro connected successfully, many times, after the change).
I didn't knowingly change anything on the MacBook Pro -- from one day to the next it just stopped connecting.
I'm really at a loss to understand what's going on and, of course, not happy that the MacBook Pro can't connect to my network anymore! Help!

The wifi icon shows no connection with the network -- the "!" mark.
However the computer sees the network, i.e. when I search in Network Preferences the network is listed.
So: 1) the computer sees the network but 2) will not connect to the network. The reason given for refusal to connect is "self-assigned IP address".
Not to be repetitive but two other Mac laptops are connected to the same network and working perfectly. The network preferences, as shown in the "advanced" section, are the same for all machines, i.e. DHCP is selected and IPv6 is Automatic.

Bizarre WiFi Connectivity Issue; Self-Assigned IPs, Static IP Doesn't work

The short and sweet of the problem: Macs/Apple Devices are pulling self-assigned IP addresses when connecting to a Linksys EA6900/AC1900 router.
Here’s the detail: I am working at an office with 1 Airport Extreme and 1 Linksys EA6900/AC1900, both are configured for Bridge Mode and both use WPA. DHCP is being handled by a Watchguard XTM5 series firewall.
When Macs (and often iPhones) connect to the Linksys (on 2.4 or 5Ghz) they get a self-assigned IP address. If you enter a manual address you still do not have any connectivity. However, if you connect to the Extreme you will instantly get an IP address, and if you switch to the Linksys your DHCP address will carry over and you will retain connectivity. This problem does not happen to the Windows machines in the office- they all connect to all base stations without any issue. Total users on the network range from 5 to 20 WiFi users at any given time plus and AppleTV (also affected).
More info: When there are between 5-10 people in the conference room for a morning meeting the Macs will all revert to self-assigned addresses (even if they were working before). The workaround has been to connect to the Extreme, but there are occasions when this occurs that the Extreme will also not seem to pass the DHCP addresses from the firewall; addresses become self-assigned and you lose all internet. To make matters more odd, this behavior seems to really only affect the network during business hours; after hours the Linksys works pretty much normally and any device can connect without issue.
Things I’ve done: Run Wireshark and located a number of rogue devices that were handing out overlapping DHCP addresses. Identified machines that were ARP storming and removed them. Expanded the DHCP pool so that we aren’t running out of addresses and confirmed that we had enough by checking the logs.
More things I’ve done: Used Netspot to check signal strength and channel overlap and isolation. I have mapped the signal strength by location and we have strong signals to the various locations (the Linksys AP is 7 feet from the conference room). I have checked that the firmware is the most recent version.
I can’t find any logical reason for the Macs (and pretty much only the Macs/Apple devices) to not be picking up DHCP info through the bridge mode devices. I would tell them to get another Extreme but they are going to be deploying a Cisco Meraki system soon and I suspect that this problem will persist since the Linksys was put in place because the last AP displayed the same behavior with the Macs picking up self-assigned IPs. Affected Macs range from 2010 era MBP and Air to 2013 MBP and Air and they are running OSX 10.8 through 10.10.
As for the history of this network, I just walked into this company and know very little about how well it worked before, but apparently it has always been flaky according to the staff.

I agree that something isn't right; I am going to cut over DHCP services from the Watchguard to the newly deployed OS X Server tonight and see if that changes anything.
On the other hand, faulty DHCP server/client settings doesn't explain why applying a static IP still leaves you with no connectivity. I think that clue is also fairly important but I can't figure out what would be blocking connectivity on a static IP setup.

Self Assigned IP? Can't connect~!

Self-Assigned IP? Cannot connect to the internet. I see the router/network name, I have good connection, but no IP? It assigns a 169.xxx.xx.xxx
-I have repaired permissions
-Deleted AirPort from the network list and re-added it
-Deleted plists
-Turned off the router and laptop, waited, turned back on
-Renew DCHP lease
Is there an order I can do things in or some other step? For some reason, it just STOPPED WORKING out of the blue today, and I have been trying to fix it for hours to no avail...
Router: Seimens Gigaset SE567
Mac OS 10.6.7
MacBook Intel Core2 Duo 2 GHz
AirPort Extreme Card

It might help to reset the connection settings on your Mac using these steps one at a time until the problem is resolved, recognizing that, depending on your problem, not all of these steps will make sense:
1) Use the AirPort menu bar item to turn AirPort off, then on again.
2) Try to select your Wi-Fi network from the AirPort menu.
3) In the Network panel of System Preferences delete the AirPort item from the left column, then add it back.
4) In the same panel as (3), define a new location and see if you can make that work.
5) In the same panel, select the AirPort connection item, click the "Advanced" button, select the "TCP/IP" tab, then click "Renew DHCP Lease".
6) In the folder /Library/Preferences ( _not_ <yourhomefolder>/Library/Preferences), move the folder SystemConfiguration onto the Desktop, then restart your computer. See if you can now make your AirPort connection work.
These steps may not help, but they'll only take a couple of minutes to try. Before you try these, if you have any special network settings on your Mac for things like DSL credentials, note all your network settings, because the latter steps will destroy them. If you got all the way to the last step, if things don't work any worse than before, you can trash the saved SystemConfiguration folder.

Self-assigned IP help

There's other topics on this thread, but I can't find the answer.
Last night everything was fine. Today, my Airport is self-assigning an IP address and although it can see the wireless network, it can't get out to the internet.
I've turned the Airport on and off, tried to manually renew DHCP lease, and deleted the network preferences plist files but to no avail.
Tried to create a new location but the new location keeps deleting itself.
Any ideas?

I have been having the same issue of the Self-Assigned IP address. I am running an Airport Extreme with an Airport Express connected for iTunes sharing. I have two other macs (iMac G5 and white MacBook) connected to the Airport Extreme as well as a PS3. These two computers and the PS3 are able to access the internet and the network (for printer sharing, iTunes sharing, etc) with out any problems. The only computer with a problem is my iMac G4.
I have tried numerous diagnostics with no luck, including everything posted earlier in this thread. The problem starts out with the iMac G4 showing that my Airport is turned on and has excellent signal strength. When I start up Mail, iChat or Safari I show that I am not connected to the Internet. I then checked System Preferences/Network and the Airport shows that it has a Self-Assigned IP address.
I then unplugged my Airport and cable modem and waited several minutes before plugging them back in. Network settings still showed a Self-Assigned IP. I confirmed that all the other computers were still able to access the Internet.
I then performed maintenance scripts on the iMac G4 as well as using disk utilities to fix any permissions problems (there were some but according to Apple Support they are notifications and can be ignored). I then restarted the iMac G4 and Network settings still showed a Self-Assigned IP.
I went into System Preferences/Network/Advanced/TCP-IP and changed Configure IPv4 from Using DHCP to Manually. I manually entered a 10.0.X.X address, set the subnet mask to match the Airport Extreme and entered the router address all of which I got off of one of the other macs which was connected to the Airport Extreme. I ensured that the 10.0.X.X address I used was not in use. Then clicked okay and Apply.
My Airport now shows Connected with a green dot but I still do not have Internet access. After all of this I re-confirmed that the other computers still had access which they did (hence I can write this post).
I have searched Apple Support as well as the Apple Discussions. I found and tried many possible solutions on posts that sounded very similar but nothing worked.
I am stuck. I don't know what the next step is except to send the iMac G4 to the dump and buy a new computer which I really can't do right now. Any help would be greatly appreciated.

Self Assigned IP from my macbook pro to xbox through ethernet...

I live in a college dorm and i have been using internet sharing through an ethernet cable to connect to xbox live and it has been working fine for months now, but has now recently decided to make everything difficult and it continuously just says self assigned IP address cannot connect to internet. Every video and forum I have tried reading generally refers back to something involving the router however in this case my wifi is working no problem its just the ethernet cable going to my xbox that has the self assigned IP problem. If anyone could help me it would be greatly appreciated, thank you!

It isn't clear what you are trying to do. Why are you connected to the Xbox? Is the Xbox suppose to share the internet through your mac?
Since there is so little information, I'm going to go through a lot of stuff you might already know.
You have two network interfaces on your Mac. en0 which is the cable and en1 which is the wireless.
IP addresses are assigned through a process called DHCP. When you have a self-assigned address there is no DHCP server.
The DHCP server -may- be on a router or it may be on several different devices such as a Unix computer (or Linux) specifically set up to provide DHCP addresses. Since you are in a dorm, is is quite likely a specifically configured host is providing DHCP.
Your wireless network will get a different DHCP address than your wired network. For example, 128.1.0.0/16 might be the network assigned to the wireless to support 253x253 different hosts (a lot of hosts and the main reason to keep DHCP off of the router). And something like 129.1.0.0/16 would be assigned to the wired network.
The DHCP server for the wireless network WILL NOT provide an address for en0.
NOTE: I have never used Apple's Internet Sharing and I -assume- that when you share that the Mac acts like a bridge.
I also assume that this is what you are attempting to do with your Xbox. This would mean that the Xbox would have to initiate a DHCP request for an address that is forwarded (bridged) through the Mac to the DHCP server. This request includes the Xbox hardware address. Now comes the part that is going to make you cry. MAC addresses are 48 bits and look like AB:CD:EF:12:34:56. The first 24-bits are assigned to a manufacturer and used for specific products. When the DHCP request gets to the DHCP server, it knows that the request is from an Xbox. Your campus may have decided that you've been playing too many games and does not respond with an IP address for the Xbox.
You can check this out by using a tool called tcpdump or you can install Wireshark. If you want to go down this rabbit hole, it is going to require quite a bit of time and you'll end up becoming quite well educated in how networking works. People go to school for years to understand this. :-)
Or, maybe you just forgot to ensure internet sharing was on.
If you have some other kind of wiring setup then perhaps you have a different problem.
BTW, when you plug the ethernet cable from the Xbox into the mac that "activates" it.
By default OSX is configured to use DHCP to provide an address.
If the Mac sends out DHCP requests over the ethernet cable and never gets a response it will then self-assign an address.
A self-assigned address cannot be used to get to the internet.
(But, I understand that it your Xbox that isn't working not the Mac, especially since you were able to post your question here.)

Self-assigned IP****cannot connect to university wireless network

After i installed snow leopard I cannot connect properly to my university network. It says that a self assigned IP and cannot connect to the internet.
I have tried many things but nothing seems to change this problem
I need to be able to connect to the internet at school.

I have the same problem with the Exchange server at my work. Once I loaded Snow Leopard, no access. I can get on my Time Machine at home fine and can even access the open WAP at work, but since Snow Leopard access to the Exchange server is gone. The hype for Snow Leopard says easier access to Exchange services but I can't find any info on what that means anywhere. Anybody find the Exchange info?

Self-assigned IP on one device at startup which eventually corrects itself

I use a Time Capsule as my primary wireless router (full disclosure: an Airport Express also acts as a repeater, and a wired Netgear router is also connected). 8 out of 9 devices connect wired and wirelessly without any issue, except for a wireless MacBook Pro which always boots and wakes with a self-assigned IP (no internet connection) despite a successful connection to my WPA wireless network. After 3-5 minutes, and perhaps coincidentally after a Time Machine backup is started manually or automatically, the internet connection rights itself.
I have tried every solution I could find - at least a dozen - including resetting all devices and waiting, deleting airport preferences, renewing DHCP lease, uninstalling and reinstalling Airport, deleting and creating locations, deleting keychain entries, turning off firewall, updating firmware and software, safe mode reboot, etc. Can anyone offer any last wisdom?

Siouxnil wrote:
deleting airport preferences, renewing DHCP lease, uninstalling and reinstalling Airport, deleting and creating locations
From your description I'm guessing you tried the steps below. If not, you might try the remaining ones.
1) Use the AirPort menu bar item to turn AirPort off, then on again.
2) In the Network panel of System Preferences delete the AirPort item from the left column, then add it back.
3) In the same panel as (2), define a new location and see if you can make that work.
4) In the folder /Library/Preferences (not <yourhomefolder>/Library/Preferences), move the folder SystemConfiguration onto the Desktop, then restart your computer. See if you can now make your AirPort connection work.

Self Assigned IP address – can't figure this out. Frustrated.

This is a long post but bear with me. It proposes a challenge for the mac connoisseur. Who knows? Might be fun?
OK, here goes:
Please help. I have been trying to fix this for about 7 months. I first noticed this issue when I started traveling around the country, from hotel to hotel. While others (PC's and Mac's) had no trouble connecting to the free wifi at these hotels, I did. I kept getting "self-assigned i.p."
This was extremely frustrating. I often had to call up the i.t. guys and ask them to help me manually put in ip address, subnet mask, router (gateway), and dns. This worked much of the time but not always.
Let me also say that, sometimes it worked perfectly! I'd say about 25% of the time (at these hotels) my internet worked perfectly – just connected immediately. The other 75... "self-assigned i.p."
I just spoke to the mac "geniuses" and they told me it's not an issue with my computer at all (either hardware or software). Are you kidding me?!?! How can they explain everyone else's internet working except mine. And I'm talking like 100 or more different hotels in a 4 month period. They were trying to tell me that it was just a coincidence every time! "You'd be surprised" one guy said. Hahaha. They said that the routers aren't accepting my computer's whatever. OK, well WHY?! The router works for everyone but me. It's something wrong with my computer right?! Well no one acknowledged this.
More background info:Just had my airport card and logic board replaced. Computer came back and the sheet said "passed all hardware tests." BUT, none of my issues (I had other ones too involving battery life and not being able to access certain websites) were fixed.
I went to an apple store. They told me to do an erase and reinstall or whatever. So I did that (by dragging and dropping everything I'd saved on an external hard drive using disk utility). By the way, I also upgraded from leopard to snow leopard. So now, if I have the same issues after this I'll know both leopard and snow leopard are screwed up.... right?
OK, so I followed their instructions on deleting and reinstalling to a tee and guess what?! Everything worked! Or so it seemed. Battery fine. Websites now accessible. I figured the airport issue was fixed too. But now that I'm not touring anymore and the airport works in my house, I never encountered any issues. Until now. At my work.
I got a new job and it's one in which I HAVE to have a computer that connects to the internet. So of course, the same issue with self assigned i.p. presents itself. Everyone else in the office has no problem. Including a Mac person that used to work there.
I've been reading some other threads that are just completely confusing me. One of them might be the solution but I thought I'd detail my troubles so that some smart computer person out there can diagnose my specific problem and give me a specific fix.
I noticed that many people believe there was a bug in one of the 10.5 updates. I am pretty quick to install updates (maybe I shouldn't be because I hear that the first updates are often buggy and maybe you should wait for a while). But this problem has continued now with Snow Leopard too so... I don't know. I don't know anything anymore. I have tried everything. And Apple is telling me it's not a problem with my computer. Give me a break.
One more interesting quirk: before doing the erase and reinstall my computer could not find the Apple Store's network. After the erase and reinstall it works. That's why I assumed everything was fine! But no. And now the Mac people are saying there's no problem because they can't see it.
BTW, I have tried all the obvious things. It's not an obvious thing. But I mean, if you think it is... then tell me I guess. But I've been in the advanced tab thousands of times. I feel like I've exhausted everything in there.
Thank you thank you thank you in advance if someone is actually able to solve my issue.

continuation of console log:
Feb 1 13:08:45 localhost kernel[0]: npvhash=4095
Feb 1 13:08:45 localhost kernel[0]: PAE enabled
Feb 1 13:08:45 localhost kernel[0]: 64 bit mode enabled
Feb 1 13:08:45 localhost kernel[0]: Darwin Kernel Version 10.2.0: Tue Nov 3 10:37:10 PST 2009; root:xnu-1486.2.11~1/RELEASE_I386
Feb 1 13:08:45 localhost kernel[0]: vmpagebootstrap: 507215 free pages and 17073 wired pages
Feb 1 13:08:45 localhost kernel[0]: standard timeslicing quantum is 10000 us
Feb 1 13:08:45 localhost kernel[0]: migtable_maxdispl = 73
Feb 1 13:08:45 localhost kernel[0]: AppleACPICPU: ProcessorId=0 LocalApicId=0 Enabled
Feb 1 13:08:45 localhost kernel[0]: AppleACPICPU: ProcessorId=1 LocalApicId=1 Enabled
Feb 1 13:08:45 localhost kernel[0]: calling mpopolicyinit for TMSafetyNet
Feb 1 13:08:45 localhost kernel[0]: Security policy loaded: Safety net for Time Machine (TMSafetyNet)
Feb 1 13:08:45 localhost kernel[0]: calling mpopolicyinit for Quarantine
Feb 1 13:08:45 localhost kernel[0]: Security policy loaded: Quarantine policy (Quarantine)
Feb 1 13:08:45 localhost kernel[0]: calling mpopolicyinit for Sandbox
Feb 1 13:08:45 localhost kernel[0]: Security policy loaded: Seatbelt sandbox policy (Sandbox)
Feb 1 13:08:45 localhost kernel[0]: Copyright (c) 1982, 1986, 1989, 1991, 1993
Feb 1 13:08:45 localhost kernel[0]: The Regents of the University of California. All rights reserved.
Feb 1 13:08:45 localhost kernel[0]: MAC Framework successfully initialized
Feb 1 13:08:45 localhost kernel[0]: using 10485 buffer headers and 4096 cluster IO buffer headers
Feb 1 13:08:45 localhost kernel[0]: IOAPIC: Version 0x20 Vectors 64:87
Feb 1 13:08:45 localhost kernel[0]: ACPI: System State [S0 S3 S4 S5] (S3)
Feb 1 13:08:45 localhost kernel[0]: mbinit: done (64 MB memory set for mbuf pool)
Feb 1 13:08:45 localhost kernel[0]: rooting via boot-uuid from /chosen: 5924DB5A-4C9F-323F-BC39-2469AEAB4D18
Feb 1 13:08:45 localhost kernel[0]: Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string> <key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>
Feb 1 13:08:45 localhost kernel[0]: com.apple.AppleFSCompressionTypeZlib load succeeded
Feb 1 13:08:45 localhost kernel[0]: AppleIntelCPUPowerManagementClient: ready
Feb 1 13:08:45 localhost kernel[0]: FireWire (OHCI) TI ID 8025 built-in now active, GUID 001b63fffe8a7584; max speed s800.
Feb 1 13:08:45 localhost kernel[0]: Got boot device = IOService:/AppleACPIPlatformExpert/PCI0 /AppleACPIPCI/SATA@1F,2/AppleICH8AHCI/PRT0@0/IOAHCIDevice@0/AppleAHCIDiskDriver /IOAHCIBlockStorageDevice/IOBlockStorageDriver/FUJITSU MHW2120BH Media/IOGUIDPartitionScheme/Untitled@2
Feb 1 13:08:45 localhost kernel[0]: BSD root: disk0s2, major 14, minor 2
Feb 1 13:08:45 localhost kernel[0]: [Bluetooth::CSRHIDTransition] switchToHCIMode (legacy)
Feb 1 13:08:45 localhost kernel[0]: [Bluetooth::CSRHIDTransition] transition complete.
Feb 1 13:08:45 localhost kernel[0]: CSRUSBBluetoothHCIController::setupHardware super returned 0
Feb 1 13:08:45 localhost kernel[0]: AppleIntelCPUPowerManagement: initialization complete
Feb 1 13:08:45 localhost kernel[0]: AppleYukon2: Marvell Yukon Gigabit Adapter 88E8055 Singleport Copper SA
Feb 1 13:08:45 localhost kernel[0]: AppleYukon2: RxRingSize <= 1024, TxRingSize 256, RXMAXLE 1024, TXMAXLE 768, STMAXLE 3328
Feb 1 13:08:46 localhost kernel[0]: yukon: Ethernet address 00:1b:63:94:9c:ad
Feb 1 13:08:46 localhost kernel[0]: systemShutdown false
Feb 1 13:08:47 localhost kernel[0]: NVDANV50HAL loaded and registered.
Feb 1 13:08:47 localhost kernel[0]: Previous Shutdown Cause: 5
Feb 1 13:08:47 localhost kernel[0]: Atheros: mac 12.2 phy 8.1 radio 12.0
Feb 1 13:08:47 localhost kernel[0]: DSMOS has arrived
Feb 1 13:08:47 localhost kernel[0]: AirPort_AthrFusion: Ethernet address 00:1e:52:77:13:82
Feb 1 13:08:47 localhost kernel[0]: IO80211Controller::dataLinkLayerAttachComplete(): adding AppleEFINVRAM notification
Feb 1 13:08:56 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Down on en1. Reason 1 (Unspecified).
Feb 1 13:09:05 Michael-Pines-MacBook-Pro kernel[0]: Warning - com.apple.driver.InternalModemSupport declares no kernel dependencies; using com.apple.kernel.6.0.
Feb 1 13:09:13 Michael-Pines-MacBook-Pro kernel[0]: en1: 802.11d country code set to 'US'.
Feb 1 13:09:13 Michael-Pines-MacBook-Pro kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 149 153 157 161 165
Feb 1 13:12:08 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Up on en1
Feb 1 13:15:38 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
Feb 1 13:15:39 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Up on en1
Feb 1 13:18:08 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
Feb 1 13:18:08 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Up on en1
Feb 1 13:31:48 Michael-Pines-MacBook-Pro kernel[0]: hibernate image path: /var/vm/sleepimage
Feb 1 13:31:48 Michael-Pines-MacBook-Pro kernel[0]: sizeof(IOHibernateImageHeader) == 512
Feb 1 13:31:48 Michael-Pines-MacBook-Pro kernel[0]: Opened file /var/vm/sleepimage, size 2147483648, partition base 0xc805000, maxio 400000
Feb 1 13:31:48 Michael-Pines-MacBook-Pro kernel[0]: hibernate image major 14, minor 2, blocksize 512, pollers 5
Feb 1 13:31:48 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Down on en1. Reason 7 (Frame received from nonassociated STA).
Feb 1 13:31:48 Michael-Pines-MacBook-Pro kernel[0]: hibernateallocpages flags 00000000, gobbling 0 pages
Feb 1 13:31:48 Michael-Pines-MacBook-Pro kernel[0]: en1: 802.11d country code set to 'US'.
Feb 1 13:31:48 Michael-Pines-MacBook-Pro kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 149 153 157 161 165
Feb 1 13:31:50 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Up on en1
Feb 1 13:31:50 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Down on en1. Reason 7 (Frame received from nonassociated STA).
Feb 1 13:31:50 Michael-Pines-MacBook-Pro kernel[0]: System SafeSleep
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: hibernatepage_listsetall start
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: hibernatepage_listsetall time: 114 ms
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: pages 274489, wire 35250, act 50684, inact 887, spec 62, zf 137, throt 0, could discard act 24613 inact 28670 purgeable 6142 spec 128044
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: hibernatepage_listsetall found pageCount 87020
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: IOHibernatePollerOpen, mlget_interruptsenabled 0
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: IOHibernatePollerOpen(0)
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: writing 86158 pages
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: image1Size 73471488
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: PMStats: Hibernate write took 4108 ms
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: all time: 4108 ms, comp time: 592 ms, deco time: 0 ms,
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: image 166148608, uncompressed 353234944 (86239), compressed 162715248 (46%), sum1 dc78ee00, sum2 4fe372a2
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: hibernatewriteimage done(0)
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: sleep
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: Wake reason = UHC3
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: System Wake
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: Previous Sleep Cause: 0
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: USB (UHCI)ort 2 on bus 0x5d has remote wakeup from some device
Feb 1 13:41:08 Michael-Pines-MacBook-Pro kernel[0]: en1: 802.11d country code set to 'US'.
Feb 1 13:41:08 Michael-Pines-MacBook-Pro kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 149 153 157 161 165
Feb 1 13:41:09 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Up on en1
Feb 1 13:50:04 Michael-Pines-MacBook-Pro kernel[0]: IOHIDSystem::relativePointerEventGated: VBL too high (33307137), capping to 20000000
Feb 1 13:55:23 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
Feb 1 13:55:23 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Up on en1
Feb 1 13:59:32 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
Feb 1 13:59:32 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Up on en1
Feb 1 15:24:13 Michael-Pines-MacBook-Pro kernel[0]: systemShutdown true
Feb 1 15:24:13: --- last message repeated 1 time ---
Feb 1 15:24:13 Michael-Pines-MacBook-Pro kernel[0]: Kext loading now disabled.
Feb 1 15:24:13 Michael-Pines-MacBook-Pro kernel[0]: Kext unloading now disabled.
Feb 1 15:24:13 Michael-Pines-MacBook-Pro kernel[0]: Kext autounloading now disabled.
Feb 1 15:24:13 Michael-Pines-MacBook-Pro kernel[0]: Kernel requests now disabled.
Feb 1 15:24:32 localhost kernel[0]: npvhash=4095
Feb 1 15:24:32 localhost kernel[0]: PAE enabled
Feb 1 15:24:32 localhost kernel[0]: 64 bit mode enabled
Feb 1 15:24:32 localhost kernel[0]: Darwin Kernel Version 10.2.0: Tue Nov 3 10:37:10 PST 2009; root:xnu-1486.2.11~1/RELEASE_I386
Feb 1 15:24:32 localhost kernel[0]: vmpagebootstrap: 507215 free pages and 17073 wired pages
Feb 1 15:24:32 localhost kernel[0]: standard timeslicing quantum is 10000 us
Feb 1 15:24:32 localhost kernel[0]: migtable_maxdispl = 73
Feb 1 15:24:32 localhost kernel[0]: AppleACPICPU: ProcessorId=0 LocalApicId=0 Enabled
Feb 1 15:24:32 localhost kernel[0]: AppleACPICPU: ProcessorId=1 LocalApicId=1 Enabled
Feb 1 15:24:32 localhost kernel[0]: calling mpopolicyinit for TMSafetyNet
Feb 1 15:24:32 localhost kernel[0]: Security policy loaded: Safety net for Time Machine (TMSafetyNet)
Feb 1 15:24:32 localhost kernel[0]: calling mpopolicyinit for Quarantine
Feb 1 15:24:32 localhost kernel[0]: Security policy loaded: Quarantine policy (Quarantine)
Feb 1 15:24:32 localhost kernel[0]: calling mpopolicyinit for Sandbox
Feb 1 15:24:32 localhost kernel[0]: Security policy loaded: Seatbelt sandbox policy (Sandbox)
Feb 1 15:24:32 localhost kernel[0]: Copyright (c) 1982, 1986, 1989, 1991, 1993
Feb 1 15:24:32 localhost kernel[0]: The Regents of the University of California. All rights reserved.
Feb 1 15:24:32 localhost kernel[0]: MAC Framework successfully initialized
Feb 1 15:24:32 localhost kernel[0]: using 10485 buffer headers and 4096 cluster IO buffer headers
Feb 1 15:24:32 localhost kernel[0]: IOAPIC: Version 0x20 Vectors 64:87
Feb 1 15:24:32 localhost kernel[0]: ACPI: System State [S0 S3 S4 S5] (S3)
Feb 1 15:24:32 localhost kernel[0]: mbinit: done (64 MB memory set for mbuf pool)
Feb 1 15:24:32 localhost kernel[0]: rooting via boot-uuid from /chosen: 5924DB5A-4C9F-323F-BC39-2469AEAB4D18
Feb 1 15:24:32 localhost kernel[0]: Waiting on <dict ID="0"><key>IOProviderClass</key> <string ID="1">IOResources</string><key>IOResourceMatch</key> <string ID="2">boot-uuid-media</string></dict>
Feb 1 15:24:32 localhost kernel[0]: com.apple.AppleFSCompressionTypeZlib load succeeded
Feb 1 15:24:32 localhost kernel[0]: AppleIntelCPUPowerManagementClient: ready
Feb 1 15:24:32 localhost kernel[0]: FireWire (OHCI) TI ID 8025 built-in now active, GUID 001b63fffe8a7584; max speed s800.
Feb 1 15:24:32 localhost kernel[0]: Got boot device = IOService:/AppleACPIPlatformExpert/PCI0/AppleACPIPCI/SATA@1F,2/AppleICH8AHCI/PR T0@0 /IOAHCIDevice@0/AppleAHCIDiskDriver/IOAHCIBlockStorageDevice/IOBlockStorageDriv er /FUJITSU MHW2120BH Media/IOGUIDPartitionScheme/Untitled@2
Feb 1 15:24:32 localhost kernel[0]: BSD root: disk0s2, major 14, minor 2
Feb 1 15:24:32 localhost kernel[0]: [Bluetooth::CSRHIDTransition] switchToHCIMode (legacy)
Feb 1 15:24:32 localhost kernel[0]: [Bluetooth::CSRHIDTransition] transition complete.
Feb 1 15:24:32 localhost kernel[0]: CSRUSBBluetoothHCIController::setupHardware super returned 0
Feb 1 15:24:32 localhost kernel[0]: AppleIntelCPUPowerManagement: initialization complete
Feb 1 15:24:32 localhost kernel[0]: AppleYukon2: Marvell Yukon Gigabit Adapter 88E8055 Singleport Copper SA
Feb 1 15:24:32 localhost kernel[0]: AppleYukon2: RxRingSize <= 1024, TxRingSize 256, RXMAXLE 1024, TXMAXLE 768, STMAXLE 3328
Feb 1 15:24:33 localhost kernel[0]: yukon: Ethernet address 00:1b:63:94:9c:ad
Feb 1 15:24:33 localhost kernel[0]: systemShutdown false
Feb 1 15:24:44 localhost kernel[0]: Previous Shutdown Cause: 5
Feb 1 15:24:44 localhost kernel[0]: Atheros: mac 12.2 phy 8.1 radio 12.0
Feb 1 15:24:44 localhost kernel[0]: NVDANV50HAL loaded and registered.
Feb 1 15:24:44 localhost kernel[0]: DSMOS has arrived
Feb 1 15:24:44 Michael-Pines-MacBook-Pro kernel[0]: AirPort_AthrFusion: Ethernet address 00:1e:52:77:13:82
Feb 1 15:24:44 Michael-Pines-MacBook-Pro kernel[0]: IO80211Controller::dataLinkLayerAttachComplete(): adding AppleEFINVRAM notification
Feb 1 15:24:45 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Down on en1. Reason 1 (Unspecified).
Feb 1 15:24:45 Michael-Pines-MacBook-Pro kernel[0]: en1: 802.11d country code set to 'US'.
Feb 1 15:24:45 Michael-Pines-MacBook-Pro kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 149 153 157 161 165
Feb 1 15:24:51 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Up on en1
Feb 1 15:24:52 Michael-Pines-MacBook-Pro kernel[0]: Warning - com.apple.driver.InternalModemSupport declares no kernel dependencies; using com.apple.kernel.6.0.
Feb 1 15:25:35 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).

Self assigned IP : still no bug fix ?

I have a problem for a long time with my Time Capsule. I use an ADSL modem and router (from Free French ADSL Provider) and my TC is plugged on it and set to "Bridge" mode.
I have many devices wired and wireless on the TC. But I have a big problem, sometimes (not all the time), my MacBook is getting a "169.254.x.x" IP address, a self assigned IP.
That's weird because sometimes it works well from 6 AM to 7 PM for example, then at 7 PM it doesn't work anymore. There is no reason why, because I haven't touch anything in my network.
It's pretty annoying. Is Apple aware of this problem ? Can we hope a fix soon ? I had many problems with the WIFI on my Mac (before, it was the "wake up" WIFI problem but it seems to be fixed in the last Lion update).
I've tried everything, reset all (TC, Macbook etc.), sometimes it works a day, the other day it's not
Thanks

7pm sounds too specific to me.. get a wifi analysing software, kismet on the mac but inssider on a pc is a better utility. Locate all the wireless around you and what channels are used. I would say you are being swamped by higher intensity wireless than the TC can produce.
Go into the wireless setup and change over to manual settings.. set to N wireless.. and set to manual channels.
In 2.4ghz try 1, 6, 11.. but pick whatever is the lowest usage from your survey of wireless usage.
Also try and use 5ghz as it has less interference. When you are bridged, the IP address is derived from the modem and not the TC so the issue can be there.. try setting dhcp to fixed for the MAC address of each wireless. and set the lease to very short.. 30min or even try 10min.
There certainly are issues with Lion networking.. exactly what is hard to figure out.. but you can also try the TC with earlier firmware.. go back to 7.5.2 which was much more reliable than later ones.
You can also try it in router mode putting the modem in bridge if the ISP supports PPPoE.. or use DMZ with the modem still doing routing. The TC will kick up a double NAT error but just select to ignore it. Sometimes it will work better in router mode.

10.5.5 Self Assigned IP OR no connection at all

Similar Messages

Maybe you are looking for