Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
General
GeneralPortable MacsHardwareNetworking
Applications
Mac ApplicationsEudoraFirefox / MozillaInternet ExplorerOutlook ExpressMS OfficeEntourageExcelPowerPointWordVirtual PCMedia PlayerOther MS Products
Programming
Mac ProgrammingCodeWarriorPerl
Country Specific
Australian Mac GroupUK Mac Group

Mac Forum / General / Hardware / February 2005



Tip: Looking for answers? Try searching our database.

afp connection error = -36

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
jt august - 13 Feb 2005 23:40 GMT
I have a beige g3 on osx 10.2.8 and a blueberry iBook on os 9.2.2.  I
have them linked with a crossover cable.  I have followed the directions
graciously given by several in these forums, and yet when I try to link,
I get:

Connecting to afp://192.168.1.101 ...

An error has occurred (error = -36)

Searching on the net using Google and searching Apple support, the only
references to this error number relate to Airport.  Can anyone tell me
what this code means, and what I need to do to correct the error and
link the two machines?

jt
jt august - 14 Feb 2005 01:02 GMT
> I have a beige g3 on osx 10.2.8 and a blueberry iBook on os 9.2.2.  I
> have them linked with a crossover cable.  I have followed the directions
[quoted text clipped - 9 lines]
> what this code means, and what I need to do to correct the error and
> link the two machines?

All I could find on the net was that -36 meant an IO error, which in all
the reference info I found said nothing about AFP, appletalk, ethernet
connections or anything networking oriented.  So, I decided to return my
crossover cable to the Laserwriter Pro and move on to other projects.  
When I tried to disconnect the iBook, I found the socket was loose, so I
decided to try a little experiment.  I turned the book on its side with
the plug face up, nestled the plug down in the socket, and tried
command-k.  It connected!

So, all these people I found had posted a similar error = -36, try
checking the ethernet connection's physical integrity.  If the
connection is loose, the connection will not communicate.

Thanks to those who replied in my previous thread on this issue.  Once I
got a solid connection, their responses were still quite valuable in
establishing a successful connection on the protocol side.

jt august
starsabre@att.net
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.