search for: samba_nt4_pdc_port_usage

...445 and 139, RPC should be on 135 if I got it right, but I have other Samba4 DC setup without port 135 open, and they work fine. This one as well has other Win10 PCs logging in correctly (tough they were W7 before, the failing one is brand new). Try reading this: https://wiki.samba.org/index.php/Samba_NT4_PDC_Port_Usage > > We tried enabling SMBv1, changing computer name, removing and adding it back to the domain, none of these actions produced a change. We also tried the three common actions suggested for this kind of error (changing dns, remove credentials caching, remove protected user (tough having no o...

...a kerberos and LDAP server independent of any samba services so port 88, 389 and 636 are not samba related. This is a "classic" samba domain. (nmap only scanned for TCP ports not UDP) According to the following link TCP port 135 should also be open. https://wiki.samba.org/index.php/Samba_NT4_PDC_Port_Usage I don't remember if TCP port 135 was open when I used samba 3.x domain controllers. The testparm command shows "allow dcerpc auth level connect = No" (which was not a parameter available with samba 3.x) Thanks On 11/17/16 16:38, Gaiseric Vandal wrote: > I updated...

...ndependent of any > samba services so port 88, 389 and 636 are not samba related. This > is a "classic" samba domain. (nmap only scanned for TCP ports not UDP) > > According to the following link TCP port 135 should also be open. > > https://wiki.samba.org/index.php/Samba_NT4_PDC_Port_Usage > > > > I don't remember if TCP port 135 was open when I used samba 3.x domain > controllers. The testparm command shows "allow dcerpc auth level > connect = No" (which was not a parameter available with samba 3.x) > > Thanks > > > > > &gt...

I have a samba classic domain, called it "DomainA." All domain controllers and servers are running 3.6.25 on Solaris 11. The PDC and BDC use an LDAP backend for unix, samba and idmap data. Member servers use LDAP backend for unix accounts, so the underlying unix and group accounts are consistent. There is a trust relationship with Windows 2008 AD domain

We've a Samba 4 domain (no AD, just DC) with LDAP backend on Ubuntu 14.04. This server has been migrated from files backend to LDAP by the previous maintainer, I know the version is pretty old but we cannot update at the moment. The domain works fine with some W7 and W10 (updated from 7) computers, but we have purchased a new Lenovo laptop with Win10 which joined the domain seamlessly but