Matthew Gork
2005-Aug-24 20:38 UTC
[Samba] Windows XP Home mounting a Samba share on Solaris 10
I have usccessfully installed Samba-3.0.10 on a Sun workstation running Solaris 10. I am now trying to view the shared directory on a laptop running Windows XP Home. I am only using Samba for a workgroup share as I know XP Home can not log on to a domain. I can see the Samba server on the XP laptop when I selecet "view workgroup computers". However, when I try to select the Samba server to view the shared directory I get a connect popup asking for User name and password. When I enter the information for the UNIX/Samba account it just continues to pop back up and does not allow access. I have created the UNIX user account on the workstation and run smbpasswd -a USER amd smbpasswd -e USER, where USER is the account name. When reviewing the log.smbd after attempting to connnect to the Samba server from Windows the following errors are generated - [2005/08/23 18:05:12, 0] lib/util_sock.c:(185) Failed to set socket option SO_KEEPALIVE (Error Invalid argument) [2005/08/23 18:05:12, 0] lib/util_sock.c:(185) Failed to set socket option TCP_NODELAY (Error Invalid argument) [2005/08/23 18:05:12, 0] lib/util_sock.c:(185) Failed to set socket option SO_KEEPALIVE (Error Invalid argument) [2005/08/23 18:05:12, 0] lib/util_sock.c:(185) Failed to set socket option TCP_NODELAY (Error Invalid argument) [2005/08/23 18:05:19, 0] lib/util_sock.c:(185) Failed to set socket option SO_KEEPALIVE (Error Invalid argument) [2005/08/23 18:05:19, 0] lib/util_sock.c:(185) Failed to set socket option TCP_NODELAY (Error Invalid argument) [2005/08/24 11:45:19, 0] lib/util_sock.c:(185) Failed to set socket option SO_KEEPALIVE (Error Invalid argument) [2005/08/24 11:45:19, 0] lib/util_sock.c:(185) Failed to set socket option TCP_NODELAY (Error Invalid argument) [2005/08/24 12:43:23, 0] lib/util_sock.c:(185) Failed to set socket option SO_KEEPALIVE (Error Invalid argument) The log.mattlaptop contains the following - [2005/08/24 11:14:31, 1] lib/util_sock.c:(937) Gethostbyaddr failed for 192.168.0.3 [2005/08/24 11:35:54, 1] lib/util_sock.c:(937) Gethostbyaddr failed for 192.168.0.3 [2005/08/24 11:44:41, 1] lib/util_sock.c:(937) Gethostbyaddr failed for 192.168.0.3 [2005/08/24 11:45:19, 0] lib/util_sock.c:(367) read_socket_data: recv failure for 4. Error Connection refused [2005/08/24 11:45:19, 1] lib/util_sock.c:(937) Gethostbyaddr failed for 192.168.0.3 [2005/08/24 12:43:15, 1] lib/util_sock.c:(937) Gethostbyaddr failed for 192.168.0.3 [2005/08/24 12:43:23, 0] lib/util_sock.c:(367) read_socket_data: recv failure for 4. Error Connection refused I am just running a generic smb.conf file to try and get this up and running. The contents are - [global] workgroup = PAM socket options = TCP_NODELAY security = user hosts allow = pam80, mattlaptop, 192.168.0. hosts deny = all [root] path = / comment = Solaris root guest ok = yes read only = yes [share] path = /share comment = Solaris share browsable = yes guest ok = yes read only = no I have also tried manually editing the registry on the XP machine to enable clear text passwords. It did not correct the issue and, in fact, made the display of the samba server in the workgroup somewhat spotty. Sometimes it's there, sometimes it's not. I would greatly appreciate any input as I'm new to Samba and am trying to go this route rather than using a third-party windows NFS client. -Matt