Os 9.2.2 TCP/IP Setting, Can't release 169. IP

I have searched the forums briefly(about 30 mins) and it seems a daunting task! There is lot if info here, please excuse me if this has been answered before, feel free to direct me to the post.
I just purchased a Lombard model PowerBook, I installed 9.2.2 on it. I am trying to hook it up to my network and it will not grab an IP. I have dumped the prefs file and restarted, and nothing it goes back to the 169.IP. I am wondering if maybe the ethernet port is bad?
Anyway, just to be clear, I have inet service through cable, TCP/IP settings:
connect via: Ethernet
configure: Using DHCP Server
Everything should be provided automatically.
Thanks for any insight.

Mac Powerbook G3 Lombard, Mac OS 9.2.x

Posted on Jan 29, 2006 6:04 AM

Reply
19 replies

Jan 29, 2006 6:58 AM in response to Darak Hollis

Hi, Darak -

Can you 'see' the modem or the router in Apple System Profiler? Is ethernet shown as being active in that?

Be sure the ethernet cable you are using to connect the PB to the router is a Patch type cable, and not a Crossover type. Often the only way to tell one kind from the other is to examine the color-coding of the wires in the end connectors -
Ethernet Cable: Color Coding Standard

Jan 29, 2006 8:34 AM in response to Darak Hollis

Hi, Darak -

Yes, the "DHCP Client" field should be left blank unless the IP has stated that a specific IP address should be used.

It sounds like something is overriding the address. Does your IP require the use of any keep-alive software, such as MacPoet or Enternet? If so, check in the settings for that software, make sure no default address has been pre-assigned.

Likewise, check in the Internet control panel, Advanced tab, Firewalls item (in the LH scrolling list). Make sure no addresses have been preset there. Ditto for the Hosts item in the scrolling list.

Jan 29, 2006 8:45 AM in response to Don Archibald

My IP doesn't require any such software to be active. I have run into this problem on other peoples Macs, and on PCs. Sometimes a 169.IP just seems to "lock" in. I'm not even sure what would issue a 169.IP, a VPN maybe? However, I have run OS 9.2.2 on my old iMac DV from this same connection with no problems at all, for 3 years in fact. Please let me know if you have any ideas, or run into any pertinent information.

Jan 29, 2006 10:15 AM in response to Darak Hollis

This reminds me of a problem I had with the LanCity modems years ago.

That 169 address would be from when something got caught in the internal addressing space inside it.

Try unplugging the modem to clear the memory in it.. give it 5 minutes or so. While that's going on (or off, as the case may be), turn off the TCP/IP in the control panel and save. Get in to your system folder, check and see if there's a mac TCP DNR file floating around, and trash it. Go into the prefs folder and get the TCP/IP prefs and trash them too. Shut down the computer, plug in the modem and when all the lights come on to show it's got bloc sync established, then reboot and do the standard TCP/IP setup.

Good luck!

Deb.

Mar 12, 2006 10:52 AM in response to Darak Hollis

I had this problem hapen to me recently, and with the help of Apple and other forums, I solved the problem. Here's how I did it.

I have a PowerPC G5 with 10.4.5 on machine A, a PowerCenter 166 upgraded to a 500 MHz G3 with an Orange Micro Firewire/USB adapter with OS 9.2.2 (modified with OS9 Helper) on machine B, a Starview 2-Port USB KVM switch, and a D-Link DI-624 wireless router between the two machines.

My first issue was that I am clueless about networking. Through hours and hours trial and error, I learned that the control panel settings for file sharing in machine B need to identify that machine (and similarly for machine A). I thought that to access one machine from another required having the other machine's info in those fields. When I was able to connect to the other machine and it asked for the name and password, I entered the name and password of the machine I was trying to access.

