<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://port25.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Infrastructure Management and Strategic Design: Part 2 – Driving Network Efficiencies</title><link>http://port25.technet.com/archive/2006/06/16/Infrastructure-Management-and-Strategic-Design_3A00_-Part-2-_1320_-Driving-Network-Efficiencies.aspx</link><description>Every computing device in existence today lives and breathes on some sort of a Network. Doesn’t matter if your Home PC is connected to a Cable Modem or if you’re office laptop is part of an extended WAN, your device is persistently living and breathing</description><dc:language>en</dc:language><generator>CommunityServer 2007.1 (Build: 40109.1145)</generator><item><title>wan accelerators</title><link>http://port25.technet.com/archive/2006/06/16/Infrastructure-Management-and-Strategic-Design_3A00_-Part-2-_1320_-Driving-Network-Efficiencies.aspx#23172</link><pubDate>Mon, 12 Jan 2009 10:10:06 GMT</pubDate><guid isPermaLink="false">af7480c4-26b7-468d-87b0-2acebabb473d:23172</guid><dc:creator>wan accelerators</dc:creator><description>&lt;p&gt;Internet Security and Acceleration (ISA) Server 2004 Standard Edition Service Pack 1 (SP1) offers updates and improvements to ISA Server 2004 Standard Edition.&lt;/p&gt;
&lt;img src="http://port25.technet.com/aggbug.aspx?PostID=23172" width="1" height="1"&gt;</description></item><item><title>The actual problem is more complicated</title><link>http://port25.technet.com/archive/2006/06/16/Infrastructure-Management-and-Strategic-Design_3A00_-Part-2-_1320_-Driving-Network-Efficiencies.aspx#2656</link><pubDate>Thu, 22 Jun 2006 15:20:17 GMT</pubDate><guid isPermaLink="false">af7480c4-26b7-468d-87b0-2acebabb473d:2656</guid><dc:creator>einhverfr</dc:creator><description>Hi Kishi,&lt;br&gt;&lt;br&gt;Imagine running a network where both the intranet and internet links run a variety of network protocols including:&lt;br&gt;&lt;br&gt;1) &amp;nbsp;Latency-sesitive high-bandwith applications such as VOIP.&lt;br&gt;2) &amp;nbsp;Intermittant, high bandwidth applications such as downloading Linux ISO's.&lt;br&gt;&lt;br&gt;Add to this a large number of protocols on the intranet such as NFS and X11 and you can see that this can be a management issue.&lt;br&gt;&lt;br&gt;I don't actually think that auditing is normally the solution. &amp;nbsp;Rather it is important to understand the nature of the biggest offenders and plan for them. &amp;nbsp;Obviously in the case of VOIP, if you don't plan, you *will* eventually get jitter and poor voice quality. &amp;nbsp;This means that *all* internal routers and gateways between the internet and intranet must support QoS and have this effectively managed. &amp;nbsp;All unplanned-for-protocol can go through a default queue where they are not expected to be latency-sensitive. &amp;nbsp;Then when a problem occurs you have &amp;nbsp;pretty good idea of what is causing the problem but it is limited to that one application (and you can add a queue for it or move it to a different queue).&lt;br&gt;&lt;br&gt;Best Wishes,&lt;br&gt;Chris Travers&lt;br&gt;Metatron Technology Consulting&lt;img src="http://port25.technet.com/aggbug.aspx?PostID=2656" width="1" height="1"&gt;</description></item></channel></rss>