On Fri, Nov 7, 2008 at 3:17 PM, Cameron <[EMAIL PROTECTED]> wrote: > I've used examples to try and setup the share and have set > "valid users" to my ID and it will prompt me for a username and password but > does not accept it.
That could be almost anything. Microsoft's own Windows SMB client code responds to just about every problem by returning "Access denied", resulting in the credentials prompt you see. It could be an incompatible protocol or security level, wrong packet signing parameters, wrong domain association, bad username or password, dragons, etc. Samba can log *everything*, up to and including dumps of every packet, if you like. Try turning the "log level" in the config file up to 3 or 5, then check the logs. After making changes to Samba's config, you have to send it a signal, so it knows to reload its configuration. The command on Red Hat Linux and derivatives is "service samba reload". I dunno about AIX. Note that a config reload is not the same as a service restart; the latter will disconnect clients. Samba logs are typically kept in plain text files under either the /var/log/samba/ or /usr/local/samba/logs/ directories, but IBM may do something different. Use "less filename" to scroll up and down through a log file. Use "tail -f filename" to monitor a log file in real time. -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
