I do not think you are supplying enough information for us to help you. The
way network neighborhood works, a system in your house (this is in your
house I presume,) becomes the network browser. This means that when systems
connect to the network, they will identify themselves to this browser giving
it their computer name, which it compiles into a list. When your PC
interrogates the network neighborhood, it actually contacts the browser to
get the list.
My first guess is that you have a master browser conflict. Now, there is a
pre-ordained order in which systems can be elected to become master browsers
and I think this may be the source of your problems. I do not know what
kinds of computers you are using or what OS they have, but this makes a
difference. You also neglected to tell us if you use DHCP and if so which
device leases the IP addresses.
These network conflicts can be a source of aggravation, but can be resolved.
If I were faced with the problem you are describing, I would try to
eliminate the master browser issue first and then move on to other areas if
this did not resolve the problem.
The first thing I would do is validate all the IP addresses in use, making
sure there were no duplicates and making sure the subnet mask was proper for
all machines. I would then change the Windows network setting to disable
all system from being the master browser except for one system. (You can
get around this by having a PDC in your environment. By default, the PDC is
the master browser. Since you refer to workgroup, I would guess there is no
PDC. Is there an NT Server? If so, by default, it will be the master
browser. However, there is an old bug in Windows 95 that makes some systems
believe they are the master browser.
So, I would then shut down all systems. Next, I would start the one that I
think I have designated as the master browser. I would then check the
network neighborhood on that system. It should show that system, by itself.
After about 15-30 minutes, I would start another one. I would then check
the network neighborhood. The two systems should appear in there within 15
minutes. They should both be accessible. I would just keep doing this
until after one system comes up and the NN goes to heck. I would then
concentrate on why that system may be at fault.
Denys
-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]]On Behalf Of
Tom Hula
Sent: Tuesday, May 28, 2002 12:16 PM
To: [log in to unmask]
Subject: OT: More Network Fun
I'm quite sure this is all about what I don't know.
Originally, when I set up the network, I was going to setup the subnet mask
as 255.255.255.0, since the addresses are all 192.168.1.xxx. However, I
could
not get file sharing working that way. I ended up trying 255.255.0.0 and
that
worked just fine.
Now, I am trying to get DSL working, and the Linksys router I bought is
really
convinced it wants to have a subnet mask of 255.255.255.0. The last octet
can be changed to other values, but the first three octets are really
insisting
on the 255.255.255 . So now I am back to trying to make 255.255.255.0 work
on the PC workstations.
>From my PC, I can see the other PC's in the network neighborhood (although
they
can't see me). But when I click on the icons of the other computers, it
gives me
an error telling me it can't find the computer or share name.
Meanwhile, if I set everything back the way it was, nothing can see my
router.
This network stuff is great when it works. Why does this subnet stuff act
like
it does?
Also, I can ping everything and getting on the 3000 is no problem no matter
what
the subnet is set to on the PCs.
Tom Hula
Victor S. Barnes Company
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
