On 11/1/05, Gustin Johnson <[EMAIL PROTECTED]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Actually you do need to worry about connecting as a user because most of > the samba installs I have encountered do not allow guest or non > authenticated users. > It was set to allow guests > Also, accounts usually have to be added to the samba via the smbpasswd > - -a command (just because a user has a shell account does not neccesarily > mean that they have a samba account). > Yeah I know this > Also, root is usually banned. > yup > Just humor me and tell me what happens when you try to connect with -U, > don't forget the // in front of the hostname. > It was the exact same > Also attach the relevant logs from /var/log/samba/ on both the client > and the server. The logs are your friend. > They both showed 100's of succsesful startups (all the restarts) > Others have asked for the smb.conf which is also a good thing. One more > question for you, how was samba configured? By hand, with SWAT, YaST > (evil) etc... I configure samba by hand, I find it the easiest and quickest way. I know it was good because it worked on another server > > Anyway I found the problem, It was with libdbsocket. A simple apt-get install --reinstall libdbsocket fixed it.
Travis R. _______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
