Unusual Addresses Like 1.10.0.184 Showing in WINS Database
Article ID: 156204
Article Last Modified on 11/1/2006
APPLIES TO
- Microsoft Windows NT Server 3.51
- Microsoft Windows NT Server 4.0 Standard Edition
This article was previously published under Q156204
SYMPTOMS
When you use WINS Manager, you notice a WINS server with an address of
1.10.0.184, 1.35.0.184, 0.62.0.184, 0.225.0.184, or 0.227.0.184, or you notice an owner with these addresses when you click Show Database on the Mappings menu.
You will also notice when you view the mappings for the selected owner (real IP address of the WINS server itself), that you do not see any name registrations for that server. An NBTSTAT -N command will show the correct WINS server registrations.
CAUSE
The Remote Access Service (RAS) WAN Wrapper is bound before the network
interface card (NIC).
RESOLUTION
Windows NT 3.51
Perform the following steps to work around this problem:
- Go to the Main group, double-click Control Panel, and
then double-click Network.
- Click Bindings.
- In the Show Bindings For list, click All Protocols, and
then double-click WINS Client (TCP/IP).
- Click Remote Access Service WAN Wrapper, and then click the
down arrow to move it below your network adapter driver.
NOTE: There may be multiple RAS WAN Wrapper entries.
Windows NT 4.0
Perform the following steps to work around this problem:
- Click the Start button, point to Settings, click Control Panel, and
double-click Network.
- Click the Bindings tab.
- In the Show Bindings For list, click All Protocols, then double-click WINS Client (TCP/IP).
- Click Remote Access Service WAN Wrapper, and then click
Move Down to move it below your network adapter driver.
NOTE: There may be multiple RAS WAN Wrapper entries.
- In the Show Bindings For list, click All services.
- For each service, select the WINS Client (TCP/IP) and verify
that the network adapter is now listed first. Move the Remote Access
Service WAN Wrappers down if needed.
NOTE: There may be multiple RAS WAN Wrapper entries.
STATUS
Microsoft has confirmed this to be a problem in Windows NT versions 3.51
and 4.0. We are researching this problem and will post new information here
in the Microsoft Knowledge Base as it becomes available.
Additional query words: weird funny bogus strange unusual
Keywords: kbbug kbpending KB156204