well.... it is on an internal network but the only thing that is separating it from the internet is my DSL router. If I remember cdforrectly the router is a busybox installation (yep.... qwest was/is<?> using linux for its DSLs). I found that out when I was playing with penetration testing with backtrack. Is it safe to put the guest account in. How could I lock it down to make it safe if it isn't?

On Mon, Mar 5, 2012 at 4:45 AM, Lisa Kachold <lisakachold@obnosis.com> wrote:
Thanks Mike:

On Mon, Mar 5, 2012 at 12:42 AM, Michael Havens <bmike1@gmail.com> wrote:
On Mon, Mar 5, 2012 at 12:18 AM, Lisa Kachold <lisakachold@obnosis.com> wrote:
Please post your entire conf file so the PLUG can assist you.
--snip conf file--

That looks acceptable, but you might copy it to a backup and use the simplist possible configuration (as described in #2 troubleshooting, below, but only after #1 verifying your XP is setup right).  I believe that your issues involve your authentication to XP.

1) As you initially asked, your XP account name was changed.  Please refer to the enabling of the guest account HowTo in:  http://unixwiz.net/techtips/samba-xp-printing.html  NOTE: I am assuming that these machines are protected inside your network, since it's usually a BAD IDEA to enable the guest account otherwise.  Verify your WORKGROUP and NetBIOS name in XP.

Please, then, attempt to connect from XP and tail the log and see what Samba is whining about?

2) Follow these troubleshooting tools to tail the nmdb.log and smdb.log as well as using command line tools in a CMD.com window on XP:  http://www.troubleshooters.com/linux/presentations/samtroub.htm


Okay.... I'll get right to it
--
:-)~MIKE~(-: