From: Paul J. T. <pt...@ma...> - 2003-02-09 00:58:08
|
Marc - Thanks for the reply. The address is definitely of the 169.x.x.x variety....curses. I tried filling in the "DHCP Client ID (optional)" field. Unfortunately, I got the same result. Any other thoughts? Has anyone else seen similar problems with this type of setup? The Orinoco Gold + Wallstreet PB worked great with my old Airport Base Station (dual ethernet), the only difference with the new setup is the Airport Extreme base station. From time to time in the past with the old Airport Base Station, this PB would self-assign itself a 169.x.x.x address. I used to be able to disable and enable the interface to fix the problem. Such steps don't seem to make a difference now. Any help would be appreciated. Thanks. PJT On Saturday, February 8, 2003, at 01:40 PM, Marc Silverman wrote: > If the "bogus" address starts with 169 it means that it is not > connecting at > all. > > If this helps, I found that one thing I had to do to make it work (but > with > the Linksys) that might work for the Airport too: > > There must be something in the "DHCP Client ID (optional)" - put in > anything, just don't leave it blank. > > --Marc > > >> Can someone tell me... >> >> Should my WallStreet Powerbook G3 running 10.2.3, using the 5.1Beta >> Wireless driver, be able to talk to my new AirportExtreme base station >> via an Orinoco Gold card? >> >> I have WEP on, am using MAC access control, am using DHCP + NAT, and >> have 802.11b/g compatibility enabled. >> >> The Powerbook continually assigns itself a bogus DHCP address. >> >> I couldn't find a conclusive answer in the mailing list archives. >> >> Any one have any ideas? >> >> Let me know and thanks. >> >> Paul Teeter >> pt...@ma... |