[OpenAFS] 1.7.3 Windows 7 client explorer window delay
Jeffrey Altman
jaltman@your-file-system.com
Tue, 20 Dec 2011 11:55:58 -0500
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigE935677C6D7C56A64B1150D0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content=3D"text/html; charset=3DUTF-8" http-equiv=3D"Content-Ty=
pe">
<title></title>
</head>
<body bgcolor=3D"#ffffff" text=3D"#000000">
With a non-\\AFS network share, the server actually exists and
responds to the request.=C2=A0 Therefore there is no delay.=C2=A0 The=
core
issue here is a design difference between XP and Vista.=C2=A0 <br>
<br>
In XP, when a \\server\share search is performed, all of the network
providers installed on the machine are queried and the answer is
delivered when all of the network providers have responded.=C2=A0 If =
the
AFS network provider responds immediately and the SMB (LanMan)
network provider doesn't return for 30 seconds, the answer provided
by the AFS network provider is not delivered to the application
(e.g., explorer shell) for 30 seconds.=C2=A0 <br>
<br>
In Vista, when a \\server\share search is performed, all of the
network providers installed on the machine are queried but the first
response is the one that is used and the request of the outstanding
queries are ignored.<br>
<br>
If the 10.254.254.253 entry in LMHOSTS is not preventing the delays,
it means that the system believes that the net is accessible and the
LanMan network provider is timing out trying to receive a
response.=C2=A0=C2=A0 You can watch this using WireShark or Microsoft=
Network
Monitor both of which are free to download and install.<br>
<br>
There are no delays when accessing \\AFS UNC paths from the command
line because the afsredir.sys driver has already registered all
paths beginning with \\AFS with the Multiple UNC Provider (UNC)
interface in the kernel.=C2=A0 This is strictly an issue with the net=
work
provider interface and applications that use the WNet APIs to
browse.=C2=A0 This is not a problem on Vista, Server 2008 or Windows =
7.<br>
<br>
There are no changes in 1.7.4 to address this because at the moment
I'm not sure what can be done.<br>
<br>
Jeffrey Altman<br>
<br>
<br>
On 12/20/2011 8:02 AM, John W. Sopko Jr. wrote:
<blockquote cite=3D"mid:4EF08781.5080305@cs.unc.edu" type=3D"cite">I
have been out of town, thus the reply delay. I had openafs 1.5.x
installed, my lmhosts file looks like this:
<br>
<br>
10.254.254.253=C2=A0=C2=A0=C2=A0 AFS=C2=A0=C2=A0=C2=A0 #PRE
<br>
<br>
Note I had removed the loopback interface in Device Manger after I
did
<br>
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
<br>
network shares.
<br>
<br>
When we get a chance we will try another machine with a single IP
address.
<br>
<br>
<br>
<br>
Jeffrey Altman wrote, On 12/16/2011 10:57 AM:
<br>
<blockquote type=3D"cite">If you install WireShark and watch the
network traffic on the machine I
<br>
suspect that you will find that the delay is being caused by the
Microsoft Lan
<br>
Manager (SMB) network provider.=C2=A0 It issues an NBNS Name quer=
y
for "AFS <20>"
<br>
and then a DNS query for "afs.<search-domain>".=C2=A0 If it=
gets a response to
<br>
either it then attempts an ICMP ping to the resulting address
and an NBNS
<br>
NBSTAT query.=C2=A0 Only after the LanMan provider times out does=
it
report failure
<br>
and it retries this sequence for every request.
<br>
<br>
Adding a fake "AFS" entry to the
%windir%\system32\drivers\etc\LMHOSTS file
<br>
prevents the NBNS Name queries for "AFS <20>" from being
sent.=C2=A0=C2=A0 At the
<br>
present time, the OpenAFS installer only creates such an entry
as part of
<br>
installing the Microsoft Loopback Adapter which is not installed
by default
<br>
now that the afs redirector driver is available.
<br>
<br>
Jeffrey Altman
<br>
<br>
<br>
<br>
</blockquote>
<br>
</blockquote>
<br>
</body>
</html>
--------------enigE935677C6D7C56A64B1150D0
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
iQEcBAEBAgAGBQJO8L4gAAoJENxm1CNJffh402kIALRILK+tRWqOmyRxDHZh19pf
t0n48t5H5PJHFJbciD2If33hrayo23Sy91JXpn4HxJI/MIaX10AYu6R68YIHsUu2
3m3Guh9OlPrBfT2Yk4nT6mlFS+fU81/hNBIQMKhERt0poXf3iABi3R1D+AWNekzd
ZaKe8Fii8yjb3L6LgKuBlabqQEZkeuXr7Ivzi68o6qPP1L+C7Pzs4ycC7uHyvNtc
8KbbrYnAVuNaIZQr9P3LxoW6VmtA39qwPozUFw0ZndnQ/g4h1Hc8Uuw3lBzhhlxM
UyWLsz8FwFIJZ0OiDjiDAMcsDHMyCDnkIEJ0iQgXqoJpCWoLApCXUxeuo0gfbK4=
=2M1z
-----END PGP SIGNATURE-----
--------------enigE935677C6D7C56A64B1150D0--