SELF-ASSIGNED IP??? (ethernet)

[ted400]

Not to sound too basic, but the 169.254.x.x IP assignment is called APIPA - Alternate Private IP Address (or assignment), which normally occurs a computer's NIC does not receive an IP assignment from its designated router or DHCP server. Once a computer's NIC is assigned an APIPA, no routing takes place. For example, the client computer can no longer ping its normal gateway (the router), nor any other computer on the network, even if also assigned an APIPA (this was covered in a class I took, but I have never independently attempted to ping two separate client computers in this scenario).

"no routing takes place"...You are correct here... but why would it occur with only ONE computer on a network? APIPA's are "handed out" by the host computer when it can't find a DHCP source. If it was truly a routing issue ALL machines would get an APIPA address upon release/renew not just one.

I first look at the, in my case, cable modem to router connection. I have found that simply powering down the cable modem and router, powering them back up (after waiting 30 seconds or longer - the cable modem first), then finally connecting the router to the cable modem normally solves the issue.

Right, this does solve the problem, but temporarily...who wants to do this every day you come home from work and sit down to use your laptop?

On one occasion, however, have I been forced to reset the router back to the factory default configuration.

OUCH! Do you really feel that rebuilding your router is a solution? How many times are you willing to do that? Once a week, once month? Not a viable or practical option for me.

