• Hello MLAers! We've re-enabled auto-approval for accounts. If you are still waiting on account approval, please check this thread for more information.

Network Oddness

willg

6502
Hi,

Nice board and I'm glad to be here, its a mine of information :)

I'm having some real problems with several of my old macs at the moment in the network department.

I have a Quadra 700, a 7100/80, a LC475 and a Performa 6200 all with the same problem, I'm trying to get them to connect to a shared external drive on my intel imac running 10.5.6. When I try to connect via the chooser (typing in theimacs ip address) it crashes out with an error and does not connect. A reboot of the machine produces a bomb with 'Appleshare error', sometimes with a -1 error code. I can trash the prefs for tcp/ip and apple talk and this enables the machine to boot but trying again the same arror cycle returns.

The macs are not connected at the same time, I plug each of them in when I want to use them, they use the same display, keyboard and mouse and network cabl

the machines are running a mix of 7.6, 8.1 and 8.6.

A 7300 with a g3 upgrade card running 9.2.2 connects no problem as do a G3 imac, a B&W and a G4 (all running 10.4).

So far I've changed the network cable and the router with no sucess.

Any ideas what doing wrong?? its really really annoying :b&w:

 
As far as I know, Shareway IP has absolutely no effect on connecting to a X.4+ machine from a machine running MacOS 7-9. Shareway IP works the other way, allowing connection from the newer to the older machine. Open Transport is what works the particular magic mentioned, and not Shareway IP.

What you do seemingly have to do in order to connect from the older machine to a X.4 share is to enter the IP address of the target machine in that little box at the bottom. Merely choosing it in the old way in the Chooser leads to a networking error. Or so it is on all my machines. Even aliases are flaky, but the IP allows consistent connections.

It is odd that entering the IP in your case doesn't do the trick. Router, perchance? Go through a hub?

 
Hi,

I tried Shareway last night, its a bit of a fiddle but with it I was able to mount an external drive connected to my imac. No sign of the 6200's drive on the imac tho. Internet access has always worked fine on any

I vaguely remember that when I was running 10.4 I never had this problem.

Don't think its hardware as I've tried various switch, hubs and cables with the same result.

 
I tried Shareway last night, its a bit of a fiddle but with it I was able to mount an external drive connected to my imac.
Now that is interesting. It is seemingly not what Shareway IP was designed to do, but it might be a new use for the software.

When you say a 'fiddle', what do you mean? Could it, for instance, be made to work to network a machine running 7.1 with your X.5 machine?

 
As far as I know, Shareway IP has absolutely no effect on connecting to a X.4+ machine from a machine running MacOS 7-9. Shareway IP works the other way, allowing connection from the newer to the older machine. Open Transport is what works the particular magic mentioned, and not Shareway IP.
What you do seemingly have to do in order to connect from the older machine to a X.4 share is to enter the IP address of the target machine in that little box at the bottom. Merely choosing it in the old way in the Chooser leads to a networking error. Or so it is on all my machines. Even aliases are flaky, but the IP allows consistent connections.

It is odd that entering the IP in your case doesn't do the trick. Router, perchance? Go through a hub?
I stand corrected. My 7300 running 7.6.1 required OT 1.1.2 and Appleshare Client 3.8 to connect to the iMac running 10.4.11, but required Shareway IP to connect the other way. It had been a couple of years since I went through that whole exercise until again today. In any case, Dan at System7Today says that the system works even better with 10.5 than 10.4; I have no experience with 10.5 so can't comment on that.

 
I'll give sharepoints a try tonight.

the really annoying thing about this is the bus error that occours, how can a slight glitch cause the whole os to grind to a halt?

 
Back
Top