UAM problem, afp://at/

[Chris Haas]

We're having a problem with UAM and saving passwords under OS X (10.2.6).
We've got an NT 4 domain with N 5 File servers that are all in a zone
(haven't removed that yet William). OS X users can connect to one server,
enter a username and password using NTLMv2 and store the password. Then they
connect to a second server, do the same and it works. However, if they
dismount or reboot when they go back in it says the credentials aren't valid
and they need to re-enter them. Once they do that it works, but it's really
annoying. They Key Chain shows:

Name: Server1
Kind: Microsoft Windows Server
Where: afp://at/

Name: Server1
Kind: Appleshare
Where: afp://10.1.1.1/Volume1

Name: Server2
Kind: Appleshare
Where: afp://10.1.1.2/Volume2

I don't get what that afp://at/ is but I think it has to do with the
problem.

Anyone?

 

[William M. Smith]

We're having a problem with UAM and saving passwords under OS X (10.2.6).
We've got an NT 4 domain with N 5 File servers that are all in a zone
(haven't removed that yet William). OS X users can connect to one server,
enter a username and password using NTLMv2 and store the password. Then they
connect to a second server, do the same and it works. However, if they
dismount or reboot when they go back in it says the credentials aren't valid
and they need to re-enter them. Once they do that it works, but it's really
annoying. They Key Chain shows:

Name: Server1
Kind: Microsoft Windows Server
Where: afp://at/

Name: Server1
Kind: Appleshare
Where: afp://10.1.1.1/Volume1

Name: Server2
Kind: Appleshare
Where: afp://10.1.1.2/Volume2

I don't get what that afp://at/ is but I think it has to do with the
problem.

Hi Chris!

I'll take a stab at your problem.

When you see "afp://at/servername", you're seeing a connection made via pure
Appletalk. When you see "afp://IPAddress", you're seeing a connection that
has been made via IP. IP is preferred because it's a faster protocol.

Since you have two Server1 entries in your keychain, remove the Appletalk
key so that the IP key remains. See if you can connect more reliably this
way.

Hope this helps! bill

 

[Chris Haas]

Thanks William. I should have stated before that I've disabled AppleTalk in
the network preferences. I don't have any connections that look like
afp://at/ServerName, I just have that single entry called "afp://at/". This
is created every time I connect to a Windows 2000 server, so when I try
connect to more than one I get a message saying that they entry already
exists. It's really weird.