FW: Winbindd timeout on unreacheable domains

Alexander Bokovoy a.bokovoy at sam-solutions.net
Thu Feb 19 15:28:05 GMT 2004


On Thu, Feb 19, 2004 at 04:21:01PM +0100, Simo Sorce wrote:
> On Thu, 2004-02-19 at 14:31, ww m-pubsyssamba wrote:
> > Hi Andrew/All,
> > 
> > 	ok I've done a snoop to see what's going on (zip password is "snoop"). Basically the timeout is caused by something repeatedly trying to contact an IP which cannot be resolved by ARP (44 failed ARP requests), you can see many failed arp lookups. I beleive the part which finally resolves the timeout is as follows,
> > 
> > 
> > 396   0.70071 bbcwwp-sun29 -> wwdc.testlan.bbc.co.uk NBT NS Query Request for CHILD1[1c], Success
> > 397   0.00146 169.254.48.167 -> bbcwwp-sun29 NBT NS Query Response for CHILD1[1c], Success
> > 
> > 192.254.48.167? is that a dummy address which Samba is generating after finally timing out? It's definately not a valid IP on my test network,
> 
> s/192/169/
> 
> No it is not something that samba do, it is the kind of address windows
> client set up by itslef when they are told to find a dynamic address but
> no dhcp is found.
Yes. This is ZeroConf address space (www.zeroconf.org).
-- 
/ Alexander Bokovoy
Samba Team                      http://www.samba.org/
ALT Linux Team                  http://www.altlinux.org/
Midgard Project Ry              http://www.midgard-project.org/


More information about the samba-technical mailing list