Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

raoulgravel

macrumors newbie
Original poster
Dec 5, 2009
2
0
Good afternoon,

I recently reimaged a 30-seat lab running iMac G3, 600 MhZ, 10.3.9.

80% of the computers are able to connect to the internet using DHCP. 20% are currently experiencing issues. When I enter into Network I find that they have assigned themselves an internal IP (169.254.50.37).

The interesting thing is that when I statically address the computers, they work fine.

I have already tried creating a new network location, renewing DHCP lease through Terminal, and using multiple user names within the system. Although, since they are relatively new images there is not much difference between the computers that are functioning and those that are not.

Anyone care to take a guess at why the device is not able to acquire DHCP? (I am not out of leases from my Netgear ProSafe VPN/Router, and I do not filter by MAC.)

Thanks,

R.J.
Director of Technology
St. Bede the Venerable
Chicago, IL
 

Consultant

macrumors G5
Jun 27, 2007
13,314
36
I find that's typically a router issue. If you can, reboot the router (maybe 6am?) to see whether you still have the issue.
 

Les Kern

macrumors 68040
Apr 26, 2002
3,063
76
Alabama
Seems like it could be a lease issue. Sometimes routers are set to hand out a limited amount of numbers... say from 192.168.1.1 to 20. Then try something simple, like trashing your networkconfig.plist from Library >Preferences (not users Library) then restarting.
Interesting....
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.