🚀 go-pugleaf

In article <41ls86$mtp@news2.deltanet.com>, jlundgre@delta1.deltanet.com 
says...
>
>Chris"Big-Kahuna"Rampson (rampson@ave050.ve.ford.com) penned:
>: MMIKEMC@IBM.NET wrote:
>: : In article <4197er$c84@bug.rahul.net>, Bill Moyer <ttk@rahul.net> 
wrote:
>: : >  Hrm..  In my past experiences with big corps, the average workers
>: : >install stuff in their own PC's themselves whenever they have the 
>: : >chance.  They (rightfully) don't trust MIS with a rubber band, let
>: : >alone tinkering around the insides of their PC's.  It's the manage-
>: : >ment that insists that hardware changes go through "proper 
channels"
>: : >and leave a paper trail.
>
>: : I can certify this is true where I work (2000+ local employees, 
17,000+ 
>: : globally); I've added a different hard-drive, set-up TCP/IP LAN 
internet 
>: : connection, installed new drivers and an updated OS on my work 
machine 
>: : because:
>: : a. MIS folks were too busy to be bothered
>: : b. wanted to make it more complicated than necessary
>: : c. MIS procedures cause way too long a waiting time before work can 
be done
>: : d. didn't know how
>
>: Where I work, the support people (myself) set up everything and handle 
all
>: of the problems. The biggest problems are created by users that 
"monkey"
>: with their systems. The service is prompt enough and the system works.
>
>That's the way I see it, too.  We have a couple thousand workstations.
>
>: --
>--

If either of you were users on my lan... i'd take you to Human Resources!
Unless you have total knowledge on the lan.. you could be exceeding
distance and station rules. Also, assigning your own ip address is a 
bad BAD practice. If my sinffer ever picked up a station out of my
subnet transmitting on my lan, id shut the port down in a heart beat.
There is a mehod to the madness.. you try to manage a large lan sometime.
Lets see what methods you use to control renegade users like yourself.


-GiGo