[dvsjr]

I had same issue, thanks for this tip. I ran changeip and checked the server thoroughly at setup so didn’t think to check it.

[dvsjr]

[QUOTE][u]Quote by: MacTroll[/u][p]So to the AFP server logs.

I’m curious as to if you see any difference between the two different issues when using Kerberos and when using non-Kerb.[/p][/QUOTE]

Im not sure I follow, as I posted this info before, maybe this isn’t what you are referring to?
If I connect I am first prompted to login with a kerberos login. If I do that, I get the error. Any subsequent attempts to connect are instant fails, until I delete the ticket using the kerberos utility.
If I dont use kerberos, but instead cancel it, I am prompted with the DHX2 style login. This works perfectly, and shares show up and mount as they should.

d

[dvsjr]

Yes, 10.4 AFP server was the OS I was connecting to, and no, I am the AD admin and we have probably no more than 4-5 groups altogether.

Another strange test: I used my own 10.4.11 Tiger OS Mac to connect to these servers. (All my Mac servers are still Tiger) I followed the same steps as my most recent post, I opened kerberos, clicked new, typed in my password (REALM.COM was correct) then connected to the server. Again I was connected using SSO but once I mounted the proper share, (this time I could see all the shares) I couldnt open the share, I got an insufficent access privileges error.

[dvsjr]

After getting the error, I deleted and recreated the realm, and this seems to have resolved the issue on the server I was originally working on.
However, I went to a client Mac that also has been known to have this issue. I opened the kerberos utility from the CoreServices folder, clicked New and created a Ticket Cache.
the ticket cache format is: (v5) [email protected] I then tried logging into the same server I used with the other Macintosh and it created a ticket in the format of: krbtgt/[email protected] 10:00 and afpserver/[email protected] 10:00 The connection to the server is made, but the shares window is empty. If I destroy the ticket, and connect again without using kerberos the shares appear and connect normally.
My domain and realm are the same name, I’m not sure where things are breaking here. Thanks for the offer to help me understand it.

[dvsjr]

Addition: I just deleted the realm, and manually recreated it using the exact same info. I connected to a server, at the kerberos prompt I logged in, and it worked (no error.) Connecting to a different server, kerberos worked (ie no credentials were asked for, I was prompted to choose my server share without logging in, as normal.) I don’t see how this is a fix, as the info for the realm I entered is identical to what it was before.

[dvsjr]

“Me too” replies actually make finding the answer even harder.

[dvsjr]

I have an Exabyte VXA-2 autoloader 1U firewire connected to an Xserve G4. I had these exact same issues with it as well, I took some server admin list advice (also called Dantz) and updated the firmware of the exabyte drive, updated the Retrospect software and also the driver and I havent had issues since. (Knock Wood)

[Author]

Posts