Unable to connect to NT server after 10.4.2

I was really hoping to be able to upgrade our other mac's to tiger.
I stopped after realizing that tiger won't connect to our Heidelberg RIP Pc (we are a print shop) running NT 4 SP6. I believed that 10.4.2 would have given back AFP connections. However I'm still getting the AFP protocol version not supported error on connecting. I don't like having NT in our office, but its not down to us, its down to Heidelberg. A feel a little angry at apple for removing the ability to connect to old servers and in the end they lose out because it means I won't be upgrading any more mac's to Tiger.

Posted on Jul 13, 2005 1:21 AM

Reply
20 replies

Jul 14, 2005 8:45 PM in response to Nicholas Dring

We have the same problem by the sounds of it. We are running an Omnis database on a Win2003 server with the data file shared for the macs via Services for Macintosh. Since upgrading to 10.4.2 I get the 'error -35 command could not be completed because one or more items could not be found'. I can still connect via SMB but this will corrupt the datafile since our Omnis application runs in Classic.

I've always been hesitant about upgrading straight away and usually use my own machine as a guinea pig before rolling it out to my users. All of the 10.3.9 are fine as is the other 10.4.0 machine. 10.4.1 was fine as well.

Really annoying. Tiger has lots of issues and there is no way I'll be rolling it out to my company. 10.3.9 forever! Or at least till some of these bugs are worked out.

Has anyone got any further info about fixing this?

Jul 15, 2005 2:44 AM in response to martyn pot1

Yes I have the same problem after doing a wipe and fresh install on a G5.
I first installed from the original g5 cd's (10.3) and then used the tiger upgrade. After creating a user I then ran sw update to bring th g5 to 10.4.2.
Since rebooting I get the ''error -35 command could not be completed because one or more items could not be found'. I can also connect via SMB. As Martyn said, anyone got a fix on this?

Jul 16, 2005 7:04 AM in response to Nicholas Dring

Update: After first trying a new install using an external drive, and following the same upgrade path as before to get to 10.4.2 I was successfully able to connect to our w2k server. I then deleted the user on the machine internal drive and created a new one. This solved the problem. However I am still unable to connect to our Win NT server, I get a protocol error as others have said. I was hoping that 10.4.2 would have reinstated this protocol support as we don't all live in an ideal world where machines can be easily upgraded to the latest OS. Fortunately I only need to connect to the Nt server to drag and drop files on to printer queues so I can use SMB.

Sep 14, 2005 4:11 PM in response to Nicholas Dring

I find it irritating when people chime in with "me too - any fix?" but that is more or less what I'm doing. I experience all the same issues including the "Error -35", and a new user can log on but the old one cannot be fixed to do so. However, I do have this to add:

Have you noticed that this error pops up INSTANTLY? long before it can even poll the server, I think. And here is an interesting variation - I UPGRADED to 10.4.2 because I was having the same problem in 10.3.9, except that in 10.3.9 the error message would say "you have the wrong name or password". But it would pop up INSTANTLY upon trying to connect and BEFORE the dialogue that asks for the name and password.

Anyway, after the upgrade the computer in question was able to connect fine for a few hours then started getting the error -35. Hmmm. Something corrupt SOMEWHERE, but I've trashed every pref I can possibly find and this does not go away. WHAT IS IT?!?

-Todd

Sep 14, 2005 4:34 PM in response to Todd Shirley

Hi Todd, just for clarification-Yours is trouble with an NT4 server?
Or are you connecting to some other flavor of Windows?
(version and service pack? Domain or workgroup?)
Can you pinpoint the failure to a more specific timeframe? (two hours? three?)

not sure any of this is relevant, but there may be something common in this thread that no one's seen...other than "Tiger broke it".
I'm betting that it's more an AFP setting that Tiger and NT4 are fighting over, and the NT machine just will not do Tiger's brand of AFP anymore...which is 'none'.

Sep 15, 2005 9:10 AM in response to Nicholas Dring

Sorry for not giving all the info. I'm trying to connect to a Windows 2000 server. I'm not sure what service pack.

However - I FOUND A FIX! I got this from a forum at macosx.com:

Trash the "GlobalPreferences.plist" in:

/<username>/Library/Preferences
and
/Library/Preferences

Trashing the /Library/Preferences one fixed the Netware logon problem, but not the Windows one, i then trashed the other one and it fixed that also.

The reason i tried trashing those files was as a last ditch attempt because it has "something" to do with AFP from some documentation i was reading about AFP plain text password issues.

Oct 12, 2005 10:20 AM in response to Nicholas Dring

We have had the same problem...and none of the above have worked. My thinking is that the NT server has SFM (services for macintosh) on and that is part of the problem. Everything I have found that is positive says that you CAN attach to a NT server it just has to be via TCP/IP. Maybe I am missing something...can someone help explain this some? I thought we were going via tcp/ip now i wonder.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Unable to connect to NT server after 10.4.2

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.