Cannot Browse Windows NT Domains Across IP Subnets
  
PSS ID Number: Q140087
Article last modified on 11-22-1995
 
95
 
WINDOWS
 

---------------------------------------------------------------------
The information in this article applies to:
 
 - Microsoft Windows 95
---------------------------------------------------------------------
 
SYMPTOMS
========
 
When you browse the network, you see only your Windows NT logon domain and
your current workgroup in the browse list.
 
CAUSE
=====
 
You may experience this behavior when TCP/IP is the only network protocol
you are using.
 
RESOLUTION
==========
 
To browse across IP subnets with a Windows 95-based computer, you must
satisfy one of the following conditions.
 
NOTE: These conditions are valid only if any NetBIOS name resolution
problems are resolved with WINS, LMHOSTS, or DNS.
 
 - You have a Windows NT server on the subnet that merges the browse list
   with other Windows NT servers on other subnets.
 
 - You have a Windows NT workstation or server in your workgroup as the
   browse master.
 
 - Your workgroup name is the same as a remote Windows NT domain. This is
   required when there are no Windows NT computers on the subnet. It is
   necessary in this case to use either WINS or an LMHOSTS file for
   NetBIOS name resolution. If you use an LMHOSTS file, you must include
   the following entry:
 
      #DOM <IP address of Domain Master Browser> 1B
 
   This makes it possible for the Windows 95 local master to participate
   in the merging of the WAN browse list.
 
 - If you have only Windows 95-based computers on the subnet and you want
   to organize them in individual workgroups that are not equal to a
   remote Windows NT domain, you must designate at least one Windows 95-
   based computer on the subnet to represent the remote domain. In other
   words, set at least one Windows 95-based computer to have its workgroup
   match the remote domain. This makes it possible for the Windows NT
   domains to have representatives on the subnet, and merges the browse
   list between a remote domain controller and a Windows 95 server.
   Windows 95 workstations in other workgroups can see the domains on the
   entire network because the Windows 95 servers are the local browse
   masters for these domains. If you choose to do this, you must have a
   Windows 95 server on your subnet for every remote domain you want to
   browse.
 
 - The above information is also true for Windows for Workgroups using the
   updated VRedir included with Windows NT 3.51. However, because of UI
   differences between Windows 95 and Windows for Workgroups, a Windows
   for Workgroups-based computer sees the logon domain (and only that
   domain) in the browse list without satisfying any of the above
   conditions.
 
KBCategory: kbnetwork kbenv
KBSubcategory: win95 msnets
Additional reference words: 95 login
=============================================================================
Copyright Microsoft Corporation 1995.
