[Samba] WINS server 127.0.0.1 timed out registering IP

[sisu .]

Hi Daniel,
Thank you for your answer. I tried your suggestion and it works. The point is that one of reasons that I want the BDC is to have 100% redundadcy with the domain, with this I mean that If the PDC'd fall down, then I would have the BDC 100% up. Thus if the BDC is sharing some services with the PDC I will not get it. I don't know if is possible to have a samba wins in the BDC as I have in the PDC. Do you know it?


> -----------------------------------------------
> 
> -----Ursprüngliche Nachricht-----
> Von: samba-bounces at lists.samba.org [mailto:samba-bounces at lists.samba.org] Im
> Auftrag von sisu .
> Gesendet: Freitag, 18. Februar 2011 13:47
> An: Samba
> Betreff: [Samba] WINS server 127.0.0.1 timed out registering IP
> 
> 
> 
> 
> Hi all.
> 
> After set up a BDC, I found a weird problem on my log.nmbd file, the case is
> that my nmb (on BDC)  is not able to connect to the local wins "server",
> just receive a time out .
> 
> I set the wins support = yes which is the only mandatory parameter according
> to samba doc.
> 
> I tried to shut down the firewall even.
> 
> The log output is:
> 
>  === ....... ===
>   become_logon_server: Atempting to become logon server for workgroup FOG on
> subnet UNICAST_SUBNET
> [2011/02/18 13:11:04.631006,  0]
> nmbd/nmbd_logonnames.c:121(become_logon_server_success)
>   become_logon_server_success: Samba is now a logon server for workgroup FOG
> on subnet 192.168.5.37
> [2011/02/18 13:11:06.130886,  2]
> nmbd/nmbd_nameregister.c:192(wins_registration_timeout)
>   wins_registration_timeout: WINS server 127.0.0.1 timed out registering IP
> 192.168.5.37
> [2011/02/18 13:11:06.130976,  2]
> nmbd/nmbd_nameregister.c:192(wins_registration_timeout)
>   wins_registration_timeout: WINS server 127.0.0.1 timed out registering IP
> 192.168.5.37
> [2011/02/18 13:11:06.131008,  2]
> nmbd/nmbd_nameregister.c:192(wins_registration_timeout)
>   wins_registration_timeout: WINS server 127.0.0.1 timed out registering IP
> 192.168.5.37
> [2011/02/18 13:11:06.131038,  2]
> nmbd/nmbd_nameregister.c:192(wins_registration_timeout)
>   wins_registration_timeout: WINS server 127.0.0.1 timed out registering IP
> 192.168.5.37
> [2011/02/18 13:11:06.131067,  2]
> nmbd/nmbd_nameregister.c:192(wins_registration_timeout)
>   wins_registration_timeout: WINS server 127.0.0.1 timed out registering IP
> 192.168.5.37
> [2011/02/18 13:11:06.131096,  2]
> nmbd/nmbd_nameregister.c:192(wins_registration_timeout)
>   wins_registration_timeout: WINS server 127.0.0.1 timed out registering IP
> 192.168.5.37
> [2011/02/18 13:11:06.131125,  0]
> nmbd/nmbd_logonnames.c:121(become_logon_server_success)
>   become_logon_server_success: Samba is now a logon server for workgroup FOG
> on subnet UNICAST_SUBNET
> ===EOF ==
> 
> 
> For another side,  I have a quick question, not really important. The case
> is that I receive from some windows machines which are not into the domain,
> user login attempts. Obviously  these users don't reach to log on:
> 
> [2011/02/18 10:47:43.906677,  2] auth/auth.c:314(check_ntlm_password)
>   check_ntlm_password:  Authentication for user [Felix] -> [Felix] FAILED
> with error NT_STATUS_NO_SUCH_USER
> [2011/02/18 10:47:43.915067,  2] auth/auth.c:314(check_ntlm_password)
>   check_ntlm_password:  Authentication for user [Felix] -> [Felix] FAILED
> with error NT_STATUS_NO_SUCH_USE
> 
> But, does anybody know why these machines are sending these login attempts?
> 
> 
> Thank everybody in advance.
> 
> 
>  		 	   		  
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
>