Ok here's the setup: Three macs, all running 10.1.3, all with Airport cards all connecting to a Base Station which in turn connects to a cable modem. All access the internet just fine (well, most of the time anyway). The Macs are a TiBook, an Orange iBook, and an iMac. All have Appletalk and Sharing turned on.
Weirdness #1
On either the iMac or the iBook, the TiBook does not appear when Appletalk is selected in the "Connect to Server" dialog box. But in each case the iMac and the iBook also "see" themselves (list themselves as servers to connect to) The TiBook can see both the iMac and the iBook, but does not "see" itself. This is all in the Appletalk section of the "Connect to server" dialog box.
Weirdness #2 (by far the more annoying)
As Appletalk doesn't always work for mounting servers, one occasionally has to resort to the "Local Network" section of the "Connect to server" dialog box. BUT in this box, MANY MANY versions of the available Servers appear. That is, if a server's name is iMac there will be 8 or so listings for "iMac" in the Local Network section. Clicking on each reveals that the different iterations each have unique afp:// numbers, but only one of them is correct Attempting to connect to any of the "false" iMacs will lead only to timeout errors.
Anybody know why these things happen? I assume it has something to do with the Airport assigning new IP numbers to each machine whenever they get restarted or whatever, but I dont understand why the old numbers should persist...
Anybody know how to fix these problems?
Anybody know when Apple's actually going to make OS X networking work like it should? (I'm willing to wait for SMB if they'll get Mac playing nice together again)
cpac
Top