Do you have more than one subnet? Are you in a domain? The links below will help you
understand how lan browsing works so you can get an idea where the problem is. The
second link is for troubleshooting. The quick list of problems are.
-- There is general misconfiguration or problems on domain controllers or computers.
Dcdiag is a must use tool to troubleshoot domain controllers after using netdiag
first which can be used on any W2K/XP computer to check network configuration and
domain resource access/membership. Always check Event Viewer on domain controllers
when you have network problems - especially the pdc/pdc fsmo.
-- Network connectivity is down, at least to important servers such as domain
controllers, dns servers, wins server, master browsers.
-- Don't rule out hardware problems such as a flaky nic on a server/domain
controller.
-- Netbios over tcp/ip needs to be enabled for a computer to access, be in the browse
list, or manage the browse list. Ipconfig /all will show if netbios over tcp/ip is
disabled on a computer.
-- At least a couple of computers need to be able to be master browsers and have the
computer browser service running.
-- Computers can be hidden from the browse list. Check via "net config server"
-- Firewalls, including built in and software ones can block network browsing as can
other "protection" applications. Often booting into safe mode with networking can
isolate that issue.
-- A computer must be have file and print sharing installed and enabled with the
server service running to appear in the browse list.
-- A computer must have Client for Microsoft Network installed and enabled with the
workstation service running to see the browse list.
-- The above two must use a common protocol, usually tcp/ip these days.
-- Computers must have correct tcp/ip configuration, as shown with ipconfig /all,
being on the same network/subnet.
-- If browsing over subnets [including VPN], wins servers for the network or lmhosts
files on master browsers must be used. VPN clients may also need a lmhosts file if
wins is not used on the network
-- If using wins, the wins servers need to replicate accross subnets, should not be
multihomed, need to be a client to themselves, and all network computers including
domain controllers need to be wins clients.
-- Master browsers, typically domain controllers and especially the pdc/pds fsmo must
not be mutilhomed or also a rras server as split or incomplete browse lists will
result.
-- Wrong entries in lmhosts files, hosts files, or static arp entries can cause
browse and network connectivity problems.
-- Windows XP is known to cause a lot of browser elections, often trying to steal the
role from even domain controllers. If that is happening disable the computer browser
service on XP computers causing the problem
-- For more advanced troubleshooting use Ethereal [free] to capture and analyze
traffic when a computer tries to access the browse list as you will see it try to
access a browse master and possibly get a referral to a backup browser.
-- Incompatible security options can cause problems with network access or network
browsing. For instance if "server: digitally sign communications (always) "is
enabled on a server, communications will fail for those computers unable to use smb
signing. In Windows 2000 the security option for "additional restrictions for
anonymous access" if set to "no access without explicit anonymous permissions" can
cause problems with network browsing and can be configured at various levels
including domain, domain controller, Organizational Unit, or local. Often a well
intentioned administrator will apply a "security lockdown" template to a domain
controller or such and cause network problems.
http://www.microsoft.com/resources/.../server/reskit/en-us/tcpip/part4/tcpappi.mspx
http://support.microsoft.com/default.aspx?scid=kb;EN-US;188305 --- how to
troubleshoot browse problems
