Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[laserski]

I have a very interesting network issue with my Laser Engraving computer. It is a dual 1GHz Quicksilver machine running dual boot OS9 and OSX 10.5.

In OS X everything works perfectly. No issues. When booted into OS9 I get a self assigned IP address using ethernet. When I put in an old airport card (and select to connect via airport) it sees the various networks and lets me choose one, but rejects the password to connect.

In OS 9 I seem to have lost my connection to the network. This happened several months ago when I tried to print to a networked printer and I just lived with it, but it is starting to get irritating. It used to work fine, and I did not change anything (that I can think of).

I have tried restoring my OS9 system folder. No help.
I have booted from another disk with OS9. No help.
I have reinstalled OS9 to another disk and to the internal disk. No help.
I have reset PRAM, no help.
I have set up manual networking instead of DHCP. No help.
I reinstalled my CLASSILA browser. No help.
I reserved an address on my 5th generation Airport Extreme router. Connects fine in OS X, but does not show up when booted into OS9.
I have held a chicken at arms length with my left hand and swung it counterclockwise three times above my head before pulling out 5 pin feathers and throwing them over my left shoulder, and it worked! (Just kidding, no help.)

I always get the same self assigned (169.x.x.x) IP address in OS9 but it always works in OSX. That tells me the hardware and cable are OK, but just to be sure I tried another cable, no help.
I replaced the ethernet switch I plug that machine into. No help.
I was able to connect with the original cable when using a old iBook booted into OS9 with no issues.

Thoughts?

[devils_advisor]

Check the cable or better test with another cable. Then check your router. Type manually in the settings. This is what I would try first. Even if you replaced the switch there seems to be no way to the router. Another issue could be your router is trying to give you a ip that has been assigned to another machine and will result in a self assigned ip. Had that too.

[laserski]

Check the cable or better test with another cable. Then check your router. Type manually in the settings. This is what I would try first.

Thanks, have done all that with no improvement.

[devils_advisor]

Assigned manually everything including gateway?

[miracman]

Hi there laserski,

     I've been surfing around here in the last few days like a tourist, really.  After hard working days, contemplating 3 G4s that need attention...

     Basically put; I wish I could help in a better way by unplugging screens and boot one of the old beasts and see if I remember well something that was obvious 10-15 years ago.  But hey, it's beer time after work...  so it's just a "my two cents" moment, before my next break during which, yeah, I'll at least have one hooked up and ready to kick ass using a recent classilla and so on...

     OK... so..  two cents.  When you say:

In OS 9 I seem to have lost my connection to the network. This happened several months ago when I tried to print to a networked printer and I just lived with it, but it is starting.....

,  this points to AppleShare / AppleTalk etc.  So, I'd say, make sure that you are sure that your TCP/IP panel is set to 'Ethernet' and not to 'AppleTalk' (or something else).  Then you can re-select your option of choice (which seems to be be the auto-assigned DHCP thingy).  In a case like this, trashing the preference file from one of the three (tcp/ip, AppleTalk, AppleShare) would seem less obtrusive than going through all that you went through.

    I can't help at all with the airport part of your thread. 

    I hope it doesn't sound too obvious or silly...  I was reading this and it reminded me of a few awkward moments I did have with AppleTalk. 

Good luck


[edit]  If you are sure about the hardware parts, just make your computer talk to your router (browse your router IP). If that doesn't work, explain furthermore what is happening on your side.

[laserski]

Thank you all for the suggestions.

Yes, I have tried setting everything up manually as well as using DHCP server. To be sure I was doing it correctly I also mirrored the manual setup in OSX. Works like a champ in OSX but not on the same machine in OS9. Yes, weird!

My printer driver is an IP driver. Appletalk is not needed, but I have tried connecting with and without Appletalk. Just for the record, Appletalk does not work either. No connection on the network is working, except I can see the names of the WiFi networks on Airport, but can not log into any of them.

I am unable to connect to the router from that OS9 machine when I type in the IP address. (Airport Extreme, 5th Gen) From another computer I get a error about not being able to connect to the server, which is correct for an Airport base station since by design you have to use the AirPort Utility to configure the router.

One other test I did since yesterday was push the small RESET button on the motherboard of the computer. No help.

What are the names of the preference files that store the TCP/IP settings in OS9? I am curious what info they hold, and maybe to delete them.

Thanks everyone!

[miracman]

Hello,

I was under the impression that you were trying to connect the easiest way (ethernet to the router; possibly with nothing else connected as a start), not through Airport.  And from there talking to the router with a browser...

As for the Preferences file; I was looking at a french install and it's called "Préférences TCP/IP".  So it's probably something quite simple like "TCP/IP Preferences"  (System Folder/Preferences/)  I thought to point towards AppleTalk because you might have the Chooser still selecting a remote printer.. through AppleTalk.. and so on up to TCP/IP.

