search for: pdcserv

Hi, some months before, I was serving files and profiles using a Samba 3 PDC server (I will name it PDCSERV), this is some abstracts fro smb.conf: PDCSERV:/etc/samba/smb.conf [general] logon path = \\%N\profile logon drive = U: logon home = \\%N\%U logon script = "logon.cmd" valid users = %S [homes] path = "/home/%U/userdisk"...

...nclature defined above since the server's pet names will mean nothing for you), and removed some data shares that works very well and are unrelated at all (by the way, I kept the unrelated "partage" share as an example, even if it's unrelated to my current problem). So, the "PDCSERV" config was the now-disabled All-In-One Samba3 PDC server. The "ADSERV" is the current AD DC Samba4 server, and the "FILESERV" is the current file sharing server (hosting homes and profiles). I have also some other file servers but they are totally unrelated to the current...

...now how to fix this issue?? My file server is a domain member of the PDC My PDC is on LDAP I use LDAP-auth on the file server this is my config on the file server [global] workgroup = DOMAINNAME server string = Samba Server security = server password server = PDCSERV log file = /var/log/samba/%m.log max log size = 50 socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 load printers = No dns proxy = No #ldap ssl = no passdb backend = ldapsam:ldap://PDCSERV ldap suffix = dc=company,dc=com...

...server's pet names will > mean nothing for you), and removed some data shares that works very > well and are unrelated at all (by the way, I kept the unrelated > "partage" share as an example, even if it's unrelated to my current > problem). > > So, the "PDCSERV" config was the now-disabled All-In-One Samba3 PDC > server. The "ADSERV" is the current AD DC Samba4 server, and the > "FILESERV" is the current file sharing server (hosting homes and > profiles). I have also some other file servers but they are totally > u...

On 27/06/16 21:03, Thomas DEBESSE wrote: > Hi, some months before, I was serving files and profiles using a Samba 3 > PDC server (I will name it PDCSERV), this is some abstracts fro smb.conf: > > PDCSERV:/etc/samba/smb.conf > > [general] > logon path = \\%N\profile > logon drive = U: > logon home = \\%N\%U > logon script = "logon.cmd" > valid users = %S > >...

...11) process_local_master_announce: Server XPmachine at IP 192.168.0.105 is announcing itself as a local master browser for workgroup BIODOM and we think we are master. Forcing election. [2006/01/19 11:01:06, 0] nmbd/nmbd_become_lmb.c:unbecome_local_master_success(149) ***** Samba name server PDCSERV has stopped being a local master browser for workgroup BIODOM on subnet 192.168.0.3 ***** [2006/01/19 11:01:20, 0] nmbd/nmbd_nameregister.c:register_name_response(130) register_name_response: server at IP 192.168.0.105 rejected our name registration of BIODOM<1d> IP 192.168.0.3 with erro...

...s pet names will mean >> nothing for you), and removed some data shares that works very well and are >> unrelated at all (by the way, I kept the unrelated "partage" share as an >> example, even if it's unrelated to my current problem). >> >> So, the "PDCSERV" config was the now-disabled All-In-One Samba3 PDC >> server. The "ADSERV" is the current AD DC Samba4 server, and the "FILESERV" >> is the current file sharing server (hosting homes and profiles). I have >> also some other file servers but they are totall...