That is how DHCP was designed to work. Simply plugging a device into the
network and booting it up gets you a network config. If the DHCP scope
includes a default gateway and DNS setting, you have Internet access.
If you want to impose restrictions on what a particular client can do,
you need to look at some other security system.
"Bruce" <(E-Mail Removed)> wrote in message
news:72A24A54-BF1C-4FA6-8589-(E-Mail Removed)...
> ok my point is this....right now my network is "open" aka you can plug in
> a
> cat 5 and you can access the internet. You can not access the network as
> that
> is locked down. Now for some this may not be a big thing and for my
> personal
> network and my friend no big deal. I am looking to fit this for my
> knowledge
> base, an example why this would be important. employee is bringing in his
> laptop and d/ling at a clients site simply by plugging in. by passing all
> set
> limits etc and slowing the works down. Oh well guess I am back to more
> reading as I can not find a white paper or anything. It seems this is one
> of
> those things that it is given people know how to configure to avoid.
>
> Bruce
>
> "Bill Grant" wrote:
>
>> This may also be a stupid question, but how does your "friend" access
>> your
>> network? Why can't you pull the plug?
>>
>> "Bruce" <(E-Mail Removed)> wrote in message
>> news:BF0A1F82-F4CD-4A55-8C08-(E-Mail Removed)...
>> > This may be a stupid question, but I have a friend who has connected to
>> > my
>> > server 03 network and can access the internet via my nat enabled 02 r2
>> > server. I have hunted for the security setting to stop this from
>> > happening
>> > or
>> > at least throttle him back. HELP?
>> >
>> > Bruce
>>
>>
>>
|