Good luck!

[ovalking]

You say you tried setting up IP manually.
What settings did you use?
Can you ping your router?

For the Airport issue, it seems like you can't get passed the security. Have you tried turning it off on the router (just for the purposes of testing)?

[laserski]

I really don't care if it works on ethernet or on airPort, as long as it works on one or the other. It was set up and working on ethernet for years with no issues. Than all at once it stops working on OS9 but continues to work in OS X 10.5.

In the OS9 TCP/IP control Panel I selected ETHERNET, USING DHCP SERVER, entered the router address as 10.0.1.1 (Which is what it is). When that did not work I entered MANUAL mode, typed in the IP address of 10.0.1.96, subnet of 255.255.255.0, router of 10.0.1.1, name server of 10.0.1.1. These settings DO work in OS X on that machine.

This should work, but on this machine it does not. I recently found out about another Quicksilver Mac that is available locally. I may buy that and move my HD and SCSI card, serial port, etc. into the new machine and give that a try.

Thanks for any ideas!

[ovalking]

OK, those settings look sensible, so it is puzzling.

I trust 10.0.1.96 is not in use by anything else.

Don't forget to check the options button.... make sure TCP/IP is set to active.

You still don't say if you can ping your router.

Can you ping any other device on the LAN, or see any other Appletalk device?

Does Apple System Profiler, Network Overview section offer any clues?

You could try removing  the preferences files:
TCP/IP Preferences
AppleShare Prep
AppleTalk Preferences
You can put them back if the action doesn't help.

[GaryN]

I'm with Ovalking on this.

When this kind of illogical stuff happens, the first step is almost always to trash the preferences and force the computer to regenerate new ones.

If you're leery of this, you don't have to actually delete the prefs, just get them out of the Sys folder or wherever they are so the System can't find them.

[laserski]

Thanks for the ideas.

I am not able to ping anything on the network from OS9. I cannot ping the OS9 machine from another machine.

Yes, 10.0.1.96 is only used by this machine. It works well at that address when booted into OS X.

Yes, TCP/IP is active. System Profile shows it as active but with the 169.x.x.x address. Appletalk also shows as active.

I tried removing the preference files and get a message that I do not have permissions to do that (Yes, from OS9). So i booted into OS X and removed those preferences and then rebooted into OS 9, but still no help.

Interesting that it says I do not have permission. It is NOT locked according to the GET INFO panel. Weird. How can this be? It is the only account in OS 9. Why is OS 9 preventing me from removing those items? Granted, I did remove them using OS X, but that sounds like a clue.

Thoughts?

[GaryN]

I tried removing the preference files and get a message that I do not have permissions to do that (Yes, from OS9). So i booted into OS X and removed those preferences and then rebooted into OS 9, but still no help.

Interesting that it says I do not have permission. It is NOT locked according to the GET INFO panel. Weird. How can this be? It is the only account in OS 9. Why is OS 9 preventing me from removing those items? Granted, I did remove them using OS X, but that sounds like a clue.

Thoughts?

I suspect you have, somewhere along the line, dragged or somehow interchanged a pref file to or from OSX. What??
What I mean is: In OS9, there are sharing permissions. In OSX, there are sharing and UNIX ownership permissions.
OSX can and does set and reset permissions all the time in ways that OS9 cannot comprehend.
There is a constant hazard with dual-boot systems where the disk utilities get to be at odds with each other.
I've recommended here many times to set both Time machine and Spotlight in OSX System Prefs to prevent them from accessing ANY OS9 volumes.
I have no idea exactly how you found yourself with an OS9 pref file that you lost ownership of in OS9 but since you were able to easily delete it in OSX it probably did become "owned" by OSX somehow.

What's important about that is that it was also unable to be changed, updated, revised in any way by OS9, meaning even if you could get the issue solved, the solution probably wouldn't stick.

Now: Let's go back to the actual, original problem.
You used to be able to access the network in OS9 - now you can't.
You used to be able to access the network in OSX - now you still can.

You said in the first post that this all "happened" when you tried to print to a networked printer.
I think it's more likely it happened before then and that's just when you noticed it.

Here's what you need to have working to reach your LAN (which is basically your router)
In the TCP/IP panel: Connect via Ethernet; Configure using DHCP server
  This should give you the same addresses as shown in OSX…router 10.0.0.1; subnet 255.255.255.0; IP address = same as in OSX
  YOU ALSO NEED: Active in System Extensions: Apple Enet; Open Transport 2.8.1 AND Open Transport ASLM Modules 2.8.1
  AND: Appletalk must be off.
  AND: An updateable TCP/IP Prefs file in System Preferences - After you check everything in the TCP/IP panel, this prefs file should show "Last date modified" as TODAY and the time

My best guess is Open transport is inactive…maybe……?

