<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>The Network Technician &#187; Cisco</title>
	<atom:link href="http://www.thenetworktechnician.com/category/cisco/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thenetworktechnician.com</link>
	<description>IT Management, Technology, Microsoft, Cisco &#38; All Else that Runs Through the Interwebz</description>
	<lastBuildDate>Fri, 27 Aug 2010 03:14:00 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>User VLAN Do Not Acquire DHCP Address</title>
		<link>http://www.thenetworktechnician.com/2009/12/user-vlan-do-not-acquire-dhcp-address/</link>
		<comments>http://www.thenetworktechnician.com/2009/12/user-vlan-do-not-acquire-dhcp-address/#comments</comments>
		<pubDate>Tue, 08 Dec 2009 17:00:30 +0000</pubDate>
		<dc:creator>The Network Technician</dc:creator>
				<category><![CDATA[Cisco]]></category>
		<category><![CDATA[ccnp]]></category>
		<category><![CDATA[networking]]></category>

		<guid isPermaLink="false">http://www.thenetworktechnician.com/?p=417</guid>
		<description><![CDATA[When configuring VLANs on a layer 3 Cisco switch we often tend to segment our network by grouping devices in certain VLANs for security/departmental/geographical purposes. Enabling inter-VLAN routing allows all the devices on different VLANs to communicate with each other. If you&#8217;ve placed DHCP devices on a VLAN separate from the DHCP server you&#8217;ll notice [...]


Related posts:<ol><li><a href='http://www.thenetworktechnician.com/2009/09/how-to-configure-a-router-on-a-stick/' rel='bookmark' title='Permanent Link: How To Configure a Router-on-a-Stick'>How To Configure a Router-on-a-Stick</a></li>
<li><a href='http://www.thenetworktechnician.com/2009/10/5-easy-steps-to-securing-your-cisco-switch-or-router/' rel='bookmark' title='Permanent Link: 5 Easy Steps to Securing Your Cisco Switch or Router'>5 Easy Steps to Securing Your Cisco Switch or Router</a></li>
<li><a href='http://www.thenetworktechnician.com/2009/10/virtual-lans-notes/' rel='bookmark' title='Permanent Link: Virtual LANs Notes'>Virtual LANs Notes</a></li>
</ol>]]></description>
			<content:encoded><![CDATA[<p></p><p>When configuring VLANs on a layer 3 Cisco switch we often tend to segment our network by grouping devices in certain VLANs for security/departmental/geographical purposes.</p>
<p>Enabling inter-VLAN routing allows all the devices on different VLANs to communicate with each other.</p>
<p>If you&#8217;ve placed DHCP devices on a VLAN separate from the DHCP server you&#8217;ll notice that those devices will not receive an IP address.</p>
<p>For example, your DHCP server is on VLAN 2 and your users are on VLAN 3. To allow your users&#8217; computers to acquire an IP address from the DHCP server on VLAN 2 you&#8217;ll have to configure the ip helper-address command on VLAN 3:</p>
<p>Enter VLAN 3 interface configuration</p>
<pre>conf t
int vlan 3</pre>
<p>configure the ip helper-address command to point to your DHCP server</p>
<pre>ip helper-address 192.168.1.5
exit</pre>
<p>When the DHCP devices on VLAN 3 send a broadcast over the network for DHCP, VLAN 3 will forward this request to 192.168.1.5. Be sure to replace 192.168.1.5 with your own DHCP server.</p>


<p>Related posts:<ol><li><a href='http://www.thenetworktechnician.com/2009/09/how-to-configure-a-router-on-a-stick/' rel='bookmark' title='Permanent Link: How To Configure a Router-on-a-Stick'>How To Configure a Router-on-a-Stick</a></li>
<li><a href='http://www.thenetworktechnician.com/2009/10/5-easy-steps-to-securing-your-cisco-switch-or-router/' rel='bookmark' title='Permanent Link: 5 Easy Steps to Securing Your Cisco Switch or Router'>5 Easy Steps to Securing Your Cisco Switch or Router</a></li>
<li><a href='http://www.thenetworktechnician.com/2009/10/virtual-lans-notes/' rel='bookmark' title='Permanent Link: Virtual LANs Notes'>Virtual LANs Notes</a></li>
</ol></p>]]></content:encoded>
			<wfw:commentRss>http://www.thenetworktechnician.com/2009/12/user-vlan-do-not-acquire-dhcp-address/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Cisco ASA Site-to-Site VPN Dropped Connection</title>
		<link>http://www.thenetworktechnician.com/2009/05/cisco-asa-site-to-site-vpn-dropped-connection/</link>
		<comments>http://www.thenetworktechnician.com/2009/05/cisco-asa-site-to-site-vpn-dropped-connection/#comments</comments>
		<pubDate>Fri, 29 May 2009 18:55:57 +0000</pubDate>
		<dc:creator>The Network Technician</dc:creator>
				<category><![CDATA[Cisco]]></category>

		<guid isPermaLink="false">http://www.thenetworktechnician.com/?p=24</guid>
		<description><![CDATA[On random, rare, occasions one of our offices will drop off the face of the Earth. After troubleshooting with users in that office, you&#8217;ll find that there is always one symptom: They can browse the web but cannot access any network resources in the company. What will work 99% of the time is entering these [...]


No related posts.]]></description>
			<content:encoded><![CDATA[<p></p><p>On random, rare, occasions one of our offices will drop off the face of the Earth. After troubleshooting with users in that office, you&#8217;ll find that there is always one symptom:</p>
<p>They can browse the web but cannot access any network resources in the company.</p>
<p>What will work 99% of the time is entering these two commands into your Cisco ASA firewall:</p>
<pre class="brush: plain;">

clear crypto isakmp sa
clear crypto ipsec sa
</pre>
<p>What these two lines of code will do is drop ALL site-to-site vpn connections and rebuild the tunnels.<br />
It takes about a minute or so for everything to start working again but these two commands have saved me time and again.</p>


<p>No related posts.</p>]]></content:encoded>
			<wfw:commentRss>http://www.thenetworktechnician.com/2009/05/cisco-asa-site-to-site-vpn-dropped-connection/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
