|
|
|
|
| Welcome, Guest | Home | Search | Login | Register | |
| Author | connecting to os X via ethernet (Read 22144 times) | ||||||||||||||||||||||||||||||||||
|
jwally
8 MB  Posts: 12 
|
on: November 19, 2006, 23:10
I have run into a problem in following your instructions on connecting my PowerMac on OS 7.6.1 to my iMac on OS 10.4.8. My physical connection is direct via an ethernet crossover cable. When trying to connect using the PowerMac (Per your instructions) I get to the step where I enter my username and password and tell it to connect. After a few seconds to think about it, the PowerMac comes back with a dialog box: "the application "unknown" has unexpectedly quit because an error of type 12 occured." I've tried restarting, reconfiguring, and reconnecting several times with the same result. Error type 12 in my book deals with an unimplemented core routine (A programmer might set breakpoints in parts of a program to inspect for errors. This requires using a debugger. If a debugger isn't installed when a breakpoint occurs, you see this error code.) What debugger do I need, and where do I find it? When trying to connect using the iMac, the systems recognize each other, and the PowerMac shows up on the network by name, but when I try to connect, I get an error dialog "This server uses an incompatible version of the AFP protocol. You cannot connect to it." Could it be that your instructions, while valid for OS 10.3, might not be valid for OS 10.4? I know I've been making some pretty simple mistakes here, so is there something I've overlooked? Thanks Wally |
||||||||||||||||||||||||||||||||||
|
dpaanlka
|
1024 MB Posts: 1646
Reply #1 on: November 20, 2006, 00:01
|
The instructions were written (and screen shots taken) with 10.4 tiger. They were not connected with a crossover cable, though. They also did not "show up" in each other's choosers, rather I connected by entering their IP address. It probably isn't working because of the crossover cable.
|
jwally
|
8 MB Posts: 12
Reply #2 on: November 20, 2006, 01:05
|
I was under the impression that you need a crossover cable to connect machine to machine (without an ethernet hub.) Do you suggest I do a direct connection with a regular cable? I don't have a hub, and really can't use one once this is complete.
|
dpaanlka
|
1024 MB Posts: 1646
Reply #3 on: November 20, 2006, 01:32
|
Quote from: "jwally" I was under the impression that you need a crossover cable to connect machine to machine (without an ethernet hub.) Nobody said anything about not having a hub. I wrote that tutorial with both machines connected to a traditional LAN with a router and hub. I have no experience with connecting machines directly together, perhaps someone else can give you some help. It probably wouldn't be a bad idea for you to just build a small LAN.
|
wove
|
1024 MB Posts: 1363
Reply #4 on: November 20, 2006, 01:34
|
Quote from: "jwally" I have run into a problem in following your instructions on connecting my PowerMac on OS 7.6.1 to my iMac on OS 10.4.8. My physical connection is direct via an ethernet crossover cable. I have had no real problems getting my 8600 to connect to a Cube running 10.4.8, but I always get the same error message about the incompatible version of AFP when going the other way. This is probably a preference problem in OS X. If you were using AppleShare with earlier version of OS X would still be the default for sharing under 10.4. However AppleShare really no longer works under 10.4, so the old preferences are blocking a successful connection. Delete your preference or turn off AppleTalk to ensure you are forcing the system to use TCP/IP networking. There are a few anomolies that I have noticed which may hinder the process. The built in networking on the 8600 never gets an IP address via DHCP until I send some outbound TCP/IP packets. Generally until I have visited some webpage my network card is useless for TCP/IP networking. This would be a big problem if the same is true on your machine and you are direct connecting via cable. The work around here would be to assign a fixed IP to the machine in TCP/IP Control Panel. An often overlooked and simple reason for a connection to not work is that Sharing has not been turned on. Depending on the age of your OS X Mac you may not need a crossover cable all the newer machines auto sense and will provide cross over functions if necessary. bill
|
douglas
|
32 MB Posts: 44
Reply #5 on: November 23, 2006, 04:40
|
Hello! I believe that your problem is trying to connect using the chooser...DON'T DO THIS!!!!! I can connect my machines using a crossover cable just fine, but ONLY if I manually input the other machines address. If I try and select it from the chooser I get the same crash. Try it again and manually enter the other machines address, it should work this way! I am using 10.4 and it works fine. Douglas 
|
wove
|
1024 MB Posts: 1363
Reply #6 on: November 23, 2006, 04:49
|
Quote from: "douglas" Hello! If you could perhaps explain this further. I am not sure I understand how you are setting your machines IP address when using a cross over cable. Do you enter it as a static IP in the TCP/IP Control Panel, and if so what do you use for the mask and other settings. bill
|
Ammo
|
2 MB Posts: 2
Reply #7 on: December 11, 2007, 07:21
|
Quote from: "douglas" Hello! I get the same thing - the iBook running 10.3.9 is seen in the Chooser from the PMac 7100 on 7.5.23 (now upgraded to 7.6.1) - I need files from the iBook but I get the error message as above. Can't put an IP address in the Chooser (have to upgrade OT to 1.1.2 I think or Appleshare to 3.8.3). Trying to connect to the iBook from the Chooser gives the above mentioned error, "incompatible version of Appleshare". Tried assigning an IP address in the TCP/IP CPanel but iBook can't ping it. Tried connecting it to a router and get an address via DHCP but nothing happened. Yes, Appletalk is running over Ethernet. Appletalk is essential if I want to use a shared printer on the PMac - it's an imagesetter controlled by Panther RIP application. Can OS X 10.3.9 print (from Acrobat, Photoshop, InDesign, etc) to a shared Laserwriter 8? How cool would that be to solve this problem? I don't know, I've never done anything that cool before. "Ammo"
|
Xanathus
|
2 MB Posts: 3
Reply #8 on: December 15, 2007, 02:52
|
On Mac OS 9 and older, you can have AppleTalk on one network port (ethernet, localtalk, AirPort, etc.) and TCP/IP on one port. OS X can have TCP/IP setup on as many ports that you want all at the same time, but AppleTalk only on one. Furthermore, you have to manually turn AppleTalk on for that port. AppleShare comes in many versions. The older versions that came with System 6 and 7 only supported File Sharing over AppleTalk. Later versions supported connecting to a AppleShare server via TCP/IP. From what I can tell, Mac OS X can use AppleTalk to "find" an AppleShare file server, but uses TCP/IP to actually connect. Your best bet is to update AppleShare AND your Chooser to a newer version that allows serving files and connecting to file servers via TCP/IP connections. Find the newest version of OpenTransport that your computer and System will work with. That should have the necessary components. AppleTalk printing still works fine with OS X. It is the file sharing aspect that has changed a lot. Just make sure AppleTalk is turned ON in System Preferences/Network/Ethernet/AppleTalk (Make AppleTalk Active). This works under 10.3 and 10.4. The most Amazing thing I've done with in this department is print from a 68k Powerbook Duo 280c to an Epson Stylus c82 color inkjet. There are no 68k drivers, and no 68k Mac has USB. I connected the printer to my Powermac G4 and used GimpPrint with Ghostscript and OS X Printer Sharing. Then on the Powerbook, I used the Desktop Printer Utility to create a network printer over TCP/IP using the LaserWriter 8 driver. How many people do that?!
|
|
Pages: [1]
|
| |||||||||
|
© 2021 System7Today.com. |
