I am attempting to connect to a new Samba-4.3 based AD-DC from a
workstation that already belongs to an existing domain. The old
domain and the new are switched on the same physical lan segment but
have different IP network blocks assigned. Both route through the same
gateway albeit on different interfaces.
I cannot seem to find the new AD-DC from the RAST package installed on
the workstation. From the workstation I can ping the Samba DC without
problem and the Samba server resolves DNS without difficulty. I have
been checking the ports and discovered that the Samba installation is
not listening on port 138. From what I have read this seems to
indicate a problem somewhere. Is this case? What setting is required
to get Samba to listen on 138 or should it just be doing it? What
would prevent it from doing so?
Any help offered on this matter is gratefully accepted.
--
*** e-Mail is NOT a SECURE channel ***
Do NOT transmit sensitive data via e-Mail
Do NOT open attachments nor follow links sent by e-Mail
James B. Byrne mailto:ByrneJB at Harte-Lyne.ca
Harte & Lyne Limited http://www.harte-lyne.ca
9 Brockley Drive vox: +1 905 561 1241
Hamilton, Ontario fax: +1 905 561 0757
Canada L8E 3C3
On 04/07/16 20:52, James B. Byrne wrote:> I am attempting to connect to a new Samba-4.3 based AD-DC from a > workstation that already belongs to an existing domain. The old > domain and the new are switched on the same physical lan segment but > have different IP network blocks assigned. Both route through the same > gateway albeit on different interfaces. > > I cannot seem to find the new AD-DC from the RAST package installed on > the workstation. From the workstation I can ping the Samba DC without > problem and the Samba server resolves DNS without difficulty. I have > been checking the ports and discovered that the Samba installation is > not listening on port 138. From what I have read this seems to > indicate a problem somewhere. Is this case? What setting is required > to get Samba to listen on 138 or should it just be doing it? What > would prevent it from doing so? > > Any help offered on this matter is gratefully accepted. >Ah, the old 'why is nmbd not listening on a DC question' :-) This is because the 'nbt' portion of the 'samba' binary doesn't have the code to do this and you cannot run the separate 'nmbd' binary on a DC. Rowland