Displaying 8 results from an estimated 8 matches for "domain_controller_name".
2018 Jul 17
2
classic upgrade error
...rv
and restart samba
servicePrincipalName attributes are created...
>
> If you are still testing the upgrade procedure, it might be easier to
> run the upgrade again, but read this first:
>
> https://wiki.samba.org/index.php/Migrating_a_Samba_NT4_Domain_to_Samba_AD_(Classic_Upgrade)#Domain_Controller_name
i did not see any warning about this
is it supported?
>
> Once you have a DC provisioned, you can use samba-tool to add SPN's
root at noordo:/var/log/kwartz# samba-tool spn list irisserv
irisserv
ERROR: User irisserv not found
root at noordo:/var/log/kwartz# samba-tool spn list noordo
n...
2018 Jul 17
2
classic upgrade error
Hello
i have a problem after classicupgrade on ubuntu 14.04/samba 4.3.11
i know this version is not supported, sorry no way for the moment to do
ubuntu upgrade...
before migration
netbios name in smb.conf (irisserv) did not match dns hostname (noordo)
so AD was provisionned but with irisserv
and there are no servicePrincipalName in irisserv ldap entry...
is there a way to fix this?
Thank
2005 Jul 22
0
winbbind not quiried by nsswitch on solaris 8
...Could someone make suggestions as to whats wrong? Any clue-bats wuld be
most appreciated.
Below is my smb.conf:
[global]
netbios name = sun_fileserver
workgroup = my_workgroup
server string = "sun_fileserver"
security = domain
password server = domain_controller_name
log file = /var/adm/samba/%m.log
max log size = 5000
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
encrypt passwords = yes
# Wins settings
wins support = no
wins proxy = no
dns proxy = No
wins server = domain_controller...
2018 Jul 17
1
classic upgrade error
...alName attributes are created...
>>
>>> If you are still testing the upgrade procedure, it might be easier
>>> to run the upgrade again, but read this first:
>>>
>>> https://wiki.samba.org/index.php/Migrating_a_Samba_NT4_Domain_to_Samba_AD_(Classic_Upgrade)#Domain_Controller_name
>> i did not see any warning about this
>> is it supported?
> It wouldn't be on a Samba wikipage if it wasn't supported.
i know, i was not
can we have a AD DC server with a netbios name that differs from DNS
hostname especially for kerberos...
the wiki only says that we c...
2018 Jul 17
0
classic upgrade error
..., but it should do what you require, but, as always, test
it before using it in production.
If you are still testing the upgrade procedure, it might be easier to
run the upgrade again, but read this first:
https://wiki.samba.org/index.php/Migrating_a_Samba_NT4_Domain_to_Samba_AD_(Classic_Upgrade)#Domain_Controller_name
Once you have a DC provisioned, you can use samba-tool to add SPN's
Rowland
2018 Jul 17
0
classic upgrade error
...incipalName attributes are created...
>
> >
> > If you are still testing the upgrade procedure, it might be easier
> > to run the upgrade again, but read this first:
> >
> > https://wiki.samba.org/index.php/Migrating_a_Samba_NT4_Domain_to_Samba_AD_(Classic_Upgrade)#Domain_Controller_name
> i did not see any warning about this
> is it supported?
It wouldn't be on a Samba wikipage if it wasn't supported.
>
>
> >
> > Once you have a DC provisioned, you can use samba-tool to add SPN's
> root at noordo:/var/log/kwartz# samba-tool spn list iriss...
2004 Oct 05
1
samba server as NT4 domain member- security=domain - need to create password db manually?
# Global parameters
[global]
workgroup = MYDOMAIN
server string = Samba Server %v on %L
security = DOMAIN
log file = /var/log/samba/%m.log
max log size = 50
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
printcap name = /etc/printcap
local master = No
dns proxy = No
wins server = MYWINSERVER
idmap
2016 Sep 20
4
samba to ad transition
On Tue, 20 Sep 2016 08:33:23 -0700 (PDT)
kajkoz via samba <samba at lists.samba.org> wrote:
> I did it again, mean. I followed the instruction
> https://wiki.samba.org/index.php/Migrating_a_Samba_NT4_domain_to_a_Samba_AD_domain_%28classic_upgrade%29
> then I tried to log in from the client computer. ANd again. If that
> user already existed on client computer there was not a