General discussion

Locked

inetinfo.exe/afd.sys

By a coward ·
Any clues on the following would be appreciated:
HP LC3, 2*Pentium II 450, 512MB, NT 4.0, SP6a

After a certain amount of time/transactions, inetinfo crashes with the message:
"The driver \Driver\Afd failed to complete a cancelled I/O request inthe allotted time."
When this happens it only affects inetinfo, I can still ping it and connect to the SQL server. However I lose complete control over explorer.exe, hence no ability to do anything at the server console. It does respond to remote commands though, such as ping, start/stop some services or devices using NT's server manager on another server.
I believe this problem has something specifically to do with inetinfo.

This conversation is currently closed to new comments.

5 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

inetinfo.exe/afd.sys

by DC1 In reply to inetinfo.exe/afd.sys

Afd.sys is a driver for Winsock. Could be corrupted or an applciation that calls it has a memory leak, etc. Try reapplying SP6a.

Collapse -

inetinfo.exe/afd.sys

by a coward In reply to inetinfo.exe/afd.sys

These answers were usefull, though not correct. Of course it turns out there was a third party app that was inserting it's own TCP stack that was causeing the problem, but I didn't know about that at the time I asked the question.

Collapse -

inetinfo.exe/afd.sys

by Brian G In reply to inetinfo.exe/afd.sys

AFD (Winsock) errors can be caused by many things. If you have any ISAPI dll's they are the most likely cause (URLs that contain "file.dll?" calls). They are likley calling across the network to a database or service.
DCOM can also cause these kinds of problems if the call is looking for a machine and can't find it and timeouts causing the ASP page to timeout.

Of course, both (dll/DCOM) are really just small exe's so they can have their own memory problems, such as corruption, file open problems, etc.
My best guess is that a DCOM or dll is corrupting itself and causing it to call across the network to a non-existent machine because the name has been trashed by a memory overwrite.

Collapse -

inetinfo.exe/afd.sys

by a coward In reply to inetinfo.exe/afd.sys

These answers were usefull, though not correct. Of course it turns out there was a third party app that was inserting it's own TCP stack that was causeing the problem, but I didn't know about that at the time I asked the question.

Collapse -

inetinfo.exe/afd.sys

by a coward In reply to inetinfo.exe/afd.sys

This question was closed by the author

Back to Windows Forum
5 total posts (Page 1 of 1)  

Related Discussions

Related Forums