Hi All,
Some background: I am porting from a Novell fileserver running Apple File Services to Windows Server 2003 running Services for Mac. I need to continue to use these file services for internal reasons and cannot switch to SMB/CIFS for my MACs.
Here is the problem I have: When I try to connect a MAC running OS X 10.3.9 to the AFP services on the Windows Server, I immediately receive a username and password error. I have checked the keychain and there is no username/password set. I have even entered the connection information as afp://username@the.server.ip.address and afp://username
assword@the.server.ip.address and still am immediately returned this error.
This happens with all MACs running OS X 10.3.9. If I use a MAC running OS X 10.4.8 to connect, I am receive an authentication box and am able to enter credentials to authenticate to the Windows Server. The volume then mounts and files are accessible properly.
Has anyone seen this? I have done quite a bit of research on this issue throughout the Internet and found the error to be a common one, however, there never seems to be a solution posted.
Any assistance would be greatly appreciated. Is this an issue that is fixed in the MAC OS X 10.4.x versions of MAC OS X?
Thank you!
Ken
Some background: I am porting from a Novell fileserver running Apple File Services to Windows Server 2003 running Services for Mac. I need to continue to use these file services for internal reasons and cannot switch to SMB/CIFS for my MACs.
Here is the problem I have: When I try to connect a MAC running OS X 10.3.9 to the AFP services on the Windows Server, I immediately receive a username and password error. I have checked the keychain and there is no username/password set. I have even entered the connection information as afp://username@the.server.ip.address and afp://username
This happens with all MACs running OS X 10.3.9. If I use a MAC running OS X 10.4.8 to connect, I am receive an authentication box and am able to enter credentials to authenticate to the Windows Server. The volume then mounts and files are accessible properly.
Has anyone seen this? I have done quite a bit of research on this issue throughout the Internet and found the error to be a common one, however, there never seems to be a solution posted.
Any assistance would be greatly appreciated. Is this an issue that is fixed in the MAC OS X 10.4.x versions of MAC OS X?
Thank you!
Ken