Networking LC 475 and Performa 6300CD

Hi Kyle
Two more links you may use:
1)thanks Jan Hedlund
http://www.dur.ac.uk/~dbl0www1/WellconnectedMac/serialguide/serial.html
2) http://homepage.mac.com/car1son/os9xnet_nfilesharing.html
I assume Appletalk is active(in the Cooser) and FileSharing is started(in FileSharing) and Users & Groups are installed with the needed privileges. IF so you only need to start the computers-and they will connect.
Good luck
PS: The Uplink port is used for connection to another net/router etc. The other ports on the switch are equal-doesn't matter which are used.

Kyle
If you connect the two subject Macs simply with a crossover cat5/5A cable, configure AppleTalk and TCP/IP, and set FileSharing (either hard disks or individual folders) from Sharing... in the File menu, both machines should list the other when you select AppleShare in the Chooser.

This is exactly parallel to what should happen when they are both connected with patch cables to your ethernet switch, with TCP/IP configuration to give each its own address within your LAN. If you already have an operational LAN, and all the evidence is that you have, you are probably using one of the private ranges of IP addresses for existing members.

In my own case, for example, an SE/30 (32MB/OS 7.5.5/AppleShare 3.7.4) at IP 10.1.1.14 and an LC II/Quadra 605 (36MB/OS 8.1/AppleShare 3.7.4) at 10.1.1.10 are members of a LAN of thirteen out of the Macs below. (I leave the modem/router at 10.1.1.1. 10.1.1.2 is reserved for USB connection to the router.) Given the setup above, clicking AppleShare in the Chooser of either Elsie or SE/30 brings up a list containing the other as well as the principal server to the LAN, iMac Snow (1GB/OS 10.3.9).

This protocol may all be well-enough known to you, and what you have done. If it does not get the required result, check that AppleTalk in one of the Macs has not switched itself to a serial port instead of Ethernet, or some other seemingly minor but debilitating mischance. Failing that, you may have a hardware fault in either of the NICs, which should become apparent in a crossover cable test of the setup.

Kyle
For thoroughness, if not novelty, I should have added that when first you open Chooser and click on AppleShare, if there has been no prior communication between the Macs there will be no server listed in the right-hand pane. You will need to click on the Server IP Address... button, enter the server machine's IP address in the succeeding window, and then authenticate the request in the next window again.

Even that will get you nowhere if you have not already set up Users and Groups, including yourself as Registered User (owner), given your computers names (as well as IP addresses), and made sure that both Macs are not asleep. Thereafter it will be adequate, if the computers are awake, to click on the name of one in the list, and authenticate the request in the following window.

Kyle
Even if you use Ethernet-the procedure is almost the same-just change from printer port to Ethernet in the Apple Talk Control Panel. You do need TCP/IP Control Panel only for connecting to Internet/Router or with OSX.
The Classic side of the setup is the same,just depends on what OS you use(as cited there).AS you want to connect more Macs,you will need a hub/switch/router and can use patch cables.For cabling you may look at:
http://docs.info.apple.com/article.html?artnum=30722
http://www.incentre.net/incentre/frame/ethernet.html

Now Denis Eddy is here you will get better info than I ever can deliver.

Kyle
AppleTalk you know about. The disks or folders for Filesharing you enable at the server end, and the ability to fileshare at the client end under the Start/Stop tab in the File Sharing pane of File Sharing. Don't forget to define your file permissions at the server end.

Open TCP/IP, and then press command-u. If you wish to add security, make yourself an administrator with a suitably secure password. Press OK, and the TCP/IP control panel will present with locks beside the fields. TCP/IP needs:

Connect via Ethernet (the system may add text to suit your cards);
Configure Manually (for the moment);
IP Address Unique for each machine, in the range 10.1.1.3 to 10.1.1.255;
Subnet mask 255.0.0.0 for all in your LAN;
Router address 10.1.1.1
Name server addr. Whatever your ISP has given you as DNS numbers;
Starting Domain Name Your ISP's domain name (optional).

