I haven't used Samba so I am not sure either, I am looking around online for likely things to try.
On this link have a look at the step number 6 restart Samba (did you do this after changing the directory name ? plus it was for the previous machine.)
and number 8, compare the method of #8 to how you set up the network to see if this area is also good.
https://help.ubuntu.com/community/How%20...f%20Way%21
Another thing I thought maybe is to check if you have made a rule in UFW to allow Samba, you will have had that on the previous machine, and if it was not added as a rule on the new machine, then it would deny incoming connections.
As I have said I am not familiar with Samba, the conf file looks odd to me it seems to contradict itself.
It says map guests as a bad user in global settings.
But it says %G are valid users in server settings.
It could be Samba needs to define the guest so it can map it as a bad user, it would seem more that if it is not a valid user then it doesnt need to be mapped as a bad user.
Or it can not be in the valid user group and do map guests as a bad user, in case guests try to access it.
Otherwise they look like it could conflict, or at the least slow the code down.
Its just an idea.
On this link have a look at the step number 6 restart Samba (did you do this after changing the directory name ? plus it was for the previous machine.)
Code:
sudo service smbd restartand number 8, compare the method of #8 to how you set up the network to see if this area is also good.
https://help.ubuntu.com/community/How%20...f%20Way%21
Another thing I thought maybe is to check if you have made a rule in UFW to allow Samba, you will have had that on the previous machine, and if it was not added as a rule on the new machine, then it would deny incoming connections.
As I have said I am not familiar with Samba, the conf file looks odd to me it seems to contradict itself.
It says map guests as a bad user in global settings.
But it says %G are valid users in server settings.
It could be Samba needs to define the guest so it can map it as a bad user, it would seem more that if it is not a valid user then it doesnt need to be mapped as a bad user.
Or it can not be in the valid user group and do map guests as a bad user, in case guests try to access it.
Otherwise they look like it could conflict, or at the least slow the code down.
Its just an idea.