RE: GMC Network

[Jorge Gomes Silva <jgs plurimarketing pt>]

On Segunda-feira, 28 de Dezembro de 1998 21:01, Brandon S. Allbery 
[SMTP:allbery@hilfy.ece.cmu.edu] wrote:
> In message <6FFC44A65DE7D111B05400600890447C04BD40@ex01.bhi-erc.com>, 
"Fox, Kev
> in M" writes:
> +-----
> | I am sorry if the "must" offends you but to be an enterprise wide 
operating
> | system unfortunatly it is a requirement. :(
> +--->8
>
> Large companies do not use Network Neighborhood, because it requires that 
> Windows boxes spew all over the network on a short schedule.  Small 
companies
> use it because they don't know better or they have so little network 
usage
> that a bunch of Windows boxes spamming the network every 30 seconds isn't 
> noticed.
You are wrong. That is true if you are running your Windows network over 
NetBEUI. However if the network runs over TCP/IP (and this is what "large 
companies" usually have) you can use WINS. WINS is a kind of dynamic DNS 
where windows machines register not only their name and ip addresses but 
also the services they provide (Server service, etc.). That, combined with 
other mechanisms which I won't explain here (Master Browsers, Domain Master 
Browser, etc.) allow for a machine to see the network neighborhood or 
connect to a network resource by consulting a limited number of machines 
(without broadcasting on the network).

But you have one point here. In many cases companies don't want to their 
employees to know what machines are available on their networks. In that 
case it is possible (even though it may not work very well) to configure 
user machines to have no access to "Network Neigborhood". This is a point 
Gnome ppl may want to be aware of.

I worked for some time with windows networks (but I'm free now) and 
customers always wanted to limit their users ability to destroy their 
systems and networks. Usually this would mean: no desktop icons, from Start 
Menu allow only access to  a limited number of apps and Explorer, in 
Explorer allow only access to C: and their home directory on the network 
(no access to A: !!! ), etc.. Network profiles were also an important 
requisite because most of the times ppl wanted to be able to logon at any 
workstation and see exactly the same environment as if they were at their 
station. Windows would allow this via network policy files, network 
profiles and login scripts (as you may expect this wouldn't work very well 
many times).

Just some food for though.

Jorge.

>
> If *you* (not enterprises!  reread the above sentence) want it so badly, 
write
> it and contribute it back.  Don't bother trying to pressure anyone on the 
> list.  (And indeed, you're not "suggesting", you're trying to pressure 
the
> list.)
>
> --
> brandon s. allbery	[os/2][linux][solaris][japh]	 allbery@kf8nh.apk.net
> system administrator	     [WAY too many hats]	   allbery@ece.cmu.edu
> electrical and computer engineering					 KF8NH
> carnegie mellon university	      ["God, root, what is difference?" -Pitr]
>
>
>
> --
>         FAQ: Frequently-Asked Questions at http://www.gnome.org/gnomefaq
>          To unsubscribe: mail gnome-list-request@gnome.org with
>                        "unsubscribe" as the Subject.