Re: [Samba] new IP on an iface and nmb's behaviour
- Date: Mon, 13 Mar 2017 11:55:56 +0100
- From: mathias dufresne via samba <samba@xxxxxxxxxxxxxxx>
- Subject: Re: [Samba] new IP on an iface and nmb's behaviour
Here we must also use corporate DNS servers. To avoid the need of starting
nmbd we asked to main DNS team to add a forward zone on their servers
(Bind) and when a DNS request arrive on non-AD-main-DNS-servers they know
where to forward these requests (on some of our DC which are declared as
forwarders for that zone).
As our AD domain is part of existing domain already managed by these
non-AD-DNS-servers they had to delegate that zone to AD servers.
This delegation is totally internal to non-AD-DNS-servers, our AD DNS
servers are not aware of that delegation.
And now to speak about your question: did you restarted nmbd after adding
the new IP? I expect yes, but in case of...
2017-03-07 17:37 GMT+01:00 lejeczek via samba <samba@xxxxxxxxxxxxxxx>:
> hi everyone,
> I observe a peculiar "behaviour" behaviour of nmb, peculiar to me at
> least, could be that "this is how it works", thus asking.
> If I add an IP on the iface that nmb is already operating then I see such
> a message:
> Samba name server GOER is now a local master browser for workgroup
> PRIV_NET on subnet 192.168.2.204
> 204 is that new IP, but then windows boxes do not seem to get logon.bat
> nor the server is accessible via \\GOER
> Unfortunately domain runs in environment where DNS is managed by third
> parties thus need for nmb.
> Can you tell if this is normal?
> And how can it be fixed so nmb would still be accessible, either it does
> not care about this new IP or it does care but clients can get to it?
> many thanks,
> To unsubscribe from this list go to the following URL and read the
> instructions: https://lists.samba.org/mailman/options/samba
To unsubscribe from this list go to the following URL and read the