[Staff]
 path = /media/see-admin/Daten/Staff
 available = yes
 browseable = yes
 guest ok = yes
 writeable = no
 
[sambashare]
    comment = Samba on Ubuntu
    path = /home/see-admin/sambashare
    read only = no
    browsable = yes

Your problem on both of these shares is the Linux permissions on the path to the shared folders. THe only user that can access these shares is "see-admin". If you want to force the client user to use the see-admin user name you have to add that user to the samba password database:

sudo smbpasswd -a see-admin

If you want guest user access or any other registered ( meaning a user added to smbpasswd ) you can change your share definition to these:

[Staff]
 path = /media/see-admin/Daten/Staff
 available = yes
 browseable = yes
 guest ok = yes
 writeable = no
 force user = see-admin
 
[sambashare]
    comment = Samba on Ubuntu
    path = /home/see-admin/sambashare
    read only = no
    browsable = yes
    force user = see-admin

Then restart smbd:

sudo service smbd restart

I FINALLY managed to solve this problem.

first of all i removed the existing connections from windows 10 using net use * /delete from the command line since the credentials where saved and i changed them on the server

also for some reason i had to specify smbpasswd in /etc/samba/smb.conf: passdb backend = smbpasswd in the [global] section

also the /home permission where wrong and all my shares are in /home so i reset the permission to 755: chmod -R 755 /home

then i reset all the shares permission and group access based on my needs.

"The hosts allow or allow hosts parameter is one of the key advantages of Samba. It allows access control of shares on the ip-address level. To allow only specific hosts to access a share, list the hosts, separated by comma's. Allowing entire subnets is done by ending the range with a dot."

Samba doesn't allow access control with this option on layer 2, only layer 3.

If you want to white list mac addresses you'll have to find another option to prevent network traffic from reaching the service.

Or if you reallllllly want to take some time doing this, you might see if its possible to modify the code and recompile.

I also would check if samba still has the big security vulnerability advertised years ago.

The additional tagging or qualifying that was added last time will be left out, but while showering it occurred to me that I forgot some things.

I apologize for this.

Before the rest is touched on lets analyze the response I gave and your setup:

1. If your network setup is not tightly controlling ip leasing and network membership, IP access control will not work.

2. If your samba server is not on the same network segment as the client machines, MAC white listing will not work.

3. If your not authenticating to the server as well, neither of these solutions will work.

4. MAC addresses can be spoofed. Its easier these days. If someone can see what the hardware IDs of your devices, by say sniffing the airways in the case of a wifi lan, once they get the key to connect to your network, or even in the case of a wired one where they can plug in somehow, this will not prevent anyone determined enough from getting into your server.

Now lets consider application.

If you're storing something vital, REALLLLLY heed what I'm saying. If you're just sharing movies or video files, not a big deal.

If you're storing executables and people will be running them, restrict write access or you're gonna have some trouble potentially and make sure these executables come from trusted sources and are not altered.

In general, SMB cannot be hardened if the network setup sucks. If I can just plug my computer into the wall and set a static ip address, or mod my MAC address and the dhcpd assigns a specific IP address, instant access.

Also if the password hashing isn't good, or a challenge isn't being sent and the password is even being even being sent in two-way encrypted form across the network, it is potentially possible to access the server.

Also. Don't trust ANY operating system you have not at the very least built yourself and then do not trust it completely. Don't trust any operating system who's code has not been hardened by people you trust or yourself, and then never completely trust an OS that people you trust have modded, because they may not be trustworthy.

But like I said, consider application and making sure people have to authenticate somehow to some network service to be granted access, and you're probably fine.

About the only way to protect data is to keep it in an isolated physically read only form and keep it in your possession or locked up these days. These are the times we live in where bad people did bad things, and tried to do even worse bad things and create our current mess and now everyone is suffering for their idiocy and the original offenders are laughing in hades, in between their pitchfork enema.