Displaying 9 results from an estimated 9 matches for "protectionpolici".
Did you mean:
protectionpolicy
2015 Dec 10
1
Fix for Windows 8.1 RSAT error when creating users
I created a new Samba4 AD DC, and attempted to add users and groups from
a Windows 8.1 computer using the Remote Server Administration Tools.
While I was able to create groups just fine, attempting to create a user
failed with the message "An Error Occurred. Contact your System
Administrator."
A quick Google shows that others on this list have had this and similar
problems, but I
2016 May 20
2
Suddenly Windows clients can't join Samba+ldap PDC anymore
I was trying to fix a problem on Windows 10 with Outlook 2013. Also
running an NT4-style domain. The machine had already been joined to
the domain and outlook had been working but recently not (probably after
patch tuesday.) I also had had problems with Win 10 mail and RDP.
I came across the following link.
2016 May 20
2
Suddenly Windows clients can't join Samba+ldap PDC anymore
You should be able to unbind ipv6 for the win 10 machine's network
interface.
does "nslookup SRV1" work?
Also, you may want to try running tcpdump or ethereal or wireshark on
our PDC and see what traffic is captres.
On 05/20/16 13:24, Pau Peris wrote:
> I'm completely lost as i can ping SRV1 without issues but i'm starting
> to think that maybe Windows tries to
2016 May 20
2
Suddenly Windows clients can't join Samba+ldap PDC anymore
Excuse me for the little flood please, i've just checked it again and
now i see SRV1 as master for exedra.cat workgroup, i event can see in
the logs Samba name server SRV1 is now a local master browser for
workgroup EXEDRA.CAT on subnet 192.168.69.203
So i'll keep digging on how to fix the issue exposed on my first
email, tomorrow i'll try to see wether it's an IPV6 issue or
2016 May 20
0
Suddenly Windows clients can't join Samba+ldap PDC anymore
I'm completely lost as i can ping SRV1 without issues but i'm starting
to think that maybe Windows tries to join the domain through IPV6.
ping -c6 SRV1 from this Windows 10 machine leads to host not found so
i'm working on this direction right now.
Any help will be really appreciated
On Fri, May 20, 2016 at 5:04 PM, Gaiseric Vandal
<gaiseric.vandal at gmail.com> wrote:
> I
2016 May 20
0
Suddenly Windows clients can't join Samba+ldap PDC anymore
Right now i'm out of the office and i have no way to remotely work
with the Windows machines so i've been upgrading the server to Ubuntu
16.04. Everything seems to be working as before but i'm wondering why
right now the Master value is blank for Workgroup exedra.cat Any idea?
# smbclient -L localhost
WARNING: The "syslog" option is deprecated
Enter root's password:
2016 May 20
1
Suddenly Windows clients can't join Samba+ldap PDC anymore
Hi,
thanks a lot for your reply.
Yes, i enabled wins through "wins support = yes", i also enabled
lmhosts lookup and wins on all clients but will check it as you
proposed. Tomorrow will try to disable ipv6 on Windows clients
following this link https://support.microsoft.com/en-us/kb/929852
Which process did you follow to disable IPV6? I'm also wondering if
it's really necessary
2016 May 20
0
Suddenly Windows clients can't join Samba+ldap PDC anymore
Are you running a wins server (maybe you already mentioned this.) That
tends to help minimize some classic samba issues.
On my PDC
root at mypdc:~# testparm -v | more
Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (256) to minimum Windows limit
(16384)
Processing section "[netlogon]"
WARNING: The
2016 May 20
2
Suddenly Windows clients can't join Samba+ldap PDC anymore
Hi,
thanks a lot for the tips. I already did the first one, importing the
following into the registry:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanManWorkstation\Parameters]
"DomainCompatibilityMode"=dword:00000001
"DNSNameResolutionRequired"=dword:00000000
I didn't do the second tip but it looks like it's not