OS X help.

[cdub1988]

I for one reason or the other, can't seem to connect to the other OS X box on the LAN.

It's running X.1.5 (methinks) and this is X.2.5.

Any issues you know of related to this?

I have AppleTalk setup active on both, and the really messed up thing is that I can launch Classic environment and then go to Chooser and connect, with the X-style mount icon and everything.

Any ideas?

TIA.

Chris

[kps]

How are you trying to connect...Go Menu --> Connect To Server...?

You need to type: afp://_and_the_local_IP of the machine.

Next time, the Connect To Server window will remember the IP and/or the Appletalk host name.

A few things to double check: Sharing panel preferences, firewall configs(router or OS X), etc.

[cdub1988]

kps -

OK.

So I pointed at the IP and that worked fine (thanks, amigo), but I'm at a loss for why it won't access the AppleTalk path.

Keeps timing out.

Any ideas?

Thanks.

Chris

P.S. - got the same occurence previous to this install. Did an "erase and install" and all seemed well till I came to this problem again.

Also, developer tools wacked out on the install and quit because it said it ran into an "error".

Chris

[kps]

Sorry Chris I don't know how OS X is implementing the AppleTalk protocol, but if you look in the Network Prefs panel under Appletalk, there's a few options you need to set up. Such as ATalk zone and node IDs...either automatically or manualy. Maybe you need to do this manually based on your LAN?

Wouldn't it be better not to use Appletalk and just use TCP/IP?

[atjurhs]

Also, your LAN must be configured to accept AppleTalk.  I know that my PC based LAN is not AppleTalk enabled, and my Network Administrator won't do it, so I must connect through the Go->Connect To Server route.

Also, you can also use smb:// and cifs:// as other IP prefixes, other than afp:// that is.

[cdub1988]

QUOTE(atjurhs @ Jun 10 2003, 4:37 PM)

Also, your LAN must be configured to accept AppleTalk.  I know that my PC based LAN is not AppleTalk enabled, and my Network Administrator won't do it, so I must connect through the Go->Connect To Server route.

Also, you can also use smb:// and cifs:// as other IP prefixes, other than afp:// that is.

atjurhs -

I'm the net admin here - if that's what you could call me.

We're running straight peer-to-peer here.

We run with three switches on our LAN behind a Cisco 1600 router.

AppleTalk is enabled on all the Macs, including the OS X boxes.

No problem running something else (thanks for the suggestion, kps - thought that would work after I read your post earlier and tried it), but in response to that, I just think it stinks that I should have to try and remember IP nums of each box (even though our LAN is really small), especially since I can't seem to remember what happened yesterday, my kid's birthdays and any other important and relevant (sp?) information.  

 

Seems I only remember the unimportant things much of the time.

My wife likens me to Cliff Claven.

Guess I'll just have to put an IP list on my 'puter soes that I can remembers.........

Take care, all, and thanks to all for your suggestions.  

Chris

[atjurhs]

Yea, my statement about having AppleTalk enabled on the LAN was only in response to cdub's statement about having it on both of the local machines.  I guess what I should have said is that if he is trying to connect via AppleTalk over a PC LAN that has not been AppleTalk enabled, it won't make any difference if the two local machines have it set on or not.

Still I could be wrong here, as I don't have a way to test it out, but I'm pretty sure what I said above is correct.