Forget Network Places. Nobody ever browses to everybody else's machine on
the LAN anyway. The "Naming" should still work even without Network Places
working because the WINS Server should take care of that part.
Distribute "Shortcuts" based on UNC pathes to all the users. The Shortcuts
will point to the Machines that contain the shares they are supposed to get
to. There should *not* be a lot of these machines. If there are a lot of
these machines,...then that is your first serious mistake.
If Naming does not work than use IP#s in the Shortcuts instead of the
machine name.
Until you have a DC and a real Windows Forest\Domain there is no point in
getting "nit-picky" about how this gets done in the meantime.
--
Phillip Windell
www.wandtv.com
The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------
"MattN" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Ahh ok no I dont have a DC setup...
> Is there not a way at all to work around this witha 3rd party tool??
>
> Thanks
>
>
>
> On Fri, 9 May 2008 09:36:41 +1000, "Bill Grant" <not.available@online>
> wrote:
>
>> Do you have at least one DC? You can't do this without one. Only a DC
>>has the ability to handle merging browse lists.
>>
>> As long as you have a DC somewhere you should be able to get a
>>network-wide browse list if you are running WINS and all machines are set
>>to
>>use WINS.
>>
>> The other thing which can cause trouble is using a DC as a VPN server.
>>
>>"MattN" <(E-Mail Removed)> wrote in message
>>news:(E-Mail Removed). ..
>>> Have successfully setup a VPN connection between two offices and can
>>> ping both devices in both locations.
>>>
>>> Problem is I want to enable the users to open my networks and be able
>>> to browse the other subnet devices...
>>>
>>> From my limited understanding I setup a WINS server in the HQ where
>>> all tunnels are connecting to..then I put in the wins address for all
>>> remote pcs connecting to the HQ network..
>>>
>>> But this does not appear to work...as the users still cant see the
>>> other devices in the network group..
>>>
>>> ANy ideas??
>>>
>>> XP and W2003 servers