Event ID 4204 Source Wins
| Event ID | 4204 |
| Source | Wins |
| Type | Error |
| Description | WINS could not read from the User Datagram Protocol (UDP) socket. |
| English, please! | Request a translation of the event description in plain English. |
| Concepts to understand | What is the role of the WINS service? |
| Comments |
Adrian Grigorof
As per Microsoft: "This message means that WINS was unable to receive a name packet. Stop the WINS service. Then double-click Network in the Control Panel. Under the Protocols tab, verify that the TCP/IP driver is installed and running. Restart WINS if necessary to correct the problem." We have seen reports on this problem even when the TCP/IP seems to be running fine. Jason Rothstein (Last update 9/19/2004): I received this error after upgrading a Win2k DC to Win2k3. The solution was to give the Local System account read rights to the following registry key: ”HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers\winreg”. Ionut Marin (Last update 9/19/2004): As per Microsoft: "This event indicates that WINS was unable to receive a name packet". See MSW2KDB for troubleshooting steps. Adrian Florin Moisei (Last update 5/19/2003): According to Microsoft this event can also occur if the file permissions on the WINS directory have been changed from their default settings. Change the file permissions back to the default of Everyone=Full Control for the %Systemroot%\System32\WINS directory. See M158865. Joe Haas Regarding M151761, I've found on my Windows 2000 server (which was an upgrade from NT4) that the suggested timeout value of FFFFFFFF (something like 136 years) does not work, it still broadcasts every 40 minutes. Why bother deciphering Event logs when GFI EventsManager can do everything for you? Free trial here! Anonymous This seems to be a common problem, here's a useful thing I found on a Google search... not really a fix, but it does help explain the problem: "I started receiving the error event 4204 on a freshly installed SBS2000 network. I used a packet sniffer to determine the source of the bad packets. Apparently WINS tries to find replicating partners on start-up and thereafter every 40 minutes by sending IGMP packets to multicast 224.0.1.24. Check out the M151761 knowledge base article. In my case some devices on the network (a couple of network enabled Moxa serial port adapters) responded to the multicast and thereby caused the error messages. A google search revealed a guy had the same problem with a bunch of Netware 6 servers. I got the problem fixed now, after consulting with the excellent technical support at Moxa, and a couple of firmware upgrades (- on the serial port adapters that is)." Doug Luxem It appears that sometimes, this error is coming from Netware servers being on the same network as the WINS servers. Every 40 minutes the WINS servers send out a multicast packet, and for some reason, Netware server reply back with an ICMP packet stating "Destination Unreachable". This results in one event logged for each Netware server on the network. Dennis B I found that when a Windows 2000 based WINS server starts and then every 40 minutes (M151761) it sends out IGMP packets to multicast address 224.0.1.24 looking for replication partners. I have four serial port adapters (MOXA) in my network (to translate serial communication to TCP/IP) and these reply to the multicast which cause the error event 4204 in the error log. One resolution could be to change the 40 minutes to a larger value as per M151761. |
| Links | M134958, M139782, M151761, M158865, MSW2KDB |
| Search | Google Web - Microsoft Support - Bing - EventID.Net Queue - More links... |
| Feedback | Send comments - Notify me when updated |
| Print version |