[Samba] SAMBA replies SAM LOGON request from different ip alias

Walter Mautner walter.mautner at reflex.at
Wed Oct 6 14:28:36 MDT 2010


On Wednesday 06 October 2010 17:27:00 Christian Brandes wrote:
> Hi all,
.....
> 1) Either it picks a SERVER2-4 with ip aliases on its interfaces. Then the
> SERVER responds with a different ip number than the client sent its
> request to. So the client does not recognize the SAM Response "user
> unknown" and does not pop up the requester for a valid domain admin
> username and password. After a while it displays an error message instead.
> And the join procedure cannot go on.
> 
> 2) Or it picks SERVER1 whithout ip aliases on its interfaces. The SERVER
> responds with the only ip number on its interface in the client's network.
> So the client does recognize the SAM Response "user unknown" and pops up
> the domain admin logon requester and the join procedure can continue.
> 
> ?????
> So, why does SAMBA not reply on the same ip number ist was queried?
> How can I get SAMBA to reply on the same ip number ist was queried?
> 
> 
> Versions:
> 
> Samba:		3.4.7
> Samba4wins:	1.0.8-2
> Linux:		Ubuntu 10.04.1 LTS
> Kernel: 	Linux tux1 2.6.32-24-server #42-Ubuntu SMP Fri Aug 20 15:38:55 UTC
> 2010 x86_64 GNU/Linux
> 
> 192.168.16.0 is one single network with netmask 255.255.254.0 !
> 
> Related interfaces (and aliases):
> 
> XP-CLIENT:	192.168.17.25
> WINS-SERVER:	192.168.16.28
> DNS-SERVER:	192.168.16.6
> SERVER1 (BDC):	192.168.16.31
> SERVER2 (BDC):	192.168.16.32	(primary)
> 		192.168.16.38	(ip alias)
> 		(and other aliases)
> SERVER3 (PDC):	192.168.16.33
> 		(and other aliases)
> 
There is no alias 192.168.16.38 listed
> 
> SERVER2 picked: (fails)
> 
> No.     Time        Source                Destination           Protocol
> Info 1 2.076876    192.168.17.25         192.168.16.28         NBNS    
> Name query NB MYDOMAIN<1c> 2 2.078163    192.168.16.28        
> 192.168.17.25         NBNS     Name query response NB 192.168.16.32 3
> 2.088111    192.168.17.25         192.168.16.32         SMB_NETLOGON SAM
> LOGON request from client 4 2.088776    192.168.16.38        
> 192.168.17.25         SMB_NETLOGON SAM Response - user unknown 5 9.530892 
>   192.168.17.25         192.168.16.32         SMB_NETLOGON SAM LOGON
> request from client 6 9.531494    192.168.16.38         192.168.17.25     
>    SMB_NETLOGON SAM Response - user unknown
> 
Then why does the server use 192.168.16.38 as source ip?


More information about the samba mailing list