SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
At work we've recently installed a Slackware 10.0 box C with Samba on it. It's connected to the XXX.YYY-domain as a little brother of client A (Windows XP) and server B (Red Hat 9). B acts as a DHCP server for a small private LAN with some Linux clients, a Windows 2000-machine and 2 Windows XP Pro-boxes (of which one is a laptop).
I copied the smb.conf of B to C and made some minor changes. I also gave everyone a Unix account and corresponding Samba account (via smbpasswd). Now, the Linux clients and the Windows 2000-box can access their Samba shares (home directories), the Windows XP clients can not.
What's confusing:
Client A finds C in its neighborhood, he can log in and sees the available shares. When accessing his home share, he gets an "Access denied"-error and a message telling him to ask for proper permissions. Even if we make his home share a 777, this message stays the same. Access to the printer map (which is empty because there's no printer attached) on the other hand, is possible without any problem.
The other troublesome XP-clients (those behind server B), can't even find C in the first place. On trying to mount the share by name, they get the same error as A did.
So, I wonder whether someone has encountered these problems too? Here's the smb.conf (after tweaking our first one with swat):
Code:
# Global parameters
[global]
workgroup = OURGROUP
server string = Samba Server
obey pam restrictions = Yes
smb passwd file = /etc/samba/smbpasswd
pam password change = Yes
passwd program = /usr/bin/passwd %u
passwd chat = *New*password* %n\n *Retype*new*password* %n\n *passwd:*all*authentication*tokens*updated*successfully*
username map = /etc/samba/smbusers
unix password sync = Yes
log file = /var/log/samba/%m.log
max log size = 1024
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
load printers = No
dns proxy = No
ldap ssl = no
valid users = @users
hosts allow = XXX.YYY., 127.
hosts deny = ALL
[homes]
comment = Home Directories
read only = No
Distribution: slack current with 2.6.16.18 (still off the hook)
Posts: 275
Rep:
The option you have if you don't want to complicate yourself very much is install dorpline gnome for Slack, it includes the pam package by default (I found that out too late), I don't like pam
I did remove those PAM-lines, but that didn't do much. After removing the DENY ALL, client D (a twin of A) and the clients behind B can access server C. I can't test client A currently, but normally it should work now.
I've been too optimistic . Client A is the only one unable to use Samba correctly. User A's Samba account works, though. We've tried it via a laptop on the same wifi-connection as client A. Both the laptop and client A have the same OS (Windows XP Pro with SP2). So, the problem isn't Slackware-related anymore.
Just for the sake of completeness, part of the error log:
Code:
NT user token of user S-1-5-21-1153249575-2565324612-427322846-501
contains 7 SIDs
SID[ 0]: S-1-5-21-1153249575-2565324612-427322846-501
SID[ 1]: S-1-5-21-1153249575-2565324612-427322846-514
SID[ 2]: S-1-1-0
SID[ 3]: S-1-5-2
SID[ 4]: S-1-5-32-546
SID[ 5]: S-1-5-21-1153249575-2565324612-427322846-1197
SID[ 6]: S-1-5-21-1153249575-2565324612-427322846-1199
[2005/01/11 11:09:13, 5] auth/auth_util.c:make_server_info_sam(844)
make_server_info_sam: made server info for user nobody -> nobody
[2005/01/11 11:09:13, 3] auth/auth.c:check_ntlm_password(268)
check_ntlm_password: guest authentication for user [] succeeded
[2005/01/11 11:09:13, 5] auth/auth.c:check_ntlm_password(305)
check_ntlm_password: guest authentication for user [] -> [] -> [nobody] succeeded
[2005/01/11 11:09:13, 5] auth/auth_util.c:free_user_info(1298)
attempting to free (and zero) a user_info structure
[2005/01/11 11:09:13, 10] auth/auth_util.c:free_user_info(1301)
structure was created for
[2005/01/11 11:09:13, 3] libsmb/ntlmssp_sign.c:ntlmssp_sign_init(319)
NTLMSSP Sign/Seal - Initialising with flags:
[2005/01/11 11:09:13, 3] libsmb/ntlmssp.c:debug_ntlmssp_flags(62)
Got NTLMSSP neg_flags=0x60088215
[2005/01/11 11:09:13, 3] smbd/password.c:register_vuid(222)
User name: nobody Real name: nobody
[2005/01/11 11:09:13, 3] smbd/password.c:register_vuid(241)
UNIX uid 99 is UNIX user nobody, and will be vuid 100
[2005/01/11 11:09:13, 3] smbd/process.c:process_smb(890)
Transaction 3 of length 82
[2005/01/11 11:09:13, 3] smbd/process.c:switch_message(685)
switch message SMBtconX (pid 31567)
[2005/01/11 11:09:13, 3] smbd/sec_ctx.c:set_sec_ctx(288)
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
[2005/01/11 11:09:13, 3] lib/access.c:check_access(313)
check_access: no hostnames in host allow/deny list.
[2005/01/11 11:09:13, 2] lib/access.c:check_access(324)
Allowed connection from (157.193.92.25)
[2005/01/11 11:09:13, 3] smbd/service.c:make_connection_snum(457)
Connect path is '/tmp' for service [IPC$]
[2005/01/11 11:09:13, 3] lib/util_seaccess.c:se_access_check(251)
[2005/01/11 11:09:13, 3] lib/util_seaccess.c:se_access_check(252)
se_access_check: user sid is S-1-5-21-1153249575-2565324612-427322846-501
se_access_check: also S-1-5-21-1153249575-2565324612-427322846-514
se_access_check: also S-1-1-0
se_access_check: also S-1-5-2
se_access_check: also S-1-5-32-546
se_access_check: also S-1-5-21-1153249575-2565324612-427322846-1197
se_access_check: also S-1-5-21-1153249575-2565324612-427322846-1199
[2005/01/11 11:09:13, 3] smbd/vfs.c:vfs_init_default(203)
Initialising default vfs hooks
[2005/01/11 11:09:13, 2] smbd/uid.c:change_to_user(205)
change_to_user: Invalid vuid used 100 or vuid not permitted access to share.
[2005/01/11 11:09:13, 0] smbd/service.c:make_connection_snum(541)
Can't become connected user!
[2005/01/11 11:09:13, 3] smbd/error.c:error_packet(118)
error packet at smbd/reply.c(389) cmd=117 (SMBtconX) NT_STATUS_LOGON_FAILURE
[2005/01/11 11:09:13, 3] smbd/process.c:process_smb(890)
Transaction 4 of length 43
[2005/01/11 11:09:13, 3] smbd/process.c:switch_message(685)
switch message SMBulogoffX (pid 31567)
[2005/01/11 11:09:13, 3] smbd/sec_ctx.c:set_sec_ctx(288)
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
[2005/01/11 11:09:13, 5] auth/auth_util.c:free_server_info(1324)
attempting to free (and zero) a server_info structure
[2005/01/11 11:09:13, 3] smbd/reply.c:reply_ulogoffX(1207)
ulogoffX vuid=100
[2005/01/11 11:09:23, 3] smbd/process.c:timeout_processing(1104)
timeout_processing: End of file from client (client has disconnected).
[2005/01/11 11:09:23, 3] smbd/sec_ctx.c:set_sec_ctx(288)
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
[2005/01/11 11:09:23, 2] smbd/server.c:exit_server(568)
Closing connections
[2005/01/11 11:09:23, 3] smbd/connection.c:yield_connection(69)
Yielding connection to
[2005/01/11 11:09:23, 3] smbd/connection.c:yield_connection(76)
yield_connection: tdb_delete for name failed with error Record does not exist.
[2005/01/11 11:09:23, 3] smbd/server.c:exit_server(611)
Server exit (normal exit)
Strange thing is: we logged in as a specific user having a UNIX and a Samba account. The log says we're logged in as nobody...
I am definitely newbie by all definitions but I think the problem might be adding some registry info into Windows: http://www.ccs.uky.edu/docs/samba.htm
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
. Client A is the only one unable to use Samba correctly. User A's Samba account works, though. We've tried it via a laptop on the same wifi-connection as client A. Both the laptop and client A have the same OS (Windows XP Pro with SP2). So, the problem isn't Slackware-related anymore.
suggestion