My second issue involved the 169. IP situation. I trashed the Mac TCP DNR file and the prefs, but to no avail. I read elsewhere that this IP prefix was used with a private network, so I assumed that my network "was" a private network, so I didn't realize that was a problem (oh, blissful ignorance). I realized that the reason machine B was using a 169 IP was that it didn't recognize my other machine. I used the DI-624 tools to ping both machines. It successfully pinged machine A, but not B. So, it seemed that machine B was using a 169. IP because it could not connect with the router. The router tools said my connection was ok, but I bought a new cable anyway. The new cable solved the problem. Apparently, the router tools only verified there was a connection, not that it was connected properly.

I hope this info helps others.

Greg

PowerMac G5 Mac OS X (10.4.5)

Mar 17, 2006 8:40 PM in response to Darak Hollis

I'm Having This Same Problem But It Works Some Times & 98% Of The Time It Doesnt I've Tried Everything You All Have Recomended But I'm Still Just Connected If I'm Lucky Once Or Twice A Week It Has To Be Somthing With My My Set Up? My Cousin Brought A Compaq Armada M700 Lap Top Ewwww!& Connected Straight Away? & Then Kinda Chuckled At me, If Some One Has Found The Problem Please Let Me Know Before I Have To Put A Whipping On My Chicken Sh*t Cousins A#s Thanks Fellow Mac Lovers!

Power Mac G4 Mac OS 9.2.x

Mar 18, 2006 7:19 AM in response to DJ151

DJ's problem seems to have th emost clues here, in that if it works 98% of the time then it's unlikely to be the settings.. at least, not the settings on the Mac that's having the problem.

Firstly, DHCP is great when it works and since it's automatic, fairly useless for testing. What happens when you try setting the addresses Manually, please?

I won't be surprised if that 169.blah is a self-assigned address, generated because the Mac can't see the DHCP controller...

Second what happens if you try to connect just to Macs, preferably directly which with older Macs will mean using a Crossover cable; otherwise if you have through a dumb hub or a switch, not any kind of smart router which may have its own ideas?

Thirdly, even before that it really matters what's turned on first, particularly with automatic settings. It can make all the difference to power up first the modem, then two minutes later the router, then two minutes later the computer. Try that only leaving everything off for at least 20 minutes.

Also much smart networking kit has two different reset levels, in which case the normal reset would restore the last saved User configurations and the deeper reset would restore the factory settings.

Also it might help to simply give the network settings the router's address as DNS Server, or Search Doman or both…

Mar 18, 2006 11:59 AM in response to Robbie Goodwin

Hey Robbie Thanks For The Response, I have Tried Entering The Adresses Manually With no Luck & it's 98% of the time it Doesnt Connect,&True When It Does ConnectIt Works Well But I Would Think That If it Was The Cable Then It Would Not Work At All,But If That Would Fix My Problem I Would Like To Know What Would Be The Best Brand Of Cable To Purchase? & Also I'm Connected Straight To The DHCP Controller Not through any Hubs or Switches, I'll Try The Manual Thing Once More,But If Just Need To Try The New Cable Then By All Means I Will. Thanks For The Help

Mar 18, 2006 2:27 PM in response to DJ151

Crikey! What happened to your keyboard? That's a real pain…

However, I think the Mac's settings are extremely unlikely to give intermittent results, almost any hardware fault including cables could easily do that… I think the only way the Mac's settings might contribute to intermittent results is if the fault is with hardware, with other settings or with start-up timings…

Sorry I've no idea what's a better cable brand - and I hope that even with the worst brand, say three cables won't all be bad…

DHCP and controllers for it may be highly desirable, and you can't make a true test without eliminating everything that's not vital… if it's a DHCP modem and it won't let you switch off DHCP, that's different; either, a direct connection between only two Ethernet devices with Manual settings is the only you can tell what's actually involved…

Mar 18, 2006 10:25 PM in response to Darak Hollis

Having recently gone through the 169.xxx mess with no connecting with the internet through an Airport Base Station as the router with a DSL modem, I can only second the advice to do the DEEP reset to the default values and to turn off everything and restart in this order: DSL modem on. Router on. Computer on.

Somehow, I think the hangup occurs in the router and it won't get/accept the correct IP from the DPHC server.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Os 9.2.2 TCP/IP Setting, Can't release 169. IP

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.