I just saw that 1.7.4 was out, I upgraded, same timeout delay issue.
John W. Sopko Jr. wrote, On 12/20/2011 8:02 AM:
I have been out of town, thus the reply delay. I had openafs 1.5.x installed,
my lmhosts file looks like this:
10.254.254.253 AFS #PRE
Note I had removed the loopback interface in Device Manger after I did
the upgrade to 1.7.3 . Also I have 2 additional 10.x.x.x IP aliases on the
interface that I use to manage various devices. I get no timeout in other
network shares.
When we get a chance we will try another machine with a single IP address.
Jeffrey Altman wrote, On 12/16/2011 10:57 AM:
If you install WireShark and watch the network traffic on the machine I
suspect that you will find that the delay is being caused by the Microsoft Lan
Manager (SMB) network provider. It issues an NBNS Name query for "AFS <20>"
and then a DNS query for "afs.<search-domain>". If it gets a response to
either it then attempts an ICMP ping to the resulting address and an NBNS
NBSTAT query. Only after the LanMan provider times out does it report failure
and it retries this sequence for every request.
Adding a fake "AFS" entry to the %windir%\system32\drivers\etc\LMHOSTS file
prevents the NBNS Name queries for "AFS <20>" from being sent. At the
present time, the OpenAFS installer only creates such an entry as part of
installing the Microsoft Loopback Adapter which is not installed by default
now that the afs redirector driver is available.
Jeffrey Altman
--
John W. Sopko Jr. University of North Carolina
email: sopko AT cs.unc.edu Computer Science Dept., CB 3175
Phone: 919-962-1844 Fred Brooks Building; Room 140
Fax: 919-962-1799 Chapel Hill, NC 27599-3175
_______________________________________________
OpenAFS-info mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-info
