DHCP problem

Discussion in 'macOS' started by Jelbert, Mar 8, 2011.

  1. Jelbert macrumors newbie

    Mar 8, 2011

    I have a mbp and a powerbook G4 both have osx 10.6.6. They are connected to a router (vigor 2300, I also tried it with other routers to the same result). The router is set to provide IP addresses. When I renew the DHCP lease on the mbp it gets assigned that is correct, the router is on
    When I renew the dhcp lease op the G4 it gets that is not OK.
    Firs I thought maybe the ethernetport is faulty but if I set it up manualy it goes ok.
    In the G4 the wifi is disabled and internet sharing is off.
    Any idea how to solve this problem?

  2. miles01110 macrumors Core


    Jul 24, 2006
    The Ivory Tower (I'm not coming down)
    Try using a different network profile on your G4.
  3. Jelbert thread starter macrumors newbie

    Mar 8, 2011
    Yeah I checked there and ended up here.
    A different profile does not work. It was a clean install.
    The assistant can not figure it out and asks me to enter the ip,mask,router info manually. Is there an obscure hardware difference in these old macs that does not make them completely compatible with 10.6.6 ?

    The whole issue is this: My girlfriend bought a new mac mini and assumed ti would work ok wen connected to a flat screen TV. That looks horrible. To hook up a monitor would be the solution. However in her room there is no space for that. So I got here a secondhand G4 titanium, thinking that with a vnc connection the problems would be solved. However with these network difficulties no problems are solved yet. I could put ubuntu on the G4 and make it so it always makes an vnc connection to the G4. That would be a weird solution and I much rather solve it with OSX.
    So any helpful tips hints and solutions out there?

  4. MacForScience macrumors 6502


    Sep 7, 2010
    This should be easy to fix.

    Manually assign the IP to the computer so for example:
    Subnet Mask

    Also make sure you set the DNS Server and Search Domain this should be the same on all machines and can be gotten from one that is working.

    This should work if not report back. (The issue is probably a self-assigned IP rather then fetching the IP over DHPP.)


Share This Page