First thing to do in cases like this is to make sure the serversoftware is updated and the Macintosh services in it are fully operational. Very often the person that controls the server does not have sufficient knowledge of the acquired actions for enabling access for Macs. Ahum... Macintoshservices.. aha !! It works!
Next; the error may be on your side ... you may not be using the correct protocol for linking to a Windows network. I do not know which OS you are using but the following may be usefull.
Try finding out whether SMB or AFP have something to do with it and try changing your settings: this might improve your connection.
Our University network administrator fixed this by using SMB rather than AFP to connect to the server. I believe it's a bug. Here's a useful article about it
I had so many problems using SMB. I found it imposiible to work with, kept getting the now infamous error -36. AFP comes with it's own problems, but as for the disconnecting error, I belive a registry hack on the server fixes it.
I haven't done this but I've been told that you can amend the reg...
-36 indicates a security problem. Make sure you've got the login information right!
I log into XP and w2k servers all the time - my only problem is that it can't seem to retrieve my password from the keychain - I have to type in every time.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.