IF by some chance this works (it should, fingers crossed) The very next time you boot OSX, immediately go to System Preferences/Spotlight and prevent it from indexing the entire OS9 volume. Then do the same thing to Time Machine - select Do Not back up OS9 volume.

The objective is to keep all of the little UNIX-based notes Spotlight and TM write in the directory area of the volumes from confusing OS9, because eventually, OS9 Disk Utility will try to "repair" that stuff it doesn't understand (and it never heard of UNIX or OSX so it doesn't understand it). When that happens, the next time you boot OSX, IT will see the OS9 utility changes as errors and RE-fix it…then back and forth and back and forth until stuff is too corrupt to fix…period.

Spotlight and TM are the culprits - lock them out from the OS9 volume and everybody's happy.
Lastly, it's prudent to NOT just copy stuff from OSX to OS9 while in OSX. You're much better off booting OS9, then fetching those things from the OSX volume. That will help prevent permissions problems where you suddenly can't move or delete a file in OS9 that came from OSX.

Good luck. I gotta go to the bathroom…

[DieHard]

Good luck. I gotta go to the bathroom…

Just when things were getting good... one wonders what gems that Gary would have bestowed only to gone forever because nature called

[GaryN]

True…some of my very best work goes down the shitter.

[laserski]

Good luck. I gotta go to the bathroom…

Just when things were getting good... one wonders what gems that Gary would have bestowed only to gone forever because nature called

So I spent 4 hours on this issue today and I am really not making any progress.

I picked up another Dual 1GHz Quicksilver machine locally to test with. It has the exact same issue (no network connection in OS9) as my main machine, even with a freshly formatted HD and a new install of 9.2.2. So I got out my 500MHz iBook G3 and tested again and it works just fine using ethernet and OS 9.2.2. I made doubly certain I was not on Airport. Amazing.

I noticed that the iBook has Open Transport 2.8.3 AND Open Transport ASLM Modules 2.8.3 instead of 2.8.1. I copied those files to a USB flash drive and updated the test QS machine (it had 2.8.0) with no help.

Wondering how this could be? I noticed my Airport Extreme Router is a couple of versions behind in firmware, but the iBook works, so not sure if I want to go down that rabbit hole since the firmware version I am on has been working perfectly for several years. I may dig out an old Digital Audio G4 I have to test later, but am not sure if the results will help shed any light on the issue anyway.

Stuck!

I will have to mull this over for a few days. Logic is failing me...

[GaryN]

So I spent 4 hours on this issue today and I am really not making any progress.

Actually, I think you did. To wit:

I picked up another Dual 1GHz Quicksilver machine locally to test with. It has the exact same issue (no network connection in OS9) as my main machine, even with a freshly formatted HD and a new install of 9.2.2. So I got out my 500MHz iBook G3 and tested again and it works just fine using ethernet and OS 9.2.2. I made doubly certain I was not on Airport. Amazing.

I noticed that the iBook has Open Transport 2.8.3 AND Open Transport ASLM Modules 2.8.3 instead of 2.8.1. I copied those files to a USB flash drive and updated the test QS machine (it had 2.8.0) with no help.

I wasn't there, so I'm deducing this from your reply (very thorough by the way - that's great!).

Try this on for size:
Your G3 works!
Another completely different Quicksilver does not work. Why?
    >>>>> "It has the exact same issue (no network connection in OS9) as my main machine, even with a freshly formatted HD and a new install of 9.2.2."

* Is that fresh install be from the same source as the install(s) you've been using on the original Quicksilver? If so, that OS may contain corrupted files or simply have another necessary extension inactive.
You didn't mention "Apple Enet" that I said has to be active - is it?

I should have been clearer about the Open Transport stuff - 2.8.0 is probably OK - you should just have the latest revs you can find, so 2.8.1 is good - 2.8.3 is better but that's probably NOT the problem.

What you need to do now is compare the System Extensions on the working G3 line by line with the ones on a non-working G4.
Somewhere in there is one missing or corrupt or something and that issue is present in the 9.2.2 you're using for "fresh" installs.

………or not. Again, I wasn't there and this is just my best guesswork.  I DO know that you're close…really close.

[ovalking]

From your reports, the Mac is behaving as if no network is connected at all.

Do you have an extra ethernet card installed? Wondered if you were configuring one, but connected to the other.

Also, did you get Appletalk working? If yes, then that probably eliminates hardware issues.

[macStuff]

just because it gets a self assigned ip doesnt mean u cant manually set the ip yourself afterwards

i have had that problem many times i swear its easily circumvented by entering gateway, ip, + subnet mask

i have a quicksilver 933 (2002) here i can try to plug in to take a look

[laserski]

Thanks everyone for your ideas!

I am out of town since my daughter is giving birth to our 4th grandchild. I will be back at some unknown future date to continue this quest for truth, goodness, and the American Way!

Keep those ideas coming...