I am now able to get Windows to see my Ubuntu Samba share, but the problem lies within the way you have to configure Ubuntu Samba sharing. To enable Samba, all one has to do is right-click on a folder, select share and then the user is prompted to select a sharing method. Once thats done, you go to System - Administration - Shared folders, change the Workgroup. At this point the configuration ends and a new user thinks thats all there is to do, which is wrong. What people aren't being prompted to do is set a samba password so they can access the share from another PC. Dropping to CLI and running the command " sudo smbpasswd -a yourusernamehere " is the final step. I went over to my XP PC, went to start-run, typed the path to the Ubuntu share, entered my username and password and everything worked. The samba configuration needs to be changed to prompt the user to create a samba user/pass. If you can do the other samba related stuff without CLI, why should this key step be any different?
I am now able to get Windows to see my Ubuntu Samba share, but the problem lies within the way you have to configure Ubuntu Samba sharing. To enable Samba, all one has to do is right-click on a folder, select share and then the user is prompted to select a sharing method. Once thats done, you go to System - Administration - Shared folders, change the Workgroup. At this point the configuration ends and a new user thinks thats all there is to do, which is wrong. What people aren't being prompted to do is set a samba password so they can access the share from another PC. Dropping to CLI and running the command " sudo smbpasswd -a yourusernamehere " is the final step. I went over to my XP PC, went to start-run, typed the path to the Ubuntu share, entered my username and password and everything worked. The samba configuration needs to be changed to prompt the user to create a samba user/pass. If you can do the other samba related stuff without CLI, why should this key step be any different?