Shouldn't it just work? Yes!...hence the solution Mlobo01 and I worked on to find. I have to say I have tested probably two dozen scenarios and all of them return the same result: a problem somewhere in this ONE machine's configuration. The other two machines (also running Leopard) never had this problem. AND...when I checked the access controls on the other two machines they were both set to allow all applications, the affected computer was the only one that had the wrong permissions set.....does that clarify the reason why we offer this solution? Plus it was (finally) confirmed by an Apple Product Specialist (APS's are tertiary support when you call apple care), that this was the issue.

I don't dispute the fact that resetting routers or some of the other things offered work TEMPORARILY, but wouldn't you want it to work all of the time and find the solution rather than using the band-aid approach? Thats why I spent a month researching and testing these problems, so I and all of you with the same problem would have a solution, not just a band aid. The whole idea of forums is to work together to find a common solution, thanks to Mlobo01 we were able to test and eliminate what worked and what didn't. We now have a solution.

Future posters, if you plan to post to this thread don't re-post things we have already tested, it just confuses people. Read the entire thread before offering ideas, chances are we have already tried them and either they didn't work OR they are temporary solutions.

I don't mean to sound trite, but we spent a lot of time trying to come up with the solution, so posting things that don't fix the problem don't help. This was a complicated problem from the start and if you do not read the thread from the beginning you won't understand that. I appreciate everyone's help, but don't confuse the issue here for those looking for a SOLUTION rather than a TEMPORARY fix.

Cheers!

 

[HawaiiMacAddict]

Aloha ted400,

I see that no one else has offered any assistance with this issue, which may have been due to the tone of your response too my last post. One thing that hasn't been mentioned is that the setup on the affected Macs could be at fault.

I, like most other people using Leopard, have no problems receiving a DHCP IP assignment - at least not from the computer's standpoint. Maybe you should do an erase and install on the Macs and start over again. After all, it's really not that hard to set up an internet connection. All I had to do is plug in my network cable.

HawaiiMacAddict

 

[Mlobo01]

Trouble shooting...

If you wish to trouble-shoot further just make another account and make it an administrative instead of standard, log off yours then into the new account and set your connection to see how stable it could be, I have done this before to compare what kind of internet plugins or files I get with the new account, or if there's different plugins that can prevent connections or trouble shooting quicktime videos that cant be watched if you have corrupt browser settings, caches or preferences etc, if your new account is better, then just move all your files into the new account and delete the old one, or if this one gets too buggy then you can always delete it for good and you still have your old account. also this account will have all fresh keychains and preferences, if you open a questionable app or widget then you know what's causing the issue. if you have too many files to copy over then through root or the superuser you can move these files without copying them holding down the command key while click-dragging the files being moved.

 

[ted400]

Aloha ted400,

I see that no one else has offered any assistance with this issue, which may have been due to the tone of your response too my last post.

First off, I apologized for sounding trite. I knew the tone sounded harsh but there is reason for that. I was a bit annoyed that you posted what you did. It showed that you had not read the entire thread. When people do that it sort of burns me. If you had read the entire thread, you would have seen the progression to the answer we came up with. When you spend a month troubleshooting something like this and someone offers the same idea on page four that was tried on page one, it is a bit frustrating.

One thing that hasn't been mentioned is that the setup on the affected Macs could be at fault.

Actually re-installing or repair installing has been tried several times (again earlier in the thread) there have been several people who have re-installed Leopard, and some that have even re-installed back to Tiger with no luck. This really seems odd to me, as the entries should be "fresh" but I guess it all depends on "how" they did the new installs too. I personally never tried it...thought that was overkill. I figured there was a logical reason why my ONE computer out of the three was having problems, especially when they were all running the same operating system.

I, like most other people using Leopard, have no problems receiving a DHCP IP assignment - at least not from the computer's standpoint. Maybe you should do an erase and install on the Macs and start over again. After all, it's really not that hard to set up an internet connection. All I had to do is plug in my network cable.

I am not really sure what you mean by these statements, they are a bit ambiguous. I guess the question is...Does the fix we have isolated fix the problem or not? Perhaps there are no other posts because the fix works for most people. If the fix does not work for some people, I would like to hear from them lets figure out why it doesn't, what the symptoms are and work from there. I'd be glad to continue working on the problem if there is a problem. When you say that you have no problem getting a DHCP assignment what do you mean? Do you mean you have an IP address but it is not routable? Do you get a 169.x.x.x address? It is important to know that because they are two completely different problems. One (the non-routable address) is much easier to fix (it's usually the way you have your router or network configurations set), the other as shown in this thread is much more difficult to diagnose.

 

[HawaiiMacAddict]

Aloha ted400,

I had read through all of your steps, but still think you are operating off a false premise - that Leopard is to blame for this issue. I have not had any issues, even with Windows, getting a DHCP IP assignment from my router - an APIPA assignment is NOT a valid DHCP IP assignment, as it is NOT assigned by a router. There is no valid reason that a fresh install of either Tiger or Leopard would preclude a NIC from receiving a valid DHCP IP assignment from a router, unless the subnet mask limits the network to a specific number of users which has already been met. That being said, the above scenario is not the case, as someone has already pointed out that a live cable was taken from one "working" computer and plugged into the Mac in question with negative results.

I originally performed an archive and install, then an erase and install, on both my iMac and MacBook Pro with Leopard (I just wanted a "clean start" with Leopard), but still get valid DHCP IP assignments on them - as well as my iPhone and the Windows computers on my home network. Instead of looking solely at the OS, look also at the NIC in question. The only reason an OS would preclude a NIC from receiving a valid DHCP IP assignment is if either the NIC's driver was not installed or the NIC was intentionally disabled. I deal with this on a daily basis, so I should know the subject matter a bit. At my worksite, we normally setup the computers with a static IP address and are not concerned about NAT (our networks are set up for training and are not connected to the internet), so we have to ensure that the switches are set up correctly - but my understanding is that this is a DHCP issue, vice a statically-assigned IP issue.

I'm also a bit confused by a couple of your questions, specifically concerning valid DHCP assignments. You asked: When you say that you have no problem getting a DHCP assignment what do you mean? Do you mean you have an IP address but it is not routable? Do you get a 169.x.x.x address? I have never received a DHCP IP assignment that was routable, because my router specifially uses the Class C non-routable IP address range for NAT assignment. The cable modem gets its IP assignment from my ISP and the router takes either the default IP address (192.168.0.1 or 192.168.1.1) or an IP address I assign to it, given the parameters within which I am able to operate as per the manufacturer. The router then performs NAT to address the incoming packets to the specific computer on my network requesting those packets. The 169.254.x.x IP addresses are also non-routable, ie., NOT issued from a router running DHCP, so your second and third questions are the same, but asked a bit differently.

It may just be me, but it appears that you're just grasping at straws to explain the APIPA situation and found a good scapegoat in the OS. As I mentioned in another post, all I had to do was simply open up my allowed number of computers enough to include my Macs, then simply plug in my network cable.

HawaiiMacAddict

 

[ted400]

Hawaii,
I just spent an hour replying to each of your concerns, however my browser decided to eat my response at the last minute so I am not even going to try to retype that whole mess. In brief, it is your thoughts not mine that are flawed. I quit, I tried, but you wound up showing that you know just enough to be dangerous. You need to read up on how 169 address are assigned, and why.(among other simple network concepts). You also have some mixed ideas of how networks work. I too have some experience in these issues as I support a 15,000 node network, and troubleshoot issues such as this on a daily basis.

You are correct on one thing, self assigned addresses COULD be caused by drivers or disabled NIC's but there are MANY other reasons why this can occur. I deal with it daily. When my normal troubleshooting items for this type of problem failed, I brought the problem to this forum, to seek help. Between my TESTING (not theories, real testing), and the help I received from Mlobo01 among others we were able to figure this one out. I am not saying this is the ONLY answer, but it sure seems very viable (as opposed to resetting your router daily, or rebuilding your router weekly as offered by you). In addition, the testing which lasted for more than a month never resulted in anything remotely near a stable situation. Since putting in this "fix" I have had a stable network for near two weeks (two days was the most I had during any of my testing). Not to mention the fact that the "fix" was confirmed by a Apple Product Specialist (also known as a Apple Software Engineer). I did not go into this willy-nilly as you seem to imply. My ideas that this was OS related were systematically determined and resulted in A solution (not THE solution, as there MAY be other reasons for other people)....oh, and did I mention CONFIRMED BY A APPLE PRODUCT SPECIALIST!!!!

I asked proper troubleshooting questions of you, despite the fact you felt they were all the same. They weren't... sorry, dude. In short each helps determine which level of the TCP/IP process is failing. I don't have the time or energy to go through this. If you want help great, if not forget it. You keep saying yes you have an address, then say you don't, then you say you can't route, then you say you don't need to because of some crazy-trying-to-sound-smart reference to a Class C network (um, all consumer routers are masked that way by default).

I quit, I don't have time for this type of banter. My connection works, thank you Mlobo01 and the others who gave helpful assistance. I will check in to see if anything changes (or if my connection again goes unstable) but I can't even reply to Aloha man's stuff anymore. Not worth my time. It's no fun troubleshooting issues when the person you try to help is fighting you.

Good luck Aloha Dude...and read up a little more, get some more knowledge and maybe you'll understand what I WAS trying to do.

 

[HawaiiMacAddict]

Aloha ted400,

Not to sound too harsh, but when exactly did I say that I had a problem on my network? I have had problems in the past, but not currently, but as I posted earlier, they have ALL been due to issues either with my router or with my ISP. I may not know everything you know about Mac OS, but then again, I only switched in August 2006. I have yet to find, myself, any OS, be it from Microsoft, Apple, a UNIX vendor, or any Linux distro that would preclude a computer from getting a valid IP address, provided that the computer was set up correctly in the first place, which is not hard to do, especially on a Mac. As a recent Mac switcher, that actually was one of the things I appreciated most - the ease with which I was able network all of the computers, Macs and PCs, as well as set up file sharing between them all. Reading comprehension is king.

Peace. Out.

HawaiiMacAddict

 

[Mlobo01]

Thanks guys for all the help...

I have been over the Apple forums, researching and getting my posts booted off by Apple itself for posting info about the impending upgrade, but people are posting success with some of the solutions, I have been cross-threading links so everyone can get diverse sources, cross check hints and obtain a commonality, some have used ted400's solution some have used the ipfw flush with good results.
My main focus with Leopard has been to resolve all bugs within the confines of a migrated account, I know that a 'clean install' will provide 95-100% purity providing little or no glitches, but Im very persistent, I love puzzles and this provided the boundaries for one, I needed to resolve this issue and I think I did well with everyone's help and even the posts that where too abstract to comprehend helped as well, it all goes showing a broader picture. I don't totally comprehend what was discussed about the IP addresses, but I think I can get a good shot at explaining this connectivity dilemma in more mundane terms since most of the users here vary in techno-know-how, but my experience comes from having used OS X since 10.0, and having read thousands of posts and fixes I can make a pretty good determination as to what's going on some of the time, when its something too deep then I just wait for the upgrade or research it further. Leopard has trouble with migrated accounts and settings, it writes stable files and better file permissions under its own environment, prior system caches are not properly trashed thus affecting the system or connectivity, repairing permission in Leopard seems iffy! the permissions themselves are different, the Firewall is not as robust nor its graphical qualities are practical, when I did a ipfw list (in Terminal) it showed that it was blocking my router, upon the flushing of the ipfw rules it unblocked it, some of the network settings did not stick at first, locked panes where found unlocked after sleep, restarts or even Sys Prfs quits, so you could of configured a setting but it did not stick, it seemed shaky, the System prefs app was ailing from the get go, and not to mentioned the corruptibility of Keychain Access and keys. Some haxies like Ape, App enhancer etc plagued the system with restarting daemons that affected Sleep, even people who did a clean install reported some of these same bugs as well caused by some small corruption that got worse, their systems decayed quickly or got worse over time, and my theory is that the few or various changes and modifications found in this posts helped Leo start writing more stable files and data, basically it got nudged to health. If the explanation of the IP addresses helps in any way so be it, I thank anyone who can sprinkle a bit of light into this great obscurity, but you just have to remember to keep it at a medium tech level so everyone can benefit from your advice. We have a lot of newbies and also switchers that are new to trouble-shooting through the forums, the last thing we would like to do is confuse them more. kindly: Mario

 

[Mlobo01]

so my key mission was...

to solve this within the frail environment of the migrated account, I think I beat the upgrade to it's airport corrections, and in the process I have learned quite a few new hints, I know that for some users time is precious and doing a clean install saves a lot of time, but the last thing I would like to experience is a disappointment at the titanic upgrade if it does not help, I do hope that it does help all those that could not get a fix with the hints posted here and on the Apple forums and now with my connectivity at full productivity I can focus on other aspects of Leopard, tests that have been over-shadowed by the attention paid to resolving this quagmire. Expect some stumbles a long the way in this Leopard trail, but expect good support and fixes as well.

 

[bobapsu]

Same Problem, with a twist

I'm having the same problem, but this is interesting. I am accessing the Internet, right now, typing this on an Internet connection thru my Airport Base Station via Airport card in my iBook (10.4) while at the same moment, my new Mac Pro (10.5.1), which is hooked to the same base station with Ethernet cable, gives the "self-assigned IP address" error and can't access the Internet.

hmmmmm....

Does this shine a light on the situation we are all experiencing? anyone..? http://images.macrumors.com/vb/images/smilies/confused.gif

 

[ted400]

I'm having the same problem, but this is interesting. I am accessing the Internet, right now, typing this on an Internet connection thru my Airport Base Station via Airport card in my iBook (10.4) while at the same moment, my new Mac Pro (10.5.1), which is hooked to the same base station with Ethernet cable, gives the "self-assigned IP address" error and can't access the Internet.

hmmmmm....

Does this shine a light on the situation we are all experiencing? anyone..? http://images.macrumors.com/vb/images/smilies/confused.gif

That was the same problem that I was having, exactly. Did you check your network password permissions or flush the ipfw on the affected machine as explained earlier in this thread? Those seeem to be the keys...good luck.

 

[deathshrub]

well update: now im running through a router and it seems to work fine, i think leopard is not compatible with older modems, apple need to release a fix on that, because not having internet is ridiculous

Don't blame Apple, they didn't do anything. You're the one who isn't familiar with your own network.

 

[ted400]

In summary....

This thread has begun to take on a life of it's own, so to make it easier to navigate here is a summary of usable troubleshooting steps. These are the steps which have helped most people rectify their self-assigned address (169.x.x.x) problem:


1) Check your firewall on your affected computer to be sure it is not blocking your NIC or ports 67-68 for DHCP
The easiest way is:
1) Go to System Preferencess -> Security,
2) In the Firewall tab, choose either "Allow all incoming connections" or "Allow all essential services"

