ctsmequon
asked on
Mac OS X 10.5 Problem: SMB overridding AFP
Hello-
I have a Windows Server 2003 providing shared volumes using both SMB and AFP. I have two Mac OS X 10.5 workstations that frequently lose their AFP connections and instead connect to the shared volumes using SMB. This is a problem in my situation because of some legacy software in our network that requires AFP connections.
Is there a way to tell Mac OS X 10.5 to always use AFP and never use SMB?
Thanks,
ctsmke
I have a Windows Server 2003 providing shared volumes using both SMB and AFP. I have two Mac OS X 10.5 workstations that frequently lose their AFP connections and instead connect to the shared volumes using SMB. This is a problem in my situation because of some legacy software in our network that requires AFP connections.
Is there a way to tell Mac OS X 10.5 to always use AFP and never use SMB?
Thanks,
ctsmke
Adrian Cantrill
How are you connecting to the shares ? with just the server name ? or afp://server ? Obviously the latter will pick AFP specifically.
And another though, have you check to see if the AFP server is having connectivity issues ? i'm wondering if thats why the machines are defaulting back to SMB ?
And if you want to remove the ability to mount smb shares altogether then you may want to consider doing a
cd /sbin
sudo chmod go-x mount_smbfs
although this could have other issues, if you use SMB elsewhere.
cd /sbin
sudo chmod go-x mount_smbfs
although this could have other issues, if you use SMB elsewhere.
ASKER
Right now, connections to the server are established using both Finder | Go | Connect to Server | "afp://10.0.x.x" and through the 'Shared' section of the Finder windows. Oftentimes method produces a good AFP connection, but then sometimes the server connection reverts to SMB.
As best I can tell, AFP is functioning properly since the other Macs on the network (running a variety of OS X 10.3-.4) don't seem to have a problem with it. Is there a specific test you can think of to have me run to verify the server's AFP capability?
And I'd be willing to experiment with the SMB lockout command you mentioned. Two questions: first, I simply enter those commands into Terminal command prompt, or do I need to do something special? And second, what is the 'undo' command in case I find I need SMB capability?
As best I can tell, AFP is functioning properly since the other Macs on the network (running a variety of OS X 10.3-.4) don't seem to have a problem with it. Is there a specific test you can think of to have me run to verify the server's AFP capability?
And I'd be willing to experiment with the SMB lockout command you mentioned. Two questions: first, I simply enter those commands into Terminal command prompt, or do I need to do something special? And second, what is the 'undo' command in case I find I need SMB capability?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
This solution did not include any step by step instructions. Rather, this solution is a starting point for research that finally resolved the problem.