I'm currently running PCLinuxOS (Mandriva based distro) and am kinda puzzled as to why both my syslog and messages logs are being filled up with a repeating message of "smbd/service.c:942(make_connection_snum) Can't become connected user! I currently have 3 Windows XP Pro computers (1 desktop, 2 laptops) that I'm attempting to connect to the Linux box to use for file/print sharing. 1 laptop and the desktop both work fine so I'm assuming the issue is with the 2nd laptop (my wife's, good luck getting her to let me have it for a while to work on it). I can access both the samba share (have it mapped as Z: on both working pcs) and the shared printer (setup under printers and faxes but used 'net use' to set it up) When I try to use the same method to setup the share drive and printer on my wife's laptop I'm getting an error about bad username or password. Currently I have accounts for both of us with identical passwords setup on the Linux box and the desktop. We also have just 1 account each (also same username/passwords) on our respective laptops. I'm thinking the issue might be a Windows configuration as the other 2 pcs work fine, and also, I'm unable to view the other computers using Windows Network Places but CAN access them using run \\<IP_ADDRESS_HERE>. All computers can ping each other successfully. Any help would be greatly appreciated as I've spent the last week trying to get this worked out.

Most likely on the Desktop and Working Laptop you are not using "Simple" file sharing, and most likely on the Miss's laptop she is.

Check the "Simple Sharing" on all three...
open my computer -> tools -> Folder Options -> "View" tab -> very bottom of the scrolling list

Simple file sharing doesn't use user/pass for protection, so shouldn't send them either and is probably doing a "guest" user or "nobody" (or null even)... remove the checkmark, and the username and password should be required and sent for connecting to shares.

I had already unchecked the simple file sharing option (during previous research). Somehow I got this all working now. Not exactly sure how but I did. I added users to the smbpasswd file (me and my wife) with corresponding passwords and enabled NTLMv2 support in Samba so I'm guessing that was the issue of her not being able to connect. Now however, I'm getting a different message filling up the log:

winbindd/idmap.c:149(smb_register_idmap) Idmap module nss already registered!

and

winbindd/idmap_tdb.c:287(idmap_tdb_open_db)
Upgrade of IDMAP_VERSION from -1 to 2 is not possible with incomplete configuration

However, everything seems to be working (all pcs access share and printer and get dynamic or static IP from dhcp) so I'm assuming these are informational messages only or warnings from a feature I may have configured that is not actually being used.

looks like the errors are happening because samba is configured for DOMAIN security rather than User or Share.

http://www.samba.org/samba/docs/man/....html#SECURITY

i have security set as security = user (As I'm authenticating the computers using mine or my wife's username/password (both accounts the same on pc's and Linux box, and added to smbpasswd)

Everything is up and running now and all computers can access the shares (disk and printer) but I'm still getting a ton of these messages in my log files (multiple files recording the same message). This leads me to believe its something on the client end configuration wise but I'm at a loss as to what (new to Samba). Any insight would be greatly appreciated.