2) Flush your ipfw cache
a) In Terminal type: sudo ipfw list _then press enter
b) In one of the lines it shows what ip addresses are being allowed, like this:"allow any from 192.168.0.0 to 24"
c) If this is different from your router then flush the rules with the following command: sudo ipfw flush

3) Check your keychain permissions for your Network login
a) open your keychain and look for your network log in password
b) open the password key and under the access control tab make sure the "Allow All Applications to Access This Item" is selected.

Still having problems after finishing these steps? Give detailed information such as the IP address you receive, the version of your OS, the configuration of your router (DHCP or static), etc. etc. and we can continue to troubleshoot this. Hopefully 10.5.2 can address this problem as that update is now up to a whopping 450MB! Tons of fixes coming soon...be patient.

 

[aibonlengket]

i have done all that, but no luck. but here is the good news!

So guys, I think I found the root of the problem. I have the same problem. the ethernet disconnect from the internet. I'm using a cable modem as well. so this is it, when ever the connection is lost, the MAC address somehow change by it self. from 001A9200F948 to 00009200F948, so it lost "1a" and turn it to "00". I don't know if this is just me or someone else have the same symptoms. I look this setting through system preferences>network>advance>ethernet.

I tried to change the mac address but no luck. I use:
sudo ifconfig en0 lladdr
and
sudo ifconfig en0 ether

