search for: howto54187

I'm having issues having WinXP client access shares on my Samba domain. The user account can authenticate to the network using a Win10 client. The win10 client maps the users drives and allows access properly. The WinXP client can join the domain & the user can login on the machine in question. However, attempting to map a drive using "net use" results in an error about an

...>> > > Two > > One, you really shouldn't still be using XP I know, but it still serves its rather meager purpose. > Two, NTLMv1, try adding 'ntlm auth = yes' to smb.conf and if this fixes > it, read this: > > https://support.symantec.com/en_US/article.HOWTO54187.html > > Rowland > However... I have another XP client that connects no problem. The machine has moved from an NT Style domain to an Active Directory domain. Are there Samba related registry tweaks that need to be made or undone?

In the process of upgrading my whole samba setup. I've setup a server as an active directory controller, I created a stand alone member server, I've gotten win10 to join the domain and drive mapping via group policies seems to work with win 10 clients. I still have a few winXP clients that have usefullness. They seem to connect to the domain ok, but they can't see any of the

Hi, I'm not able to join a windows XP machine in samba AD DC. This XP machine is a VM. No problems when joining Windows 10 machines to this DC. On XP machine, after inserting the Administrator username\password to join the domain, the error message is - error while attempting to join the domain "VIDROESTE.IND": Internal error. I can see that the XP machine account was created in AD

...) > or the XP registry settings to make it work? This is probably where the problem lies, but this is just a guess. Your XP machines are probably expecting/sending NTLMv1 and your AD domain has this turned off, see here for how to make XP use NTLMv2: https://support.symantec.com/en_US/article.HOWTO54187.html Rowland

...ry settings to make it work? > >This is probably where the problem lies, but this is just a guess. Your >XP machines are probably expecting/sending NTLMv1 and your AD domain >has this turned off, see here for how to make XP use NTLMv2: > >https://support.symantec.com/en_US/article.HOWTO54187.html > >Rowland > > > >-- >To unsubscribe from this list go to the following URL and read the >instructions: https://lists.samba.org/mailman/options/samba

...th = /var/lib/samba/sysvol read only = No Check that you have your forwarders set in your named.conf files (they are in your smb.conf at the moment, where they will do nothing) Next turn your attention to the XP machine and make it use NTLMv2, see here: https://support.symantec.com/en_US/article.HOWTO54187.html Finally, I do not know what kerberos your SUSE packages are using, so you need to find out. If it is MIT, then I would suggest you stop using them, using MIT is experimental and shouldn't be used in production. Rowland

...th = /var/lib/samba/sysvol read only = No Check that you have your forwarders set in your named.conf files (they are in your smb.conf at the moment, where they will do nothing) Next turn your attention to the XP machine and make it use NTLMv2, see here: https://support.symantec.com/en_US/article.HOWTO54187.html Finally, I do not know what kerberos your SUSE packages are using, so you need to find out. If it is MIT, then I would suggest you stop using them, using MIT is experimental and shouldn't be used in production. Rowland -- To unsubscribe from this list go to the following URL and read th...