search for: blueyestest

...in a reply to > this thread, do not attached it, the mailing list strips off attachments. > > The script output will help in identifying just what you have and any > possible basic errors. I put the trace of the script : Collected config? --- 2019-10-16-10:23 ----------- Hostname: blueyestest DNS Domain: sambadom.calais.fr FQDN: blueyestest.sambadom.calais.fr ipaddress: 192.168.xx.230 ----------- Kerberos SRV _kerberos._tcp.sambadom.calais.fr record verified ok, sample output: Server:??? ??? 192.168.xx.230 Address:??? 192.168.xx.230#53 _kerberos._tcp.sambadom.calais.fr??? service =...

...put the trace of the script : > OK, only two problems, one minor, one possibly catastrophic ;-) >> >> Collected config?? --- 2019-10-16-10:23 ----------- >> >> ???????????? Checking file: /etc/hosts >> >> 127.0.0.1?????? localhost >> 192.168.xx.230?????? blueyestest.sambadom.calais.fr >> sambadom.calais.fr blueyestest > > You should only have the domain once i.e. > > 192.168.xx.230 blueyestest.sambadom.calais.fr blueyetest > ok - >> >> # The following lines are desirable for IPv6 capable hosts >> ::1???????? localhost i...

...</cifsmount> <umount>/bin/umount %(MNTPT) </umount> <volume options="username=%(DOMAIN_USER),workgroup=%(DOMAIN_NAME),uid=%(DOMAIN_USER),fmask=700,file_mode=0700,dir_mode=0700" mountpoint="/etudiants/%(USER)" path="%(DOMAIN_USER)" server="blueyestest" fstype="cifs" /> </pam_mount> The home of my user? mount correctly. I have juste problem via les acl . on the server my user have this rights root at blueyestest:/home/SAMBADOM/specifique/testjeudi# ls -l total 12 -rwxrwxr--+ 1 SAMBADOM/testjeudi SAMBADOM/specifique???...

...ng has more problems then unstable.. So would start with running : apt-get dist-upgrade Then you configs, these dont look bad, but you need to make some adjustments. /etc/hosts 127.0.0.1??? localhost 192.168.xx.233??? clientblues2.sambadom.calais.fr clientblues2 Remove > 192.168.xx.230??? blueyestest.sambadom.calais.fr??? blueyestest Not needed. In /etc/resolv.conf Remove the ip's to the internet( or disable them for now), the AD-DC dns should forward it. And your primary search domain is not set. Add : search your.domain.tld Now, your using networkManager, in its config, add: dns-se...

...sitename_fetch: Returning sitename for realm 'SAMBADOM.CALAIS.FR': "Default-First-Site-Name" ads_dns_lookup_srv: 1 records returned in the answer section. sitename_fetch: Returning sitename for realm 'SAMBADOM.CALAIS.FR': "Default-First-Site-Name" no entry for blueyestest.sambadom.calais.fr#20 found. resolve_hosts: Attempting host lookup for name blueyestest.sambadom.calais.fr<0x20> namecache_store: storing 1 address for blueyestest.sambadom.calais.fr#20: 192.168.xx.xxx Connecting to 192.168.xx.xxx at port 445 Socket options: ??? SO_KEEPALIVE = 0 ??? SO_RE...

Hello, I need help you to understand my error. I have juste generate samba ad with the following command samba-tool domain provision --use-rfc2307 --interactive Realm:? SAMBADOM.CALAIS.FR Domain [SAMBADOM]: Server Role (dc, member, standalone) [dc]:? dc DNS backend (SAMBA_INTERNAL, BIND9_FLATFILE, BIND9_DLZ, NONE) [SAMBA_INTERNAL]:? SAMBA_INTERNAL DNS forwarder IP address (write 'none'

...: sambadom.calais.fr FQDN: clientblues2.sambadom.calais.fr ipaddress: 192.168.xx.233 ----------- Kerberos SRV _kerberos._tcp.sambadom.calais.fr record verified ok, sample output: Server:??? ??? 192.168.xx.230 Address:??? 192.168.xx.230#53 _kerberos._tcp.sambadom.calais.fr??? service = 0 100 88 blueyestest.sambadom.calais.fr. Samba is running as an Unix domain member but 'winbindd' is NOT running. Check that the winbind package is installed. Detected, Samba is running winbind only. Auth-only server, Unix domain member ?????? Checking file: /etc/os-release PRETTY_NAME="Debian GNU/Linux...

...: ldb_wrap open of secrets.ldb /usr/sbin/smbd: Starting GENSEC mechanism spnego /usr/sbin/smbd: Starting GENSEC submechanism gssapi_krb5 Does it test different authentication methods ? My smb.conf server is? : # Global parameters [global] ??? dns forwarder = 193.49.xxx.xxx ??? netbios name = BLUEYESTEST ??? realm = SAMBADOM.CALAIS.FR ??? server role = active directory domain controller ??? workgroup =SAMBADOM ??? idmap_ldb:use rfc2307 = yes ??? log level =5 ??? log file =/var/log/samba3/log.%M ??? max log size = 1000 ??? host msdfs = no #??? vfs objects = acl_xattr #??? map acl inherit =ye...

...rote: >> ???????????? Checking file: /etc/samba/smb.conf >> >> # Global parameters >> [global] >> ?????? dns forwarder = 192.168.xx.230 > You cannot forward to the DC itself, it needs to be a dns server > outside the AD dns domain. >> ?????? netbios name = BLUEYESTEST >> ?????? realm = SAMBADOM.CALAIS.FR >> ?????? server role = active directory domain controller >> ?????? workgroup = SAMBADOM >> ?????? idmap_ldb:use rfc2307 = yes >> ?????? log level = 3 >> ?????? log file = /var/log/samba/log.%M >> >> [sysvol] >...

...Checking file: /etc/samba/smb.conf >>> >>> # Global parameters >>> [global] >>> ?????? dns forwarder = 192.168.xx.230 >> You cannot forward to the DC itself, it needs to be a dns server >> outside the AD dns domain. >>> ?????? netbios name = BLUEYESTEST >>> ?????? realm = SAMBADOM.CALAIS.FR >>> ?????? server role = active directory domain controller >>> ?????? workgroup = SAMBADOM >>> ?????? idmap_ldb:use rfc2307 = yes >>> ?????? log level = 3 >>> ?????? log file = /var/log/samba/log.%M >&gt...

...with Samba, but 'The users must to connect on windows or on linux with the same home' may give a hint, are you using something like pam-mount ? > > My smb.conf server is? : > > # Global parameters > [global] > ??? dns forwarder = 193.49.xxx.xxx > ??? netbios name = BLUEYESTEST > ??? realm = SAMBADOM.CALAIS.FR > ??? server role = active directory domain controller > ??? workgroup =SAMBADOM > ??? idmap_ldb:use rfc2307 = yes > ??? log level =5 > ??? log file =/var/log/samba3/log.%M > ??? max log size = 1000 > ??? host msdfs = no > #??? vfs objects...