I'm just a noob, so this is just a hunch, but it does explain why it cannot find the proper ip and self assigned.

Well, i feel stupid. nevermind what i said above. the MAC adress doesn't change. I saw it change when i upgrade security 2007-009. after reboot it did not change anymore. silly me. sori folks.

 

[Mlobo01]

Also this...

If you log into your router, under the performance or info page, look into any fields that yields any external DNS addresses your ISP may be using, If you get this info then I suggest you input this info on the DNS tab within your Network>advanced>DNS tab, click on the plus sign and add one at a time.

 

[aibonlengket]

just screw around, I search for all file that has the name firewall and moved it to desktop (if it goes wrong I copy it back)
- system>library>coreservices>ApplicationFirewall.bundle
- usr>libexec>ApplicationFirewall>Firewall
- system>library>extensions>IPFirewall.kext

reboot and it turns out the ethernet works but it's giving the usual ip self-assigned address. tried to manual input ip, and no luck. then i return the
- usr>libexec>ApplicationFirewall>Firewall
rebot, and it is working again (note:without the other two). have not tested long enough, but who knows.

I was really wondering why that (usr>libexec>ApplicationFirewall>Firewall) is required for the ethernet to work; because I though since maybe the problem was because of the firewall, I just get rid of it for good.

any thoughts?

 

