samba - Jul 2019 - Samba4 - global catalog (GC) cannot be contacted using Windows 7 RSAT

Hi Rowland,

In fact currently in my test environment using the same version of OS 6.10
and Samba 4.8.5.
I ran 'netstat -plaunt | egrep "ntp|bind|named|samba|?mbd"', I
have
:::3268, :::3269, I do not see 0.0.0.0:3268 and 0.0.0.03269.
While I use a Windows PC join to my test domain, I have no issues with GC.

Not sure how the GC problem can happen but seems to me it looks like a
sometimes thing.
Would the chances of getting be lower if were to use a higher version of OS
and Samba? =)

Now that I have quite a number of Windows PC under this AD, hope you can
correct me if I were to use the below steps:
I referred from Samba wiki
Example to remove DC1 from AD
1) Transfer FSMO to DC2
2) Demote DC1
3) stop DC1 samba service
4) Disconnect DC1 IP
5) Configure new_DC1 IP
6) Join new_DC1 to AD
7) Transfer FSMO from DC2 to the new_DC1

I am considering to use CentOS 7.6.1810 with Samba 4.10.6 for my new_DC1.
Prefer to use back the same hostname and IP address.
Thanks for your advice.

Thanks and Regards

On Mon, Jul 22, 2019 at 3:05 PM Rowland penny via samba <
samba at lists.samba.org> wrote:
> On 22/07/2019 01:21, Alfonso Conner wrote:
> > Hi Rowland,
> >
> > Currently using Samba 4.8.5
> > 2 x DCs running on CentOS 6.10 (Final)
> > Configured 1 DC via classic upgrade, and the latter DC join AD forest.
> > Would it be alright if I were to redo the classic upgrade?
>
> You can if you want to, but I feel that your problem may have nothing to
> do with Samba.
>
> Your first problem is your choice of OS, Centos 6 is as good as EOL, it
> is in maintenance mode and as such, the various packages may just be too
> old.
>
> you ran 'netstat -plaunt | egrep
"ntp|bind|named|samba|?mbd"'
>
> Amongst your output was this:
>
> tcp        0      0 :::3268                     :::* LISTEN 2578/samba
> tcp        0      0 :::3269                     :::* LISTEN 2578/samba
>
> Now I am no network expert, but doesn't ':::' mean IPv6 ?
>
> When I run the same command, I get:
>
> tcp        0      0 0.0.0.0:3268  0.0.0.0:* LISTEN 14227/samba: task[l
> tcp6       0      0 :::3268       :::*      LISTEN 14227/samba: task[l
>
> tcp        0      0 0.0.0.0:3269  0.0.0.0:* LISTEN 14227/samba: task[l
> tcp6       0      0 :::3269       :::*      LISTEN 14227/samba: task[l
>
> As you can 'tcp6' uses ':::3268'
>
> Rowland
>
>
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
>

On 22/07/2019 09:23, Alfonso Conner wrote:
> Hi Rowland,
>
> In fact currently in my test environment using the same version of OS 
> 6.10 and Samba 4.8.5.
> I ran 'netstat -plaunt | egrep
"ntp|bind|named|samba|?mbd"', I have
> :::3268, :::3269, I do not see 0.0.0.0:3268 <http://0.0.0.0:3268> and
> 0.0.0.03269.
> While I use a Windows PC join to my test domain, I have no issues with GC.
>
> Not sure how the GC problem can happen but seems to me it looks like a 
> sometimes thing.
> Would the chances of getting be lower if were to use a higher version 
> of OS and Samba? =)
Possibly, but I do not use Centos, so I do not really know
:-(
>
> Now that I have quite a number of Windows PC under this AD, hope you 
> can correct me if I were to use the below steps:
> I referred from Samba wiki
> Example to remove DC1 from AD
> 1) Transfer FSMO to DC2
> 2) Demote DC1
> 3) stop DC1 samba service
> 4) Disconnect DC1 IP
> 5) Configure new_DC1 IP
> 6) Join new_DC1 to AD
> 7) Transfer FSMO from DC2 to the new_DC1
>
> I am considering to use CentOS 7.6.1810 with Samba 4.10.6 for my 
> new_DC1. Prefer to use back the same hostname and IP address.
you might prefer to use the same name & IP, but experience has shown 
this isn't a good idea, apart from that, the above is a reasonable way 
to upgrade.

Rowland

Hi Rowland,

Noted with thanks.

Regards

On Mon, Jul 22, 2019 at 4:31 PM Rowland penny via samba <
samba at lists.samba.org> wrote:
> On 22/07/2019 09:23, Alfonso Conner wrote:
> > Hi Rowland,
> >
> > In fact currently in my test environment using the same version of OS
> > 6.10 and Samba 4.8.5.
> > I ran 'netstat -plaunt | egrep
"ntp|bind|named|samba|?mbd"', I have
> > :::3268, :::3269, I do not see 0.0.0.0:3268
<http://0.0.0.0:3268> and
> > 0.0.0.03269.
> > While I use a Windows PC join to my test domain, I have no issues with
> GC.
> >
> > Not sure how the GC problem can happen but seems to me it looks like a
> > sometimes thing.
> > Would the chances of getting be lower if were to use a higher version
> > of OS and Samba? =)
> Possibly, but I do not use Centos, so I do not really know :-(
> >
> > Now that I have quite a number of Windows PC under this AD, hope you
> > can correct me if I were to use the below steps:
> > I referred from Samba wiki
> > Example to remove DC1 from AD
> > 1) Transfer FSMO to DC2
> > 2) Demote DC1
> > 3) stop DC1 samba service
> > 4) Disconnect DC1 IP
> > 5) Configure new_DC1 IP
> > 6) Join new_DC1 to AD
> > 7) Transfer FSMO from DC2 to the new_DC1
> >
> > I am considering to use CentOS 7.6.1810 with Samba 4.10.6 for my
> > new_DC1. Prefer to use back the same hostname and IP address.
>
> you might prefer to use the same name & IP, but experience has shown
> this isn't a good idea, apart from that, the above is a reasonable way
> to upgrade.
>
> Rowland
>
>
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
>