Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Yesterday, my MacBook Pro connected fine, but today won't connect to the Cisco wireless router. I'm running OS 10.6.8. I don't know how this happened but I do know that my IP address is reading 162.... and should likely be a 192.... address.

Does anyone know how to optimize my system to correct for this IP address problem?

Many Thanks!!!

share|improve this question
    
What happens when you try to connect? How far do you get? What's the first thing that goes wrong? Can you detect the wireless network? – David Schwartz Jul 26 '12 at 3:11

Addresses in the 169.254.0.0 range are IPv4 link-local addresses. Are you sure it was 162 and not 169? A link-local address would indicate that DHCP is not available. DHCP is the service from your router which automatically provides an IP address to your computer. It can be very useful to set a static IP address while you troubleshoot DHCP.

Unfortunately, troubleshooting DHCP can be a bear. Start by putting yourself back on the network your router is on (the router is most likely 192.168.0.1 or 192.168.1.1) and navigating to your router's settings to see if DHCP is on. If you can't find your router at 192.168.0.1 or 192.168.1.1 by putting http://[ip address] in your browser, something is probably wrong with the router. Otherwise you're going to need help troubleshooting DHCP issues on OS X.

share|improve this answer
    
Whoa, I had no idea APIPA was a Microsoft thing. Thanks Spiff! – Tanner Faulkner Jul 26 '12 at 7:36

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .