Self-assigned IP using ethernet

[lskdjf]

I've already read some threads about the problem with the self-assigned ip, but couldn't find a solution. Also the situation is always slightly different to mine.

I have a macbook pro with OSX 10.6.8. I use it at work with ethernet connection and DHCP and it works fine. Also airport works.

At home i have a cable modem (no wifi) and connect my laptop via ethernet. It once used to work, but not anymore. I get a self-assigned ip and can't use the internet. i also have a laptop running with windows and when i connect that one to the modem it works fine. I don't get a regular 192.x.x.x. ip but some strange other number, but i can access the internet.

So somehow, it's not about the modem or internet provider, but also not about the macbook. i guess it's rather about the combination of both...
Does anyone know an answer to my problem?

Cheers

 

[miles01110]

Try making another network location.

 

[lskdjf]

yea, i tried that. I also chose the manual settings and entered the ip, subnet... from the windows laptop. but no success

 

[rowley]

if you are not getting a 192.x.x.x ip address automatically (when you connect to the network), then it might be that the DHCP server on your cable modem has stopped.

You will need to put in a static IP Address similar to the routers.
Check the routers IP (might be on a sticker somethere, 192.168.0.254), set the computers ip address to something similar

eg.
192.168.0.100
subnet mask 255.255.255.0
gateway to the routers (192.168.0.2)
dns 8.8.8.8

If all those numbers are in right you should at least get connectivity.
open a terminal and use ping to check

ping 192.168.0.254

if you get a reply - you are then connected to the gateway.

try and ping google.com

If you get a reply - you are connected to the internet

----------

yea, i tried that. I also chose the manual settings and entered the ip, subnet... from the windows laptop. but no success

Oh, ok.

Your windows laptop is fine connecting?

 

[lskdjf]

yes, windows laptop works fine. But as i said, the IP i'm getting is a bit strange 56.x.x.x., something like that.

 

[bigjobby]

Can you get into the router's console (eg. via a browser)? If so, check and see if your MBP's MAC address needs to be registered to use the network. Worth a shot.

 

[rowley]

odd IP, but hey.

Check DHCP - it's be a service running on the router, enable that.
then renew lease on Mac.

 

[lskdjf]

I checked the modem's console once. and as far i can remember, there were only very few options. unlike a wireless router. but i will check again.

 

[GuitarG20]

try resetting the modem (unplugging and leaving for a couple of hours) then plugging back in. that always seemed to fix mine at home.

 

[bigjobby]

try resetting the modem (unplugging and leaving for a couple of hours) then plugging back in. that always seemed to fix mine at home.

I think ~20-30 secs would normally be fine.

 

[lskdjf]

hmm, restarting the modem really did the trick... although i don't really understand why it worked on windows but not with the mac.

----------

and thanks for the replies!

 

[GuitarG20]

I think ~20-30 secs would normally be fine.

yeah, 2-3 hours is kinda overkill... xD

 

[rowley]

Probably the DHCP service had stalled. Yes apps can stall on embedded OSes too.
Your windows machine was still connected because it had picked up a valid ip address before the service bombed on the router.

Such is life.

R.