[OpenAFS] Windows XP event log warning entry with ID 4117 and
4133
David Bear
david.bear@asu.edu
Mon, 09 Mar 2009 16:20:52 -0700
This is a multi-part message in MIME format.
--------------060002060607000809040003
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jeffrey Altman wrote:
> Michal Svamberg wrote:
>> Greetings,
>> does anybody know what means the Windows XP event log warning entry with
>> ID 4117 and 4133? I am experiencing problems of openafs client v. 1.5.26
>> for Windows, it sometimes hangs up for about two minutes. In this time
>> an event log warning entries with IDs 4117 and 4133 are created, no
>> meaningful description is available. I have failed to google these
>> events so I would be very glad if someone has an idea.
>> Thank you very much.
>>
>> Michal Svamberg
>
> The values mean the following:
>
> 4117 - smb reply sent on an invalid smb session (already closed by the
> client)
>
> 4133 - fs crypt is on
>
> the connection between the microsoft smb client and the afs smb server
> on your machine has been lost. Could be the result of an IP address
> change or simply a bug in the microsoft smb redirector that has been
> plaguing us for many years but has never been tracked down sufficiently
> to get Microsoft's attention.
>
> FYI, the current version of OpenAFS for Windows is 1.5.57. A lot of
> bugs have been fixed since 1.5.26.
>
> Jeffrey Altman
>
Is there any news on when we can kill for ever the SMB client and have a
pure IFS AFS client? I thought this was set to be release (in beta
version) last december?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iD8DBQFJtaRUcjLlygO2EbARArDWAJoC1QUjOZuc7x/Z0w+7HWjl58QL8gCgpmwh
WYmUBDxSRzWgYkZ4Bz59G74=
=26MW
-----END PGP SIGNATURE-----
--------------060002060607000809040003
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by epo-int2.asu.edu id n29NKosq000481
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content=3D"text/html;charset=3DUTF-8" http-equiv=3D"Content-Type"=
>
</head>
<body bgcolor=3D"#ffffff" text=3D"#000000">
-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
Jeffrey Altman wrote:<br>
<span style=3D"white-space: pre;">> Michal Svamberg wrote:<br>
>> Greetings,<br>
>> does anybody know what means the Windows XP event log warning
entry with<br>
>> ID 4117 and 4133? I am experiencing problems of openafs client
v. 1.5.26<br>
>> for Windows, it sometimes hangs up for about two minutes. In
this time<br>
>> an event log warning entries with IDs 4117 and 4133 are
created, no<br>
>> meaningful description is available. I have failed to google
these<br>
>> events so I would be very glad if someone has an idea.<br>
>> Thank you very much.<br>
>><br>
>> Michal Svamberg<br>
><br>
> The values mean the following:<br>
><br>
> 4117 - smb reply sent on an invalid smb session (already closed by
the<br>
> client)<br>
><br>
> 4133 - fs crypt is on<br>
><br>
> the connection between the microsoft smb client and the afs smb
server<br>
> on your machine has been lost.=C2=A0 Could be the result of an IP
address<br>
> change or simply a bug in the microsoft smb redirector that has
been<br>
> plaguing us for many years but has never been tracked down
sufficiently<br>
> to get Microsoft's attention.<br>
><br>
> FYI, the current version of OpenAFS for Windows is 1.5.57.=C2=A0 A l=
ot
of<br>
> bugs have been fixed since 1.5.26.<br>
><br>
> Jeffrey Altman<br>
></span><br>
Is there any news on when we can kill for ever the SMB client and have
a pure IFS AFS client? I thought this was set to be release (in beta
version) last december?<br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v2.0.4-svn0 (GNU/Linux)<br>
Comment: Using GnuPG with SUSE - <a class=3D"moz-txt-link-freetext" href=3D=
"http://enigmail.mozdev.org">http://enigmail.mozdev.org</a><br>
<br>
iD8DBQFJtaRUcjLlygO2EbARArDWAJoC1QUjOZuc7x/Z0w+7HWjl58QL8gCgpmwh<br>
WYmUBDxSRzWgYkZ4Bz59G74=3D<br>
=3D26MW<br>
-----END PGP SIGNATURE-----<br>
<br>
</body>
</html>
--------------060002060607000809040003--