Still having trouble?

have you looked for any error messages? Connect via SSH as root to your pogoplug and issue the "dmesg" command. Check for error messages related to your memory stick (usually sda or sdb or sdc, etc). If that shows too much information you can try to limit it with "dmesg | grep 'sda'" and do that for each drive (sda, sdb, sdc, etc). That should tell you if your usb sticks are getting read/write errors.

We can check if your device is rebooting itself by setting the date and then checking the next day to see if it's correct. Do a "date" command as see what it says. If you haven't set the date it's probably something that is not correct.

Now set the correct date like this "date -u MMDDHHmmYYYY.SS" So to set the date for January 3, 2012 at 4:45:00pm it would be:
date -u 010316452012.00
notice the 4pm is done with military time of 16 (12+4). I'm doing this from memory but I'm pretty sure that will update your date and time. If you do another "date" command (without any other parameters) it should show your correct date. Now tomorrow, if you do the "date" command it should still show the correct time unless your unit has rebooted itself overnight.

You can check what Samba is sharing with the
"smbclient -N -L pogo.plug.ip.address" command. it should show you a list of the shares. Remove the "-N" and add a user parameter if you have user security setup.

Next look in your samba log file for problems. The log file was setup in your smb.conf. Usually it's something like /opt/var/log/samba/ so change the directory to the log directory with the CD command "cd /opt/var/log/samba/". Then list what's in the directory with the "ls" command.

Go through each file with "more" command: "more file.name" Use the spacebar to advance to the next page of the file. You're looking for error messages that might cause your problem. One nice thing is that if you set the correct date and time then the log file will have good dates and times in them also.

None of this solves your problem but it's a start to finding out what your problem is. If you find error messages then get on google and start hunting them down.

One thing to remember is that there are different pogoplugs and some have different cpu's and busybox versions. To tell which you have use these two commands:

"head -n 1 /proc/cpuinfo" will tell you what cpu you are using
"cat --busybox" is an invalid command that will cause busybox to show what version it is.

Good luck.

SWAT is nice if you are going to be making a lot of changes to your samba config. I find that using the text editor of your choice (my vote is for nano) and doing it manually is okay for me. Usually once I have it set up I don't change it much. Also it's not a bad idea to copy your /opt directory over to another drive every once in a while just to back it up in case of a failure. You can use the copy ("cp") or "tar" commands. Do a google search for more information on them. You might still have to re-install everything but at least your various config files will be saved. Six months from now if you need to redo them you'll have forgotten how (if you're like me).

Glad to hear you got it all working.

Looking at the notes on this site:

http://www.nslu2-linux.org/wiki/Optware/SWAT

at the bottom where it talks about plug users, did you follow those instructions?

It looks like SWAT is included. Like I said I don't use SWAT and I didn't need xinetd, so I haven't installed it but it does look like swat is included with the samba2 package.