[Samba] samba and mac clients

[John Stile]

On my network, when a mac client tries to access a windows share, they
are presented with a dialog box, prompting them for the share to connect
and then the authentication credentials.

However, when a mac client tires to connect to a samba share, it
immediately receive a dialog box with the error: "Could not connect to
the sever because the name or password is not correct.".

Does anyone know which smb.conf settings effect this behavior?

On the samba logs, I don't see any messages, so the mac is not even
trying to authenticate. From server: Mac_client=192.168.60.208; tcpdump
-i eth0 -n "host $Mac_client"
13:35:25.844578 IP 192.168.60.208.49803 > 192.168.60.48.137: NBT UDP PACKET(137): QUERY; REQUEST; UNICAST
13:35:25.844761 IP 192.168.60.48.137 > 192.168.60.208.49803: NBT UDP PACKET(137): QUERY; POSITIVE; RESPONSE; UNICAST
13:35:25.845579 IP 192.168.60.208.49677 > 192.168.60.48.139: S 4284939447:4284939447(0) win 65535 <mss 1460,nop,wscale 0,nop,nop,timestamp 2653034266 0>
13:35:25.846105 IP 192.168.60.208.49678 > 192.168.60.48.139: S 3344627758:3344627758(0) win 65535 <mss 1460,nop,wscale 0,nop,nop,timestamp 2653034266 0>

Command issued from the mac: mount_smbfs -Ujohns //smbdev1/htdocs tmp

Samba Server: samba version:3.0.14a-3, Distribution debian 3.1, Linux kernel:2.6.8-2-386

--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba

[John Stile]

Thank you Stewart,

Going back to basics, I checked what ports smbd listens:
netstat -lnp |grep smb
tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN 8330/smbd

My smb.conf had an 'smb ports' option with a note:
#Added ports option to clear the error: 'getpeername failed. Error was Transport endpoint is not connected'
smb ports = 445

I commenting out the line, restarting samba, and now smbd is listening
on tcp 139 and 445 and mac clients can connect just fine.
netstat -lnp |grep smb
tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN 8330/smbd
tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN 8330/smbd

Thank you for your help.
Looks like a mac client requires tcp139.

On Fri, 2006-03-17 at 14:08 +1100, Stewart wrote:
> Hi John..
>
> have you checked that the Windows Workgroup or Domain is correctly
> configured in /Applications/Utilities/Directory Access.app? I had
> this problem once ages ago and /think/ that was the fix though my
> memory is fuzzy. :)
>
> (The name of the Directory Services app might have changed too - i'm
> on 10.4 now and can't remember if it was different under 10.3)
>
> ..S.

[andrew....@jpmchase.com]

Hi John,

I know from experience that OS X and Samba work just fine together, I
even had Kerberos auth to AD working (works pretty much by default
actually). Two suggestions, have u tried connecting from the GUI rather
than command line (maybe something in the command syntax u are trying isnt
right)? And also have u tried using the full command line syntax including
"//[workgroup;][user[password]@] server[/share] path" ??

cheers Andy.