Cannot Access Server Using NetBIOS Name or IP Address

 Last reviewed: March 28, 1997
Article ID: Q159770
The information in this article applies to:
  • Microsoft Windows NT Server version 4.0
  • Microsoft Windows NT Workstation version 4.0

SYMPTOMS

If you use an IP address to establish a session with a server, and then use the server's NetBIOS name to attempt to access the server, you receive the error message "Access is denied."

For example, if you use the following command to establish a session with a server 

   net use \\<###.###.###.###>\ipc$ /u:<domain name>\<user name>
where <###.###.###.###> is the server's IP address, and then attempt to access the server using its NetBIOS name, you receive the error message.

NOTE: This problem also occurs if you establish a session with a server using the server's NetBIOS name and then attempt to access the server using its IP address.

CAUSE

The redirector does not recognize that the IP address and the NetBIOS name denote the same computer.

RESOLUTION

Use either the IP address or the NetBIOS name to establish a session with and access the server.

Additional query words: prodnt
Keywords : kbnetwork NTSrvWkst nttcp
Version : 4.0
Platform : WinNT
Issue type : kberrmsg

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: March 28, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.