search for: wanacri

On Sat, 19 Aug 2017 17:56:06 -0700 ToddAndMargo via samba <samba at lists.samba.org> wrote: > The cure was to add to smb.conf > > ; To operate with XP, add the following to the [global] section: > ; lanman auth = yes > ; ntlm auth = yes > lanman auth = yes > ntlm auth = yes > > Sorry, but you seem to have fixed the wrong thing ;-) Did you miss

On 08/20/2017 02:14 AM, ToddAndMargo via samba wrote: > On 08/20/2017 01:20 AM, Rowland Penny via samba wrote: >> On Sat, 19 Aug 2017 17:56:06 -0700 >> ToddAndMargo via samba <samba at lists.samba.org> wrote: >> >>> The cure was to add to smb.conf >>> >>> ; To operate with XP, add the following to the [global] section: >>> ; lanman

If this is a customer rather than your employer you may find that you need to just part ways, which I know isn't easy.   If you provide a customer with your professional advice, and they choose to ignore it, then I think you can't really help them. Is the customer using XP for all client machines or just select machines that may run some legacy app? Do you have at least one Win 7

As you may remember I went through a classic-upgrade a few months ago. I have a second domain to migrate and I am again/still scared to attack that ;-) As I prepare my test VM and try to remember all those details the customer has purchase 2 new Windows 10 PCs and I was asked to take them into production. Is there a way to join them to the existing NT4-based Samba-domain or not? I find various

On 03/06/2020 22:41, Fernando Gon?alves via samba wrote: > So that it doesn't end without a conclusion I will inform you what has been > accomplished. > As our time was short to complete the migration I decided to install the > same version of SAMBA that was already running on the old machine (3.6.6). > After the migration is complete, I will have more time to update the SAMBA

Am 2017-05-15 um 14:06 schrieb Rowland Penny via samba: > Windows doesn't support joining Windows 7 to an NT4-style domain, so > they definitely won't support windows 10. Well, I joined Win7 to NT4-domain back then ... (reg-hack, but anyway) > You may find a way around this lack of Microsoft support, you may also > find that a subsequent Windows update stops it working

Dear list, Help! I just upgrade a samba server. Server: Fedora 26 samba-4.6.8-0.fc26.x86_64 Workstations (5 of them): XP Pro SP3 The old server was set up as a Domain controller. I copied the smb.conf over to the new server. The XP workstations can see and mount everything. On the workstations, I removed myself from the old domain and rebooted, powered off the old server,

On 05/15/17 08:06, Rowland Penny via samba wrote: > On Mon, 15 May 2017 13:25:03 +0200 > "Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote: > >> As you may remember I went through a classic-upgrade a few months ago. >> >> I have a second domain to migrate and I am again/still scared to >> attack that ;-) >> >> As I

On 09/30/2017 12:58 AM, Rowland Penny via samba wrote: > On Fri, 29 Sep 2017 18:27:29 -0700 > ToddAndMargo via samba <samba at lists.samba.org> wrote: > >> Dear list, >> >> Help! >> >> I just upgrade a samba server. >> >> Server: >> Fedora 26 >> samba-4.6.8-0.fc26.x86_64 >> >> Workstations (5 of them):

Hello everyone. I'm back because I decided to follow your advice and deploy the system using a new version of SAMBA with encrypted passwords. I added the SAMBA server in the AD domain without any problems and I am already accessing the shares with AD users. However I have a new problem for which I need help. When I try to access SAMBA shares with local Linux users, it is necessary to include

On Mon, 15 May 2017 13:25:03 +0200 "Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote: > > As you may remember I went through a classic-upgrade a few months ago. > > I have a second domain to migrate and I am again/still scared to > attack that ;-) > > As I prepare my test VM and try to remember all those details the > customer has

On Mon, 15 May 2017 14:11:54 +0200 "Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote: > Am 2017-05-15 um 14:06 schrieb Rowland Penny via samba: > > > Windows doesn't support joining Windows 7 to an NT4-style domain, so > > they definitely won't support windows 10. > > Well, I joined Win7 to NT4-domain back then ... (reg-hack, but

On Fri, 29 Sep 2017 18:27:29 -0700 ToddAndMargo via samba <samba at lists.samba.org> wrote: > Dear list, > > Help! > > I just upgrade a samba server. > > Server: > Fedora 26 > samba-4.6.8-0.fc26.x86_64 > > Workstations (5 of them): > XP Pro SP3 > > The old server was set up as a Domain controller. I copied the > smb.conf over to

Hi Fernando, What kind of system are using your Samba's clients? If they are using Windows systems joined to AD, you can join your Samba server into AD too. Then your users will be able to use Kerberos (ie SSO) to authenticate against your Samba server. Your Samba system users could be local (in /etc/passwd) or coming from AD (using winbindd). If system users are in /etc/passwd, they would

On 09/30/2017 08:21 AM, Gaiseric Vandal via samba wrote: > If this is a customer rather than your employer you may find that you > need to just part ways, which I know isn't easy.   If you provide a > customer with your professional advice, and they choose to ignore it, > then I think you can't really help them. Hi Gaiseric, Easier said than done. We are still suffering

Hello Rowland. Thanks for answering. The linux server is already in the AD domain and resolving Ad users as normal. To map the linux server share using AD users I use the following command: net use \\linuxserver\share /U:AD_user and it works perfectly. But I would like to use the same command for users who are in /etc/passwd, like this: net use \\linuxserver\share /U:linuxserver_user and so

On 09/30/2017 12:58 AM, Rowland Penny via samba wrote: > I understand that you have to use XP, but you don't have to use NTLM, > haven't you heard of 'wanacry' ? > Go here and read it:http://www.imss.caltech.edu/node/396 WannaCry did not infect XP or for that matter, Windows Nein, oops, Ten. Doesn't mean it couldn't if altered to do so: Reference:

I apologize for forgetting to pass on all the information. In fact, this problem is occurring because of the migration from a VM with Oracle SunOS to another VM with Oracle Linux 7. This old VM is for production and runs the CACH? database, so we decided to create a new VM and migrate everything to it. We have already migrated the database and users without problems. Only on each machine of these

Hi All, Fedora Core 26 # rpm -qa \*samba\* samba-common-4.6.7-0.fc26.noarch samba-common-libs-4.6.7-0.fc26.x86_64 samba-4.6.7-0.fc26.x86_64 samba-client-libs-4.6.7-0.fc26.x86_64 samba-winbind-modules-4.6.7-0.fc26.x86_64 samba-libs-4.6.7-0.fc26.x86_64 samba-client-4.6.7-0.fc26.x86_64 samba-common-tools-4.6.7-0.fc26.x86_64 samba-winbind-4.6.7-0.fc26.x86_64 I am replacing a CentOS 5 Samba Server