Re: How Do I Keep Private Computers Off of Our Network?
- From: razor <razor@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 24 Jan 2007 11:20:01 -0800
About 100.
"kj" wrote:
I suspect a viable solution would depend upon the scale of your.
environement. How many workstations & locations do you have?
--
/kj
"razor" <razor@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:90D42BA3-F201-434D-AA45-7BCE5531123B@xxxxxxxxxxxxxxxx
Ah, thanks. I just stumbled across the fact that somone had done this. I
am
not sure how I can set up some kind of an alert if they try it
again--other
than just checking every day.
sd
"kj" wrote:
If you have managed switches you can in most cases restrict their ability
to
connect to the network.
When you determine the MAC address of the personal laptop and you are
using
DHCP, you can set up a "Reservation" that gives the laptop totally bogus
lease values and discourage future use. 802.1x is the effective method
for
this, but time consuming to setup and hardware capable dependant.
--
/kj
"razor" <razor@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:92848A13-4227-4EB3-98C3-2E27C6D1A9D1@xxxxxxxxxxxxxxxx
Thanks. This is an employee that has done this arleady, and we are
trying
to
locate them if they do it again. What we believe is happening is that
they
are using their business computer's wired connection to connect their
personal laptop. I was just wondering if they did it again if there was
a
way
to trace where the connection took place?
sd
"Al Mulnick" wrote:
NAC is a term that is often bandied about when trying to do this; have
a
look for that term and check with your network vendor to get more
details.
Controlling ethernet drops (or token ring for that matter) at the wall
plate
by leaving them all off unless otherwise instructed has worked fairly
well
for many but doesn't preven the really dedicated from unplugging one
and
then introducing the next. Using secured wireless networks is
helpful
but
users sometimes have a tendency to find out the ssid and giving it
out;
they
should be shot but there are apparently some laws against that. (I'm
kidding
although penalties should be stiff.) Those kinds of things prevent
people
from connecting to your network.
Al
"razor" <razor@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:586908AB-9C45-4C6B-B00E-CEFB0CC0FEEE@xxxxxxxxxxxxxxxx
Hello--
I was going through some routine systems managment when I saw that
someone
had connected a personal computer to our network--where it created
an
unrecognized workgroup name.
We sent out an email instructing everyone not to do this in the
future,
but
wondered if there are any monitoring or other utilities that we can
implement
that will notify us when this happens again, and what instructions
we
can
use
to take some action...
Any ideas or help is appreciated.
Thanks,
sd
- Follow-Ups:
- References:
- Prev by Date: Re: kerberos authentication with new DST
- Next by Date: Re: active directory in win2003 : accessing users & computers
- Previous by thread: Re: How Do I Keep Private Computers Off of Our Network?
- Next by thread: Re: How Do I Keep Private Computers Off of Our Network?
- Index(es):
Relevant Pages
|
