Is there a possibility that the aft.sys file has been changed or compromised. There are some viruses that will cloak themselves as that file and run as an LSP using afd.sys
In services startup, strip out and stop all unnecessary services that could interact with the network such as backup services, auto update etc. Are you running print spooling services from this machine to network based printers. Certain print drivers were known to interact with afd.sys.
If it works, I would try XPwinsockfix. or its equivalent. It calls a number netsh commands and does a full reset the TCP IP stack back to factory, copies in all the needed drivers clears out the registry and cleans up everything. Microsoft has a fixit for windows 2008 that is the same.
On this machine, is the HN nic a broadcom or something else. Virtualization is suppose to hide hardware level difference but broadcoms seem to be a bit of pain.
Are these clean new installs or existing installs that were migrated to this box.
In services startup, strip out and stop all unnecessary services that could interact with the network such as backup services, auto update etc. Are you running print spooling services from this machine to network based printers. Certain print drivers were known to interact with afd.sys.
If it works, I would try XPwinsockfix. or its equivalent. It calls a number netsh commands and does a full reset the TCP IP stack back to factory, copies in all the needed drivers clears out the registry and cleans up everything. Microsoft has a fixit for windows 2008 that is the same.
On this machine, is the HN nic a broadcom or something else. Virtualization is suppose to hide hardware level difference but broadcoms seem to be a bit of pain.
Are these clean new installs or existing installs that were migrated to this box.