Ensure latest updates are installed for Windows and any third-party networking software including NIC drivers, firewalls, or other security products. This happens typically due to misbehaving network drivers. Setting your TCP/IP and AFD registry parameters for optimum performance. Also, afs. However I can manually start DHCP and connect. The local port number may not be available until the close operation is completed. Looking at the event viewer I see DHCP fails to start, then shortly after, AFD failed to start. Ensure latest updates are installed for Windows and any third-party networking software including NIC drivers, firewalls, or other security products.Ĭlosing a UDP socket with local port number 55104 in process 3772 is taking longer than expected. This happens typically due to misbehaving network drivers. The local port number may not be available until the close operation is completed. Only way to resolve the issue is by rebooting the serverĬlosing a UDP socket with local port number 61573 in process 3772 is taking longer than expected. The most trouble some is the event ID 16002 error which when it appears in the logs it happens constantly and we lose all network connectivity to the server.
After AFD creates a new socket, allocate a cache area to each Socket, you can change the size of the transceiver cache area by changing the following registry key: HKEYLOCALMACHINE \SYSTEM \CurrentControlSet\Services\Afd\Parameters DefaultReceiveWindow 16384 DefaultSendWindow 16384. We have recently added several new Server 2012 r2 servers in our environment and are receiving the same multiple errors for them. From the functional hierarchy of this operating system, on AFD.SYS, it is a system library implementation (DLL).