<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0" xmlns:blogChannel="http://backend.userland.com/blogChannelModule">

<channel>
<title>[HELP] Internet restriction in LAN in Cisco</title>
<link>http://www.dslreports.com/forum/r20864675</link>
<description></description>
<language>en</language>
<pubDate>Wed, 11 Nov 2009 11:39:14 EDT</pubDate>
<lastBuildDate>Wed, 11 Nov 2009 11:39:14 EDT</lastBuildDate>

<item>
<title>Re: [HELP] Internet restriction in LAN</title>
<link>http://www.dslreports.com/forum/remark,20869742</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : 802.1x(wired or wireless), dynamic vlans with VMPS, Cisco NAC...  to name a few, though 802.1x sounds like it fits your scenario best.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20869742</guid>
<pubDate>Tue, 29 Jul 2008 23:17:17 EDT</pubDate>
</item>

<item>
<title>Re: [HELP] Internet restriction in LAN</title>
<link>http://www.dslreports.com/forum/remark,20866724</link>
<description><![CDATA[<A HREF="/useremail/u/1455989"><b>Euphrates</b></A> : Well, I believe you could configure Active Directory to issue only a certain block of ip ranges to Active Directory computers and then have the DHCP Server (probably running on the DC) issue out another range of ip addresses to "other" computers not a part of Active Directory.  Once done, then the configuration on the router is a simple access list denying internet access to the non-Active Directory range of ip addresses.<br><br>This is a quick and dirty solution, but should work.  However, because it isn't relying on Active Directory on the router side, it can be bypassed.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20866724</guid>
<pubDate>Tue, 29 Jul 2008 14:26:48 EDT</pubDate>
</item>

<item>
<title>Re: [HELP] Internet restriction in LAN</title>
<link>http://www.dslreports.com/forum/remark,20865012</link>
<description><![CDATA[<A HREF="/useremail/u/676954"><b>aryoba</b></A> : Are you referring to MS Active Directory Domain? If yes, then the management setup you are looking for should be centralized on the Domain Controller. In addition, you may need external authentication server such as RADIUS to restrict which destination IP addresses certain users can or cannot access.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20865012</guid>
<pubDate>Tue, 29 Jul 2008 08:46:07 EDT</pubDate>
</item>

<item>
<title>[HELP] Internet restriction in LAN</title>
<link>http://www.dslreports.com/forum/remark,20864675</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : hi, <br><br>i want to configure my LAN so that only those PCs which are registered in Domain and are logged through Domain can access the internet and LAN resources, the rest of the users which are logged to their PC as local user should not be able even to get IP from DHCP and use static IP given manually to their PC for accessing any thing on the LAN.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20864675</guid>
<pubDate>Tue, 29 Jul 2008 05:55:32 EDT</pubDate>
</item>

</channel>
</rss>
