machines not showing up in Network Neighborhood

From: Sandra L Miller (slm_at_cs.arizona.edu)
Date: 03/28/05


Date: Mon, 28 Mar 2005 08:48:36 -0700
To: netdiscuss <netdiscuss@tick.telcom.arizona.edu>

We have a domain of approximately 250 Windows XP workstations, with
2 Windows 2003 Servers as domain controllers. The workstations are
spread over 3 student labs, many desktop machines, and some laptops.
Two of the student labs are in remote buildings.

Our problem is that the 48 machines that are in the student lab that
is in the same building as the domain controllers, on the same IP
subnet, are not showing up in Network Neighborhood. All other machines
in the domain show up, including those in the remote student labs, one
of which is on a separate IP subnet.

Strangely, this seemed to happen slowly over time, with machines
dropping off one by one until now none of them show up. The machines
can be pinged, and I can log on to them remotely, and they are getting
updates, etc. In other words, nothing seems to be wrong with the
connections, they just do not show up in Network Neighborhood.

This is a mystery I would like to solve for its own sake, but also
because machines that don't show up in Network Neighborhood, also do
not show up in the Sophos Enterprise Manager's SAVAdmin, which is
what we use to monitor the status of our virus checking software.
I cannot push a configuration to those machines.

I am at a loss as to what the problem might be. Can anyone give me
ideas as to what to look for?

TIA,
Sandy

-- 
Sandra L Miller
Windows System Administrator
Department of Computer Science
University of Arizona
"The opinions or statements expressed herein are my own and should not be
taken as a position, opinion, or endorsement of the University of Arizona."


Relevant Pages

  • Re: Slow initial TCP connection to any machine.
    ... Assuming the Domain Controllers are Server2000: ... Windows 2000 Domain ... > why this is happening on the XP machines, because these update are now> taking a very long time to complete when multiplied by the number of> machines we have. ...
    (microsoft.public.windows.server.networking)
  • Deployment of adminpak.msi is off the rails
    ... I have an environment where we use Windows 2000 Advanced ... Server with two domain controllers. ... When the adminpak was deployed, the GPO was linked to the ... Since these machines ...
    (microsoft.public.win2000.active_directory)
  • Re: Server 2003XP Pro Connection Problems
    ... connecting to 2003 domain controllers and am running Norton AV Corp Ed. I'm ... > Windows 2003 Server. ... About 30 machines connect to this ...
    (microsoft.public.windows.server.networking)
  • RE: Upgrade path to 2003
    ... You should not have any problems completing the upgrade. ... moved and all DCs are 2003, then you will want to change to Windows 2003 mode. ... > Domain Controllers and 2 windows 2003 member servers. ... > only the 2003 machines as Domain controllers. ...
    (microsoft.public.windows.server.general)
  • Re: Windows 98 in a Server 2003 Domain and trouble with shares
    ... The Win98 machines both look to the Domain for credentials. ... As Richard mentioned, SMB signing needs to be disabled on each DC's Domain Controller policy, or in the Default Domain Controllers GPO on each domain, that you are allowing share access from a pre-Windows 2000 computer ... Overview of Server Message Block signingDescribes how to configure SMB signing and how to determine whether SMB ... How to upgrade Windows 2000 domain controllers to Windows Server 2003For information about how to disable SMB signing (search in the article for "To disable SMB signing" ...
    (microsoft.public.windows.server.active_directory)