Leave the remaining fields blank unless you need to fill them in. Click the button Options, and accept the two defaults of 'Active' and 'Load only when needed'. Now press command-k. If the Default configuration is highlighted, rename it 'Shared' or 'Cod-liver Oil' or something that appeals to you. (You may later wish to set up other configurations with distinguishing names, such as for dial-up.) Close and confirm the Configurations and TCP/IP windows.

Users and Groups needs only you as owner, for the moment. You need to enter your system name and password under 'Identity', from the Open button. You can add other Users and Groups when and as you please. Network Identity (under the Start/Stop tab) needs a Computer Name and your Owner Password. The IP address will already have been imported from TCP/IP.

That should be it. There is no immediate necessity to use DHCP address allocation. With NAT enabled in your router you may never need it, even to access the Web from one of your oldies. There is nothing particular against using it, either. You may still need to do a communication hardware test before you start all this so as not to be misled by failure by either machine to connect to the LAN.

Rainer
Thank you for your kind words. Would that I had had you at my side during the just-past five days, while I have been swearing my way through the exercise of downgrading an iMac 500 from OS 10.3.9 to 10.2.8 in order to use a no-longer-supported application. One Archive and Install, and two scorched-earth reformats and installations, and even then a painstaking comparison between the iMac and another iMac 500 beside it, still running 10.3.9, to realign file permissions with need. Imagine being shut out of your own computer by a @#$%&* Installer ... Grrrr. Dumping me into Console after log-in, and then freezing. By our Lady-minded refusal to write configuration preferences to file. You name it, and I saw it. Sydney nearly saw its first intercontinental ballistic iMac.

Denis
Thank you.I thought Australians wouldn't use any ballistic!
I've connected another MAC(7200/120) to my network(not yet Internet!).My problem is setting the permissions correct-but runs.The Button Options didn't show up either. Another: You told me to update AppleShare,which I did.
Maybe Kyle has to do the same?

Kyle and Rainer
The kbase article (106657) cited by Kyle in an early post leads to a number of useful links, but this one is of particular interest when you have mixed-age machines to connect. The upshot of it all is that you set all of the (available) parameters above, knowing that access to them may be found in differing ways because of the different versions of AppleShare that accompany versions of the System/OS.

The lowest-numbered OS in my LAN at the moment is 7.5.5 on the two SE/30s. I haven't modified the version of AppleShare in any of the Macs, which include PDS, PCI and inbuilt Ethernet capabilities. There is none with a comm. slot, but it should be a matter of indifference (apart from data rate) which is used in a given context, as long as it is functional. Nine of my chilluns have only 10Base-T capability, and, by and large it matters not a whit. I haven't found any of the 13 to be inherently unconnectable so far, and even if I did, I should just do a two-step transfer A to B to C if A to C was not feasible directly.

Rainer

My problem is setting the permissions correct-but runs.

I'm not sure what is giving you grief, but I suggest that all you need to start with is to give yourself read and write permission everywhere. Other users you can add later, if you wish. I have, however, everywhere given myself the 'short name' (deniseddy) bestowed by OS X, because OS X is the most intransigent of the OSs concerned when it comes to making changes.

Kyle
I haven't any experience of 10.4.x yet, and will not try before it reaches 10.4.6 at least. However, my reading has left me with the suspicion that Apple's dumping of AppleTalk in more recent OSs may have the effect that OS X machines may have difficulty in taking the client, as opposed to the server, role in communicating with older OSs. Within that constraint, however, there should be no problems in your flock. My Elsie and PB 540c (OS 8.1) have no trouble fitting in, nor do the OS 8.6 PowerBooks and OS 9 whatevers (including the OS 9 partitions for Classic Mode within OS X). Functional cards and cables a given, persistence should win through for you.

Denis
No grief-just forgotten! I've got different patterns to use even with both my OS 9.1(Option button,none) and mixed systems(english,german) from 7.0 upwards. Brain is fading away!
Rainer
Kyle
Good luck!

Denis, Kyle and Rainer,

Another link in KB article 106657 leads to document # 106461. I guess that the information in the three paragraphs under
i AppleTalk issues
in the
i IV. Troubleshooting
section possibly could be of interest as far as the relationship between 8.1 and 10.4.2 is concerned.

Jan

Kyle
Good to hear that Murphy is on holiday, and that all is coming together.