search for: ostling

/etc/resolv.conf (Both DC's (windows) listed) domain ho-pla.se search ho-pla.se nameserver 10.0.2.10 nameserver 10.0.2.64 /etc/krb5.conf [libdefaults] dns_lookup_realm = false dns_lookup_kdc = true default_realm = HO-PLA.SE On Tue, Aug 6, 2024 at 9:01?PM Luis Peromarta via samba <samba at lists.samba.org> wrote: > > What?s the content of krb conf file and resolv.conf?

On Tue, Jun 30, 2020 at 11:57 AM Rowland penny via samba <samba at lists.samba.org> wrote: > > On 30/06/2020 10:34, Anders ?stling wrote: > > On Tue, Jun 30, 2020 at 11:24 AM Rowland penny via samba > > <samba at lists.samba.org> wrote: > >> On 30/06/2020 09:50, Anders ?stling wrote: > >> > >>>> You have 'workgroup = HPLTS' and

Hi Rowland, and thank you for quick feedback On Wed, Jun 17, 2020 at 6:45 PM Rowland penny via samba < samba at lists.samba.org> wrote: > On 17/06/2020 17:27, Anders ?stling via samba wrote: > > So my question is; does Win 7 behave differently than Win 10? The shares > > are the same as for the Win 10 clients, including the home directories. > Yes, unless you have changed

Hi Thanks for the tip, but i have tried that too. No go. The only thing right now that works is to omit S from /COPY:DATSO, ie skip security descriptors. Makes no sense but that's what I have found out after dozens of tests. I will recreate the shares and be careful to follow Rowlands advise on setting the correct rights on the share. m?n 19 juni 2023 kl. 23:42 skrev spindles7 via samba

Well spoken. If I understand correctly, OP's organisation is a Russian STATE agency, so they can ask for support from Putin and his war criminal friends. Not here. Not now and not ever. On Mon, Dec 4, 2023 at 9:46?AM Rowland Penny via samba < samba at lists.samba.org> wrote: > On Mon, 4 Dec 2023 06:12:23 +0000 > ??????? ?????? ????????? via samba <samba at lists.samba.org>

I have a customer with a couple of industrial robots running Linux 2.6.34 and Samba 3.4.7 (smbclient -V). They are able to connect to SMB shares on Windows servers IF I "allow unsafe connections?, ie lower the SMB minimum level. The servers are on Windows 2019, and this setup has worked for a couple of years now. I have created a virtual Debian/Samba 4.19 server with the intention of moving

Hi Some may remember that I asked about configuring a Samba server for the legacy NT1 protocol due to a couple of old industrial systems that do not support SMB2/3. I noticed this today from the Samba server, probably doesnt mean anything but I still would like to ask the group. The server is of course joined to a domain and operates as it should. sysman at hp-srv03:~$ *net domain testjoin -U

Rowland, you nailed it. I had both libpam and libnss installed, but they were not automatically upgraded together witn winbind and samba. They were still on 4.17 from the staged upgrade, but now updated to 4.20. And the shares are working again! Amazing :) Thanks Anders On Tue, Aug 6, 2024 at 9:19?PM Rowland Penny via samba <samba at lists.samba.org> wrote: > > On Tue, 6 Aug 2024

Hi all I have setup a Samba server for a client, and most things work fine (except a strange problem with some clients and SMB1). However, when I created the virtual server before migrating it to the client, I obviously forgot to change a parameter. [global] netbios name = CLIENTNETBIOSNAME realm = CLIENTNETBIOSNAME.SE workgroup = CLIENTNETBIOSNAME idmap config * : backend = tdb idmap config * :

I wrote a message a couple of days ago asking about Samba and SMB protocol levels on an old industrial robot with a pre-2010 Samba. That was resolved successfully. I now have another question concerning the same systems (the robots and the new Samba server, HP-SRV03). root at hp-srv03:/ *smbclient -L localhost -U administrator* Enter HPLTS\administrator's password: Sharename Type

I have a client with 10+ Windows 10/32-bit clients and 3 Windows 7/32-bit. I converted them today to Samba 4.12, and after some fixes, I now have working shares and roaming profiles for the Win 10 clients. However, the Win7 clients dont get the shares mapped at logon properly (at all). I tried to run the netlogon script manually from Windows/Sysvol/sysvol/<domain>/scripts after mounting the

Actually, I made it work by adding the ?min server protocol = NT1? on the virtual dedicated server. So I guess that this will solve our dilemma (unless I missed something). In any case, one of the robots now have access to the new server. Will try the second one as soon as I get a chance (they are busy bending steel ;:) ) Anders > On 11 Apr 2024, at 14:55, Rowland Penny via samba <samba

Hello I have an older Debian 11 with Samba 4.13 as domain member serving som industrial systems with files. Today I decided to upgrade both Debian (to 12) and Samba (to 4.17 and then 4.20). The upgrade using the backport repo worked after some extra steps. Som dependencies had to be installed separately (winbind and samba-common-bin) before the main samba package was installed. So far so good. The

Hi My lab setup: A windows server 2019, configured as PDC called X A windows 10 pro workstation, domain member called Y An Ubuntu 18 server w Samba 4.7, configured as a member server called Z All are KVM virtual machines on a single host. IP and DNS works fine between all. Sharing setup on Samba Personal home shares in /User, configured in the AD profiles as home directories

Hi I'd like to learn more on the pros and cons of a mixed domain that consists of both MS and Samba domain controllers and member servers. What I have learnt so far is this; I created a new lab domain with an MS DC 2019. I then added a Samba 4.19-3 file server as a domain member w/o any issues. The clients are 2 Win 10 VM's for tests of shares, GPO's and related technologies. Still

I am not convinced that it's a Samba issue, but someone might be able to answer anyway We replicate directories and files from a Windows 2019 server to two destinations, both are supposed to be used in case of a disaster, but are also used for some specific tasks. One of the replication targets is a physical Windows 2012 server and the other one an Ubuntu/Samba virtual machine. The Samba VM

On Tue, Jun 30, 2020 at 11:24 AM Rowland penny via samba <samba at lists.samba.org> wrote: > > On 30/06/2020 09:50, Anders ?stling wrote: > > >> You have 'workgroup = HPLTS' and 'idmap config dg11', again, they must match > > As I wrote in the previous reply, that was a mistake from the initial > > deployment. However, I have a copy of the VM and

Hi Samba 4.12 on Ubuntu 20.04 Windows 10 and 7 clients I have configured recycle on two shares, /Users and /Documents. vfs objects = recycle recycle:versions = yes recycle:keeptree = yes On the Users share I have recycle:repository = /share/data On the Documents share I have recycle:repository = .Papperskorg (recycle bin in Swedish) The Document share recycle works. Folder was created and the

I have a problem that I am unable to sort out. Maybe someone can assist with advice and troubleshooting. Client computer is Windows 10 Pro with latest updates as of today. Servers are a Windows 2019 Standard (logon and AD server) and a Samba 4.11 running on Ubuntu (domain member. AD account configured with account profile \\hp-fssrv\profiles\<username>. Home directory is mapped to