Error 404 Object Not Found When Accessing Intranet Using NetBIOS Server Name in Internet Explorer

This article was previously published under Q174339
This article has been archived. It is offered "as is" and will no longer be updated.
When you attempt to access an intranet Web site using its NetBIOS name inInternet Explorer instead of using its host name, you may receive thefollowing error message:
http:/1.0 404 Object Not Found
Instead of the above error message, you may experience long delays when youattempt to load intranet Web pages.
The client system on which you are running Internet Explorer has a domainname configured within its TCP/IP properties.
To resolve this issue, use one of the following methods:

  • Add the web server's NetBIOS name to your Domain Name Service (DNS) server. This will keep the DNS server from forwarding the query to other DNS servers -- possibly root servers on the Internet -- in an attempt to resolve the name. If your DNS server is authoritative for the domain being queried, it can respond almost instantly with a positive or negative response, avoiding any timeouts. If the DNS server is not authoritative for the domain being queried, and its cache file contains root servers, it will forward the name query to the root servers that are authoritative for that domain and wait for a response before replying to the client. This can make the client wait up to five seconds, after which time it will resend its query to the same DNS server. -or-

  • If the client receives DNS server IP addresses from a Dynamic Host Configuration Protocol (DHCP) server, do not configure static DNS server IP addresses in the client's TCP/IP properties. This increases the number of servers from which it will wait for a response before trying to resolve the name via a NetBIOS name service.
When you type a name in the address line of Internet Explorer, such as"server", and your computer is configured with a domain name, such as"", a name query is first sent with the domain appended to thename, "". This query will be sent to all DNS servers forwhich your computer is configured before trying to resolve the name of just"server" through a NetBIOS naming service such as Windows Internet NameService (WINS).

Computers configured for DHCP and running Windows 95 and Windows NT thathave DNS server addresses manually specified in their TCP/IP configurationwill effectively have four DNS servers to send queries to. The client willtry to use all DNS addresses available. The client queries its primary andsecondary DNS addresses first and it will then wait for a response for upto five seconds before querying again. If it fails to resolve the name onthe first two servers, it will then try the third and fourth DNS addressesand wait for responses from them. While waiting for these servers torespond, the client browser may timeout.

Article ID: 174339 - Last Review: 10/07/2013 06:19:25 - Revision: 2.1

  • Microsoft Windows 95
  • Microsoft Windows NT Workstation 3.51
  • Microsoft Windows NT Workstation 4.0 Developer Edition
  • Microsoft Windows NT Server 3.51
  • Microsoft Windows NT Server 4.0 Standard Edition
  • kbnosurvey kbarchive kberrmsg kbinterop kbnetwork kbprb KB174339