Event ID - 102

Event Id	102
Source	Microsoft-Windows-SpoolerTCPMon
Description	The standard TCP/IP printer port monitor (TCPMon.dll) failed to cleanup the sockets it was using. The WSACleanup function in WS2_32.DLL returned an error. This can occur if there is a serious failure of the network subsystem, the network interface, or the local network itself.
Event Information	According to Microsoft : Cause : This event is logged when the standard TCP/IP printer port monitor (TCPMon.dll) failed to cleanup the sockets it was using. Resolution : Correct network issues This issue usually occurs when there is a problem with the network or the network subsystem. Try connecting to other servers on the network to determine whether the network is functioning properly. If you cannot reach any other servers, try obtaining a new IP address, resetting the network adapter, or restarting the computer. To resolve this issue, use the following procedure: On the print server, open the Command Prompt window, and then type ipconfig /all at the command prompt. Make sure that the print server has an IP address in the correct IP address range, and that it does not have an Automatic Private IP Addressing (APIPA) address (an IP address in the 169.254.x.x range). Ping the loopback address of 127.0.0.1 to verify that TCP/IP is installed and correctly configured on the local computer. If the ping is unsuccessful, this may indicate a corrupt TCP/IP stack or a problem with the network adapter. Try disabling the network adapter, restarting the computer or replacing the network adapter. Test whether you can ping the local IP address. If you can ping the loopback address but not the local IP address, there may be an issue with either the routing table or the network adapter driver. Ping the DNS servers. If you cannot ping the DNS servers, this indicates a potential problem with the DNS servers, or possibly a network problem between the print server and the DNS servers. However, it can also mean that the server is not configured to reply to ping requests. To determine if this is the case, ping the DNS server from a computer that has full network functionality. If you cannot ping the DNS server or any other server address that replies to ping requests from other computers, perform the following actions: Check the Event Viewer for any error messages. In Device Manager, check the status of the network adapter. Check network connectivity indicator lights at the server and at the hub or router. Check network cabling. At the command prompt, type nslookup print_server_name, where print_server_name is the computer name of the print server, and then press ENTER. If you can ping the DNS server but the nslookup command fails, restart the DNS Server service on the DNS server. To do this, open the Services snap-in from the Administrative Tools folder, select the DNS Server service, and then click the Restart Service toolbar button. Verify : Retry printing to the printer, using the standard TCP/IP printing port monitor.
Reference Links	Event ID 102 from Source Microsoft-Windows-SpoolerTCPMon

Catch threats immediately

We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.

See what we caught