search for: share_directory

Hi all, This is one of ur Samba Fans , although I have not mailed to talk bout Pizzas , I have something pressing me,please read on : I have two Domains - TIDOMAIN which is the Network server (NT) which also is the Mail server , the Clients in the network make TIDOMAIN as their Primary wins server ,OK, I have installed Samba in the Solaris Box and have made it Point to this domain

Hi, I run samba very happily, but now I recognized problems with restoring files from a tape. If I use certain german characters, like ??? (hope you can read them), it builds file this "Verkn\201pfung". I can use this files from the sambaclient, but I can't access or delete this files out of Linux. I used client codepage = 850 Now I found out, that if I use the options

....conf cd /opt/samba3011/bin ./net join -U administrator (put the password in) and.... Poof, I'm back in the domain. All's well. I check with my PC client and I naturally see all my shares. Cool. But now I cannot write to any of the shared folders, again, unless I do a chmod 777 /share_directory in Solaris. I've checked for errors in all samba log files - NON. I've even used Steve Christianen's pre-compiled (version 3.0.10) version to check my compilation. His does the same thing. NOTE: When I revert back to my old Samba 3.0.2a and rejoin the domain, all's well agai...

I have this warning when I mount MS Windows shares, tunneling SMB over SSH in order to create a VPN-like shares management. Here the steps: # ssh -2 -N -L 445:shares_server:445 user@shares_server And after creating the port forwarding: # smbmount //share_server_netbios_name/share_directory /mnt/Samba -o username=user%pass,ip=127.0.0.1 On the shares_server runs a MS Windows XP Professional, with Cygwin installed for sshd emulating. I disable NetBios over TCP/IP because of well-known security flaws. Although the warning, the mounted resources are OK. I used also Ethereal for analyzing...

...is will be /home/DOMAIN/username, you may wish to change this. >? ? I also don't see any of the share sections of the old smb.conf file in the new. You will have to manually copy them from the old smb.conf to your new one, but they must be in this format: [sharename] ??? path = /path/to/share_directory ??? read only = no Do not add anything like valid users, force user, etc , you MUST set the permissions from Windows, see here: https://wiki.samba.org/index.php/Setting_up_a_Share_Using_Windows_ACLs and for profiles (if you use them): https://wiki.samba.org/index.php/Roaming_Windows_User_Pro...

...is will be /home/DOMAIN/username, you may wish to change this. > ? I also don't see any of the share sections of the old smb.conf file in the new. You will have to manually copy them from the old smb.conf to your new one, but they must be in this format: [sharename] ??? path = /path/to/share_directory ??? read only = no Do not add anything like valid users, force user, etc , you MUST set the permissions from Windows, see here: https://wiki.samba.org/index.php/Setting_up_a_Share_Using_Windows_ACLs and for profiles (if you use them): https://wiki.samba.org/index.php/Roaming_Windows_User_Pro...

...is will be /home/DOMAIN/username, you may wish to change this. >? ? I also don't see any of the share sections of the old smb.conf file in the new. You will have to manually copy them from the old smb.conf to your new one, but they must be in this format: [sharename] ??? path = /path/to/share_directory ??? read only = no Do not add anything like valid users, force user, etc , you MUST set the permissions from Windows, see here: https://wiki.samba.org/index.php/Setting_up_a_Share_Using_Windows_ACLs and for profiles (if you use them): https://wiki.samba.org/index.php/Roaming_Windows_User_Pro...

On Friday, July 17, 2020, 03:35:19 p.m. EDT, Rowland penny via samba <samba at lists.samba.org> wrote: On 17/07/2020 20:12, Carl Hunter via samba wrote: >? On Friday, July 17, 2020, 02:26:53 p.m. EDT, Rowland penny via samba <samba at lists.samba.org> wrote: >? >? >? On 17/07/2020 19:17, Carl Hunter via samba wrote: >>? ? On Friday, July 17, 2020, 12:43:33 p.m.