[Mlobo01]

sometimes...

When you move a file back at times it makes a copy, this copy sometimes is better than what you extracted. the trouble of moving files is that you never now what other systems are being affected, but yes if you move a file, do it so you can replace it, or sometimes getting a file from a stable computer works too, as long as its the same OS version. and if you want riskier try it with using Tiger files. I just dont recommend that too much, you would have to be an advanced user.

 

[Mlobo01]

How about this

I have 2 macs, I have the following settings, maybe this can help you obtain a stable connection, starting with my router settings: I have one channel instead of Automatic, mixed mode until you get stability then you can switch to G or N, short preamble, SSID is off, but on is fine, WPA encrypted, WEP is fine but you need MAC filtering anyways on both, in the MAC filtering fields you should have all your Mac's Airport Ids registered, only these will access the internet. In the DCHP field enable a DHCP Server, which means that one of your machines needs to become this server, I selected the mini since that is what I use the most. with the Server enabled give your main mac the address of your choice preferably any numbers starting with x.x.x.100 this machine will now distribute these numbers to all machines that connect including the main Mac itself, it will get an IP address of x.x.x.101 or if you make a second location on that same machine it will become 102. (using "emac" to represent any computer)it will show up like this:"Static DHCP list:eMac: x.x.x.100 with the MAC address of (your eMac's Airport ID) in the Dynamic DHCP list your eMac shows like this: eMac:x.x.x.101 Mac address: (a string of about twenty numbers aprox.) next to it will be the lease expiration date. The IP address of the router could be 192.168.1.1 or 0.1, this field shows the subnet mask and the Domain name should be your network's name.
To my network settings, I use a secondary account, I think that the "Automatic" location is glitchy
I have checked"ask to join new networks" in the network name: (the one you use) in the Advanced section under Airport I only have my network and nothing else for now, it shows the type of security or nothing if its an open network, checked below is "Remember any networks this computer has joined" and "Disconnect from wireless networks when logging out" this enables the connection to log out properly during sleep,log outs and shut-downs. Under the TCP/IP tab: in the DHCP Client ID: is the DHCP server's IP address:x.x.x.100, ipv6 is off, hit OK, go back to the Airport network pane and select: "apply" if you get connected to the router only and no internet, then log back to your router and see if there are any DNS addresses in the Status page and input those numbers in the DNS tab in the network setting, hit ok and then Apply. try any web page and try for stability. Also before you start go to the terminal app and type: sudo ipfw flush then enter Y for yes, that flushes the ip rules of the secondary firewall thats been causing issues.In the DNS tab you should see the Routers ip address of x.x.x.1 and the Search Domain field; (the name of your network) try and post any results.

 

[aibonlengket]

Thanks Mlobo01, you have contribute alot. i did want to replace that firewall with the one from tiger, but i look at tiger and it does not have usr/libexec/ApplicationFirewall/

