Troubleshooting NET USE Failure (when PING NetBIOS Name Works)

ID: Q142027

3.10 3.50 3.51 3.11 WINDOWS kbtshoot

The information in this article applies to:

Microsoft Windows NT operating system version 3.1
Microsoft Windows NT Advanced Server version 3.1
Microsoft Windows NT Workstation versions 3.5, 3.51, 4.0
Microsoft Windows NT Server versions 3.5, 3.51, 4.0
Microsoft TCP/IP-32
Microsoft Windows for Workgroups version 3.11
Microsoft Windows 95

SUMMARY

In some circumstances, pinging a NetBIOS name (with the PING utility) returns a reply, but using other commands (such as NET USE or NET VIEW) to connect to or view a NetBIOS resource may not complete successfully. In some cases this is due to the fact that the PING utility uses ICMP packets and does not require a session to be established, whereas the NET Commands require a session to be established.

MORE INFORMATION

If you can ping a NetBIOS name but cannot use the NET command, follow these steps:

1. If this occurs only across a router, check to see if TCP Port 139 is

   enabled.

   The NET commands and the Map Network Drive command in Windows rely on
   TCP Port 139. To enable this port the administrator of the router
   should be contacted. If further help is needed, contact the router
   manufacturer.

2. If this occurs only across a router, check to see if the Router is

   unable to Pass the Large Packet Sizes.

   The PING utility sends 74 bytes of data. It is possible that the PING
   requests can pass through the router, but not the larger NET requests.
   The following procedure can be used to see if packet size is the
   problem:

   a. Use PING -L <buffer size to send>". For example:

         PING <computername> -l 4048
         PING <computername> -l 3036
         PING <computername> -l 2024
         PING <computername> -l 1012

   b. Edit the registry to specify a smaller packet size.

3. Check to make sure the Server Service is started on the computer in

   Control Panel, Services.

   If the Server Service is not started, that computer still responds to
   the PING utility, but a session cannot be established. Start the Server
   Service in Control Panel, Services.

4. Check to make sure the destination computer is responding.

   If the destination computer is not responding (hung), it is possible
   for the PING utility to receive a response even though a session cannot
   be established.

   Take appropriate steps to restore the hung computer. Reboot, repair, or
   reinstall as necessary.

5. Check to make sure the destination computer has a valid license.

   If there are no licenses available for the destination computer, it
   still responds to the PING utility, but it is unable to establish a
   session.

6. Verify if DNS or a HOSTS file is in use. Since the HOST name resolution

   methods are used first ping may be resolved, yet NET USE may timeout
   before the HOST methods can be utilized.

KBCategory: kbtshoot KBSubcategory: nttcp Additional reference words: 3.50 3.51 prodnt tcpip wfw wfwg win95 win95x

Keywords          : nttcp 
Version           : 3.10 3.50 3.51 3.11 4.0 95
Platform          : WINDOWS

Last Reviewed: August 14, 1998