I've recently noticed that, when I take my 1.5GHz, 17" G4 PowerBook out of sleep, it fails to connect to the internet. It's doing so via AirPort, using my NETGEAR WGR614v4.
More specifically, what I find in the TCP/IP tab of the AirPort configuration of the Network System Preferences thingie, is that DHCP gives it an IP Address and a Subnet Mask, but no Router IP Address. Poking the "Renew DHCP Lease" button doesn't change that situation.
It doesn't seem to be having any difficulties physically communicating over AirPort, since the NETGEAR critter's DHCP server is successfully supplying an IP address for it. Also, the signal strength meter in the menu bar is showing up at full power, and I've never seen it have problems other than when coming out of sleep.
Do any of you have any guesses as to what could cause it to not get a router address (only)?
Thanks for the ideas!
Gary Morrison mr88cet@redacted.invalid wrote:
I've recently noticed that, when I take my 1.5GHz, 17" G4 PowerBook out of sleep, it fails to connect to the internet. It's doing so via AirPort, using my NETGEAR WGR614v4.
More specifically, what I find in the TCP/IP tab of the AirPort configuration of the Network System Preferences thingie, is that DHCP gives it an IP Address and a Subnet Mask, but no Router IP Address. Poking the "Renew DHCP Lease" button doesn't change that situation.
It doesn't seem to be having any difficulties physically communicating over AirPort, since the NETGEAR critter's DHCP server is successfully supplying an IP address for it. Also, the signal strength meter in the menu bar is showing up at full power, and I've never seen it have problems other than when coming out of sleep.
Do any of you have any guesses as to what could cause it to not get a router address (only)?
Thanks for the ideas!
Are you sure you're getting an address? A DHCP client often (might be in the RFC, not sure) assigns a dummy number if it tries to negotiate and fails.
Unless your IP address is in the 192.x range then it's probably not coming from netgear.
As far as reasons why, the bandwidth may be crowded. Are you in an apartment complex? I live in a complex. I have only two or three channels that are usable. It's a real bummer when a new techie neighbor moves in, sets up a router, picks channel 10, and forces us all to play musical chairs.
Ah, those are very good thoughts; thanks! The next time it happens, I'll check on exactly what IP address I have when there's no router address.
I cycled power on the router earlier today, and I don't think it has happened since then, but that could still be just coincidence, until I can gather some more statistics on it (i.e., time will tell, but so far, not much time has told anything yet).
I do in fact live in a house, but I have seen some occasional signs of interference from other networks. Occasionally, somebody else's router shows up in the AirPort menu. And on extremely rare occasions, my router does not show up and somebody else's does, although I suspect something else is going wrong when that happens.
brian wrote:
Are you sure you're getting an address? A DHCP client often (might be in the RFC, not sure) assigns a dummy number if it tries to negotiate and fails.
Unless your IP address is in the 192.x range then it's probably not coming from netgear.
As far as reasons why, the bandwidth may be crowded. Are you in an apartment complex? I live in a complex. I have only two or three channels that are usable. It's a real bummer when a new techie neighbor moves in, sets up a router, picks channel 10, and forces us all to play musical chairs.