Plaintext password for Samba shares....
Background:
Back when 10.4 came out in order to connect to a samba share with plaintext passwords you had to create a nsmb.conf file in the private/etc folder with the following information:
[default]
minauth=none
This allowed from 10.4 and 10.5 mac clients to connect to a samba share with a plaintext password.
Problem:
After upgrading or doing a fresh install of 10.6 and ensuring that the nsmb.conf file was in the private/etc folder we get the error that +"You do not have permission to access the server "server_name"."+ We have 3 main file servers that our users need to be able to mount to and we can no longer do so.
Environment:
Our file servers are running Redhat 5.3, Samba is the version that shipped with that. 10.4/10.5 clients can still connect to the Samba file servers, but 10.6 cannot. At this time our LDAP backend does not support encrypted passwords (sambaSamAccount object class and associated attributes) yet, and is a year or two before we will be able to implement that.
Concerns:
Once new hardware is available I fear that it will be difficult to run 10.5 or older Operating systems on that hardware meaning that we will be forced to use 10.6. I want to be able to use 10.6, but if we can't access file shares via mounting a samba share then we may have to deny getting any "new" apple equipment for our campus.
Solutions:
We have an open case with Apple support and they were very helpful. They identified that they haven't officially supported plaintext passwords from a mac client since 10.4. Though I explained that there was a workaround for this and that something obviously changed in 10.6 from 10.5 that causes the workaround to no longer work for us. They are going to get back to me in a few days to let me know if there is an alternative or that there is nothing they can do.
Does anybody have any alternative solutions or share any similar situations in their environments? I have looked everywhere online and every idea I have seen or tried has not worked. I am at a loss of what else to try. Any suggestions, comments, or thinking outside the box is highly recommended.
Thanks,
Shaun
Back when 10.4 came out in order to connect to a samba share with plaintext passwords you had to create a nsmb.conf file in the private/etc folder with the following information:
[default]
minauth=none
This allowed from 10.4 and 10.5 mac clients to connect to a samba share with a plaintext password.
Problem:
After upgrading or doing a fresh install of 10.6 and ensuring that the nsmb.conf file was in the private/etc folder we get the error that +"You do not have permission to access the server "server_name"."+ We have 3 main file servers that our users need to be able to mount to and we can no longer do so.
Environment:
Our file servers are running Redhat 5.3, Samba is the version that shipped with that. 10.4/10.5 clients can still connect to the Samba file servers, but 10.6 cannot. At this time our LDAP backend does not support encrypted passwords (sambaSamAccount object class and associated attributes) yet, and is a year or two before we will be able to implement that.
Concerns:
Once new hardware is available I fear that it will be difficult to run 10.5 or older Operating systems on that hardware meaning that we will be forced to use 10.6. I want to be able to use 10.6, but if we can't access file shares via mounting a samba share then we may have to deny getting any "new" apple equipment for our campus.
Solutions:
We have an open case with Apple support and they were very helpful. They identified that they haven't officially supported plaintext passwords from a mac client since 10.4. Though I explained that there was a workaround for this and that something obviously changed in 10.6 from 10.5 that causes the workaround to no longer work for us. They are going to get back to me in a few days to let me know if there is an alternative or that there is nothing they can do.
Does anybody have any alternative solutions or share any similar situations in their environments? I have looked everywhere online and every idea I have seen or tried has not worked. I am at a loss of what else to try. Any suggestions, comments, or thinking outside the box is highly recommended.
Thanks,
Shaun
MacBook Pro 2.4Ghz, Mac OS X (10.6)