Could you post a copy of your /etc/samba/smb.conf file, or post the full
output of [ testparm -v ], without the brackets, from the command line?
The -v option list everything including defaults.
Try to connect your Mac user to samba using smbclient. I'm running
samba locally and can connect to samba from 192.168.1.109 using the
following command:
smbclient -L 192.168.1.78 --user=leland
After typing the above into a command line, I'm prompted for a password,
and able to connect after entering it. The password must be enter into
the samba server using the
Make sure you have samba install on the Mac.
Make sure the Mac samba user has been properly added with samba
password. http://www.cyberciti.biz/faq/adding-a-user-to-a-samba-smb-share/
Make sure the samba ports 137, 138, and 139 and not blocked by any
firewalls.
Regards,
LelandJ
On 03/11/2014 10:11 AM, Ken Dibble wrote:
A gray share means that the user is already connected, most likely
with his default account.
Thanks Christof.
"Default account"? I am not familiar with Macs, but the user is not
logging into his local machine with the domain user account I am
referring to. He has his own local account for the Mac. I don't see
how the Mac would automatically know his domain user account
credentials in order to connect to a network share. However, he is
clearly not connected to the share I want him to access.
The user can see all machines on the network.
The user can see all the share folders on the CentOS file server.
Sometimes the Mac indicates the user is connected to the file server
as "Guest", and sometimes it does not. Clearly there are bugs in this
interface. However, whether or not a successful connection is
indicated, the user has no access to the contents of the share I want
him to have. Being "allegedly" connected as "Guest" no longer confers
access since changes were made to the file server to disallow guest
access.
From the Network list, the Mac user can click on the share folder on
the server and press "Connect As..." and get a dialog to present his
credentials today (yesterday this wouldn't work). He can then enter
the domain user credentials to log into the share, but the Mac won't
accept them. The dialog box shakes back and forth and nothing happens.
As I mentioned, I know these credentials are correct because they work
for the internal email being served by the SAMBA 3 domain controller.
It has been suggested that these problems may be due to bugs in SMB2.
If you have any further thoughts I would be most appreciative.
Thanks.
Ken Dibble
www.stic-cil.org
[excessive quoting removed by server]
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
