<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss' xmlns:gd='http://schemas.google.com/g/2005' xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-3312932509559653332</id><updated>2011-11-27T15:19:45.379-08:00</updated><category term='WWAN'/><title type='text'>Networking</title><subtitle type='html'></subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://thenetworkingworld.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3312932509559653332/posts/default?max-results=100'/><link rel='alternate' type='text/html' href='http://thenetworkingworld.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><author><name>piyush b</name><uri>http://www.blogger.com/profile/08681531766322786460</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>4</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>100</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-3312932509559653332.post-1245628951663588687</id><published>2007-12-31T10:42:00.000-08:00</published><updated>2007-12-31T10:59:22.669-08:00</updated><title type='text'>Campus Wide Area Network</title><content type='html'>&lt;table style="width: 573px; height: 1283px;" class="menu_table" id="table3" border="0" cellpadding="2" cellspacing="0"&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td valign="top" width="300"&gt;&lt;p align="center"&gt;&lt;span style=";font-family:Arial;font-size:130%;"  &gt;&lt;b&gt;A Campus wide area    network&lt;/b&gt;&lt;/span&gt;&lt;/p&gt; &lt;p align="justify"&gt;&lt;span style="font-family:Arial;"&gt;The diagram opposite &lt;/span&gt;&lt;span style="font-family:Arial;"&gt;shows a typical  campus wide area network.&lt;span style="font-weight: bold;"&gt; &lt;/span&gt;&lt;br /&gt;The buildings are connected together using a variety  of different&lt;br /&gt;methods including fibre-optic and wireless links.&lt;/span&gt;&lt;/p&gt; &lt;p align="justify"&gt;&lt;span style="font-family:Arial;"&gt;Although the diagram opposite is not an  exact representation of the&lt;br /&gt;University of Wales Aberystwyth network, it does show the  type of&lt;br /&gt;wide area network backbone connections currently in use.&lt;/span&gt;&lt;/p&gt;   &lt;p align="justify"&gt;&lt;span style="font-family:Arial;"&gt;A wide area network or WAN is a    computer network covering a wide&lt;br /&gt;geographical area involving a vast    array of computers. This is&lt;br /&gt;different from personal area networks    (PAN's), metropolitan area&lt;br /&gt;networks (MAN's) or local area networks    (LAN's) which are usually&lt;br /&gt;limited to a room, building or campus.&lt;/span&gt;&lt;/p&gt;   &lt;p align="justify"&gt;&lt;span style="font-family:Arial;"&gt;Typically, a WAN consists of two    or more local-area networks (LANs).&lt;br /&gt;Computers connected to a wide-area    network are often connected&lt;br /&gt;through public networks, such as the    telephone system. They can also&lt;br /&gt;be connected through leased lines    usually fibre-optic cables or satellites.&lt;br /&gt;The largest WAN in existence    is the Internet.&lt;/span&gt;&lt;/p&gt;   &lt;p align="justify"&gt;&lt;span style="font-family:Arial;"&gt;WANs are normally built for    individual private organizations including&lt;br /&gt;Internet service providers    (ISP's).    The ISP provides connections from&lt;br /&gt;an    organization's LAN to the Internet, a router connects to the LAN&lt;br /&gt;on one    side and a hub/switch within the WAN on the other.&lt;/span&gt;&lt;img src="http://www.inf.aber.ac.uk/ns3/networking/network-operations/images/network%20diagrams/a%20campus%20network.jpg" usemap="#FPMap0" style="border: 1px solid rgb(128, 128, 128); width: 419px; height: 834px;" alt="campus wide area network diagram" align="middle" border="1" /&gt;&lt;/p&gt;&lt;/td&gt;   &lt;td width="8"&gt;&lt;br /&gt;&lt;/td&gt;   &lt;td valign="top" width="629"&gt;&lt;!-- START MAIN BODY --&gt;   &lt;img alt="" src="http://www.inf.aber.ac.uk/ns3/networking/network-operations/images/network%20diagrams/1x1_tran.gif" height="10" width="1" /&gt; &lt;!-- START Table to hold main body content --&gt;   &lt;img alt="" src="http://www.inf.aber.ac.uk/ns3/networking/network-operations/images/network%20diagrams/1x1_tran.gif" height="10" width="1" /&gt;   &lt;map name="FPMap0"&gt;&lt;area target="_top" coords="83, 83, 155, 162" shape="rect" href="http://www.inf.aber.ac.uk/ns3/networking/network-operations/building_backbone.asp"&gt;&lt;area target="_top" coords="525, 65, 592, 139" shape="rect" href="http://www.inf.aber.ac.uk/ns3/networking/network-operations/building_backbone.asp"&gt;&lt;area target="_top" coords="170, 161, 208, 199" shape="rect" href="http://www.inf.aber.ac.uk/ns3/networking/network-operations/fibre_network.asp"&gt;&lt;area target="_top" coords="294, 188, 337, 227" shape="rect" href="http://www.inf.aber.ac.uk/ns3/networking/network-operations/fibre_network.asp"&gt;&lt;area target="_top" href="http://www.inf.aber.ac.uk/ns3/networking/network-operations/fibre_network.asp" shape="rect" coords="469, 212, 511, 252"&gt;&lt;area target="_top" href="http://www.inf.aber.ac.uk/ns3/networking/network-operations/network_monitoring_and_admin.asp" shape="rect" coords="274, 237, 364, 317"&gt;&lt;area target="_top" coords="121, 281, 171, 321" shape="rect" href="http://www.inf.aber.ac.uk/ns3/networking/network-operations/fibre_network.asp"&gt;&lt;area target="_top" href="http://www.inf.aber.ac.uk/ns3/networking/network-operations/fibre_network.asp" shape="rect" coords="396, 289, 438, 330"&gt;&lt;area target="_top" href="http://www.inf.aber.ac.uk/ns3/networking/network-operations/laser_and_wireless_links.asp" shape="rect" coords="95, 373, 170, 485"&gt;&lt;area target="_top" href="http://www.inf.aber.ac.uk/ns3/networking/network-operations/laser_and_wireless_links.asp" shape="rect" coords="31, 547, 220, 687"&gt;&lt;area target="_top" href="http://www.inf.aber.ac.uk/ns3/networking/network-operations/fibre_network.asp" shape="rect" coords="285, 400, 336, 447"&gt;&lt;area target="_top" href="http://www.inf.aber.ac.uk/ns3/networking/network-operations/laser_and_wireless_links.asp" shape="rect" coords="479, 305, 566, 402"&gt;&lt;area target="_top" coords="277, 645, 376, 758" shape="rect" href="http://www.inf.aber.ac.uk/ns3/networking/network-operations/computer_backups.asp"&gt;&lt;area target="_top" href="http://www.inf.aber.ac.uk/ns3/networking/network-operations/laser_and_wireless_links.asp" shape="rect" coords="482, 604, 568, 738"&gt;&lt;area href="http://www.inf.aber.ac.uk/ns3/networking/network-operations/fibre_network.asp" shape="rect" coords="202, 740, 251, 790"&gt; &lt;/map&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3312932509559653332-1245628951663588687?l=thenetworkingworld.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://thenetworkingworld.blogspot.com/feeds/1245628951663588687/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=3312932509559653332&amp;postID=1245628951663588687' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3312932509559653332/posts/default/1245628951663588687'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3312932509559653332/posts/default/1245628951663588687'/><link rel='alternate' type='text/html' href='http://thenetworkingworld.blogspot.com/2007/12/campus-wide-area-network.html' title='Campus Wide Area Network'/><author><name>piyush b</name><uri>http://www.blogger.com/profile/08681531766322786460</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3312932509559653332.post-8111394901777478348</id><published>2007-12-26T05:03:00.000-08:00</published><updated>2007-12-26T05:14:52.523-08:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='WWAN'/><title type='text'>Wireless Wide Area Network(WWAN)</title><content type='html'>&lt;p&gt; Once you begin using wireless data, you'll wonder how you ever lived without it. Wireless data gives you the freedom to work from almost anywhere and gives you access to personal information when you are on the go. Whether the wireless sytem is accessing e-mail from an airport or receiving dispatch instructions as a taxi driver, you'll find it extremely effective to be able to maintain a data connection with a remote network from almost anywhere. &lt;/p&gt;&lt;p&gt;Radio communications has been with us for a long time, with analog voice as the principal application. Today, tens of millions of people in the United States are using two-way radio for point-to-point or point-to-multipoint voice communications. Although engineers have known for some time how to modulate a radio signal to send binary data, only recently have they been able to develop and deploy wireless data services on a large comme rcial scale. &lt;/p&gt;&lt;p&gt;Wire or fiber-based data communications spans a huge range of throughputs and distances--28.8 Kbps over a modem connection; 10/100 Mbps over an Ethernet segment; and gigabit speeds over fiber. Similarly, wireless connections span a huge range. The world of wireless data includes fixed microwave links, wireless LANs, data over cellular networks, wireless WANs, satellite links, digital dispatch networks, one-way and two-way paging networks, diffuse infrared, laser-based communications, keyless car entry, the Global Positioning System and more. &lt;/p&gt;&lt;p&gt;The benefits of wireless include connections when no others are possible, connections at lower cost in many scenarios, faster connections, backups to landlines, networks that are much faster to install and data connections for mobile users. That last benefit is the focus of this chapter. &lt;/p&gt;&lt;p&gt;In this chapter, we'll concentrate on wide-area wireless data; a future chapter will discuss wireless LANs. The types of WANs we will examine include cellular-based systems, paging networks and dedicated wireless WANs, such as CDPD, Metricom's Ricochet, ARDIS and RAM Mobile Data. &lt;/p&gt;&lt;p&gt; &lt;img src="http://img.cmpnet.com/nc/netdesign/graphics/wireless1.gif" /&gt;&lt;/p&gt;&lt;p&gt;First, let's walk through a planning process that highlights the key issues in working with wireless data. From there we drill into the technology, including protocols and interfaces, hardware, middleware. Next we survey the various wireless networks. We conclude with some pointers for integrating your wireless solution. &lt;/p&gt;One important distinction in the uses wireless data is between vertical market applications and horizontal market applications. In vertical markets, applications addresses a very specific business need for a particular company or industry. The applications provides a clear benefit through higher productivity or other competitive advantage. Today most wireless applications are in the vertical arena. But wireless vendors strongly desire to address much larger horizontal markets where a broad spectrum of business users and consumers wil l use wireless communications. This transition will occur once wireless communications is inexpensive enough, broadly deployed and easy to use and once a large number of off-the-shelf applications are available.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3312932509559653332-8111394901777478348?l=thenetworkingworld.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://thenetworkingworld.blogspot.com/feeds/8111394901777478348/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=3312932509559653332&amp;postID=8111394901777478348' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3312932509559653332/posts/default/8111394901777478348'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3312932509559653332/posts/default/8111394901777478348'/><link rel='alternate' type='text/html' href='http://thenetworkingworld.blogspot.com/2007/12/wireless-wide-area-networkwwan.html' title='Wireless Wide Area Network(WWAN)'/><author><name>piyush b</name><uri>http://www.blogger.com/profile/08681531766322786460</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3312932509559653332.post-5982958431544695724</id><published>2007-12-24T06:18:00.000-08:00</published><updated>2007-12-24T07:22:44.519-08:00</updated><title type='text'>Configuring WPAD Support for ISA Firewall Web Proxy and Firewall Clients</title><content type='html'>&lt;div id="art-content" class="text-block"&gt;  &lt;p&gt;The Web Proxy Autodiscovery Protocol (WPAD) can be used to allow Web browsers and the Firewall client application to automatically discover the address of the ISA firewall. The client can then download autoconfiguration information from the firewall after the Web Proxy or Firewall client discovers the address. &lt;/p&gt; &lt;p&gt;WPAD solves the problem of automatically provisioning Web browsers. The default setting on Internet Explorer is to autodiscover Web proxy client settings. When this setting is enabled, the browser can issue a DHCPINFORM message or a DNS query to find the address of the ISA firewall from which it can download autoconfiguration information. This greatly simplifies Web browser setup so that it automatically uses the firewall to connect to the Internet.&lt;/p&gt; &lt;p&gt;The ISA firewall’s Firewall client application can also use the wpad entry to find the ISA firewall and download Firewall client configuration information.&lt;/p&gt; &lt;p&gt;In this article&lt;b&gt; &lt;/b&gt;we will discuss the following procedures:&lt;/p&gt; &lt;ul&gt;&lt;li&gt;Configure DHCP WPAD support  &lt;/li&gt;&lt;li&gt;Configure DNS WPAD support&lt;/li&gt;&lt;/ul&gt; &lt;p&gt;After the wpad information is entered into DHCP and DNS, Web Proxy and Firewall clients will not require manual configuration to connect to the Internet through the ISA firewall.&lt;/p&gt; &lt;p align="center"&gt; &lt;/p&gt;&lt;table id="AutoNumber2" align="center" border="2" bordercolor="#111111" cellpadding="4" cellspacing="0"&gt; &lt;tbody&gt; &lt;tr&gt; &lt;td width="100%"&gt; &lt;p align="center"&gt;&lt;strong&gt;Discuss this article&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt; &lt;p align="center"&gt;&lt;a href="http://www.amazon.com/exec/obidos/ASIN/1931836191/wwwshindernet-20" target="_blank"&gt;&lt;img alt="" src="http://www.isaserver.org/img/upl/ISAServer20041179136384389.jpg" align="bottom" border="0" hspace="0" /&gt;&lt;/a&gt;&lt;/p&gt; &lt;h2&gt;Configure DHCP WPAD Support&lt;/h2&gt; &lt;p&gt;The DHCP scope option number 252 can be used to automatically configure Web Proxy and Firewall clients. In order for the DHCP wpad method to work, the Web Proxy or Firewall client computer must be configured as a DHCP client, and the logged on user must be a member of the local administrators group or Power users group (for Windows 2000). On Windows XP systems, the Network Configuration Operators group also has permission to issue DHCP queries (DHCPINFORM messages).&lt;/p&gt; &lt;p&gt;&lt;b&gt;Note:&lt;br /&gt;&lt;/b&gt;For more information about the limitations of using DHCP for autodiscovery for Internet Explorer 6.0, please see KB article &lt;b&gt;Automatic Proxy Discovery in Internet Explorer with DHCP Requires Specific Permissions&lt;/b&gt; at http://support.microsoft.com/default.aspx?scid=kb;en-us;312864 However, if you’ve been good and upgraded to Windows XP SP2, this is no longer a problem. I assume that the problem remains “fixed” in Windows Vista, but I don’t know that for sure. I also assume that the Windows XP SP2 fix also enables Internet Explorer 7.0 to work correct without requiring administrator permissions.&lt;/p&gt; &lt;p&gt;Perform the following steps at the DHCP server to create the custom DHCP option:&lt;/p&gt; &lt;ol&gt;&lt;li&gt;Open the &lt;b&gt;DHCP&lt;/b&gt; console from the &lt;b&gt;Administrative Tools&lt;/b&gt; menu and right click your server name in the left pane of the console. Click the &lt;b&gt;Set Predefined Options&lt;/b&gt; command.  &lt;/li&gt;&lt;li&gt;In the &lt;b&gt;Predefined Options and Values&lt;/b&gt; dialog box, click the &lt;b&gt;Add&lt;/b&gt; button.&lt;/li&gt;&lt;/ol&gt; &lt;p class="Graphic"&gt;&lt;b&gt;&lt;img alt="" src="http://www.isaserver.org/img/upl/image0041197305974116.jpg" align="bottom" border="0" hspace="0" /&gt;&lt;br /&gt;Figure 1&lt;/b&gt;&lt;/p&gt; &lt;ol start="3"&gt;&lt;li&gt;In the &lt;b&gt;Option Type&lt;/b&gt; dialog box, enter the following information:&lt;/li&gt;&lt;/ol&gt; &lt;p&gt;&lt;b&gt;Name:&lt;/b&gt; wpad&lt;/p&gt; &lt;p&gt;&lt;b&gt;Data type:&lt;/b&gt; String&lt;/p&gt; &lt;p&gt;&lt;b&gt;Code:&lt;/b&gt; 252&lt;/p&gt; &lt;p&gt;&lt;b&gt;Description:&lt;/b&gt; wpad entry&lt;/p&gt; &lt;p&gt;Click &lt;b&gt;OK&lt;/b&gt;.&lt;/p&gt; &lt;p&gt;&lt;b&gt;&lt;img alt="" src="http://www.isaserver.org/img/upl/image0061197305974132.jpg" align="bottom" border="0" hspace="0" /&gt;&lt;br /&gt;Figure 2&lt;/b&gt;&lt;/p&gt; &lt;ol start="4"&gt;&lt;li&gt;In the &lt;b&gt;Value&lt;/b&gt; frame, enter the URL to the ISA firewall in the &lt;b&gt;String&lt;/b&gt; text box. The format for this value is:&lt;br /&gt;&lt;br /&gt;&lt;em&gt;http://ISAServername:AutodiscoveryPort Number/wpad.dat&lt;br /&gt;&lt;br /&gt;&lt;/em&gt;The default autodiscovery port number is TCP 80. You can customize this value in the &lt;b&gt;ISA Firewall console&lt;/b&gt;. We will cover this subject in more detail later in this document.&lt;br /&gt;&lt;br /&gt;In the current example, enter the following into the &lt;b&gt;String&lt;/b&gt; text box:&lt;br /&gt;&lt;br /&gt;&lt;em&gt;http://isalocal.msfirewall.org:80/wpad.dat&lt;/em&gt;&lt;br /&gt;&lt;br /&gt;Make sure to enter wpad.dat in all &lt;i&gt;lower case&lt;/i&gt; letters. For more information on this problem, please refer to KB article &lt;a href="http://support.microsoft.com/default.aspx?scid=kb;en-us;307502" target="Blank"&gt;"Automatically Detect Settings" Does Not Work if You Configure DHCP Option 252&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Click &lt;b&gt;OK&lt;/b&gt;.&lt;/li&gt;&lt;/ol&gt; &lt;p&gt;&lt;b&gt;&lt;img alt="" src="http://www.isaserver.org/img/upl/image0081197306027491.jpg" align="bottom" border="0" hspace="0" /&gt;&lt;br /&gt;Figure 3&lt;/b&gt;&lt;/p&gt; &lt;ol start="5"&gt;&lt;li&gt;Right click the &lt;b&gt;Scope Options&lt;/b&gt; node in the left pane of the console and click the &lt;b&gt;Configure Options&lt;/b&gt; command.  &lt;/li&gt;&lt;li&gt;In the &lt;b&gt;Scope Options&lt;/b&gt; dialog box, scroll through the list of &lt;b&gt;Available Options&lt;/b&gt; and put a checkmark in the &lt;b&gt;252 wpad&lt;/b&gt; checkbox. Click &lt;b&gt;Apply&lt;/b&gt; and then click &lt;b&gt;OK&lt;/b&gt;.&lt;/li&gt;&lt;/ol&gt; &lt;p&gt;&lt;b&gt;&lt;img alt="" src="http://www.isaserver.org/img/upl/image0101197306027491.jpg" align="bottom" border="0" hspace="0" /&gt;&lt;br /&gt;Figure 4&lt;/b&gt;&lt;/p&gt; &lt;ol start="7"&gt;&lt;li&gt;The &lt;b&gt;252 wpad&lt;/b&gt; entry now appears in the right pane of the console under the list of &lt;b&gt;Scope Options&lt;/b&gt;.&lt;/li&gt;&lt;/ol&gt; &lt;p&gt;&lt;b&gt;&lt;img alt="" src="http://www.isaserver.org/img/upl/image0121197306027507.jpg" align="bottom" border="0" hspace="0" /&gt;&lt;br /&gt;Figure 5&lt;/b&gt;&lt;/p&gt; &lt;ol start="8"&gt;&lt;li&gt;Close the &lt;b&gt;DHCP &lt;/b&gt;console.&lt;/li&gt;&lt;/ol&gt; &lt;p&gt;At this point DHCP clients will be able to use DHCP wpad support to automatically discover the ISA firewall and subsequently autoconfigure itself. However, the ISA firewall must be configured to support publishing autodiscovery information, which we will do later in this article.&lt;/p&gt; &lt;h2&gt;Configure DNS WPAD Support&lt;/h2&gt; &lt;p&gt;Another method that can be used to deliver autodiscovery information to Web Proxy and Firewall clients is DNS. You can create a wpad alias entry in DNS and allow browser clients to use this information to automatically configure themselves. DNS is a viable option, but you have to be aware that if you have multiple networks, each with it’s own ISA Firewall, then you’ll need to have different wpad entries for each network. While you can support multiple networks and multiple ISA Firewalls using DNS by taking advantage of netmask ordering, most companies perform to use DHCP wpad to support local networks, since they need to use local DHCP server anyway to assign local clients addressing information.&lt;/p&gt; &lt;p&gt;Name resolution is a pivotal component to making this method of Web Proxy and Firewall client autodiscovery work correctly. In this case, the client operating system must be able to correctly fully qualify the name &lt;i&gt;wpad&lt;/i&gt;. The reason for this is that the Web Proxy and Firewall client only knows that it needs to resolve the name wpad; it does not know what specific domain name it should append to the query to resolve the name wpad. We will cover this issue in detail later in this document.&lt;/p&gt; &lt;p&gt;&lt;b&gt;Note:&lt;br /&gt;&lt;/b&gt;In contrast to the DHCP method of assigning autodiscovery information to Web Proxy and Firewall clients, you do not have the option to use a custom port number to publish autodiscovery information when using the DNS method. You must publish autodiscovery information on TCP 80 when using the DNS method.&lt;/p&gt; &lt;p&gt;You need to perform the following steps to configure DNS support for Web Proxy and Firewall client autodiscovery of the ISA firewall:&lt;/p&gt; &lt;ul&gt;&lt;li&gt;Create the wpad entry in DNS  &lt;/li&gt;&lt;li&gt;Configure the client to use the fully qualified wpad alias  &lt;/li&gt;&lt;li&gt;Configure the client browser to use autodiscovery &lt;/li&gt;&lt;/ul&gt; &lt;h2&gt;Create the Wpad Entry in DNS&lt;/h2&gt; &lt;p&gt;The first step is to create a wpad alias entry in DNS. This alias (also known as a CNAME record) points to a Host (A) record for the ISA Server 2004 firewall. The Host (A) record resolves the name of the ISA Server 2004 firewall to the internal IP address of the firewall. I should note her that you don’t have to use a CNAME record, you can use an A record if you like, but CNAME records have some management advantages.&lt;/p&gt; &lt;p&gt;The Host (A) record must be created before you create the CNAME record. If you enable automatic registration in DNS, the ISA firewall’s name and IP address will already be entered into a DNS Host (A) record. If you have not enabled automatic registration, you will need to create the Host (A) record for the ISA firewall yourself. &lt;/p&gt; &lt;p&gt;In the following example, the ISA firewall has automatically registered itself with DNS because the internal interface of the ISA firewall is configured to automatically register with DNS and the DNS server is configured to accept unsecured dynamic registrations. In a production environment, I’d recommend that you only accept secure DNS registrations. This won’t be a problem for your ISA Firewall, since it should be a member of the domain for security reasons.&lt;/p&gt; &lt;p&gt;Perform the following steps on the DNS server on the domain controller on the internal network:&lt;/p&gt; &lt;ol&gt;&lt;li&gt;Click &lt;b&gt;Start&lt;/b&gt; and select &lt;b&gt;Administrative Tools&lt;/b&gt;. Click the &lt;b&gt;DNS &lt;/b&gt;entry. In the &lt;b&gt;DNS&lt;/b&gt; management console, right click on the forward lookup zone for your domain and click the &lt;b&gt;New Alias (CNAME)&lt;/b&gt; command.  &lt;/li&gt;&lt;li&gt;In the &lt;b&gt;New Resource Record&lt;/b&gt; dialog box, enter &lt;b&gt;wpad&lt;/b&gt; in the &lt;b&gt;Alias name (uses parent domain if left blank)&lt;/b&gt; text box. Click the &lt;b&gt;Browse&lt;/b&gt; button.&lt;/li&gt;&lt;/ol&gt; &lt;p class="Graphic"&gt;&lt;b&gt;&lt;img alt="" src="http://www.isaserver.org/img/upl/image0141197306052616.jpg" align="bottom" border="0" hspace="0" /&gt;&lt;br /&gt;Figure 6&lt;/b&gt;&lt;/p&gt; &lt;ol start="3"&gt;&lt;li&gt;In the &lt;b&gt;Browse&lt;/b&gt; dialog box, double click on your server name in the &lt;b&gt;Records&lt;/b&gt; list.&lt;/li&gt;&lt;/ol&gt; &lt;p&gt;&lt;b&gt;&lt;img alt="" src="http://www.isaserver.org/img/upl/image0161197306052616.jpg" align="bottom" border="0" hspace="0" /&gt;&lt;br /&gt;Figure 7&lt;/b&gt;&lt;/p&gt; &lt;ol start="4"&gt;&lt;li&gt;In the &lt;b&gt;Browse&lt;/b&gt; dialog box, double click on the &lt;b&gt;Forward Lookup Zone&lt;/b&gt; entry in the &lt;b&gt;Records&lt;/b&gt; frame.&lt;/li&gt;&lt;/ol&gt; &lt;p&gt;&lt;b&gt;&lt;img alt="" src="http://www.isaserver.org/img/upl/image0181197306052616.jpg" align="bottom" border="0" hspace="0" /&gt;&lt;br /&gt;Figure 8&lt;/b&gt;&lt;/p&gt; &lt;ol start="5"&gt;&lt;li&gt;In the &lt;b&gt;Browse&lt;/b&gt; dialog box, double click on the name of your forward lookup zone in the &lt;b&gt;Records&lt;/b&gt; frame.&lt;/li&gt;&lt;/ol&gt; &lt;p&gt;&lt;b&gt;&lt;img alt="" src="http://www.isaserver.org/img/upl/image0201197306092788.jpg" align="bottom" border="0" hspace="0" /&gt;&lt;br /&gt;Figure 9&lt;/b&gt;&lt;/p&gt; &lt;ol start="6"&gt;&lt;li&gt;In the &lt;b&gt;Browse&lt;/b&gt; dialog box, select the name of the ISA firewall in the &lt;b&gt;Records&lt;/b&gt; frame. Click &lt;b&gt;OK&lt;/b&gt;.&lt;/li&gt;&lt;/ol&gt; &lt;p align="center"&gt; &lt;/p&gt;&lt;table id="AutoNumber2" align="center" border="2" bordercolor="#111111" cellpadding="4" cellspacing="0"&gt; &lt;tbody&gt; &lt;tr&gt; &lt;td width="100%"&gt; &lt;p align="center"&gt;&lt;strong&gt;Discuss this article&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt; &lt;p align="center"&gt;&lt;a href="http://www.amazon.com/exec/obidos/ASIN/1931836191/wwwshindernet-20" target="_blank"&gt;&lt;img alt="" src="http://www.isaserver.org/img/upl/ISAServer20041179136384389.jpg" align="bottom" border="0" hspace="0" /&gt;&lt;/a&gt;&lt;/p&gt; &lt;p&gt;&lt;b&gt;&lt;img alt="" src="http://www.isaserver.org/img/upl/image0221197306092788.jpg" align="bottom" border="0" hspace="0" /&gt;&lt;br /&gt;Figure 10&lt;/b&gt;&lt;/p&gt; &lt;ol start="7"&gt;&lt;li&gt;Click &lt;b&gt;OK&lt;/b&gt; in the &lt;b&gt;New Resource Record&lt;/b&gt; dialog box. &lt;/li&gt;&lt;/ol&gt; &lt;p&gt;&lt;b&gt;&lt;img alt="" src="http://www.isaserver.org/img/upl/image0241197306092804.jpg" align="bottom" border="0" hspace="0" /&gt;&lt;br /&gt;Figure 11&lt;/b&gt;&lt;/p&gt; &lt;ol start="8"&gt;&lt;li&gt;The CNAME (alias) entry appears in the right pane of the &lt;b&gt;DNS&lt;/b&gt; management console.&lt;/li&gt;&lt;/ol&gt; &lt;p&gt;&lt;b&gt;&lt;img alt="" src="http://www.isaserver.org/img/upl/image0261197306131851.jpg" align="bottom" border="0" hspace="0" /&gt;&lt;br /&gt;Figure 12&lt;/b&gt;&lt;/p&gt; &lt;ol start="9"&gt;&lt;li&gt;Close the &lt;b&gt;DNS Management&lt;/b&gt; console.&lt;/li&gt;&lt;/ol&gt; &lt;h2&gt;Configure the Client to Use the Fully Qualified wpad Alias&lt;/h2&gt; &lt;p&gt;The Web Proxy and Firewall client needs to be able to correctly resolve the name &lt;i&gt;wpad&lt;/i&gt;. Both the Web Proxy and Firewall client configurations are &lt;i&gt;not aware of the domain containing the wpad alias&lt;/i&gt;. The Web Proxy and Firewall client operating system must be able to provide this information to the Web Proxy and Firewall client.&lt;/p&gt; &lt;p&gt;DNS queries must be &lt;i&gt;fully qualified&lt;/i&gt; before the query is sent to the DNS server. A fully qualified request contains a host name and a domain name. The Web Proxy and Firewall client only know the &lt;i&gt;host name&lt;/i&gt; portion. The Web Proxy and Firewall client operating system must be able to provide the correct domain name, which it appends to the &lt;i&gt;wpad&lt;/i&gt; host name, before it can send a DNS query to the DNS server.&lt;/p&gt; &lt;p&gt;There are a number of methods you can use to insure that a proper domain name is appended to &lt;i&gt;wpad&lt;/i&gt; before the query is sent to the DNS server. Two popular methods for doing this include:&lt;/p&gt; &lt;ul&gt;&lt;li&gt;Using DHCP to assign a primary domain name  &lt;/li&gt;&lt;li&gt;Configuring a primary domain name in the client operating system’s network identification dialog box. &lt;/li&gt;&lt;/ul&gt; &lt;p&gt;We already configured a primary DNS name to assign DHCP clients when we configured the DHCP scope. The following steps demonstrate how to set the primary domain name to append to unqualified DNS queries:&lt;/p&gt; &lt;p&gt;&lt;b&gt;Note:&lt;br /&gt;&lt;/b&gt;You do not need to perform these steps on the client machine on the Internal network in our example network. The reason for this is that the client is a member of the Active Directory domain on the internal network. However, you should go through the following steps to see how the primary domain name can be configured on non-domain member computers.&lt;/p&gt; &lt;ol&gt;&lt;li&gt;Right click the &lt;b&gt;My Computer&lt;/b&gt; icon on the desktop and click the &lt;b&gt;Properties&lt;/b&gt; command.  &lt;/li&gt;&lt;li&gt;In the &lt;b&gt;System Properties&lt;/b&gt; dialog box, click the &lt;b&gt;Network Identification&lt;/b&gt; tab. Click the &lt;b&gt;Properties&lt;/b&gt; button.&lt;/li&gt;&lt;/ol&gt; &lt;p&gt;&lt;b&gt;&lt;img alt="" src="http://www.isaserver.org/img/upl/image0281197306131851.jpg" align="bottom" border="0" hspace="0" /&gt;&lt;br /&gt;Figure 13&lt;/b&gt;&lt;/p&gt; &lt;ol start="3"&gt;&lt;li&gt;In the &lt;b&gt;Identification Changes&lt;/b&gt; dialog box, click the &lt;b&gt;More&lt;/b&gt; button.&lt;/li&gt;&lt;/ol&gt; &lt;p&gt;&lt;b&gt;&lt;img alt="" src="http://www.isaserver.org/img/upl/image0301197306131866.jpg" align="bottom" border="0" hspace="0" /&gt;&lt;br /&gt;Figure 14&lt;/b&gt;&lt;/p&gt; &lt;ol start="4"&gt;&lt;li&gt;In the &lt;b&gt;DNS Suffix and NetBIOS Computer Name&lt;/b&gt; dialog box, enter the domain name that contains your wpad entry in the &lt;b&gt;Primary DNS suffix of this computer&lt;/b&gt; text box. This is the domain name that the operating system will append to the wpad name before sending the DNS query to the DNS server. By default, the primary domain name is the same as the domain name the machine belongs to. If the machine is not a member of a domain, then this text box will be empty. Note the &lt;b&gt;Change primary DNS suffix when domain membership changes&lt;/b&gt; is enabled by default. In the current example, the machine is not a member of a domain.&lt;/li&gt;&lt;/ol&gt; &lt;p&gt;Cancel out of each of the dialog boxes so that you do not configure a primary domain name at this time.&lt;/p&gt; &lt;p&gt;&lt;b&gt;&lt;strong&gt;&lt;img alt="" src="http://www.isaserver.org/img/upl/image0321197306156413.jpg" align="bottom" border="0" hspace="0" /&gt;&lt;br /&gt;Figure 15&lt;/strong&gt;&lt;/b&gt;&lt;/p&gt; &lt;p&gt;Note that if you have multiple domains and clients on your internal network that belong to multiple domains, then you will need to create wpad CNAME alias entries for each of the domains.&lt;/p&gt; &lt;h2&gt;Configure the Client Browser to Use Autodiscovery&lt;/h2&gt; &lt;p&gt;The next step is to configure the browser to use autodiscovery. If you have not already done so, perform the following steps to configure the Web browser to use autodiscovery to automatically configure itself to use the ISA firewall’s Web Proxy service:&lt;/p&gt; &lt;ol&gt;&lt;li&gt;Right click on the &lt;b&gt;Internet Explorer &lt;/b&gt;icon on the desktop and click &lt;b&gt;Properties&lt;/b&gt;.  &lt;/li&gt;&lt;li&gt;In the &lt;b&gt;Internet Properties&lt;/b&gt; dialog box, click the &lt;b&gt;Connections&lt;/b&gt; tab. Click the &lt;b&gt;LAN Settings&lt;/b&gt; button.  &lt;/li&gt;&lt;li&gt;In the &lt;b&gt;Local Area Network (LAN) Settings&lt;/b&gt; dialog box, put a checkmark in the &lt;b&gt;Automatically detect settings&lt;/b&gt; checkbox. Click &lt;b&gt;OK&lt;/b&gt;.&lt;/li&gt;&lt;/ol&gt; &lt;p&gt;&lt;b&gt;&lt;img alt="" src="http://www.isaserver.org/img/upl/image0331197306156413.gif" align="bottom" border="0" hspace="0" /&gt;&lt;br /&gt;Figure 16&lt;/b&gt;&lt;/p&gt; &lt;ol start="4"&gt;&lt;li&gt;Click &lt;b&gt;Apply&lt;/b&gt; and then click &lt;b&gt;OK&lt;/b&gt; in the &lt;b&gt;Internet Properties&lt;/b&gt; dialog box.&lt;/li&gt;&lt;/ol&gt; &lt;p&gt;The next step is to configure the ISA firewall to publish autodiscovery information for autodiscovery Web Proxy and Firewall clients.&lt;/p&gt; &lt;h2&gt;Configuring the ISA Firewall to Publish Autodiscovery Information&lt;/h2&gt; &lt;p&gt;The DHCP and DNS wpad entries are designed to point the Web proxy and Firewall client applications to the IP address and port that the ISA Firewall uses to provide autodiscovery information to the clients. However, by default autodiscovery publishing on the ISA Firewall is disabled. It’s your job to enable this setting on each ISA Firewall Network that contains Web proxy and Firewall clients.&lt;/p&gt; &lt;ol&gt;&lt;li&gt;In the ISA Firewall console, expand the server name in the left pane of the console and then expand the &lt;b&gt;Configuration&lt;/b&gt; node in the left pane. Click on the &lt;b&gt;Networks&lt;/b&gt; node.  &lt;/li&gt;&lt;li&gt;In the &lt;b&gt;Networks&lt;/b&gt; node, click on the &lt;b&gt;Networks&lt;/b&gt; tab in the middle pane of the console. Double click the ISA Firewall Network that you want to enable autodiscovery publishing. In this example, we’ll enable autodiscovery publishing for the default Internal ISA Firewall Network. &lt;/li&gt;&lt;li&gt;In the &lt;b&gt;Internal Properties&lt;/b&gt; dialog box, click on the &lt;b&gt;Auto Discovery&lt;/b&gt; tab. Put a checkmark in the &lt;b&gt;Publish automatic discovery information for this network&lt;/b&gt; checkbox. By default, the ISA Firewall will listen for requests from Web Proxy and Firewall clients on TCP port 80. If you’re using DHCP wpad entries, then you can change this port. However, if you use DNS based wpad support, then you must leave the value at its default, TCP port 80.&lt;/li&gt;&lt;/ol&gt; &lt;p&gt;&lt;b&gt;&lt;img alt="" src="http://www.isaserver.org/img/upl/image0351197306156429.jpg" align="bottom" border="0" hspace="0" /&gt;&lt;br /&gt;Figure 17&lt;/b&gt;&lt;/p&gt; &lt;ol start="4"&gt;&lt;li&gt;Click &lt;b&gt;Apply&lt;/b&gt; and then click &lt;b&gt;OK&lt;/b&gt;.  &lt;/li&gt;&lt;li&gt;Click &lt;b&gt;Apply &lt;/b&gt;to save the changes and update the firewall policy.&lt;/li&gt;&lt;/ol&gt; &lt;p&gt;At this point you can close all browser windows and open them. The new settings will work at this point and the Web browsers will be able to get autoconfiguration information from the ISA firewall. For the Firewall clients, you can wait for about six hours for the update, or you can manually configure them to update their configuration. Right click on the Firewall client icon in the system tray and select the &lt;b&gt;Automatically detect ISA Server&lt;/b&gt; option and click &lt;b&gt;Detect Now&lt;/b&gt;.&lt;/p&gt; &lt;p&gt;&lt;b&gt;&lt;img alt="" src="http://www.isaserver.org/img/upl/image0371197306175226.jpg" align="bottom" border="0" hspace="0" /&gt;&lt;br /&gt;Figure 18&lt;/b&gt;&lt;/p&gt; &lt;p&gt;&lt;b&gt;&lt;img alt="" src="http://www.isaserver.org/img/upl/image0391197306175241.jpg" align="bottom" border="0" hspace="0" /&gt;&lt;br /&gt;Figure 19&lt;/b&gt;&lt;/p&gt; &lt;p&gt;Click &lt;b&gt;OK&lt;/b&gt; to save the settings.&lt;/p&gt; &lt;p align="center"&gt; &lt;/p&gt;&lt;table id="AutoNumber2" align="center" border="2" bordercolor="#111111" cellpadding="4" cellspacing="0"&gt; &lt;tbody&gt; &lt;tr&gt; &lt;td width="100%"&gt; &lt;p align="center"&gt;&lt;strong&gt;Discuss this article&lt;/strong&gt;&lt;/p&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt; &lt;p align="center"&gt;&lt;a href="http://www.amazon.com/exec/obidos/ASIN/1931836191/wwwshindernet-20" target="_blank"&gt;&lt;img alt="" src="http://www.isaserver.org/img/upl/ISAServer20041179136384389.jpg" align="bottom" border="0" hspace="0" /&gt;&lt;/a&gt;&lt;/p&gt; &lt;h2&gt;Conclusion&lt;/h2&gt; &lt;p&gt;In this article we discussed how to automatically configure the Web proxy and Firewall clients to use wpad entries to automatically discover the ISA Firewall and automatically configure themselves. We went over the two methods you an use for autodiscovery: DHCP and DNS. We also demonstrated how to configure the client to correctly qualify the unqualified wpad name and how to configure the ISA Firewall to publish autodiscovery information on the appropriate ISA Firewall Networks that contain clients that wish to use autodiscovery.&lt;/p&gt;  &lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3312932509559653332-5982958431544695724?l=thenetworkingworld.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://thenetworkingworld.blogspot.com/feeds/5982958431544695724/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=3312932509559653332&amp;postID=5982958431544695724' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3312932509559653332/posts/default/5982958431544695724'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3312932509559653332/posts/default/5982958431544695724'/><link rel='alternate' type='text/html' href='http://thenetworkingworld.blogspot.com/2007/12/configuring-wpad-support-for-isa.html' title='Configuring WPAD Support for ISA Firewall Web Proxy and Firewall Clients'/><author><name>piyush b</name><uri>http://www.blogger.com/profile/08681531766322786460</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3312932509559653332.post-850405951829632677</id><published>2007-09-11T03:48:00.000-07:00</published><updated>2007-09-11T03:51:13.452-07:00</updated><title type='text'>The Networking World</title><content type='html'>&lt;h2&gt;&lt;span class="mw-headline"&gt;Definition&lt;/span&gt;&lt;/h2&gt; &lt;p&gt;Experts in the field of networking debate whether &lt;i&gt;two&lt;/i&gt; computers that are connected together using some form of communications medium constitute a network. Therefore, some works state that a network requires &lt;i&gt;three&lt;/i&gt; connected computers. One such source, "Telecommunications: Glossary of Telecommunication Terms" states that a computer network is "A network of data processing nodes that are interconnected for the purpose of data communication". The term "network" being defined in the same document as "An interconnection of three or more communicating entities".&lt;sup id="_ref-FS1037C_0" class="reference"&gt;[1]&lt;/sup&gt; A computer connected to a non-computing device (e.g., networked to a printer via an Ethernet link) may also represent a computer network, although this article does not address this configuration.&lt;/p&gt; &lt;p&gt;This article uses the definition which requires &lt;i&gt;two&lt;/i&gt; or more computers to be connected together to form a network. &lt;sup id="_ref-Groth_0" class="reference"&gt;[2]&lt;/sup&gt; The same basic functions are generally present in this case as with larger numbers of connected computers. In order for a network to function, it must meet three basic requirements, it must provide connections, communications and services. &lt;i&gt;Connections&lt;/i&gt; refers to the hardware, &lt;i&gt;communications&lt;/i&gt; is the way in which the devices talk to each other, and &lt;i&gt;services&lt;/i&gt; are the things which are shared with the rest of the network.&lt;sup id="_ref-MS_A.2B_certification_0" class="reference"&gt;[3]&lt;/sup&gt;&lt;/p&gt; &lt;p&gt;&lt;a name="Classification_of_computer_networks" id="Classification_of_computer_networks"&gt;&lt;/a&gt;&lt;/p&gt; &lt;h2&gt;&lt;span class="editsection"&gt;[edit]&lt;/span&gt; &lt;span class="mw-headline"&gt;Classification of computer networks&lt;/span&gt;&lt;/h2&gt; &lt;p&gt;&lt;a name="By_network_layer" id="By_network_layer"&gt;&lt;/a&gt;&lt;/p&gt; &lt;h3&gt;&lt;span class="editsection"&gt;[edit]&lt;/span&gt; &lt;span class="mw-headline"&gt;By network layer&lt;/span&gt;&lt;/h3&gt; &lt;p&gt;Computer networks may be classified according to the network layer at which they operate according to some basic reference models that are considered to be standards in the industry such as the seven layer OSI reference model and the four layer Internet Protocol Suite model. In practice, the great majority of networks use the Internet Protocol (IP) as their network layer. Some networks, however, are using IP Version 6 IPv6, usually in coexistence with IPv4. IPv6 use is often experimental.&lt;/p&gt; &lt;p&gt;&lt;a name="By_scale" id="By_scale"&gt;&lt;/a&gt;&lt;/p&gt; &lt;h3&gt;&lt;span class="editsection"&gt;[edit]&lt;/span&gt; &lt;span class="mw-headline"&gt;By scale&lt;/span&gt;&lt;/h3&gt; &lt;p&gt;Computer networks may be classified according to the scale: Personal Area Network (PAN), Local Area Network, Campus Area Network, Metropolitan area network (MAN), or Wide area network (WAN). As Ethernet increasingly is the standard interface to networks, these distinctions are more important to the network administrator than the end user. Network administrators may have to tune the network, based on delay that derives from distance, to achieve the desired Quality of Service (QoS).&lt;/p&gt; &lt;p&gt;Controller Area Networks are a special niche, as in control of a vehicle's engine, a boat's electronics, or a set of factory robots.&lt;/p&gt; &lt;p&gt;&lt;a name="By_connection_method" id="By_connection_method"&gt;&lt;/a&gt;&lt;/p&gt; &lt;h3&gt;&lt;span class="editsection"&gt;[edit]&lt;/span&gt; &lt;span class="mw-headline"&gt;By connection method&lt;/span&gt;&lt;/h3&gt; &lt;p&gt;Computer networks may be classified according to the hardware technology that is used to connect the individual devices in the network such as Ethernet, Wireless LAN, HomePNA, or Power line communication.&lt;/p&gt; &lt;p&gt;&lt;a name="By_functional_relationship" id="By_functional_relationship"&gt;&lt;/a&gt;&lt;/p&gt; &lt;h3&gt;&lt;span class="editsection"&gt;[edit]&lt;/span&gt; &lt;span class="mw-headline"&gt;By functional relationship&lt;/span&gt;&lt;/h3&gt; &lt;p&gt;Computer networks may be classified according to the functional relationships which exist between the elements of the network, for example Active Networking, Client-server and Peer-to-peer (workgroup) architectures.&lt;/p&gt; &lt;p&gt;&lt;a name="By_network_topology" id="By_network_topology"&gt;&lt;/a&gt;&lt;/p&gt; &lt;h3&gt;&lt;span class="editsection"&gt;[edit]&lt;/span&gt; &lt;span class="mw-headline"&gt;By network topology&lt;/span&gt;&lt;/h3&gt; &lt;dl&gt;&lt;dd&gt; &lt;div class="noprint"&gt;&lt;i&gt;Main article: Network Topology&lt;/i&gt;&lt;/div&gt; &lt;/dd&gt;&lt;/dl&gt; &lt;p&gt;Computer networks may be classified according to the network topology upon which the network is based, such as Bus network, Star network, Ring network, Mesh network, Star-bus network, Tree or Hierarchical topology network, etc.&lt;/p&gt; &lt;p&gt;Network Topology signifies the way in which intelligent devices in the network see their logical relations to one another. The use of the term "logical" here is significant. That is, network topology is independent of the "physical" layout of the network. Even if networked computers are physically placed in a linear arrangement, if they are connected via a hub, the network has a Star topology, rather than a Bus Topology. In this regard the visual and operational characteristics of a network are distinct.&lt;/p&gt; &lt;p&gt;&lt;a name="By_protocol" id="By_protocol"&gt;&lt;/a&gt;&lt;/p&gt; &lt;h3&gt;&lt;span class="editsection"&gt;[edit]&lt;/span&gt; &lt;span class="mw-headline"&gt;By protocol&lt;/span&gt;&lt;/h3&gt; &lt;p&gt;Computer networks may be classified according to the communications protocol that is being used on the network. See the articles on List of network protocol stacks and List of network protocols for more information.&lt;/p&gt; &lt;p&gt;&lt;a name="Types_of_networks:" id="Types_of_networks:"&gt;&lt;/a&gt;&lt;/p&gt; &lt;h2&gt;&lt;span class="editsection"&gt;[edit]&lt;/span&gt; &lt;span class="mw-headline"&gt;Types of networks:&lt;/span&gt;&lt;/h2&gt; &lt;p&gt;Below is a list of the most common types of computer networks in order of scale.&lt;/p&gt; &lt;p&gt;&lt;a name="Personal_Area_Network_.28PAN.29" id="Personal_Area_Network_.28PAN.29"&gt;&lt;/a&gt;&lt;/p&gt; &lt;h3&gt;&lt;span class="editsection"&gt;[edit]&lt;/span&gt; &lt;span class="mw-headline"&gt;Personal Area Network (PAN)&lt;/span&gt;&lt;/h3&gt; &lt;dl&gt;&lt;dd&gt; &lt;div class="noprint"&gt;&lt;i&gt;Main article: Personal area network&lt;/i&gt;&lt;/div&gt; &lt;/dd&gt;&lt;/dl&gt; &lt;p&gt;A personal area network (PAN) is a computer network used for communication among computer devices (including telephones and personal digital assistants) close to one person. The devices may or may not belong to the person in question. The reach of a PAN is typically a few meters. PANs can be used for communication among the personal devices themselves (intrapersonal communication), or for connecting to a higher level network and the Internet (an uplink).&lt;/p&gt; &lt;p&gt;Personal area networks may be wired with computer buses such as USB and FireWire. A wireless personal area network (WPAN) can also be made possible with network technologies such as IrDA and Bluetooth.&lt;/p&gt; &lt;p&gt;&lt;a name="Local_Area_Network_.28LAN.29" id="Local_Area_Network_.28LAN.29"&gt;&lt;/a&gt;&lt;/p&gt; &lt;h3&gt;&lt;span class="editsection"&gt;[edit]&lt;/span&gt; &lt;span class="mw-headline"&gt;Local Area Network (LAN)&lt;/span&gt;&lt;/h3&gt; &lt;dl&gt;&lt;dd&gt; &lt;div class="noprint"&gt;&lt;i&gt;Main article: Local Area Network&lt;/i&gt;&lt;/div&gt; &lt;/dd&gt;&lt;/dl&gt; &lt;p&gt;A network covering a small geographic area, like a home, office, or building. Current LANs are most likely to be based on Ethernet technology. The defining characteristics of LANs, in contrast to WANs (wide area networks), include their much higher data transfer rates, smaller geographic range, and lack of a need for leased telecommunication lines. Hosts can be made part of a specific LAN can be defined by setting their address to one within the address range of the LAN subnet This can be done by manual configuration, or by configuring DHCPDynamic Host Configuration Protocol autoconfiguration to give the host an address in the appropriate range.&lt;/p&gt; &lt;p&gt;Currently standardized LAN technologies operate at speeds up to 10 Gigabits/sec. IEEE has projects investigating the standardization of 100 Gigabits/second, and possibly 40 Gigabits/second. &lt;span class="new"&gt;Inverse multiplexing&lt;/span&gt; is commonly used to build a faster aggregate from slower physical streams, such as bringing 4 Gigabits/second aggregate stream into a computer or network element with four 1 Gigabit/second interfaces.&lt;/p&gt; &lt;p&gt;&lt;a name="Campus_Area_Network_.28CAN.29" id="Campus_Area_Network_.28CAN.29"&gt;&lt;/a&gt;&lt;/p&gt; &lt;h3&gt;&lt;span class="editsection"&gt;[edit]&lt;/span&gt; &lt;span class="mw-headline"&gt;Campus Area Network (CAN)&lt;/span&gt;&lt;/h3&gt; &lt;dl&gt;&lt;dd&gt; &lt;div class="noprint"&gt;&lt;i&gt;Main article: Campus Area Network&lt;/i&gt;&lt;/div&gt; &lt;/dd&gt;&lt;/dl&gt; &lt;p&gt;A network that connects two or more LANs but that is limited to a specific and contiguous geographical area such &lt;b&gt;as a college campus&lt;/b&gt;, industrial complex, or a military base. A CAN, may be considered a type of MAN (metropolitan area network), but is generally limited to an area that is smaller than a typical MAN, so it is called a CAN.&lt;/p&gt; &lt;p&gt;This term is most often used to discuss the implementation of networks for a contiguous area. In the past, when layer 2 switching (i.e., bridging (networking) was cheaper than routing, campuses were good candidates for layer 2 networks, until they grew to very large size. Today, a campus may use a mixture of routing and bridging. The network elements used, called "campus switches", tend to be optimized to have many Ethernet interfaces rather than an arbitrary mixture of Ethernet and WAN interfaces.&lt;/p&gt; &lt;p&gt;&lt;a name="Metropolitan_Area_Network_.28MAN.29" id="Metropolitan_Area_Network_.28MAN.29"&gt;&lt;/a&gt;&lt;/p&gt; &lt;h3&gt;&lt;span class="editsection"&gt;[edit]&lt;/span&gt; &lt;span class="mw-headline"&gt;Metropolitan Area Network (MAN)&lt;/span&gt;&lt;/h3&gt; &lt;dl&gt;&lt;dd&gt; &lt;div class="noprint"&gt;&lt;i&gt;Main article: Metropolitan Area Network&lt;/i&gt;&lt;/div&gt; &lt;/dd&gt;&lt;/dl&gt; &lt;p&gt;A network that connects two or more Local Area Networks or CAN together but does not extend beyond the boundaries of the immediate town, city, or metropolitan area. Multiple routers, switches &amp;amp; hubs are connected to create a MAN&lt;/p&gt; &lt;p&gt;&lt;a name="Wide_Area_Network_.28WAN.29" id="Wide_Area_Network_.28WAN.29"&gt;&lt;/a&gt;&lt;/p&gt; &lt;h3&gt;&lt;span class="editsection"&gt;[edit]&lt;/span&gt; &lt;span class="mw-headline"&gt;Wide Area Network (WAN)&lt;/span&gt;&lt;/h3&gt; &lt;dl&gt;&lt;dd&gt; &lt;div class="noprint"&gt;&lt;i&gt;Main article: Wide Area Network&lt;/i&gt;&lt;/div&gt; &lt;/dd&gt;&lt;/dl&gt; &lt;p&gt;A WAN is a data communications network that covers a relatively broad geographic area (i.e. one country to another and one continent to another continent) and that often uses transmission facilities provided by common carriers, such as telephone companies. WAN technologies generally function at the lower three layers of the OSI reference model: the physical layer, the data link layer, and the network layer.&lt;/p&gt; &lt;p&gt;The highest data rate commercially available, as a single bitstream, on WANs is 40 Gigabits/second, principally used between large service providers. Wavelength Division Multiplexing, however, can put multiple 10 or 40 GBps streams onto the same optical fiber.&lt;/p&gt; &lt;p&gt;&lt;a name="Global_Area_Network_.28GAN.29" id="Global_Area_Network_.28GAN.29"&gt;&lt;/a&gt;&lt;/p&gt; &lt;h3&gt;&lt;span class="editsection"&gt;[edit]&lt;/span&gt; &lt;span class="mw-headline"&gt;Global Area Network (GAN)&lt;/span&gt;&lt;/h3&gt; &lt;dl&gt;&lt;dd&gt; &lt;div class="noprint"&gt;&lt;i&gt;Main article: Global Area Network&lt;/i&gt;&lt;/div&gt; &lt;/dd&gt;&lt;/dl&gt; &lt;p&gt;Global area networks (GAN) specifications are in development by several groups, and there is no common definition. In general, however, a GAN is a model for supporting mobile communications across an arbitrary number of wireless LANs, satellite coverage areas, etc. The key challenge in mobile communications is "handing off" the user communications from one local coverage area to the next. In IEEE Project 802, this involves a succession of terrestrial Wireless local area networks (WLAN) is the &lt;sup id="_ref-0" class="reference"&gt;[4]&lt;/sup&gt;. INMARSAT has defined a satellite-based Broadband Global Area Network (BGAN).&lt;/p&gt; &lt;p&gt;IEEE mobility efforts focus on the data link layer and make assumptions about the media. Mobile IP is a network layer technique, developed by the IETF, which is independent of the media type and can run over different media while still keeping the connection.&lt;/p&gt; &lt;p&gt;&lt;a name="Internetwork" id="Internetwork"&gt;&lt;/a&gt;&lt;/p&gt; &lt;h3&gt;&lt;span class="editsection"&gt;[edit]&lt;/span&gt; &lt;span class="mw-headline"&gt;Internetwork&lt;/span&gt;&lt;/h3&gt; &lt;dl&gt;&lt;dd&gt; &lt;div class="noprint"&gt;&lt;i&gt;Main article: Internetwork&lt;/i&gt;&lt;/div&gt; &lt;/dd&gt;&lt;/dl&gt; &lt;p&gt;Two or more networks or network segments connected using devices that operate at layer 3 (the 'network' layer) of the OSI Basic Reference Model, such as a router. Any interconnection among or between public, private, commercial, industrial, or governmental networks may also be defined as an internetwork.&lt;/p&gt; &lt;p&gt;In modern practice, the interconnected networks use the Internet Protocol. There are at least three variants of internetwork, depending on who administers and who participates in them:&lt;/p&gt; &lt;ul&gt;&lt;li&gt;Intranet&lt;/li&gt;&lt;li&gt;Extranet&lt;/li&gt;&lt;li&gt;"The" Internet&lt;/li&gt;&lt;/ul&gt; &lt;p&gt;Intranets and extranets may or may not have connections to the Internet. If connected to the Internet, the intranet or extranet is normally protected from being accessed from the Internet without proper authorization. The Internet itself is not considered to be a part of the intranet or extranet, although the Internet may serve as a portal for access to portions of an extranet.&lt;/p&gt; &lt;p&gt;&lt;a name="Intranet" id="Intranet"&gt;&lt;/a&gt;&lt;/p&gt; &lt;h4&gt;&lt;span class="editsection"&gt;[edit]&lt;/span&gt; &lt;span class="mw-headline"&gt;Intranet&lt;/span&gt;&lt;/h4&gt; &lt;dl&gt;&lt;dd&gt; &lt;div class="noprint"&gt;&lt;i&gt;Main article: Intranet&lt;/i&gt;&lt;/div&gt; &lt;/dd&gt;&lt;/dl&gt; &lt;p&gt;An &lt;b&gt;intranet&lt;/b&gt; is a set of interconnected networks, using the Internet Protocol and uses IP-based tools such as web browsers, that is under the control of a single administrative entity. That administrative entity closes the intranet to the rest of the world, and allows only specific users. Most commonly, an intranet is the internal network of a company or other enterprise.&lt;/p&gt; &lt;p&gt;&lt;a name="Extranet" id="Extranet"&gt;&lt;/a&gt;&lt;/p&gt; &lt;h4&gt;&lt;span class="editsection"&gt;[edit]&lt;/span&gt; &lt;span class="mw-headline"&gt;Extranet&lt;/span&gt;&lt;/h4&gt; &lt;dl&gt;&lt;dd&gt; &lt;div class="noprint"&gt;&lt;i&gt;Main article: Extranet&lt;/i&gt;&lt;/div&gt; &lt;/dd&gt;&lt;/dl&gt; &lt;p&gt;A &lt;b&gt;extranet&lt;/b&gt; is network or internetwork that is limited in scope to a single organization or entity but which also has limited connections to the networks of one or more other usually, but not necessarily, trusted organizations or entities (e.g., a company's customers may be provided access to some part of its intranet thusly creating an extranet while at the same time the customers may not be considered 'trusted' from a security standpoint). Technically, an extranet may also be categorized as a CAN, MAN, WAN, or other type of network, although, by definition, an extranet cannot consist of a single LAN, because an extranet must have at least one connection with an outside network.&lt;/p&gt; &lt;p&gt;&lt;a name="Internet.2C_The" id="Internet.2C_The"&gt;&lt;/a&gt;&lt;/p&gt; &lt;h4&gt;&lt;span class="editsection"&gt;[edit]&lt;/span&gt; &lt;span class="mw-headline"&gt;Internet, The&lt;/span&gt;&lt;/h4&gt; &lt;dl&gt;&lt;dd&gt; &lt;div class="noprint"&gt;&lt;i&gt;Main article: Internet&lt;/i&gt;&lt;/div&gt; &lt;/dd&gt;&lt;/dl&gt; &lt;p&gt;A specific internetwork, consisting of a worldwide interconnection of governmental, academic, public, and private networks based upon the Advanced Research Projects Agency Network (ARPANET) developed by ARPA of the U.S. Department of Defense – also home to the World Wide Web (WWW) and referred to as the 'Internet' with a capital 'I' to distinguish it from other generic internetworks.&lt;/p&gt; &lt;p&gt;Participants in the Internet, or their service providers, use IP Addresses obtained from address registries that control assignments. Service providers and large enterprises also exchange information on the reachability of their address ranges through the Border Gateway Protocol.&lt;/p&gt; &lt;p&gt;&lt;a name="Basic_Hardware_Components" id="Basic_Hardware_Components"&gt;&lt;/a&gt;&lt;/p&gt; &lt;h2&gt;&lt;span class="editsection"&gt;[edit]&lt;/span&gt; &lt;span class="mw-headline"&gt;Basic Hardware Components&lt;/span&gt;&lt;/h2&gt; &lt;p&gt;All networks are made up of basic hardware building blocks to interconnect network nodes, such as Network Interface Cards (NICs), Bridges, Hubs, Switches, and Routers. In addition, some method of connecting these building blocks is required, usually in the form of galvanic cable (most commonly Category 5 cable). Less common are microwave links (as in IEEE 802.11) or optical cable ("optical fiber").&lt;/p&gt; &lt;p&gt;&lt;a name="Network_Interface_Cards" id="Network_Interface_Cards"&gt;&lt;/a&gt;&lt;/p&gt; &lt;h3&gt;&lt;span class="editsection"&gt;[edit]&lt;/span&gt; &lt;span class="mw-headline"&gt;Network Interface Cards&lt;/span&gt;&lt;/h3&gt; &lt;dl&gt;&lt;dd&gt; &lt;div class="noprint"&gt;&lt;i&gt;Main article: Network card&lt;/i&gt;&lt;/div&gt; &lt;/dd&gt;&lt;/dl&gt; &lt;p&gt;A &lt;b&gt;network card&lt;/b&gt;, &lt;b&gt;network adapter&lt;/b&gt; or &lt;b&gt;NIC&lt;/b&gt; (network interface card) is a piece of computer hardware designed to allow computers to communicate over a &lt;strong class="selflink"&gt;computer network&lt;/strong&gt;. It provides physical access to a networking medium and provides a low-level addressing system through the use of MAC addresses. It allows users to connect to each other either by using cables or wirelessly.&lt;/p&gt; &lt;p&gt;&lt;a name="Repeaters" id="Repeaters"&gt;&lt;/a&gt;&lt;/p&gt; &lt;h3&gt;&lt;span class="editsection"&gt;[edit]&lt;/span&gt; &lt;span class="mw-headline"&gt;Repeaters&lt;/span&gt;&lt;/h3&gt; &lt;dl&gt;&lt;dd&gt; &lt;div class="noprint"&gt;&lt;i&gt;Main article: Repeater&lt;/i&gt;&lt;/div&gt; &lt;/dd&gt;&lt;/dl&gt; &lt;p&gt;A &lt;b&gt;repeater&lt;/b&gt; is an electronic device that receives a signal and retransmits it at a higher level or higher power, or onto the other side of an obstruction, so that the signal can cover longer distances without degradation.&lt;/p&gt; &lt;p&gt;Because repeaters work with the actual physical signal, and do not attempt to interpret the data being transmitted, they operate on the Physical layer, the first layer of the OSI model.&lt;/p&gt; &lt;p&gt;&lt;a name="Hubs" id="Hubs"&gt;&lt;/a&gt;&lt;/p&gt; &lt;h3&gt;&lt;span class="editsection"&gt;[edit]&lt;/span&gt; &lt;span class="mw-headline"&gt;Hubs&lt;/span&gt;&lt;/h3&gt; &lt;dl&gt;&lt;dd&gt; &lt;div class="noprint"&gt;&lt;i&gt;Main article: Network hub&lt;/i&gt;&lt;/div&gt; &lt;/dd&gt;&lt;/dl&gt; &lt;p&gt;A hub is a repeater with more than two ports, thus also being called "multiport repeater". It interconnects devices at the physical layer (layer 1) of the OSI model.. &lt;sup id="_ref-dic_of_comp_0" class="reference"&gt;[5]&lt;/sup&gt; It does this in a rudimentary way, it simply copies the data to all of the Nodes connected to the hub. Hubs are commonly used to connect segments of a LAN. A hub contains multiple ports. When a packet arrives at one port, it is copied the packets to all the ports of the hub. When the packets are copied, the destination address in the frame does not change to a broadcast address.&lt;/p&gt; &lt;p&gt;&lt;a name="Bridges" id="Bridges"&gt;&lt;/a&gt;&lt;/p&gt; &lt;h3&gt;&lt;span class="editsection"&gt;[edit]&lt;/span&gt; &lt;span class="mw-headline"&gt;Bridges&lt;/span&gt;&lt;/h3&gt; &lt;dl&gt;&lt;dd&gt; &lt;div class="noprint"&gt;&lt;i&gt;Main article: Network bridge&lt;/i&gt;&lt;/div&gt; &lt;/dd&gt;&lt;/dl&gt; &lt;p&gt;A &lt;b&gt;network bridge&lt;/b&gt; connects multiple network segments at the data link layer (layer 2) of the OSI model. Bridges do not promiscuously copy traffic to all ports, as does a hub. but learns which MAC addresses are reachable through specific ports. Once the bridge associates a port and an address, it will send traffic for that address only to that port. Bridges do send broadcasts to all ports except the one on which the broadcast was received.&lt;/p&gt; &lt;p&gt;Bridges learn the association of ports and addresses by examining the source address of frames that it sees on various ports. Once a frame arrives through a port, its source address is stored and the bridge assumes that MAC address is associated with that port. The first time that a previously unknown destination address is seen, the bridge will forward the frame to all ports other than the one on which the frame arrived.&lt;/p&gt; &lt;p&gt;Bridges come in three basic types:&lt;/p&gt; &lt;ol&gt;&lt;li&gt;Local bridges: Directly connect local area networks (LANs)&lt;/li&gt;&lt;li&gt;Remote bridges: Can be used to create a wide area network (WAN) link between LANs. Remote bridges, where the connecting link is slower than the end networks, largely have been replaced by routers.&lt;/li&gt;&lt;li&gt;Wireless bridges: Can be used to join LANs or connect remote stations to LANs&lt;/li&gt;&lt;/ol&gt; &lt;p&gt;&lt;a name="Switches" id="Switches"&gt;&lt;/a&gt;&lt;/p&gt; &lt;h3&gt;&lt;span class="editsection"&gt;[edit]&lt;/span&gt; &lt;span class="mw-headline"&gt;Switches&lt;/span&gt;&lt;/h3&gt; &lt;dl&gt;&lt;dd&gt; &lt;div class="noprint"&gt;&lt;i&gt;Main article: Network switch&lt;/i&gt;&lt;/div&gt; &lt;/dd&gt;&lt;/dl&gt; &lt;p&gt;Switches are a marketing term that encompasses routers and bridges, as well as devices that may distribute traffic on load or by application content (e.g., a Web URL identifier). Switches may operate at one or more OSI layers, including physical, data link, network, or transport (i.e., end-to-end). A device that operates simultaneously at more than one of these layers is called a multilayer switch.&lt;/p&gt; &lt;p&gt;Overemphasizing the ill-defined term "switch" often leads to confusion when first trying to understand networking. Many experienced network designers and operators recommend starting with the logic of devices dealing with only one protocol level, not all of which are covered by OSI. Multilayer device selection is an advanced topic that may lead to selecting particular implementations, but multilayer switching is simply not a real-world design concept.&lt;/p&gt; &lt;p&gt;&lt;a name="Routers" id="Routers"&gt;&lt;/a&gt;&lt;/p&gt; &lt;h3&gt;&lt;span class="editsection"&gt;[edit]&lt;/span&gt; &lt;span class="mw-headline"&gt;Routers&lt;/span&gt;&lt;/h3&gt; &lt;dl&gt;&lt;dd&gt; &lt;div class="noprint"&gt;&lt;i&gt;Main article: Router&lt;/i&gt;&lt;/div&gt; &lt;/dd&gt;&lt;/dl&gt; &lt;p&gt;Routers are the networking device that forwards data packets along networks by using headers and forwarding tables to determine the best path to forward the packets. Routers work at the network layer (layer 3) of the OSI model. Routers also provide interconnectivity between like and unlike media.&lt;sup id="_ref-MS_A.2B_certification_1" class="reference"&gt;[3]&lt;/sup&gt; This is accomplished by examining the Header of a data packet.&lt;sup id="_ref-dic_of_comp_1" class="reference"&gt;[5]&lt;/sup&gt; They use routing protocols such as Open Shortest Path First (OSPF) to communicate with each other and configure the best route between any two hosts. A router is connected to at least two networks, commonly two LANs or WANs or a LAN and its ISP's network. Some DSL and Cable Modems have been integrated with routers for home consumers.&lt;/p&gt; &lt;p&gt;&lt;a name="Building_a_simple_computer_network" id="Building_a_simple_computer_network"&gt;&lt;/a&gt;&lt;/p&gt; &lt;h2&gt;&lt;span class="editsection"&gt;[edit]&lt;/span&gt; &lt;span class="mw-headline"&gt;Building a simple computer network&lt;/span&gt;&lt;/h2&gt; &lt;p&gt;A simple computer network may be constructed from two computers by adding a network adapter (Network Interface Controller (NIC)) to each computer and then connecting them together with a special cable called a crossover cable. This type of network is useful for transferring information between two computers that are not normally connected to each other by a permanent network connection or for basic home networking applications. Alternatively, a network between two computers can be established without dedicated extra hardware by using a standard connection such as the RS-232 serial port on both computers, connecting them to each other via a special crosslinked &lt;i&gt;null modem&lt;/i&gt; cable.&lt;/p&gt; &lt;p&gt;Practical networks generally consist of more than two interconnected computers and generally require special devices in addition to the Network Interface Controller that each computer needs to be equipped with. Examples of some of these special devices are hubs, switches and routers.&lt;/p&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3312932509559653332-850405951829632677?l=thenetworkingworld.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://thenetworkingworld.blogspot.com/feeds/850405951829632677/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=3312932509559653332&amp;postID=850405951829632677' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3312932509559653332/posts/default/850405951829632677'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3312932509559653332/posts/default/850405951829632677'/><link rel='alternate' type='text/html' href='http://thenetworkingworld.blogspot.com/2007/09/networking-world.html' title='The Networking World'/><author><name>piyush b</name><uri>http://www.blogger.com/profile/08681531766322786460</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry></feed>
