NetworkPlaces does not "prove" nor does it "disprove" networkability.
You can connect to any machine from a command prompt or the "Run" line by
doing
\\homer
or
\\bart
or
\\lisa
(the workgroup name does *not* even have to match)
NetworkPlaces is just a "display" of the contents of the workgroup's Master
Browse List. Like Highlander,...there can be only one,...and the machine
that possesses it must be running. The machine that gets used for this is
"decided" among the machines by having a "Browser Election" and the winner
is the one that holds the Browse List. If you keep turing your machines on
and off this will always be in turmoil. If "winner" machine is not running
or gets blocked by running a firewall on it then all the machines can get
into an "argument" over who is the real Master Browser and therefore "argue"
about which browse List is the *real* browse list. This obviously causes
inconsistant "views" in NetworkPlaces from different machines.
Microsoft have been trying for years to eliminate the whole use of
NetworkPlaces due to problems like this,...but unfortunately they have not
been able to *ween* people off of it. I have been working where I am for 10
years (since NT40 domains) and my system of about 100 machines has never in
ten years consistantly showed all the machine in NetworkPlaces, and on top
of that has not consistantly showed the same machine everytime. We just
simply don't use it.
On each of your machines place a Shortcut for the other two machine into the
Desktop Folder within the All Users Profile and they will show no matter who
logges into the machine. To create a shortcut open Windows Explorer and
type \\machinename in the Address Bar. When it loads drag and drop the icon
in the Address Bar to a conveinent place. Once you have collected Shortcuts
for each machine then copy them where the need to be.
Here is some information on the whole Network Browsing mechanism:
191611 - Symptoms of Multihomed Browsers
http://support.microsoft.com/default...b;EN-US;191611
(Even a simple PC with a VPN connection to somewhere else is considered
MulitHomed)
188305 - Troubleshooting the Microsoft Computer Browser Service
http://support.microsoft.com/default...b;en-us;188305
--
Phillip Windell
The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------
"Pete Zahut" <dont@bother> wrote in message
news:(E-Mail Removed)...
> Jack,
>
> I have exactly the same problem as the OP (or very similar, anyway) and
> have turned *all* firewalls off for testing purposes without success, so
> I'd say it's not firewall related in my case.
>
> I have one desktop and two laptops (let's call them Homer, Bart and Lisa),
> all running XP Pro SP3, all wired ethernet connections and all updated.
> All can access the internet through the router and all of them can (or
> could) see each other/transfer files etc., on the workgroup WORKGROUP.
>
> Now, for whatever reason, Homer (the desktop) cannot be seen by the other
> two, nor can it see them. More puzzling, when I look in My Network Places
> on Homer and click on View Workgroup Computers, it doesn't even list
> itself in there, which it normally should do. I'm actually
> posting/browsing from Homer now, proving that I've got access to the
> outside world but I can't get to my LAN from here.
>
> Any further ideas?
>
> TIA,
>
> Pete
>
> Jack-MVP wrote:
>> Hi
>> Keep running the Network wizard when there is malfunction does not
>> make things no better.
>> Maybe this can Help, Make sure that the Software Firewall on each
>> computer allows free local traffic. If you use 3rd party Firewall On,
>> Vista/XP Native Firewall should be Off, and the active Firewall has
>> to adjusted to your Network IP numbers on what is some time called
>> the Trusted Zone (consult your 3rd Party Firewall instructions.
>> General example, http://www.ezlan.net/faq#trusted
>> Vista File and Printer Sharing-
>> http://technet.microsoft.com/en-us/l.../bb727037.aspx
>> Windows XP File Sharing -
>> http://support.microsoft.com/default...b;en-us;304040
>> http://support.microsoft.com/default...b;en-us;304040
>> Printer Sharing XP -
>> http://www.microsoft.com/windowsxp/u...utt_july2.mspx
>> Windows Native Firewall setting for Sharing XP -
>> http://support.microsoft.com/kb/875357
>> Windows XP patch for Sharing with Vista (Not need for XP-SP3) -
>> http://support.microsoft.com/kb/922120
>> Note: Every thing need to be checked, thinking that because it worked
>> before, or and because One did not do any thing means that there is No
>> reason to check all the settings is a misleading approach.
>> Jack (MVP-Networking).
>>
>>
>> "Ripper" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>> I have 2 desktops, 1 Vista Biz, 1 XP Pro and 3 laptops, 2 Vista Home
>>> Premium, 1 XP Pro. All have latest service packs and updates. All
>>> connected (laptops wirelessly) all working and seeing each other
>>> (for months) - until today at about 3 pm. All of sudden the two XP
>>> machines can't find MSHOME. "MSHOME is not accessible. You might not
>>> have permissions to use this
>>> network resource. Contact the admin of this server to find out if
>>> you have access permissions. The network path was not found."
>>>
>>> The XP laptop has 2 mapped drives to directories on the XP desktop
>>> and 1 to the Vista Biz machine. One of the mapped drives continued
>>> to work even after I got the error message, but now it doesn't work.
>>> All machines have ZoneAlarm Free; I shut it down on the two XP
>>> machines with no change. Rebooted everything several times. I can
>>> log into the router from the suspect machines and all machines can
>>> ping each other, but that pesky MSHOME just won't show on the 2 XP
>>> machines. I'm scanning both with AVG presently but it's just finding
>>> cookies. I'm not sure what to check for because I know I have the
>>> connection and all the machines can access the internet too. I reran
>>> the network setup wizard again on the suspect machines with no
>>> change. Please help! Rip
>
>
Similar Threads
Linear Mode
