Microsoft Knowledge Base Email Alertz

When you use all numeric NetBIOS computer names, some TCP/IP utilities will misinterpret these NetBIOS names as IP addresses.

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 190294 - Last Review: January 23, 2007 - Revision: 2.2

Use of all Numeric NetBIOS Names Can Cause Problems

System TipThis article applies to a different version of Windows than the one you are using. Content in this article may not be relevant to you. Visit the Windows Vista Solution Center
This article was previously published under Q190294

SYMPTOMS

When you use all numeric NetBIOS computer names, some TCP/IP utilities will misinterpret these NetBIOS names as IP addresses.

For example, if you have a computer named 4754755 and its IP address is 10.1.5.17. When pinging the computer, ping will misinterpret the computer name as an IP address and will send an echo request to 0.72.141.67 rather than 10.1.5.17. This will result in a request timed out error.

RESOLUTION

The use of all numeric NetBIOS computer names should be avoided when you are using the TCP/IP protocol.

STATUS

This behavior is by design.

REFERENCES

For more information about NetBIOS over TCP, please see:

  • RFC 1001 - Protocol Standard for a NetBIOS Service on a TCP/UDP Transport: Concepts and Methods
  • RFC 1002 - Protocol Standard for a NetBIOS Service on a TCP/UDP Transport: Detailed Specifications
RFCs may be obtained via the Internet as follows:

Paper copies of all RFCs are available from the NIC, either individually or on a subscription basis (for more information, contact NIC@NIC.DDN.MIL). Online copies are available via FTP or Kermit from NIC.DDN.MIL as rfc/rfc####.txt or rfc/rfc####.PS (#### is the RFC number without leading zeros).

Additionally, RFCs may be requested through electronic mail from the automated NIC mail server by sending a message to SERVICE@NIC.DDN.MIL with a subject line of "rfc ####" for text versions, or a subject line of "rfc ####.PS" for PostScript versions. To obtain the RFC index, the subject line of your message should read "rfc index".

APPLIES TO
  • Microsoft Windows NT Server 3.5
  • Microsoft Windows NT Server 3.51
  • Microsoft Windows NT Server 4.0 Standard Edition
  • Microsoft Windows NT Workstation 3.5
  • Microsoft Windows NT Workstation 3.51
  • Microsoft Windows NT Workstation 4.0 Developer Edition
  • Microsoft Windows NT Server 4.0 Enterprise Edition
  • Microsoft Windows 3.11 Standard Edition
  • Microsoft Windows 95
  • Microsoft Windows 98 Standard Edition
Keywords: 
kbnetbios kbnetwork kbprb KB190294
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate