Windows nt4 event log

Download Microsoft Edge More info. Contents Exit focus mode. Please rate your experience Yes No. Any additional feedback? Note Authenticated users cannot, by default, log events to the Application log on a remote computer. Privacy policy. You may receive different WINS event log messages, depending on the version of Microsoft Windows and the service pack that you have installed on your computer. The Microsoft Knowledge Base contains information about all the changes to event log messages.

Always note the error message and the event ID. An event ID alone may mislead you. Before you troubleshoot WINS replication-related error messages, make sure that your network uses a true hub-and-spoke replication topology. Make sure that you configure each server to point to itself. You must avoid push-pull replication in a loop. Microsoft recommends that you use a true hub-and-spoke WINS model.

If the servers are located across routers, verify that there isn't a lost network connection or a failed router on an intermediate link.

Also make sure that TCP port 42 isn't blocked on an intervening network device, such as a router or a firewall. The following event ID message is an example of an event ID message.

The WINS Server event log messages contain data that you can use to determine the reason for an error. Change the view of the data section of the event from bytes to words. The second data word in the data section is associated with the type of error that was logged. The type of error that was logged is the key to troubleshooting this issue.

Check for disconnected or unreachable systems. To troubleshoot this problem, search for disconnected or unreachable computers. Because this error is network-related, you can perform a network trace to determine which WINS server is failing.

To resolve the WINS event message, perform a Network Monitor trace to find all the obsolete replication partners, and then remove all the obsolete replication partners. You can pre-filter the trace for frames on this port. Search the trace for frames where the TCP Flags property includes "Synchronize Sequence numbers," and then determine if all these frames were answered.

An obsolete replication partner is a server that sends a TCP Reset packet or a server that doesn't answer. Remove the obsolete replication partners from the list of replication partners for your WINS server.

Search related threads. Remove From My Forums. Answered by:. Archived Forums. Sign in to vote. Hi, A few days ago one of the programs installed on our R2 server has "disappeared", as if it was uninstalled. I've searched through the event viewer for anything related but found nothing. Typically, a shortage of ephemeral ports causes this issue. Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly.

Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:.

Examine your replication topology, and make sure that you are configured for a true Hub-and-Spokes replication topology. Verify that there is not a TCP connection shortage.

Before the TCP packet is sent, the computer verifies that it has sufficient resources, for example free outgoing TCP ports.

To verify that there is not a TCP connection shortage, follow these steps:. Run the following command on the failing computer at the time that this computer is logging the event ID errors , and then save the output to a file.

To do so, run the following command from a command prompt:. Look for total number of sessions and used ports, examine the state of the sessions to determine whether the number of sessions has reached the maximum value. By default, the maximum value is For additional information, click the following article number to view the article in the Microsoft Knowledge Base:. To resolve this issue, follow these steps:. Note: is the maximum value for the MaxUserPort value.

On Windows , you may receive the WINS event log event messages if any of the following conditions is true:. A computer receives a push notification. Based on this notification the computer uses the pull mechanism to obtain all the newer records than are indicated by the highest version ID. When a pull partner tries to obtain the records based on the version IDs that the pull partner was informed about, those records no longer exist on the partner's database.

This issue may occur if a push partner lists an entry that is already outdated before the pull time is reached. For example, if you send a push, the entry is updated, and then you send the push again before a pull occurs, you may receive this event message.

To resolve this behavior, tune the push count and pull time.