Seeing computer on Network Neighbourhood

  • Thread starter Thread starter Wendy
  • Start date Start date
W

Wendy

Hi all,

I recently had my computer changed from a stand alone PC
to a small peer-2-peer network by adding a second computer.

All I wanted to do on the computer acting as the file
server, was to map some directories on the C:/ to drive
letters (eg c:/APPS = H:/) so that data could be accessed
across the network.

I have done this many times at other business sites, and
each time have done so by being able to see the computer
and its directories listed in "Network Neighbourhood".

When I went to do the same thing with my own computer, I
found I couldn't even SEE my 'server' computer on the
Network Neighbourhood - therefore was unable to do mapping.

Someone came in and looked at it, and while I was out of
the room, they fixed the problem, but then they refused to
tell me what they did to fix it!!

It surely has to be something very small, and perhaps
embarassing since they won't tell me what it was, but I
don't know what it was, and I really think it would be in
my best interests to know in case I have the same issue
again.

Does anyone know what was done to fix this up?

TIA.

Wendy
 
Look for a file on your system called HOSTS. Open it up in notepad. Read the
instructions. Edit the file and save it.
Most likely what he did.
 
Hi,

Thanks for that suggestion. I checked it out and found a
couple different versions of this file, but they were all
the same and had no changes to it.

I'm wondering if it is possible that the 'Server' service
wasn't properly started, and starting it automatically was
his fix? There is a few slightly strange messages in the
Event Log indicating that there was a forced browser re-
election around then.

Thanks for your help.
 
As to the Browser elections this is a normal windows thing. When ever a
machine joins a Windows network it tries to set itself up as the master
Browser especially if you have no server.
And yes the server service should be started at boot up.
As a quick fix you could map your drives by IP address rather then name.
Such as "net use Z: \\10.1.1.10\ShareName"
 
Back
Top