Jaime,
Thank you for your share. Youhave blown 3years of confusion on my part right into the dirt! Nope, not worrying about machine unique 'shares.' That is a separate bucket of snakes.
I got it, and, it makes so much sense to me ATM.
TNX,
Duncan

On 09/19/2013 18:17, Jamie Furtner wrote:
On 2013-09-19 3:56 PM, DSinc wrote:
All of my Brother's LAN clients appear to be: WORKGROUP=MSHOME. Is
this an OS default?
I do know how to change this value. And, all of my Brother's clients
are set to get their network specs
automatically - the MS Default (like from his router). Fine.

When he brings his laptop to my home once a year, he can somehow get
to the internet via my router, but he
can not get to any of my other LAN services/PC's//appliances. Odd. I
used to admin his laptop 'into' my LAN, but this
never really fixed everything. Confusing?

Is WORKGROUP= ? a router DHCP assigned value?
I have recently turned on my router's DHCP server, and the logic seems
to work fine.

My home LAN and all of my PC clients us WORKGROUP=WORKGROUP (probably
from back in Win2K times).
All of my PC's and appliances work just fine.

If this makes little sense, I apologize. I just had to ask.
Duncan

Workgroup is not something a router sets (at all - it's not a property
of a DHCP scope), instead it's statically set in System properties. What
its intention was to have a collection of computers that are on the same
network and share resources, but not in a corporate domain (Active
Directory). It's an arbitrary name you assign, and on new installs I
believe the default is WORKGROUP, but I've seen MSHOME on some people's
machines - it might be a default in the non-pro edition of Windows.

Workgroups have always been slightly imperfect in my experience - what's
supposed to happen is that machines broadcast to find all the other
machines in the same workgroup and show them in network neighbourhood.
I've occasionally found that some machines don't respond or are never
browsable via network neighbourhood, but you should still be able to
navigate to your other machines using the a syntax like \\MACHINENAME or
\\<IP.ADDRESS>. Don't forget that newer operating systems may not turn
on sharing by default, and depending on the sharing model (Simple or
not) it still may not work even if you navigate directly to the machines
- everything has to use the same model I think.

Jamie


Reply via email to