after further tinkering, I figured out that socketfilterfw in the usr/libexec/ApplicationFirewall/ have to be there in order to work (ofcurse just for the a while then the connection failed). so I google socketfilterfw, and come to this interesting link. http://www.extrapepperoni.com/2007/11/10/leopards-socket-firewall/

that come to my question, how to make this to allow anything and everything to go in/out? the thing is, it will deny some thing that was allowed IF, for example, the binary change.

 

[nomuno]

CAT5 connected from router to Mac Book (cable has been tested and works on several computers)
Windows partition gets correct IP Address and internet works fine.
Leopard Partition does not get internet. This is what the NIC is doing -
Green light on NIC is off, Amber Light on NIC blinks in a repetitive pattern.
IP Address for Ethernet is 169.x.x.x (x being any random number) with subnet mask of 255.255.0.0
In left pane 'Ethernet' says 'Self-Assigned IP Address'

Things I have tried to Repair issue.
1) Recycled Modem (Linksys BEFCMU10 Version 4.0) and Router (WRT54g Version 8.0) - Still 169.x.x.x
2) Loaded new Firmware in router to 8.0.4 - still 169.x.x.x
3) Hard Reset Router - still 169.x.x.x
4) Assigned static IP Address (Manual) in Leopard - Static IP address is displayed properly, but amber light on NIC is still blinking in same pattern as 169.x.x.x did and will not access internet.
5) Adjusted Mac Firewall to pass everything through - still no internet
a. Go to System Preferencess -> Security,
b. In the Firewall tab, choose either "Allow all incoming connections" or "Allow all essential services"
6) flushed ipfw firewall cache using terminal - still no internet
a) In Terminal type: sudo ipfw list _then press enter
b) In one of the lines it shows what ip addresses are being allowed, like this:"allow any from 192.168.0.0 to 24"
c) If this is different from your router then flush the rules with the following command: sudo ipfw flush
7) reset items in 'Key Chain' for anything Network related - still no internet
a) open your keychain and look for your network log in password
b) open the password key and under the access control tab make sure the "Allow All Applications to Access This Item" is selected.
8) Reinstalled OS - Issue still exists, Windows XP Partition still working great.

Things I haven't tried:
Connect directly to Cable Modem
Set static IP Address in the Router

Internet was working without issues a few days ago. World of Warcraft connects, updates and everything good a few days ago. now all the NIC does is Blink in the same Amber blinking pattern.
Amber light will blink with or without the CAT5 connected. Again, all this worked flawlessly a few days ago, no updates where done to 10.5.1 Leopard. Last thing that was done before this problem was that World of Warcraft Updated and then played.

 

[anubbus]

same issue

i have a macbook and i have been trying to connect via eathernet for hrs now.


i am set to DHCP
tried to renew DHCP lease
Reset router 10000 times

i am connecting right from the router, any ideas

 

[mike12806]

i have a macbook and i have been trying to connect via eathernet for hrs now.


i am set to DHCP
tried to renew DHCP lease
Reset router 10000 times

i am connecting right from the router, any ideas

It might help someone troubleshoot this if you could give us the router make/model, what your internet connection is, and to make sure your router is set to act as a DHCP server...

 

[Anasti]

After loading Windows XP (SP2) under Boot Camp all my problems went away. It is not a router or network problem, it really has to be a problem with the way that Leopard is handling DHCP.

If I boot in Leopard, I have the self-assigned IP address issue, if I boot as XP DHCP works normally. This is the same machine, same cable, same router, same network set-up, same desk, same chair, same room temperature settings, just that one OS can connect and another cannot.

As an aside, if I use Parallels and boot to a Vista virtual machine under Leopard, it's iffy. Sometimes connects, sometimes not.

 

[whooleytoo]

Weird!

Last night, my Airport & Ethernet worked perfectly, this morning, neither work!

The problem is - Leopard can't get a DHCP address from the server on either Ethernet or Wifi. It's not a router issue, it's Leopard. If I give it a (valid) manual IP address, it gets the router/mask settings from the DHCP server fine and networking works.

Works ok for me, but not everyone can use this workaround. A lot of people seem to be having this problem anyone know a proper fix?

 

[whooleytoo]

Ignore the above - a bit of investigating revealed it was the DHCP server stopped issuing new IP addresses for some reason. It's the same DHCP server on both Airport and Ethernet; and most of the PCs in the office have static IP which is why I thought it was only the Mac at fault.

Leopard, I'm sorry for doubting you!