tag:blogger.com,1999:blog-75299036327138102002011-11-27T16:10:44.819-08:00Indian Bloggernoreply@blogger.comBlogger771100tag:blogger.com,1999:blog-7529903632713810200.post-27805819994696839812009-12-07T09:57:00.000-08:002009-12-07T10:05:38.356-08:00<span style="font-weight: bold;">By Raymond W. Yeung, Shuo-Yen Robert Li, Ning Cai and Zhen Zhang</span><br /><br /><div style="text-align: justify;">Consider a network consisting of point-to-point communication channels. Each channel transmits information noiselessly subject to the channel capacity. Data is to be transmitted from the source node to a prescribed set of destination nodes. Given the transmission requirements, a natural question is whether the network can fulfill these requirements and how it can be done efficiently.<br /></div><div style="text-align: justify;"><blockquote></blockquote>In existing computer networks, information is transmitted from the source node to each destination node through a chain of intermediate nodes by a method known as store-and-forward. In this method, data packets received from an input link of an intermediate node are stored and a copy is forwarded to the next node via an output link. In the case when an intermediate node is on the transmission paths toward multiple destinations, it sends one copy of the data packets onto each output link that leads to at least one of the destinations. It has been a folklore in data networking that there is no need for data processing at the intermediate nodes except for data replication.<br /><blockquote></blockquote>This text aims to be a tutorial on the basics of the theory of network coding. The intent is a transparent presentation without necessarily presenting all results in their full generality. Part I is devoted to network coding for the transmission from a single source node to other nodes in the network. It starts with describing examples on network coding in the next section. Part II deals with the problem under the more general circumstances when there are multiple source nodes each intending to transmit to a different set of destination nodes.<br /></div><br />Following are the few topics covered in this Network coding book.<br /><ul><li>Linear coding</li><li>Nonlinear coding</li><li>Random coding</li><li>Static codes</li><li>Convolutional codes</li><li>Group codes</li><li>Alphabet size</li><li>Code construction</li><li>Algorithms/protocols</li><li>Cyclic networks</li><li>Undirected networks</li><li>Link failure/Network management</li><li>Separation theorem</li><li>Error correction/detection</li><li>Cryptography</li><li>Multiple sources</li><li>Multiple unicasts</li><li>Cost criteria</li><li>Non-uniform demand</li><li>Correlated sources</li><li>Max-flow/cutset/edge-cut bound</li><li>Superposition coding</li><li>Networking</li><li>Routing</li><li>Wireless/satellite networks</li><li>Ad hoc/sensor networks</li><li>Data storage/distribution</li><li>Implementation issues</li><li>Matrix theory</li><li>Complexity theory</li><li>Graph theory</li><li>Random graph</li><li>Tree packing</li><li>Multicommodity flow</li><li>Game theory</li><li>Matriod theory</li><li>Information inequalities</li><li>Noisy channels</li><li>Queueing analysis</li><li>Rate-distortion</li><li>Multiple descriptions</li><li>Latin squares</li><li>Reversible networks</li><li>Multiuser channels</li><li>Joint network-channel coding</li></ul><a href="http://iest2.ie.cuhk.edu.hk/%7Ewhyeung/publications/tutorial.pdf" target="_blank">Read More/Try It</a><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-2780581999469683981?l=more-networking.blogspot.com' alt='' /></div>Indian Bloggernoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-30219566334930476892009-12-07T09:51:00.000-08:002009-12-07T09:54:41.356-08:00<div style="text-align: justify;"><span style="font-weight: bold;">By Kieran Greer</span><br /><blockquote></blockquote>The book is titled 'Thinking Networks - the Large and Small of it'. The topics covered span from large global networks to small local neural-like networks, hence the title. The book is mainly a research monograph, but it also contains blue sky research suggestions and also some informative or teaching sections. This book tries to cover research areas that look at adding autonomous or reasoning capabilities to information networks. It would be of interest to both academic or industrial researchers looking to build intelligent networks. For example, the telecommunications sector might want to add intelligent services to the Internet or a mobile environment. The book however could be used to build networks that range in size from large Internet-based networks to small local neural network-like structures, and ultimately suggests an architecture on which to build a network that might even begin to 'think'. Some of the research has been proven, while the more ambitious claims or suggestions are for future research.<br /><blockquote></blockquote>The book covers areas such as the Internet/p2p/ mobile networks, SOA, Semantic Networks (Semantic Web, Ontologies, Web Services, Grid), AI (including Autonomous systems, Intelligent, Cognitive or Neural Network-like systems, and Bio-inspired networks), XML-based languages and query processes. It is available from different online stores and is also listed on the ACM portal. The technologies that are described in this book are also strongly related to the new 'Cloud Computing' architecture that is being talked about for the Internet.<br /><a href="http://kierangreer.co.uk/books.aspx" target="_blank"><blockquote></blockquote>Read More/Try It</a><br /></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-3021956633493047689?l=more-networking.blogspot.com' alt='' /></div>Indian Bloggernoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-2066328999641751182008-12-27T12:08:00.000-08:002008-12-27T13:29:31.844-08:00<div style="text-align: justify;">Traffic Management For High-Speed Networks is written by H.T. Kung, Gordon McKay - Professor of Electrical Engineering &amp; Comuputer Science and Harvard University. This network management book is published by National Academies Press.<br /><blockquote></blockquote><span style="font-weight: bold;">Abstract</span><br />Network congestion will increase as network speed increases. New control methods are needed, especially for handling "bursty" traffic expected in very high speed networks such as asynchronous transfer mode (ATM) networks. Users should have instant access to all available network bandwidth when they need it, while being assured that the chance of losing data in the presence of congestion will be negligible. At the same time, high network utilization must be achieved, and services requiting guaranteed performance must be accommodated. This paper discusses these issues and describes congestion control solutions under study at Harvard University and elsewhere. Motivations, theory, and experimental results are presented.<br /><blockquote></blockquote>Following are the topics covered in this network management book.<br /><ol><li>Why New Control Methods Are Needed</li><li>Rapid Increase in Network Speeds</li><li>Network Congestion Problem</li><li>Inadequacy of Brute-Force Approach to Providing Large Buffers</li><li>Use of Flow Control</li><li>Control of Congestion for ATM Networks</li><li>Technical Goals of Flow Control for Supporting ATM ABR Services</li><li>Two Traffic Models</li><li>A Flood Control Principle</li><li>Credit-based Flow Control</li><li>Credit Update Protocol</li><li>Static vs. Adaptive Credit Control</li><li>Adaptive Buffer Allocation</li><li>Receiver-oriented Adaptive Buffer Allocation</li><li>Rationale for Credit-based Flow Control</li><li>Overallocation of Resources to Achieve High Efficiency</li><li>Link-by-Link Flow Control to Increase Quality of Control</li><li>Per-VC Queueing to Achieve a High Degree of Fairness</li><li>Rate-based Flow Control</li><li>CreditNet ATM Switch</li><li>Experimental Network Configurations</li><li>Measured Performance on CreditNet Experimental Switches</li><li>Summary and Concluding Remarks</li><li>Acknowledgments</li><li>References</li></ol>You can download or read this book from the following link.<br /><blockquote></blockquote><a href="http://www.nap.edu/openbook.php?isbn=0309057981" target="_blank">Read More/Download</a><br /><blockquote></blockquote><span style="color: rgb(255, 0, 0); font-weight: bold;">Buy this book</span><br /><a href="http://www.amazon.com/gp/product/0309057981?ie=UTF8&amp;tag=frsaabeb-20&amp;linkCode=as2&amp;camp=1789&amp;creative=9325&amp;creativeASIN=0309057981" target="_blank">Traffic Management for High-Speed Networks: Fourth Lecture International Science Lecture Se ries</a><br /><blockquote></blockquote><span style="font-weight: bold; color: rgb(255, 0, 0);">Related Networking Ebooks</span><br /><ol><li><a href="http://more-networking.blogspot.com/2008/01/download-free-computer-networking.html">Computer Networking Ebooks</a></li><li><a href="http://freee-booksdownload.blogspot.com/2008/02/free-computer-security-ebooks-download.html">Computer Security Ebooks</a></li><li><a href="http://freee-booksdownload.blogspot.com/2008/02/free-artificial-neural-networks-ebooks.html">Artificial Neural Networks Ebooks<br /></a></li><li><a href="http://freee-booksdownload.blogspot.com/2008/02/free-cryptography-ebooks-download.html">Cryptography Ebooks</a></li></ol><br /></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-206632899964175118?l=more-networking.blogspot.com' alt='' /></div>Indian Bloggernoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-82897485485855309982008-01-31T11:19:00.000-08:002011-10-26T09:03:26.500-07:00<div dir="ltr" style="text-align: left;" trbidi="on"><br /><div dir="ltr" style="text-align: justify;" trbidi="on">This posting helps you to get free computer networking ebooks focuses on computer networking, computer network security, requirements for network security, tcp ip protocols, internetworking, osi model, socket programming, internet protocols, ipv6, voice over internet protocol, port authority, port forwarding, wireless networking, home networking, computer networking, client server computing, client server software, virtual private networks, socket programming, tcp/ip protocols, ATM networks asynchronous transfer mode, DNS, Parallel Virtual Machine, Networking fundamentals, SSH secure shell, IPX routing, etc.</div><div style="text-align: justify;"><blockquote></blockquote>You can download free computer networking ebooks from the following links. Visit this free computer networking ebooks.</div><ul><li><a href="http://more-networking.blogspot.com/2007/02/beginners-guide-to-network-security.html">A Beginner’s Guide to Network Security</a></li><li><a href="http://more-networking.blogspot.com/2007/02/comprehensive-guide-to-virtual-private.html">A Comprehensive Guide to Virtual Private Networks, Volume II: IBM Nways Router Solutions</a></li><li><a href="http://more-networking.blogspot.com/2007/02/comprehensive-guide-to-virtual-private_14.html">A Comprehensive Guide to Virtual Private Networks, Volume III: Cross-Platform Key and Policy Management</a></li><li><a href="http://more-networking.blogspot.com/2006/12/guide-to-tcpip-internetworking-by.html">A Guide to TCP/IP Internetworking By Vincenzo Mendillo</a></li><li><a href="http://more-networking.blogspot.com/2007/02/new-tcp-congestion-control-with-empty.html">A new TCP congestion control with empty queues and scalable stability</a></li><li><a href="http://more-networking.blogspot.com/2007/02/introduction-to-socket-programming.html">An Introduction to Socket Programming By Reg Quinton</a></li><li><a href="http://more-networking.blogspot.com/2006/12/overview-of-tcpip-protocols-and.html">An Overview of TCP/IP Protocols and the Internet By Gary C. Kessler</a></li><li><a href="http://more-networking.blogspot.com/2007/02/asynchronous-transfer-mode-atm.html">Asynchronous Transfer Mode (ATM) Technical Overview</a></li><li><a href="http://more-networking.blogspot.com/2006/12/becoming-internet-service-provider-by.html">Becoming an Internet Service Provider by Rob Kolstad</a></li><li><a href="http://more-networking.blogspot.com/2007/02/bsd-sockets.html">BSD Sockets</a></li><li><a href="http://more-networking.blogspot.com/2007/03/building-internet-firewalls-first.html">Building Internet Firewalls First Edition By D. Brent Chapman and Elizabeth D. Zwicky</a></li><li><a href="http://more-networking.blogspot.com/2007/03/building-internet-firewalls-second.html">Building Internet Firewalls Second Edition By Elizabeth D. Zwicky, Simon Cooper and D. Brent Chapman</a></li><li><a href="http://more-networking.blogspot.com/2007/02/clientserver-computing-second-edition.html">Client/Server Computing Second Edition</a></li><li><a href="http://more-networking.blogspot.com/2007/04/communication-networks.html">Communication Networks By Sharam Hekmat</a></li><li><a href="http://more-networking.blogspot.com/2006/12/comp.html">comp.protocols.tcp-ip.domains FAQ'S</a></li><li><a href="http://more-networking.blogspot.com/2007/02/complete-wap-security.html">Complete WAP Security from Certicom</a></li><li><a href="http://more-networking.blogspot.com/2007/02/computer-networks-and-internets.html">Computer Networks and Internets</a></li><li><a href="http://more-networking.blogspot.com/2007/02/computer-networks.html">Computer Networks By Hans-Peter Bischof</a></li><li><a href="http://more-networking.blogspot.com/2006/12/daryls-tcpip-primer-by-daryl-banttari.html">Daryl's TCP/IP Primer By Daryl Banttari</a></li><li><a href="http://more-networking.blogspot.com/2006/12/design-and-validation-of-computer.html">Design and Validation of Computer Protocols By Gerard J. Holzmann</a></li><li><a href="http://more-networking.blogspot.com/2007/02/designing-wireless-network.html">Designing A Wireless Network By Jeffrey Wheat, Randy Hiser, Jackie Tucker, Alicia Neely and Andy McCullough</a></li><li><a href="http://more-networking.blogspot.com/2007/03/dns-and-bind-fourth-edition.html">DNS and BIND Fourth Edition By Paul Albitz and Cricket Liu</a></li><li><a href="http://more-networking.blogspot.com/2007/03/dns-and-bind-third-edition.html">DNS and BIND Third Edition By Cricket Liu &amp; Paul Albitz</a></li><li><a href="http://more-networking.blogspot.com/2007/03/essential-snmp-first-edition.html">Essential SNMP First Edition by Douglas R. Mauro and Kevin J. Schmidt</a></li><li><a href="http://more-networking.blogspot.com/2006/12/fundamentals-of-wireless-communication.html">Fundamentals of Wireless Communication By David Tse and Pramod Viswanath</a></li><li><a href="http://more-networking.blogspot.com/2006/12/high-performance-networking-unleashed.html">High-Performance Networking Unleashed</a></li><li><a href="http://more-networking.blogspot.com/2007/02/high-speed-networking-technology.html">High-Speed Networking Technology: An Introductory Survey</a></li><li><a href="http://more-networking.blogspot.com/2006/12/ieeeacm-transactions-on-networking-ton.html">IEEE/ACM Transactions on Networking (TON) 43 Books</a></li><li><a href="http://more-networking.blogspot.com/2006/12/implementing-cifs-common-internet.html">Implementing CIFS The Common Internet FileSystem By Christopher R. Hertel</a></li><li><a href="http://more-networking.blogspot.com/2006/12/internet-protocol-tutorial-by-bradley.html">Internet Protocol Tutorial By Bradley Mitchell</a></li><li><a href="http://more-networking.blogspot.com/2006/12/internet-protocol-version-6-ipv6.html">Internet Protocol, Version 6 (IPv6) Specification</a></li><li><a href="http://more-networking.blogspot.com/2007/02/internetwork-troubleshooting-handbook.html">Internetwork Troubleshooting Handbook</a></li><li><a href="http://more-networking.blogspot.com/2007/02/internetworking-over-atm-introduction.html">Internetworking over ATM: An Introduction</a></li><li><a href="http://more-networking.blogspot.com/2007/02/internetworking-technology-handbook.html">Internetworking Technology Handbook</a></li><li><a href="http://more-networking.blogspot.com/2007/04/introduction-to-data-communications.html">Introduction to Data Communications by Eugene Blanchard</a></li><li><a href="http://more-networking.blogspot.com/2007/02/introduction-to-intrusion-protection.html">Introduction to Intrusion Protection and Network Security By Jennifer Vesperman</a></li><li><a href="http://more-networking.blogspot.com/2007/02/introduction-to-networking-technologies.html">Introduction to Networking Technologies</a></li><li><a href="http://more-networking.blogspot.com/2007/02/introduction-to-securing-data-in.html">Introduction to Securing Data in Transit By Jennifer Vesperman</a></li><li><a href="http://more-networking.blogspot.com/2007/02/introduction-to-internet-protocols.html">Introduction to the Internet Protocols</a></li><li><a href="http://more-networking.blogspot.com/2006/12/ip-addressing-and-subnetting-by-charles.html">IP Addressing and Subnetting By Charles C. Botsford</a></li><li><a href="http://more-networking.blogspot.com/2007/02/linux-ipv6-howto.html">Linux IPv6 HOWTO By Peter Bieringer</a></li><li><a href="http://more-networking.blogspot.com/2007/02/local-area-network-concepts-and.html">Local Area Network Concepts and Products: Routers and Gateways</a></li><li><a href="http://more-networking.blogspot.com/2007/02/looking-over-fence-at-networks.html">Looking Over the Fence at Networks: A Neighbor's View of Networking Research (2001)</a></li><li><a href="http://more-networking.blogspot.com/2006/12/managing-multivendor-networks-by-john.html">Managing Multivendor Networks By John Enck and Dan W. Blacharski</a></li><li><a href="http://more-networking.blogspot.com/2007/02/maximum-security-hackers-guide-to.html">Maximum Security: Hacker's Guide to Protecting Your Internet Site and Network</a></li><li><a href="http://more-networking.blogspot.com/2007/02/netizens-on-history-and-impact-of-net.html">Netizens On the History and Impact of the Net By Michael Hauben and Ronda Hauben</a></li><li><a href="http://more-networking.blogspot.com/2007/03/network-troubleshooting-tools-first.html">Network Troubleshooting Tools First Edition by Joseph D. Sloan</a></li><li><a href="http://more-networking.blogspot.com/2007/02/networking-fundamentals-v40.html">Networking Fundamentals, v4.0 By Brian Brown</a></li><li><a href="http://more-networking.blogspot.com/2007/02/networking-with-zos-and-cisco-routers.html">Networking with z/OS and Cisco Routers: An Interoperability Guide</a></li><li><a href="http://more-networking.blogspot.com/2006/12/planning-computer-system-facility-in.html">Planning a computer system facility in an intercomputer network By Barry Wessler</a></li><li><a href="http://more-networking.blogspot.com/2007/02/pvm-parallel-virtual-machine-users.html">PVM: Parallel Virtual Machine - A Users' Guide and Tutorial for Networked Parallel Computing</a></li><li><a href="http://more-networking.blogspot.com/2007/02/realizing-information-future-internet.html">Realizing the Information Future - The Internet and Beyond</a></li><li><a href="http://more-networking.blogspot.com/2006/12/rfc-1180-tcpip-tutorial-by-theodore.html">RFC 1180 - TCP/IP tutorial By Theodore John Socolofsky and Claudia Jeanne Kale</a></li><li><a href="http://more-networking.blogspot.com/2006/12/running-perfect-intranet-by-rich.html">Running a Perfect Intranet by Rich Casselberry</a></li><li><a href="http://more-networking.blogspot.com/2007/03/sendmail-desktop-reference-first.html">Sendmail Desktop Reference First Edition By Bryan Costales and Eric Allman</a></li><li><a href="http://more-networking.blogspot.com/2007/03/ssh-secure-shell-definitive-guide.html">SSH: The Secure Shell - The Definitive Guide by Daniel J. Barrett and Richard E. Silverman</a></li><li><a href="http://more-networking.blogspot.com/2006/12/tcpip-and-ipx-routing-tutorial-sangoma.html">TCP/IP and IPX Routing Tutorial</a></li><li><a href="http://more-networking.blogspot.com/2006/12/tcpip-fundamentals-osi-seven-layer.html">TCP/IP Fundamentals - OSI Seven Layer Model</a></li><li><a href="http://more-networking.blogspot.com/2006/12/tcpip-fundamentals-for-microsoft.html">TCP/IP Fundamentals for Microsoft Windows</a></li><li><a href="http://more-networking.blogspot.com/2007/03/tcpip-network-administration-second.html">TCP/IP Network Administration Second Edition By Craig Hunt</a></li><li><a href="http://more-networking.blogspot.com/2007/03/tcpip-network-administration-third.html">TCP/IP Network Administration Third Edition by Craig Hunt</a></li><li><a href="http://more-networking.blogspot.com/2006/12/tcpip-tutorial-and-technical-overview.html">TCP/IP Tutorial and Technical Overview -IBM</a></li><li><a href="http://more-networking.blogspot.com/2006/12/teach-yourself-tcpip-in-14-days-second.html">Teach Yourself TCP/IP in 14 Days</a></li><li><a href="http://more-networking.blogspot.com/2007/02/teach-yourself-internet-in-24-hours.html">Teach Yourself THE INTERNET in 24 Hours By Noel Estabrook</a></li><li><a href="http://more-networking.blogspot.com/2006/12/networking-cd-bookshelf-gd.html">The Networking CD Bookshelf - 6 Books</a></li><li><a href="http://more-networking.blogspot.com/2006/12/tcpip-guide-by-charles-welcome-to-free.html">The TCP/IP Guide By Charles</a></li><li><a href="http://more-networking.blogspot.com/2006/12/tricks-of-internet-gurus-introduction.html">Tricks of the Internet Gurus</a></li><li><a href="http://more-networking.blogspot.com/2006/12/understanding-osi-by-john-larmouth-this.html">Understanding OSI By John Larmouth</a></li><li><a href="http://more-networking.blogspot.com/2006/12/understanding-tcpip-by-julian-moss.html">Understanding TCP/IP By Julian Moss</a></li><li><a href="http://more-networking.blogspot.com/2007/02/wireless-lan-communications.html">Wireless LAN Communications</a></li><li><a href="http://more-networking.blogspot.com/2007/02/wireless-network-security-80211.html">Wireless Network Security 802.11, Bluetooth and Handheld Devices By Tom Karygiannis and Les Owens</a></li><li><a href="http://more-networking.blogspot.com/2006/12/wireless-networking-in-developing-world.html">Wireless Networking in the Developing World</a></li></ul><a href="http://more-networking.blogspot.com/"><br /></a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-8289748548585530998?l=more-networking.blogspot.com' alt='' /></div>Indian Bloggernoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-31860042237489859272007-04-27T04:14:00.000-07:002008-12-18T13:28:06.879-08:00<div align="center">By Sharam Hekmat</div><blockquote></blockquote><div align="justify">This book is concerned with post-computer communication networks and two of its important streams: data communication and telecommunication. Data communication refers to the communication between digital computers, facilitated by computer networks. Telecommunication refers to the primarily human-to-human communication facilitated by the global telephone system. The differences between these two streams are mainly due to historical reasons. Telecommunication is increasingly relying on digital computer technology, and data communication is relying more than ever on telecommunication networks. The two streams are rapidly converging.</div><div align="justify"><blockquote></blockquote>Newcomers to this field are often bewildered by the substantial wealth of information already published on the subject. This book is aimed at this group of people. It provides a broad coverage of the key concepts, techniques, and terminology, so as to prepare readers for more advanced discussions. In-depth discussions of technically-involved topics are intentionally avoided in favor of more general concepts. No previous knowledge of networks or programming is assumed.<blockquote></blockquote>The structure of the book is as follows. Chapter 1 introduces computer networks and explains some of their elementary concepts. It also introduces the OSI reference model, upon which later chapters are based. Each of Chapters 2-8 describes one of the seven layers of the OSI model in the context of wide area data networks. Chapter 9 looks at local area networks and their applications. Chapter 10 provides an introduction to telecommunication. Chapter 11 builds on earlier chapters by examining ISDN as the merging point of data and voice networks. Chapter 12 looks at the ATM technology and the potential applications that it can support.</div><div align="justify"><blockquote></blockquote><a href="http://www.pragsoft.com/books/CommNetwork.pdf" target="_blank">Click to Download</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-3186004223748985927?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-30467288230876260862007-04-27T04:09:00.000-07:002008-12-18T13:28:06.880-08:00<div align="center">by Eugene Blanchard</div><blockquote></blockquote><div align="justify">Data Communications is the transfer of data or information between a source and a receiver. The source transmits the data and the receiver receives it. The actual generation of the information is not part of Data Communications nor is the resulting action of the information at the receiver. Data Communication is interested in the transfer of data, the method of transfer and the preservation of the data during the transfer process.</div><blockquote></blockquote><div align="justify">In Local Area Networks, we are interested in "connectivity", connecting computers together to share resources. Even though the computers can have different disk operating systems, languages, cabling and locations, they still can communicate to one another and share resources. </div><div align="justify"><blockquote></blockquote>The purpose of Data Communications is to provide the rules and regulations that allow computers with different disk operating systems, languages, cabling and locations to share resources. The rules and regulations are called protocols and standards in Data Communications.....</div><blockquote></blockquote><div align="justify">What is a Network? A network can consist of two computers connected together on a desk or it can consist of many Local Area Networks (LANs) connected together to form a Wide Area Network (WAN) across a continent. </div><div align="justify"><blockquote></blockquote>The key is that 2 or more computers are connected together by a communication medium and they are sharing resources. The resources can be files, printers, hard-drives or cpu number crunching power.....</div><div align="justify"><blockquote></blockquote><a href="http://www.cadvision.com/blanchas/Intro2dcRev2/pagetoc.html#toc" target="_blank">Click to Read More</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-3046728823087626086?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-74076973385978489282007-03-24T03:14:00.000-07:002008-12-18T13:28:06.880-08:00<div align="center">By Elizabeth D. Zwicky, Simon Cooper and D. Brent Chapman</div><blockquote><a name="ch00-66"></a><a name="ch00-66"></a></blockquote><div align="justify"><a name="ch00-66">This book is divided into five parts.</a></div><blockquote></blockquote><div align="justify">Part I, "Network Security", explores the problem of Internet security and focuses on firewalls as part of an effective strategy to address that problem.</div><ul><li><div align="justify">Chapter 1, "Why Internet Firewalls?", introduces the major risks associated with using the Internet today; discusses what to protect, and what to protect against; discusses various security models; and introduces firewalls in the context of what they can and can't do for your site's security.</div></li><li><div align="justify">Chapter 2, "Internet Services", outlines the services users want and need from the Internet, and summarizes the security problems posed by those services.</div></li><li><div align="justify">Chapter 3, "Security Strategies", outlines the basic security principles an organization needs to understand before it adopts a security policy and invests in specific security mechanisms.</div></li></ul><p align="justify">Part II, "Building Firewalls", describes how to build firewalls.</p><ul><li><div align="justify">Chapter 4, "Packets and Protocols ", describes the basic network concepts firewalls work with.</div></li><li><div align="justify">Chapter 5, "Firewall Technologies", explains the terms and technologies used in building firewalls.</div></li><li><div align="justify">Chapter 6, "Firewall Architectures", describes the major architectures used in constructing firewalls, and the situations they are best suited to.</div></li><li><div align="justify">Chapter 7, "Firewall Design", presents the process of designing a firewall.</div></li><li><div align="justify">Chapter 8, "Packet Filtering" describes how packet filtering systems work, and discusses what you can and can't accomplish with them in building a firewall.</div></li><li><div align="justify">Chapter 9, "Proxy Systems", describes how proxy clients and servers work, and how to use these systems in building a firewall.</div></li><li><div align="justify">Chapter 10, "Bastion Hosts", presents a general overview of the process of designing and building the bastion hosts used in many firewall configurations.</div></li><li><div align="justify">Chapter 11, "Unix and Linux Bastion Hosts", presents the details of designing and building a Unix or Linux bastion host.</div></li><li><div align="justify">Chapter 12, "Windows NT and Windows 2000 Bastion Hosts ", presents the details of designing and building a Windows NT bastion host.</div></li></ul><p align="justify">Part III, "Internet Services", describes how to configure services in the firewall environment.</p><ul><li><div align="justify">Chapter 13, "Internet Services and Firewalls", describes the general issues involved in selecting and configuring services in the firewall environment.</div></li><li><div align="justify">Chapter 14, "Intermediary Protocols", discusses basic protocols that are used by multiple services.</div></li><li><div align="justify">Chapter 15, "The World Wide Web", discusses the Web and related services.</div></li><li><div align="justify">Chapter 16, "Electronic Mail and News", discusses services used for transferring electronic mail and Usenet news.</div></li><li><div align="justify">Chapter 17, "File Transfer, File Sharing, and Printing", discusses the services used for moving files from one place to another.</div></li><li><div align="justify">Chapter 18, "Remote Access to Hosts", discusses services that allow you to use one computer from another computer.</div></li><li><div align="justify">Chapter 19, "Real-Time Conferencing Services", discusses services that allow people to interact with each other online.</div></li><li><div align="justify">Chapter 20, "Naming and Directory Services", discusses the services used to distribute information about hosts and users.</div></li><li><div align="justify">Chapter 21, "Authentication and Auditing Services", discusses services used to identify users before they get access to resources, to keep track of what sort of access they should have, and to keep records of who accessed what and when.</div></li><li><div align="justify">Chapter 22, "Administrative Services", discusses other services used to administer machines and networks.</div></li><li><div align="justify">Chapter 23, "Databases and Games", discusses the remaining two major classes of popular Internet services, databases and games.</div></li><li><div align="justify">Chapter 24, "Two Sample Firewalls", presents two sample configurations for basic firewalls.</div></li></ul><p align="justify">Part IV, "Keeping Your Site Secure", describes how to establish a security policy for your site, maintain your firewall, and handle the security problems that may occur with even the most effective firewalls.</p><ul><li><div align="justify">Chapter 25, "Security Policies", discusses the importance of having a clear and well-understood security policy for your site, and what that policy should and should not contain. It also discusses ways of getting management and users to accept the policy.</div></li><li><div align="justify">Chapter 26, "Maintaining Firewalls", describes how to maintain security at your firewall over time and how to keep yourself aware of new Internet security threats and technologies.</div></li><li><div align="justify">Chapter 27, "Responding to Security Incidents", describes what to do when a break-in occurs, or when you suspect that your security is being breached.</div></li></ul><p align="justify">Part V, "Appendixes", consists of the following summary appendixes:</p><ul><li><div align="justify">Appendix A, "Resources", contains a list of places you can go for further information and help with Internet security: World Wide Web pages, FTP sites, mailing lists, newsgroups, response teams, books, papers, and conferences.</div></li><li><div align="justify">Appendix B, "Tools", summarizes the best freely available firewall tools and how to get them.</div></li><li><div align="justify">Appendix C, "Cryptography", contains background information on cryptography that is useful to anyone trying to decrypt the marketing materials for security products.</div></li></ul><blockquote></blockquote><div align="justify"><a href="http://docstore.mik.ua/orelly/networking_2ndEd/fire/index.htm" target="_blank">Click to Read More</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-7407697338597848928?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-3277175424203284052007-03-24T03:05:00.000-07:002008-12-18T13:28:06.880-08:00<div style="text-align: justify;"><div style="text-align: center;">By Paul Albitz and Cricket Liu<br /></div><br />The Domain Name System is a distributed database. This allows local control of the segments of the overall database, yet the data in each segment is available across the entire network through a client-server scheme. Robustness and adequate performance are achieved through replication and caching.<br /><blockquote></blockquote>Programs called name servers constitute the server half of DNS's client-server mechanism. Name servers contain information about some segments of the database and make it available to clients, called resolvers. Resolvers are often just library routines that create queries and send them across a network to a name server.<br /><blockquote></blockquote>The structure of the DNS database is very similar to the structure of the Unix filesystem, as shown in Figure 1-1. The whole database (or filesystem) is pictured as an inverted tree, with the root node at the top. Each node in the tree has a text label, which identifies the node relative to its parent. This is roughly analogous to a "relative pathname" in a filesystem, like bin. One label -- the null label, or "" -- is reserved for the root node. In text, the root node is written as a single dot ( .). In the Unix filesystem, the root is written as a slash ( / ).<br /><blockquote></blockquote>The first implementation of the Domain Name System was called JEEVES, written by Paul Mockapetris himself. A later implementation was BIND, an acronym for Berkeley Internet Name Domain, which was written for Berkeley's 4.3 BSD Unix operating system by Kevin Dunlap. BIND is now maintained by the Internet Software Consortium.<br /><blockquote></blockquote>BIND is the implementation we'll concentrate on in this book and is by far the most popular implementation of DNS today. It has been ported to most flavors of Unix and is shipped as a standard part of most vendors' Unix offerings. BIND has even been ported to Microsoft's Windows NT.<br /><blockquote></blockquote>The fourth edition of this book deals with the new 9.1.0 and 8.2.3 versions of BIND as well as the older 4.9 versions. While 9.1.0 and 8.2.3 are the most recent versions as of this writing, they haven't made their way into many vendors' versions of Unix yet, partly because both versions have only recently been released and many vendors are wary of using such new software. We also occasionally mention other versions of BIND, especially 4.8.3, because many vendors continue to ship code based on this older software as part of their Unix products. Whenever a feature is available only in the 4.9, 8.2.3, or 9.1.0 version, or when there is a difference in the behavior of the versions, we try to point out which version does what.<br /><blockquote></blockquote>We use nslookup, a name server utility program, very frequently in our examples. The version we use is the one shipped with the 8.2.3 BIND code. Older versions of nslookup provide much, but not quite all, of the functionality in the 8.2.3 nslookup. We've used commands common to most nslookup sin most of our examples; when this was not possible, we tried to note it.<br /></div><div align="justify"><blockquote></blockquote><a href="http://docstore.mik.ua/orelly/networking_2ndEd/dns/index.htm" target="_blank">Click to Read More</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-327717542420328405?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-53466586365556015232007-03-24T03:01:00.000-07:002008-12-18T13:28:06.880-08:00<div style="text-align: justify;"><div style="text-align: center;">by Joseph D. Sloan<br /></div><br />This book is not a general introduction to network troubleshooting. Rather, it is about one aspect of troubleshooting -- information collection. This book is a tutorial introduction to tools and techniques for collecting information about computer networks. It should be particularly useful when dealing with network problems, but the tools and techniques it describes are not limited to troubleshooting. Many can and should be used on a regular basis regardless of whether you are having problems.<br /><blockquote></blockquote>Some of the tools I have selected may be a bit surprising to many. I strongly believe that the best approach to troubleshooting is to be proactive, and the tools I discuss reflect this belief. Basically, if you don't understand how your network works before you have problems, you will find it very difficult to diagnose problems when they occur. Many of the tools described here should be used before you have problems. As such, these tools could just as easily be classified as network management or network performance analysis tools.<br /><blockquote></blockquote>This book does not attempt to catalog every possible tool. There are simply too many tools already available, and the number is growing too rapidly. Rather, this book focuses on the tools that I believe are the most useful, a collection that should help in dealing with almost any problem you see. I have tried to include pointers to other relevant tools when there wasn't space to discuss them. In many cases, I have described more than one tool for a particular job. It is extremely rare for two tools to have exactly the same features. One tool may be more useful than another, depending on circumstances. And, because of the differences in operating systems, a specific tool may not be available on every system. It is worth knowing the alternatives.<br /><blockquote></blockquote>The book is about freely available Unix tools. Many are open source tools covered by GNU- or BSD-style licenses. In selecting tools, my first concern has been availability. I have given the highest priority to the standard Unix utilities. Next in priority are tools available as packages or ports for FreeBSD or Linux. Tools requiring separate compilation or available only as binaries were given a lower priority since these may be available on fewer systems. In some cases, PC-only tools and commercial tools are noted but are not discussed in detail. The bulk of the book is specific to Ethernet and TCP/IP, but the general approach and many of the tools can be used with other technologies.<br /><blockquote></blockquote>While this is a book about Unix tools, at the end of most of the chapters I have included a brief section for Microsoft Windows users. These sections are included since even small networks usually include a few computers running Windows. These sections are not, even in the wildest of fantasies, meant to be definitive. They are provided simply as starting points -- a quick overview of what is available.<br /><blockquote></blockquote>Finally, this book describes a wide range of tools. Many of these tools are designed to do one thing and are often overlooked because of their simplicity. Others are extremely complex tools or sets of tools. I have not attempted to provide a comprehensive treatment for each tool discussed. Some of these tools can be extremely complex when used to their fullest. Some have manuals and other documentation that easily exceed the size of this book. Most have additional documentation that you will want to retrieve once you begin using them.<br /><blockquote></blockquote>My goal is to make you aware of the tools and to provide you with enough information that you can decide which ones may be the most useful to you and in what context so that you can get started using the tools. Each chapter centers on a collection of related tasks or problems and tools useful for dealing with these tasks. The discussion is limited to features that are relevant to the problem being discussed. Consequently, the same tool may be discussed in several places throughout the book.<br /><blockquote></blockquote>Please be warned: the suitability or behavior of these tools on your system cannot be guaranteed. While the material in this book is presented in good faith, neither the author nor O'Reilly &amp; Associates makes any explicit or implied warranty as to the behavior or suitability of these tools. We strongly urge you to assess and evaluate these tool as appropriate for your circumstances.<br /><a href="http://docstore.mik.ua/orelly/networking_2ndEd/tshoot/index.htm" target="_blank"><blockquote></blockquote>Click to Read More/Download</a><br /><a href="http://www.amazon.com/gp/product/059600186X?ie=UTF8&amp;tag=frsaabeb-20&amp;linkCode=as2&amp;camp=1789&amp;creative=9325&amp;creativeASIN=059600186X" target="_blank"><blockquote></blockquote>Network Troubleshooting Tools (O'Reilly System Administration)</a><br /><br /></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-5346658636555601523?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-31101098412019896342007-03-24T02:57:00.000-07:002008-12-18T13:28:06.881-08:00<div style="text-align: justify;"><div style="text-align: center;">by Douglas R. Mauro and Kevin J. Schmidt<br /></div><br />The Simple Network Management Protocol (SNMP) is an Internet-standard protocol for managing devices on IP networks. Many kinds of devices support SNMP, including routers, switches, servers, workstations, printers, modem racks, and uninterruptible power supplies (UPSs). The ways you can use SNMP range from the mundane to the exotic: it's fairly simple to use SNMP to monitor the health of your routers, servers, and other pieces of network hardware, but you can also use it to control your network devices and even send pages or take other automatic action if problems arise. The information you can monitor ranges from relatively simple and standardized items, like the amount of traffic flowing into or out of an interface, to more esoteric hardware- and vendor-specific items, like the air temperature inside a router.<br /><blockquote></blockquote>Given that there are already a number of books about SNMP in print, why write another one? Although there are many books on SNMP, there's a lack of books aimed at the practicing network or system administrator. Many books cover how to implement SNMP or discuss the protocol at a fairly abstract level, but none really answers the network administrator's most basic questions: How can I best put SNMP to work on my network? How can I make managing my network easier?<br /><blockquote></blockquote>We provide a brief overview of the SNMP protocol in Chapter 2, "A Closer Look at SNMP" then spend a few chapters discussing issues such as hardware requirements and the sorts of tools that are available for use with SNMP. However, the bulk of this book is devoted to discussing, with real examples, how to use SNMP for system and network administration tasks.<br /><blockquote></blockquote>Most newcomers to SNMP ask some or all of the following questions:<br /><ul><li>What exactly is SNMP?</li><li>How can I, as a system or network administrator, benefit from SNMP?</li><li>What is a MIB?</li><li>What is an OID?</li><li>What is a community string?</li><li>What is a trap?</li><li>I've heard that SNMP is insecure. Is this true?</li><li>Do any of my devices support SNMP? If so, how can I tell if they are configured properly?</li><li>How do I go about gathering SNMP information from a device?</li><li>I have a limited budget for purchasing network-management software. What sort of free/open source software is available?</li><li>Is there an SNMP Perl module that I can use to write cool scripts?<br /></li></ul>This book answers all these questions and more. Our goal is to demystify SNMP and make it more accessible to a wider range of users.<br /><br /><a href="http://docstore.mik.ua/orelly/networking_2ndEd/snmp/index.htm" target="_blank">Click to Read More</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-3110109841201989634?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-5475469662012049892007-03-24T02:51:00.000-07:002008-12-18T13:28:06.881-08:00<div style="text-align: justify;"><div style="text-align: center;">by Hal Stern, Mike Eisler and Ricardo Labiaga<br /></div><br />This book is of interest to system administrators and network managers who are installing or planning new NFS and NIS networks, or debugging and tuning existing networks and servers. It is also aimed at the network user who is interested in the mechanics that hold the network together.<br /><blockquote></blockquote>We'll assume that you are familiar with the basics of Unix system administration and TCP/IP networking. Terms that are commonly misused or particular to a discussion will be defined as needed. Where appropriate, an explanation of a low-level phenomenon, such as Ethernet congestion will be provided if it is important to a more general discussion such as NFS performance on a congested network. Models for these phenomena will be drawn from everyday examples rather than their more rigorous mathematical and statistical roots.<br /><blockquote></blockquote>This book focuses on the way NFS and NIS work, and how to use them to solve common problems in a distributed computing environment. Because Sun Microsystems developed and continues to innovate NFS and NIS, this book uses Sun's Solaris operating system as the frame of reference. Thus if you are administering NFS on non-Solaris systems, you should use this book in conjunction with your vendor's documentation, since utilities and their options will vary by implementation and release. This book explains what the configuration files and utilities do, and how their options affect performance and system administration issues. By walking through the steps comprising a complex operation or by detailing each step in the debugging process, we hope to shed light on techniques for effective management of distributed computing environments. There are very few absolute constraints or thresholds that are universally applicable, so we refrain from stating them. This book should help you to determine the fair utilization and performance constraints for your network.<br /><blockquote></blockquote><a href="http://docstore.mik.ua/orelly/networking_2ndEd/nfs/ch00_08.htm" target="_blank">Click to Read More</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-547546966201204989?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-13460872454088117012007-03-24T02:48:00.000-07:002008-12-18T13:28:06.881-08:00<div align="center">by Daniel J. Barrett and Richard E. Silverman</div><blockquote></blockquote><div align="justify">Privacy is a basic human right, but on today's computer networks, privacy isn't guaranteed. Much of the data that travels on the Internet or local networks is transmitted as plain text, and may be captured and viewed by anybody with a little technical know-how. The email you send, the files you transmit between computers, even the passwords you type may be readable by others. Imagine the damage that can be done if an untrusted third party -- a competitor, the CIA, your in-laws -- intercepted your most sensitive communications in transit.</div><blockquote></blockquote><div align="justify">Network security is big business as companies scramble to protect their information assets behind firewalls, establish virtual private networks (VPNs), and encrypt files and transmissions. But hidden away from all the bustle, there is a small, unassuming, yet robust solution many big companies have missed. It's reliable, reasonably easy to use, cheap, and available for most of today's operating systems.</div><div align="justify"><blockquote></blockquote>It's SSH, the Secure Shell.</div><div align="justify"><blockquote></blockquote><a href="http://docstore.mik.ua/orelly/networking_2ndEd/ssh/index.htm" target="_blank">Click to Read More</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-1346087245408811701?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-29998728367108806262007-03-24T02:44:00.000-07:002008-12-18T13:28:06.882-08:00<div align="center">by Craig Hunt</div><div align="justify"><blockquote></blockquote>The first edition of TCP/IP Network Administration was written in 1992. In the decade since, many things have changed, yet some things remain the same. TCP/IP is still the preeminent communications protocol for linking together diverse computer systems. It remains the basis of interoperable data communications and global computer networking. The underlying Internet Protocol (IP), Transmission Control Protocol, and User Datagram Protocol (UDP) are remarkably unchanged. But change has come in the way TCP/IP is used and how it is managed.<br />A clear symbol of this change is the fact that my mother-in-law has a TCP/IP network connection in her home that she uses to exchange electronic mail, compressed graphics, and hypertext documents with other senior citizens. She thinks of this as "just being on the Internet," but the truth is that her small system contains a functioning TCP/IP protocol stack, manages a dynamically assigned IP address, and handles data types that did not even exist a decade ago.<br /><blockquote></blockquote>In 1991, TCP/IP was a tool of sophisticated users. Network administrators managed a limited number of systems and could count on the users for a certain level of technical knowledge. No more. In 2002, the need for highly trained network administrators is greater than ever because the user base is larger, more diverse, and less capable of handling technical problems on its own. This book provides the information needed to become an effective TCP/IP network administrator.<br /><blockquote></blockquote>TCP/IP Network Administration was the first book of practical information for the professional TCP/IP network administrator, and it is still the best. Since the first edition was published there has been an explosion of books about TCP/IP and the Internet. Still, too few books concentrate on what a system administrator really needs to know about TCP/IP administration. Most books are either scholarly texts written from the point of view of the protocol designer, or instructions on how to use TCP/IP applications. All of those books lack the practical, detailed network information needed by the Unix system administrator. This book strives to focus on TCP/IP and Unix and to find the right balance of theory and practice.<br /><blockquote></blockquote>I am proud of the earlier editions of TCP/IP Network Administration. In this edition, I have done everything I can to maintain the essential character of the book while making it better. Dynamic address assignment based on Dynamic Host Configuration Protocol (DHCP) is covered. The Domain Name System material has been updated to cover BIND 8 and, to a lesser extent, BIND 9. The email configuration is based on current version of sendmail 8, and the operating system examples are from the current versions of Solaris and Linux. The routing protocol coverage includes Routing Information Protocol version 2 (RIPv2), Open Shortest Path First (OSPF), and Border Gateway Protocol (BGP). I have also added a chapter on Apache web server configuration, new material on xinetd, and information about building a firewall with iptables. Despite the additional topics, the book has been kept to a reasonable length.<br /><blockquote></blockquote>TCP/IP is a set of communications protocols that define how different types of computers talk to each other. TCP/IP Network Administration is a book about building your own network based on TCP/IP. It is both a tutorial covering the "why" and "how" of TCP/IP networking, and a reference manual for the details about specific network programs. </div><div align="justify"><blockquote></blockquote><a href="http://docstore.mik.ua/orelly/networking_2ndEd/tcp/index.htm" target="_blank">Click to Read More</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-2999872836710880626?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-41829495205058967252007-03-24T02:40:00.000-07:002008-12-18T13:28:06.882-08:00<div align="center">By D. Brent Chapman and Elizabeth D. Zwicky</div><div align="justify"><blockquote></blockquote>This book is a practical guide to building your own firewall. It provides step-by-step explanations of how to design and install a firewall at your site, and how to configure Internet services such as electronic mail, FTP, the World Wide Web, and others to work with a firewall. Firewalls are complex, though, and we can't boil everything down to simple rules. Too much depends on exactly what hardware, operating system, and networking you are using at your site, and what you want your users to be able to do, and not do. We've tried to give you enough rules, examples, and resources here so you'll be able to do the rest on your own.<br /><blockquote></blockquote>What is a firewall, and what does it do for you? A firewall is a way to restrict access between the Internet and your internal network. You typically install a firewall at the point of maximum leverage, the point where your network connects to the Internet. The existence of a firewall at your site can greatly reduce the odds that outside attackers will penetrate your internal systems and networks. The firewall can also keep your own users from compromising your systems by sending dangerous information - unencrypted passwords and sensitive data - to the outside world.<br /><blockquote></blockquote>The attacks on Internet-connected systems we are seeing today are more serious and more technically complex than those in the past. To keep these attacks from compromising our systems, we need all the help we can get. Firewalls are a highly effective way of protecting your site from these attacks. For that reason, we strongly recommend you include a firewall in your site's overall Internet security plan. However, a firewall should be only one component in that plan. It's also vital that you establish a security policy, that you implement strong host security, and that you consider the use of authentication and encryption devices that work with the firewalls you install. This book will touch on each of these topics while maintaining its focus on firewalls.</div><div align="justify"><blockquote></blockquote><a href="http://doc.novsu.ac.ru/oreilly/tcpip/firewall/index.htm" target="_blank">Click to Read More</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-4182949520505896725?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-36728672179057510982007-03-24T02:36:00.000-07:002008-12-18T13:28:06.882-08:00<div align="center">By Bryan Costales and Eric Allman</div><div align="justify"><blockquote></blockquote>The sendmail program is a Mail Transport Agent (MTA). It accepts mail from Mail User Agents (MUAs), mail users (humans), and other MTAs. It then delivers that mail to Mail Delivery Agents (MDAs) on the local machine, or transports that mail to another MTA at another machine. The behavior of sendmail is determined by its command line and by commands in its configuration file.<br /><blockquote></blockquote>The sendmail program is written and maintained by Eric Allman at sendmail.org. Versions V8.7 and earlier are no longer supported and are no longer considered secure. If you are not currently running V8.8, we recommend you upgrade now. This Desktop Reference covers sendmail version 8.8.5.<br /><blockquote></blockquote>This Desktop Reference is a companion to the second edition of the sendmail book by Bryan Costales with Eric Allman, published by O'Reilly & Associates. Section numbers herein reference the section numbers in that book. This is a reference guide only - for detail or tutorial information, refer to the full sendmail book.</div><div align="justify"><blockquote></blockquote><a href="http://doc.novsu.ac.ru/oreilly/tcpip/smdref/index.htm" target="_blank">Click to Read More</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-3672867217905751098?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-72840042835007972312007-03-24T02:31:00.000-07:002008-12-18T13:28:06.882-08:00<div align="center">By Craig Hunt</div><div align="justify"><blockquote></blockquote>The protocol wars are over and TCP/IP won. TCP/IP is now universally recognized as the pre-eminent communications protocol for linking together diverse computer systems. The importance of interoperable data communications and global computer networks is no longer debated. But that was not always the case. When I wrote the first edition of this book, IPX was far and away the leading PC communications protocol. Microsoft did not bundle communications protocols in their operating system. Corporate networks were so dependent on SNA that many corporate network administrators had not even heard of TCP/IP. Even UNIX, the mother of TCP/IP, nursed a large number of pure UUCP networks. Back then I felt compelled to tout the importance of TCP/IP by pointing out that it was used on thousands of networks and hundreds of thousands of computers. How times have changed! Today we count the hosts and users connected to the Internet in the tens of millions. And the Internet is only the tip of the TCP/IP iceberg. The largest market for TCP/IP is in the corporate<a class="indexterm" name="AUTOID-20"></a> "intranet." An intranet is a private TCP/IP network used to disseminate information within the enterprise. The competing network technologies have shrunk to niche markets where they fill special needs - while TCP/IP has grown to be the communications software that links the world.<br /><blockquote></blockquote>The acceptance of TCP/IP as a worldwide standard and the size of its global user base are not the only things that have changed. In 1991 I lamented the lack of adequate documentation. At the time it was difficult for a<a class="indexterm" name="AUTOID-24"></a> network administrator to find the information he or she needed to do the job. Since that time there has been an explosion of books about TCP/IP and the Internet. However, there are still too few books that concentrate on what a system administrator really needs to know about TCP/IP administration and too many books that try to tell you how to surf the Web. In this book I strive to focus on TCP/IP and UNIX, and not to be distracted by the phenomenon of the Internet.<br /><blockquote></blockquote>I am very proud of the first edition of TCP/IP Network Administration. In the second edition, I have done everything I can to maintain the essential character of the book while making it better. The Domain Name Service material has been updated to cover the latest version of the<a class="indexterm" name="AUTOID-30"></a> BIND 4 software. The email configuration is now based on sendmail<a class="indexterm" name="AUTOID-32"></a> version 8, and the operating system examples are from the current versions of Solaris and Linux. The routing protocol coverage has been expanded to include<a class="indexterm" name="AUTOID-35"></a> Open Shortest Path First (OSPF) and Border Gateway<a class="indexterm" name="AUTOID-37"></a> Protocol (BGP). I have also added new topics such as<a class="indexterm" name="AUTOID-39"></a> one-time passwords and configuration servers based on Dynamic Host<a class="indexterm" name="AUTOID-42"></a> Configuration Protocol (DHCP) and Bootstrap Protocol<a class="indexterm" name="AUTOID-44"></a> (BOOTP). Despite the additional topics, the book has been kept to a reasonable length.<br /><blockquote></blockquote>The bulk of this edition is derived directly from the first edition of the book. To emphasize both that times have changed and that my focus on practical information has not, I have left the introductory paragraphs from the first edition intact.</div><div align="justify"><blockquote></blockquote><a href="http://doc.novsu.ac.ru/oreilly/tcpip/tcpip/index.htm" target="_blank">Click to Read More</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-7284004283500797231?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-78900252532255768822007-03-24T02:20:00.000-07:002008-12-18T13:28:06.883-08:00<div align="center">By Cricket Liu &amp; Paul Albitz</div><div align="justify"><blockquote></blockquote>You may not know much about the<a class="indexterm" name="AUTOID-23"></a> Domain Name System - yet - but whenever you use the Internet, you use DNS. Every time you send electronic mail or surf the World Wide Web, you rely on the Domain Name System.<br /><blockquote></blockquote>You see, while you, as a human being, prefer to remember the names of computers, computers like to address each other by number. On an internet, that number is 32 bits long, or between zero and four billion or so.[1] That's easy for a computer to remember, because computers have lots of memory ideal for storing numbers, but it isn't nearly as easy for us humans. Pick ten phone numbers out of the phone book at random, and then try to remember them. Not easy? Now flip to the front of the book and attach random area codes to the phone numbers. That's about how difficult it would be to remember ten arbitrary internet addresses.<br /><blockquote></blockquote>[1] And, with IP version 6, it's soon to be a whopping 128 bits long, or between zero and a decimal number with 39 digits.<br /><blockquote></blockquote>This is part of the reason we need the Domain Name System. DNS handles mapping between host names, which we humans find convenient, and internet addresses, which computers deal with. In fact, DNS is the standard mechanism on the Internet for advertising and accessing all kinds of information about hosts, not just addresses. And DNS is used by virtually all internetworking software, including electronic mail, remote terminal programs such as telnet, file transfer programs such as ftp, and web browsers such as Netscape Navigator and Microsoft Internet Explorer.<br /><blockquote></blockquote>Another important feature of DNS is that it makes host information available all over the Internet. Keeping information about hosts in a formatted file on a single computer only helps users on that computer. DNS provides a means of retrieving information remotely, from anywhere on the network.<br /><blockquote></blockquote>More than that, DNS lets you distribute the management of host information among many sites and organizations. You don't need to submit your data to some central site or periodically retrieve copies of the "master" database. You simply make sure your section, called a zone, is up to date on your name servers. Your name servers make your zone's data available to all the other name servers on the network.<br /><blockquote></blockquote>Because the database is distributed, the system also needs the ability to locate the data you're looking for by searching a number of possible locations. The Domain Name System gives name servers the intelligence to navigate through the database and find data in any zone.<br />Of course, DNS does have a few problems. For example, the system allows more than one name server to store data about a zone, for redundancy's sake. But inconsistencies can crop up between copies of the zone data.<br /><blockquote></blockquote>But the worst problem with DNS is that despite its widespread use on the Internet, there's really very little<a class="indexterm" name="AUTOID-54"></a><a class="indexterm" name="AUTOID-57"></a> documentation about managing and maintaining it. Most administrators on the Internet make do with the documentation their vendors see fit to provide, and with whatever they can glean from following the Internet mailing lists and Usenet newsgroups on the subject.<br /><blockquote></blockquote>This lack of documentation means that the understanding of an enormously important internet service - one of the linchpins of today's Internet - is either handed down from administrator to administrator like a closely-guarded family recipe, or relearned repeatedly by isolated programmers and engineers. New administrators of domains suffer through the same mistakes made by countless others.<br /><blockquote></blockquote>Our aim with this book is to help remedy this situation. We realize that not all of you have the time or the desire to become DNS experts. Most of you, after all, have plenty to do besides managing a domain or a name server: system administration, network engineering, or software development. It takes an awfully big institution to devote a whole person to DNS. We'll try to give you enough information to allow you to do what you need to do, whether that's running a small domain or managing a multinational monstrosity, tending a single name server or shepherding a hundred of them. Read as much as you need to know now, and come back later if you need to know more.<br /><blockquote></blockquote>DNS is a big topic - big enough to require two authors, anyway - but we've tried to present it as sensibly and understandably as possible. The first two chapters give you a good theoretical overview and enough practical information to get by, and later chapters fill in the nitty-gritty details. We provide a roadmap up front, to suggest a path through the book appropriate for your job or interest.<br /><blockquote></blockquote>When we talk about actual DNS software, we'll concentrate almost exclusively on BIND, the Berkeley Internet Name Domain software, which is the most popular implementation of the DNS specs (and the one we know best). We've tried to distill our experience in managing and maintaining a domain with BIND into this book - a domain, incidentally, that is one of the largest on the Internet. (We don't mean to brag, but we can use the credibility.) Where possible, we've included the real programs that we use in administration, many of them rewritten into Perl for speed and efficiency.<br /><blockquote></blockquote>We hope that this book will help you get acquainted with DNS and BIND if you're just starting out, let you refine your understanding if you're already familiar with them, and provide valuable insight and experience even if you know 'em like the back of your hand.</div><div align="justify"><blockquote></blockquote><a href="http://doc.novsu.ac.ru/oreilly/tcpip/dnsbind/index.htm" target="_blank">Click to Read More</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-7890025253225576882?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-83391228078500201042007-02-14T15:39:00.000-08:002010-09-20T02:02:30.452-07:00<div align="justify">Hacking and cracking are activities that generate intense public interest. Stories of hacked servers and downed Internet providers appear regularly in national news. Consequently, publishers are in a race to deliver books on these subjects. To its credit, the publishing community has not failed in this resolve. Security books appear on shelves in ever-increasing numbers. However, the public remains wary. Consumers recognize driving commercialism when they see it, and are understandably suspicious of books such as this one. They need only browse the shelves of their local bookstore to accurately assess the situation.</div><blockquote></blockquote><div align="justify">Books about Internet security are common (firewall technology seems to dominate the subject list). In such books, the information is often sparse, confined to a narrow range of products. Authors typically include full-text reproductions of stale, dated documents that are readily available on the Net. This poses a problem, mainly because such texts are impractical. Experienced readers are already aware of these reference sources, and inexperienced ones are poorly served by them. Hence, consumers know that they might get little bang for their buck. Because of this trend, Internet security books have sold poorly at America's neighborhood bookstores.</div><blockquote></blockquote><div align="justify">Another reason that such books sell poorly is this: The public erroneously believes that to hack or crack, you must first be a genius or a UNIX guru. Neither is true, though admittedly, certain exploits require advanced knowledge of the target's operating system. However, these exploits can now be simplified through utilities that are available for a wide range of platforms. Despite the availability of such programs, however, the public remains mystified by hacking and cracking, and therefore, reticent to spend forty dollars for a hacking book.</div><div align="justify">So, at the outset, Sams.net embarked on a rather unusual journey in publishing this book. The Sams.net imprint occupies a place of authority within the field. Better than two thirds of all information professionals I know have purchased at least one Sams.net product. For that reason, this book represented to them a special situation.</div><div align="justify">Hacking, cracking, and Internet security are all explosive subjects. There is a sharp difference between publishing a primer about C++ and publishing a hacking guide. A book such as this one harbors certain dangers, including </div><ul><li>The possibility that readers will use the information maliciously</li><li>The possibility of angering the often-secretive Internet-security community</li><li><br /><br /><div align="justify">The possibility of angering vendors that have yet to close security holes within their software </div></li></ul><div align="justify"><a href="http://w3.msi.vxu.se/%7Edna/760/nykurs/Maximum%20Security%20-%20A%20Hacker%27s%20Guide%20to%20Protecting%20Your%20Inter.pdf" target="_blank">Click to Read More</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-8339122807850020104?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-83146925457293736472007-02-14T15:34:00.000-08:002008-12-18T13:28:06.883-08:00<div align="justify">This document presents an overview of two IBM wireless LAN products, IBMWireless LAN Entry and IBM Wireless LAN, and the technology they use for wireless communications. The information provided includes product descriptions, features and functions. Some known product limitations as well as a cross-product comparison are included to assist the reader in understanding where and which product to use for given circumstances.</div><div align="justify"><blockquote></blockquote>Also documented are examples of product setup, configuration and the development of various scenarios conducted by the authors. Our intended audience is customers, network planners, network administrators and system specialists who have a need to evaluate, implement and maintain wireless networks. A basic understanding of LAN communications terminology and familiarity with common IBM and industry network products and tools is assumed.</div><div align="justify"><blockquote></blockquote><a href="http://www.redbooks.ibm.com/abstracts/sg244466.html" target="_blank">Click to Download</a></div><div align="justify"> </div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-8314692545729373647?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-28162054703227964462007-02-14T15:27:00.000-08:002008-12-18T13:28:06.884-08:00<div align="center">By Michael Hauben and Ronda Hauben</div><blockquote></blockquote><p> </p><p><strong>Introduction By Thomas Truscott</strong></p><div align="justify">Netizens: On the Impact and History of Usenet and the Internet is an ambitious look at the social aspects of computer networking. It examines the present and the turbulent future, and especially it explores the technical and social roots of the "Net". A well told history can be entertaining, and an accurately told history can provide us valuable lessons. Here follow three lessons for inventors and a fourth for social engineers. Please test them out when reading the book. </div><blockquote></blockquote><div align="justify">The first lesson is to keep projects simple at the beginning. Projects tend to fail so the more one can squeeze into a year the better the chance of stumbling onto a success. Big projects do happen, but there is not enough time in life for very many of them, so choose carefully. </div><blockquote></blockquote><div align="justify">The second lesson is to innovate by taking something old and something new and putting them together in a new way. In this book the "something new" is invariably the use of a computer network. For example, ancient timesharing computer systems had local "mail" services so its users could communicate. But the real power of E-mail was when mail could be distributed to distant computers and all the networked users could communicate. Similarly, Usenet is a distributed version of preexisting bulletin-board-like systems. The spectacularly successful World Wide Web is just a distributed version of a hypertext document system. It was remarkably simple, and seemingly obvious, yet it caught the world by complete surprise. Here is another way to state this lesson: If a feature is good, then a distributed version of the feature is good. And vice-versa. </div><blockquote></blockquote><div align="justify">The third lesson is to keep on the lookout for "something new", or for something improved enough to make a qualitative difference. For example, in the future we will have home computers that are always on and connected to the Net. That is a qualitative difference that will trigger numerous innovations. </div><blockquote></blockquote><div align="justify">The fourth lesson is that we learn valuable lessons by trying out new innovations. Neither the original ARPAnet nor Usenet would have been commercially viable. Today there are great forces battling to structure and control the information superhighway, and it is invaluable that the Internet and Usenet exist as working models. Without them it would be quite easy to argue that the information superhighway should have a top-down hierarchical command and control structure. After all there are numerous working models for that. </div><div align="justify"><blockquote></blockquote>It seems inevitable that new innovations will continue to make the future so bright that it hurts. And it also seems inevitable that as innovations permeate society the rules for them will change. I am confident that Michael Hauben and Ronda Hauben will be there to chronicle the rapidly receding history and the new future, as "Netizens" increasingly becomes more than a title for a book.</div><div align="justify"><blockquote></blockquote><a href="http://www.columbia.edu/~hauben/netbook/" target="_blank">Click to Read More</a></div><div align="justify"> </div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-2816205470322796446?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-28910601937711103432007-02-14T15:21:00.000-08:002008-12-18T13:28:06.884-08:00<div align="justify">The Internet has been highly successful in meeting the original vision of providing ubiquitous computer-to-computer interaction in the face of heterogeneous underlying technologies. No longer a research plaything, the Internet is widely used for production systems and has a very large installed base. Commercial interests play a major role in shaping its ongoing development. Success, however, has been a double-edged sword, for with it has come the danger of ossification, or inability to change, in multiple dimensions:</div><blockquote></blockquote><ul><li><div align="justify">Intellectual ossification—The pressure for compatibility with the current Internet risks stifling innovative intellectual thinking. For example, the frequently imposed requirement that new protocols not compete unfairly with TCP-based traffic constrains the development of alternatives for cooperative resource sharing. Would a paper on the NETBLT protocol that proposed an alternative approach to control called “rate-based” (in place of “window-based”) be accepted for publication today?</div></li><li><div align="justify">Infrastructure ossification—The ability of researchers to affect what is deployed in the core infrastructure (which is operated mainly by businesses) is extremely limited. For example, pervasive network-layer multicast remains unrealized, despite considerable research and efforts to transfer that research to products.</div></li><li><div align="justify">System ossification—Limitations in the current architecture have led to shoe-horn solutions that increase the fragility of the system. For example, network address translation violates architectural assumptions about the semantics of addresses. The problem is exacerbated because a research result is often judged by how hard it will be to deploy in the Internet, and the Internet service providers sometimes favor more easily deployed approaches that may not be desirable solutions for the long run.</div></li></ul><p align="justify">At the same time, the demands of users and the realities of commercial interests present a new set of challenges that may very well require a fresh approach. The Internet vision of the last 20 years has been to have all computers communicate. The ability to hide the details of the heterogeneous underlying technologies is acknowledged to be a great strength of the design, but it also creates problems because the performance variability associated with underlying network capacity, time-varying loads, and the like means that applications work in some circumstances but not others. More generally, outsiders advocated a more user-centric view of networking research—a perspective that resonated with a number of the networking insiders as well. Drawing on their own experiences, insiders commented that users are likely to be less interested in advancing the frontiers of high communications bandwidth and more interested in consistency and quality of experience, broadly defined to include the “ilities”—reliability, manageability, configurability, predictability, and so forth—as well as non-performance-based concerns such as security and privacy. (Interest was also expressed in higher-performance, broadband last-mile access, but this is more of a deployment issue than a research problem.) Outsiders also observed that while as a group they may share some common requirements, users are very diverse—in experience, expertise, and what they wish the network could do. Also, commercial interests have given rise to more diverse roles and complex relationships that cannot be ignored when developing solutions to current and future networking problems. These considerations argue that a vision for the future Internet should be to provide users the quality of experience they seek and to accommodate a diversity of interests.</p><p align="justify"><a href="http://www.nap.edu/books/0309076137/html/" target="_blank">Click to Read More</a></p><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-2891060193771110343?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-23772983441246514682007-02-14T15:02:00.000-08:002008-12-18T13:28:06.884-08:00<div align="center">By Reg Quinton</div><blockquote></blockquote><div align="justify">These course notes are directed at Unix application programmers who want to develop client/server applications in the TCP/IP domain (with some hints for those who want to write UDP/IP applications). Since the Berkeley socket interface has become something of a standard these notes will apply to programmers on other platforms. </div><blockquote></blockquote><div align="justify">Fundamental concepts are covered including network addressing, well known services, sockets and ports. Sample applications are examined with a view to developing similar applications that serve other contexts. Our goals are </div><blockquote></blockquote><ul><li><div align="justify">to develop a function, tcpopen(server,service), to connect to service. </div></li><li><div align="justify">to develop a server that we can connect to. </div></li></ul><p align="justify">This course requires an understanding of the C programming language and an appreciation of the programming environment (ie. compilers, loaders, libraries, Makefiles and the RCS revision control system). </p><p align="justify"><strong>Netstat Observations:</strong><br />Inter Process Communication (or IPC) is between host.port pairs (or host.service if you like). A process pair uses the connection -- there are client and server applications on each end of the IPC connection. </p><p align="justify">Note the two protocols on IP -- TCP (Transmission Control Protocol) and UDP (User Datagram Prototocol). There's a third protocl ICMP (Internet Control Message Protocol) which we'll not look at -- it's what makes IP work in the first place! </p><p align="justify">TCP services are connection orientated (like a stream, a pipe or a tty like connection) while UDP services are connectionless (more like telegrams or letters). </p><p align="justify">We recognize many of the services -- SMTP (Simple Mail Transfer Protocol as used for E-mail), NNTP (Network News Transfer Protocol service as used by Usenet News), NTP (Network Time Protocol as used by xntpd(8)), and SYSLOG is the BSD service implemented by syslogd(1M). </p><p align="justify">The netstat(1M) display shows many TCP services as ESTABLISHED (there is a connection between client.port and server.port) and others in a LISTEN state (a server application is listening at a port for client connections). You'll often see connections in a CLOSE_WAITE state -- they're waiting for the socket to be torn down. </p><p align="justify"><a href="http://www.ods.com.ua/win/eng/program/socket/socketprg.html" target="_blank">Click to Read More</a></p><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-2377298344124651468?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-45069166344852402392007-02-14T14:58:00.000-08:002008-12-18T13:28:06.884-08:00<div align="center">By <a name="AEN4">Jennifer Vesperman</a></div><div align="justify"><blockquote></blockquote>The secure transmission of data in transit relies on both encryption and authentication - on both the hiding or concealment of the data itself, and on ensuring that the computers at each end are the computers they say they are. </div><blockquote></blockquote><div align="justify"><strong>Authentication</strong><br />Authentication is a difficult task - computers have no way of knowing that they are 'the computer that sits next to the printer on the third floor' or 'the computer that runs the sales for www.dotcom.com'. And those are the matters which are important to humans - humans don't care if the computer is '10.10.10.10', which is what the computers know. </div><blockquote></blockquote><div align="justify">However, if the computer can trust the human to tell it which computer address to look for - either in the numeric or the name form - the computers can then verify that each other is, in fact, the computer at that address. It's similar to using the post office - we want to know if 100 Somewhere Street is where our friend Sally is, but the post office just wants to know where to send the parcel. </div><blockquote></blockquote><div align="justify">The simplest form of authentication is to exchange secret information the first time the two computers communicate and check it on each subsequent connection. Most exchanges between computers take place over a long period of time, in computer terms, so they tend to do this in a small way for the duration of each connection - as if you were checking, each time you spoke in a phone call, that the person you were talking to was still that person. (Sally, is that you? Yeah. Good, now I was telling you about the kids .. is that still you?) </div><div align="justify"><blockquote></blockquote>It may sound paranoid, but this sort of verification system can inhibit what is called a 'man in the middle' attack - where a third party tries to 'catch' the connection and insert their own information. Of course, this relies on the first communication not being intercepted. </div><div align="justify"><blockquote></blockquote>Public key encryption (see below) is the other common means of authentication. It doesn't authenticate the sender, but it does authenticate the receiver - and if both parties exchange public keys, and verify by some independant means that the key they have is the key of the party they wish to send to, it authenticates both. </div><div align="justify"><blockquote></blockquote><a href="http://www.faqs.org/docs/SecuringData-INTRO/" target="_blank">Click to Read More</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-4506916634485240239?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-5938186705705544232007-02-14T14:53:00.000-08:002008-12-18T13:28:06.885-08:00<div align="justify">There are many different computing and networking technologies -- some available today, some just now emerging, some well-proven, some quite experimental. Understanding the computing dilemma more completely involves recognizing technologies; especially since a single technology by itself seldom suffices, and instead, multiple technologies are usually necessary.</div><blockquote></blockquote><div align="justify">This document describes a sampling of technologies of various types, by using a tutorial approach. It compares the technologies available in the three major technology areas: application support, transport networks, and subnetworking. In addition, the applicability of these technologies within a particular situation is illustrated using a set of typical customer situations.</div><div align="justify"><blockquote></blockquote>This document can be used by consultants and system designers to better understand, from a business and technical perspective, the options available to solve customers' networking problems.</div><div align="justify"><blockquote></blockquote><a href="http://publib-b.boulder.ibm.com/Redbooks.nsf/RedbookAbstracts/gg244338.html" target="_blank">Click to Download</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-593818670570554423?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-31065204712220594282007-02-14T14:48:00.000-08:002008-12-18T13:28:06.885-08:00<div align="center">By <a name="AEN5">Jennifer Vesperman</a></div><blockquote></blockquote><div align="justify">If your computer is not connected to any other computers and doesn't have a modem, the only way anyone can access your computer's information is by physically coming to the computer and sitting at it. So securing the room it's in will secure the computer. As soon as your computer is connected to another computer you add the possibility that someone using the other computer can access your computer's information.<br /></div><blockquote></blockquote><div align="justify">If your network (your connected computers) consists only of other computers in the same building you can still secure the network by securing the rooms the computers are in. An example of this would be two computers sharing the same files and printer, but not having a modem and not being connected to any other computers.</div><div align="justify"><blockquote></blockquote>However, it's wise to learn about other ways to secure a network of connected computers, in case you add something later. Networks have a tendency to grow. If you have a network, an intruder who gains access to one computer has at least some access to all of them.</div><div align="justify"><blockquote></blockquote>Note: Note that once someone has physical access to your computer, there are a number of ways that they can access your information. Most systems have some sort of emergency feature that allows someone with physical access to get in and change the superuser password, or access the data. Even if your system doesn't have that, or it's disabled, they can always just pick up the computer or remove the hard drive and carry it out. More on this in the physical security article.</div><div align="justify"><blockquote></blockquote><a href="http://www.faqs.org/docs/Intrusion-INTRO/" target="_blank">Click to Read More</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-3106520471222059428?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-83943315212832311982007-02-14T14:44:00.000-08:002008-12-18T13:28:06.885-08:00<div align="justify">This is an introduction to the Internet networking protocols (TCP/IP).It includes a summary of the facilities available and briefdescriptions of the major protocols in the family.</div><div align="justify"><blockquote></blockquote><strong>What is TCP/IP?</strong></div><div align="justify">TCP/IP is a set of protocols developed to allow cooperating computersto share resources across a network. It was developed by a communityof researchers centered around the ARPAnet. Certainly the ARPAnet isthe best-known TCP/IP network. However as of June, 87, at least 130different vendors had products that support TCP/IP, and thousands ofnetworks of all kinds use it.</div><blockquote></blockquote><div align="justify">First some basic definitions. The most accurate name for the set ofprotocols we are describing is the "Internet protocol suite". TCP andIP are two of the protocols in this suite. (They will be describedbelow.) Because TCP and IP are the best known of the protocols, ithas become common to use the term TCP/IP or IP/TCP to refer to thewhole family. It is probably not worth fighting this habit. Howeverthis can lead to some oddities. For example, I find myself talkingabout NFS as being based on TCP/IP, even though it doesn't use TCP atall. (It does use IP. But it uses an alternative protocol, UDP,instead of TCP. All of this alphabet soup will be unscrambled in thefollowing pages.)</div><div align="justify"><blockquote></blockquote>The Internet is a collection of networks, including the Arpanet,NSFnet, regional networks such as NYsernet, local networks at a numberof University and research institutions, and a number of militarynetworks. The term "Internet" applies to this entire set of networks.The subset of them that is managed by the Department of Defense isreferred to as the "DDN" (Defense Data Network). This includes someresearch-oriented networks, such as the Arpanet, as well as morestrictly military ones. (Because much of the funding for Internetprotocol developments is done via the DDN organization, the termsInternet and DDN can sometimes seem equivalent.) All of thesenetworks are connected to each other. Users can send messages fromany of them to any other, except where there are security or otherpolicy restrictions on access. Officially speaking, the Internetprotocol documents are simply standards adopted by the Internetcommunity for its own use. More recently, the Department of Defenseissued a MILSPEC definition of TCP/IP. This was intended to be a moreformal definition, appropriate for use in purchasing specifications.However most of the TCP/IP community continues to use the Internetstandards. The MILSPEC version is intended to be consistent with it.</div><div align="justify"><blockquote></blockquote><a href="http://www.comms.scitech.susx.ac.uk/fft/networking/IntroToInternetProtocols.txt" target="_blank">Click to Read More</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-8394331521283231198?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-43917321710675877672007-02-14T14:38:00.000-08:002008-12-18T13:28:06.886-08:00<div align="justify">Because of the rapid and ongoing developments in the field of networking, accurate troubleshooting information is an ever sought-after commodity. Because of this, the Cisco Press Internetworking Troubleshooting Handbook is a valuable resource for networking professionals throughout the industry. </div><div align="justify"><blockquote></blockquote>For the second edition of this book, we gathered together a team of troubleshooting experts who thoroughly revised the material in each of the technology areas to include the most current and relevant troubleshooting information and solutions available today. Their goal and ours was to provide networking professionals with a guide containing solutions to the problems encountered in the field in a format that is easy to apply. We hope that this publication meets that goal. </div><div align="justify"><blockquote></blockquote>The Internetworking Troubleshooting Handbook was written as a resource for anyone working in the field of networking who needs troubleshooting reference information. We anticipate that the information in this publication will assist users in solving specific technology issues and problems that they encounter in their existing environments. </div><div align="justify"><blockquote></blockquote><a href="http://www.cisco.com/univercd/cc/td/doc/cisintwk/itg_v1/index.htm" target="_blank">Click to Read More</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-4391732171067587767?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-50408778763942340362007-02-14T14:31:00.000-08:002008-12-18T13:28:06.886-08:00<div align="justify">For the foreseeable future a significant percentage of devices usingan ATM network will do so indirectly, and will continue to be directly attached to "legacy" media (such as Ethernet and token ring). In addition these devices will continue to utilize "legacy" internetwork layer protocols (for example, IP, IPX, APPN, etc.). This means that inorder to effectively use ATM, there must be efficient methods available for operating multiple internetwork layer protocols over heterogeneous networks built from ATM switches, routers, and other switched devices. This challenge is commonly referred to as theoperation of multiprotocol over ATM.</div><blockquote></blockquote><div align="justify">This book reviews the various options for the transport and support of multiprotocols over ATM.</div><blockquote></blockquote><div align="justify">This book was written for networking consultants, systems specialists, system planners, network designers and network administrators who need to learn about SVN and associated protocols in order to design and deploy networks that utilize components from this framework. It provides readers with the ability to differentiate between the different offerings. A working knowledge of ATM is assumed.</div><div align="justify"><blockquote></blockquote>It is intended to be used with "High-Speed Networking Technology: An Introductory Survey", which describes methods for data transmission in high speed networks, and "Asynchronous Transport Mode (ATM) Technical Overview", which describes ATM, a link-level protocol using the methods described in "High-Speed Networking Technology: An Introductory Survey"to transmit various types of data together over the same physical links. This book describes the networking protocols that use ATM as the underlying link level protocol.</div><div align="justify"><blockquote></blockquote><a href="http://www.redbooks.ibm.com/abstracts/sg244699.html" target="_blank">Click to Download</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-5040877876394234036?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-91896020880043012262007-02-14T14:00:00.000-08:002008-12-18T13:28:37.823-08:00<div align="justify">This publication presents a broad overview on the emerging technology ofvery-high-speed communication. It is written at the technical conceptuallevel with some areas of greater detail. It is intended to be read bycomputer professionals who have some understanding of communications(but who do not necessarily consider themselves experts).</div><blockquote></blockquote><div align="justify">The primary topics of the book are:- </div><ul><li><div align="justify">The Principles of High-Speed Networking</div></li><li><div align="justify">Fibre Optical Technology and Optical Networks</div></li><li><div align="justify">Local Area Networks (Token-Ring, FDDI, MetaRing, CRMA,Radio LANs)</div></li><li><div align="justify">Metropolitan Area Networks (DQDB, SMDS)</div></li><li><div align="justify">High-Speed Packet Switches (Frame Relay, Paris, plaNET)</div></li><li><div align="justify">High-Speed Cell Switching (ATM)</div></li></ul><p align="justify"><a href="http://www.redbooks.ibm.com/abstracts/gg243816.html" target="_blank">Click to Download</a></p><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-9189602088004301226?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-26090544375168133662007-02-14T13:37:00.000-08:002008-12-18T13:28:37.824-08:00<div align="justify">Contains various network component specifications and photos with explanation. Following networking topics are covered</div><ul><li>Motivation and Tools</li><li>Network Programming And Applications</li><li>Transmission Media</li><li>Local Asynchronous Communication (RS-232)</li><li>Long-Distance Communication (Carriers, Modulation, And Modems)</li><li>Packets, Frames, And Error Detection</li><li>LAN Technologies And Network Topology</li><li>Hardware Addressing And Frame Type Identification</li><li>LAN Wiring, Physical Topology, And Interface Hardware</li><li>Extending LANs: Fiber Modems, Repeaters, Bridges, and Switches</li><li>Long-Distance And Local Loop Digital Technologies</li><li>WAN Technologies And Routing</li><li>Connection-Oriented Networking And ATM</li><li>Network Characteristics: Ownership, Service Paradigm, And Performance</li><li>Protocols And Layering</li><li>Internetworking: Concepts, Architecture, and Protocols</li><li>IP: Internet Protocol Addresses</li><li>Binding Protocol Addresses (ARP)</li><li>IP Datagrams And Datagram Forwarding</li><li>IP Encapsulation, Fragmentation, And Reassembly</li><li>The Future IP (IPv6)</li><li>An Error Reporting Mechanism (ICMP)</li><li>UDP: Datagram Transport Service</li><li>TCP: Reliable Transport Service</li><li>Network Address Translation</li><li>Internet Routing</li><li>Client-Server Interaction</li><li>The Socket Interface</li><li>Example Of A Client And A Server</li><li>Naming With The Domain Name System</li><li>Electronic Mail Representation And Transfer</li><li>IP Telephony (VoIP)</li><li>File Transfer And Remote File Access</li><li>World Wide Web Pages And Browsing</li><li>Dynamic Web Document Technologies (CGI, ASP, JSP, PHP, ColdFusion)</li><li>Active Web Document Technologies (Java, JavaScript)</li><li>RPC and Middleware</li><li>Network Management (SNMP)</li><li>Network Security</li><li>Initialization (Configuration)</li></ul><p><a href="http://www.netbook.cs.purdue.edu/toc/toc00.htm" target="_blank">Click to Read More</a></p><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-2609054437516813366?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-87764044894517571062007-02-14T13:28:00.000-08:002008-12-18T13:28:37.824-08:00<div align="center">By Hans-Peter Bischof </div><blockquote></blockquote><div align="justify">An introduction to the organization and structuring of computer networks. </div><blockquote></blockquote><div align="justify">The following quesions describe what will be covered in this course. </div><ul><li><div align="justify">What is a computer network? </div></li><li><div align="justify">What can we do with a computer network? </div></li></ul><p align="justify">Keywords: (IPethernet)-address, TCP/IP, UDP, router, bridge, socket, rpc, rpcgen, server, client, arp, rarp ... </p><p align="justify"><strong>Protocol Layering<br /></strong>Protocol layering is a common technique to simplify networking designs by dividing them into functional layers, and assigning protocols to perform each layer's task. </p><p align="justify">For example, it is common to separate the functions of data delivery and connection management into separate layers, and therefore separate protocols. Thus, one protocol is designed to perform data delivery, and another protocol, layered above the first, performs connection management. The data delivery protocol is fairly simple and knows nothing of connection management. The connection management protocol is also fairly simple, since it doesn't need to concern itself with data delivery. </p><p align="justify">Protocol layering produces simple protocols, each with a few well-defined tasks. These protocols can then be assembled into a useful whole. Individual protocols can also be removed or replaced.<br />The most important layered protocol designs are the Internet's original DoD model, and the OSI Seven Layer Model. The modern Internet represents a fusion of both models. </p><p align="justify"><a href="http://www.cs.rit.edu/~hpb/Lectures/98_445/all.html" target="_blank">Click to Read More</a></p><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-8776404489451757106?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-79040615099847326822007-02-14T13:13:00.000-08:002008-12-18T13:28:37.824-08:00<div align="center">from Certicom</div><div align="justify"><br />The Wireless Application Protocol (WAP) is a leading technology for companies trying to unlock the value of the Mobile Internet.</div><div align="justify"><blockquote></blockquote>Certicom products and services provide complete WAP security solutions today for all of those players involved in bringing the Internet to the mobile end-user — including content providers, equipment manufacturers, network operators, application service providers and enterprises.</div><div align="justify"><blockquote></blockquote><strong>WAP</strong><br />The WAP (Wireless Application Protocol) is a suite of specifications that enable wireless Internet applications; these specifications can be found at http://www.wapforum.org). WAP provides the framework to enable targeted Web access, mobile e-commerce, corporate intranet access, and other advanced services to digital wireless devices, including mobile phones, PDAs, two-way pagers, and other wireless devices. The suite of WAP specifications allows manufacturers, network operators, content providers and application developers to offer compatible products and services that work across varying types of digital devices and networks. Even for companies wary of WAP, individual elements of the WAP standards can prove useful by providing industry-standard wireless protocols and data formats.<br /><blockquote></blockquote>The WAP architecture is based on the realization that for the near future, networks and client devices (e.g., mobile phones) will have limited capabilities. The networks will have bandwidth and latency limitations, and client devices will have limited processing, memory, power, display and user interaction capabilities. Therefore, Internet protocols cannot be processed as is; an adaptation for wireless environments is required. The entire suite of WAP specifications are derived from equivalent IETF specifications used on the Internet, modified for use within the limited capabilities in the wireless world.<br /><blockquote></blockquote>Furthermore, the WAP model introduces a Gateway that translates between WAP and Internet protocols. This Gateway is typically located at the site of the mobile operator, although sometimes it may be run by an application service provider or enterprise.</div><div align="justify"><blockquote></blockquote><a href="http://www.comms.scitech.susx.ac.uk/fft/networking/WAPsec.pdf" target="_blank">Click to Download</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-7904061509984732682?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-45508432031530038562007-02-14T13:07:00.000-08:002008-12-18T13:28:37.824-08:00This file contains examples of client and servers using several protocols, might be very usefull.<br /><blockquote></blockquote><div align="justify">Sockets are a generalized networking capability first introduced in 4.1cBSD and subsequently refined into their current form with 4.2BSD. The sockets feature is available with most current UNIX system releases. (Transport Layer Interface (TLI) is the System V alternative). Sockets allow communication between two different processes on the same or different machines. Internet protocols are used by default for communication between machines; other protocols such as DECnet can be used if they are available. </div><blockquote></blockquote><div align="justify">To a programmer a socket looks and behaves much like a low level file descriptor. This is because commands such as read() and write() work with sockets in the same way they do with files and pipes. The differences between sockets and normal file descriptors occurs in the creation of a socket and through a variety of special operations to control a socket. These operations are different between sockets and normal file descriptors because of the additional complexity in establishing network connections when compared with normal disk access. </div><blockquote></blockquote><div align="justify">For most operations using sockets, the roles of client and server must be assigned. A server is a process which does some function on request from a client. As will be seen in this discussion, the roles are not symmetric and cannot be reversed without some effort. </div><blockquote></blockquote><div align="justify">This description of the use of sockets progresses in three stages: </div><blockquote></blockquote><div align="justify">The use of sockets in a connectionless or datagram mode between client and server processes on the same host. In this situation, the client does not explicitly establish a connection with the server. The client, of course, must know the server's address. The server, in turn, simply waits for a message to show up. The client's address is one of the parameters of the message receive request and is used by the server for response. </div><blockquote></blockquote><div align="justify">The use of sockets in a connected mode between client and server on the same host. In this case, the roles of client and server are further reinforced by the way in which the socket is established and used. This model is often referred to as a connection-oriented client-server model. </div><blockquote></blockquote><div align="justify">The use of sockets in a connected mode between client and server on different hosts. This is the network extension of Stage 2, above. </div><div align="justify"><blockquote></blockquote>The connectionless or datagram mode between client and server on different hosts is not explicitly discussed here. Its use can be inferred from the presentations made in Stages 1 and 3.</div><div align="justify"><blockquote></blockquote><a href="http://home.mit.bme.hu/%7Ecsertan/oktatas/beagyazott/sinfo1.html" target="_blank">Click to Read More</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-4550843203153003856?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-1310069641230734122007-02-14T13:01:00.000-08:002008-12-18T13:28:37.824-08:00<div align="justify">This publication presents a broad overview on the emerging technology of very high-speed communications. It is written at the "technical conceptual" level with some areas of greater detail. </div><div align="justify"><blockquote></blockquote>It was written for computer professionals who have some understanding of communications (but who do not necessarily consider themselves experts).</div><blockquote></blockquote><div align="justify">The primary topics of the book are:</div><ul><li><div align="justify">Asynchronous Transfer Mode (ATM)</div></li><li><div align="justify">High-Speed Cell Switching</div></li><li><div align="justify">Broadband ISDN</div></li></ul><p align="justify">This publication is published by Prentice Hall and will be sold inexternal bookstores.</p><p align="justify"><a href="http://www.redbooks.ibm.com/abstracts/sg244625.html" target="_blank">Click to Download</a></p><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-131006964123073412?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-733275536644478672007-02-14T12:53:00.000-08:002008-12-18T13:28:37.825-08:00<div align="center">By Fernando Paganini, Steven H. Low, ZhikuiWang, Sanjeewa Athuraliya and John C. Doyle</div><div align="justify"><br />We describe a new congestion avoidance system designed to maintain dynamic stability on networks of arbitrary delay, capacity, and topology. This is motivated by recent work showing the limited stability margins of TCP Reno/RED as delay or network capacity scale up. Based on earlier work establishing mathematical requirements for local stability, we develop new flow control laws that satisfy these conditions together with a certain degree of fairness in bandwidth allocation. When a congestion measure signal from links to sources is available, the system can satisfy also the key objectives of high utilization and emptying the network queues in equilibrium.</div><div align="justify"><blockquote></blockquote>We develop a packet-level implementation of this protocol, where the congestion measure is communicated back to sources via random exponential marking of an ECN bit. We discuss parameter choices for the marking and estimation system, and demonstrate using ns-2 simulations the stability of the protocol, and the nearempty equilibrium queues, for a wide range of delays. Comparisons with the behavior of Reno /RED are provided. We also explore the situation where ECN is not used, and instead queueing delay is used as a pricing signal. This alternative protocol is also stable, but will inevitably exhibit nontrivial queues.</div><div align="justify"><blockquote></blockquote><a href="http://www.comms.scitech.susx.ac.uk/fft/networking/scalable2.pdf" target="_blank">Click to Download</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-73327553664447867?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-31751731728655470872007-02-14T12:49:00.000-08:002008-12-18T13:28:37.825-08:00<div align="justify">This redbook closely examines the functionality of the Internet Key Exchange protocol (IKE) - which is derived from the Internet Security Associations Key Management Protocol (ISAKMP) and the Oakley protocol. IKE provides a framework and key exchange protocol for Virtual Private Networks (VPN) that are based on the IP Security Architecture (IPSec) protocols. An overview of VPN technologies based on the latest standards is provided in Part I.</div><blockquote></blockquote><div align="justify">This redbook also helps you understand, install and configure the most current VPN product implementations from IBM, in particular AIX, OS/400, Nways routers, OS/390, and several client and OEM platforms. After reading this redbook, you will be able to use those products to implement different VPN scenarios. An overview of the functions and configuration of the VPN components of those products is provided in Part II.</div><blockquote></blockquote><div align="justify">The main focus of this redbook is on how to implement complete VPN solutions using state-of-the-art VPN technlogoies, and to document IBM product interoperability. This redbook is therefore not meant to be an exhaustive VPN design guide. The authors would like to refer the reader to IBM security and network consulting services for that purpose.</div><div align="justify"><blockquote></blockquote>This redbook is a follow-on to the VPN Vol. 1 (SG24-5201) and VPN Vol. 2 (SG24-5234) redbooks. A basic understanding of IP security and cryptographic concepts and network security policies is assumed.</div><div align="justify"><blockquote></blockquote><a href="http://www.redbooks.ibm.com/abstracts/sg245309.html" target="_blank">Click to Download</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-3175173172865547087?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-70798277611516193232007-02-14T12:45:00.000-08:002008-12-18T13:28:37.825-08:00<div align="justify">The Internet nowadays is not only a popular vehicle to retrieve and exchange information in traditional ways, such as e-mail, file transfer and Web surfing. It is being used more and more by companies to replace their existing telecommunications infrastructure with virtual private networks by implementing secure IP tunnels across the Internet between corporate sites as well as to business partners and remote locations. </div><blockquote></blockquote><div align="justify">This updated redbook includes the IPSec enhancements provided by Version 3.3 of the IBM Nways Multiprotocol Routing Services (MRS), Nways Multiprotocol Access Services (MAS) and Access Integration Services (AIS) that implement the Internet Key Exchange (IKE) protocol. This redbook also includes other new features, such as the policy engine, digital certificate and LDAP support, and QoS. The VPN scenarios are enhanced to reflect the latest implementation of IPSec and L2-tunneling functionality.</div><blockquote></blockquote><div align="justify">In this redbook we delve further into these scenarios by showing you how to implement solutions that exploit Data Link Switching (DLSw), IP Bridging Tunnels, Enterprise Extender (HPR over IP), APPN DLUR, TN3270, and Tunneling on layer 2 (L2TP, L2F, PPTP) through an IPSec tunnel.</div><div align="justify"><blockquote></blockquote>A working knowledge of the IPSec protocols is assumed.</div><div align="justify"><blockquote></blockquote><a href="http://www.redbooks.ibm.com/abstracts/sg245234.html" target="_blank">Click to Download</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-7079827761151619323?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-16061698085429998172007-02-14T12:28:00.000-08:002008-12-18T13:28:37.825-08:00<div align="center">By Jeffrey Wheat, Randy Hiser, Jackie Tucker, Alicia Neely and Andy McCullough</div><div align="justify"><br />Understand How Wireless Communication Works</div><ul><li><div align="justify">Step-by-Step Instructions for Designing a Wireless Project from Inception to Completion</div></li><li><div align="justify">Everything You Need to Know about Bluetooth,LMDS, 802.11, and Other Popular Standards</div></li><li><div align="justify">Complete Coverage of Fixed Wireless,Mobile Wireless, and Optical<br />Wireless Technology</div></li></ul><p align="justify"><strong>Introduction</strong></p><p align="justify">You’ve been on an extended business trip and have spent the long hours of the flight drafting follow-up notes from your trip while connected to the airline’s onboard server. After deplaning, you walk through the gate and continue into the designated public access area. Instantly, your personal area network (PAN) device, which is clipped to your belt, beeps twice announcing that it automatically has retrieved your e-mail, voicemail, and videomail.You stop to view the videomail—a finance meeting—and also excerpts from your children’s school play.</p><p align="justify">Meanwhile, when you first walked into the public access area, your personal area network device contacted home via the Web pad on your refrigerator and posted a message to alert the family of your arrival.Your spouse will know you’ll be home from the airport shortly. </p><p align="justify">You check the shuttlebus schedule from your PAN device and catch the next convenient ride to long-term parking.You also see an e-mail from your MP3 group showing the latest selections, so you download the latest MP3 play list to listen to on the way home.</p><p align="justify">As you pass through another public access area, an e-mail comes in from your spouse.The Web pad for the refrigerator inventory has noted that you’re out of milk, so could you pick some up on the way home? You write your spouse back and say you will stop at the store.When you get to the car, you plug your PAN device into the car stereo input port.With new music playing from your car stereo’s MP3 player, you drive home, with a slight detour to buy milk at the nearest store that the car’s navigation system can find.</p><p align="justify">The minute you arrive home, your PAN device is at work, downloading information to various devices.The data stored on your PAN device is sent to your personal computer (PC) and your voicemail is sent to the Bluetooth playback unit on the telephone-answering device.The PAN device sends all video to the television, stored as personal files for playback. As you place the milk in the refrigerator, the Web pad updates to show that milk is currently in inventory and is no longer needed.The kids bring you the television remote and you check out possible movies<br />together to download later that night.</p><p align="justify"><a href="http://www.ebookee.com.cn/Designing-a-Wireless-Network_178062.html" target="_blank">Click to Download</a></p><p align="justify"><a href="http://www.amazon.com/gp/product/1928994458?ie=UTF8&amp;tag=frsaabeb-20&amp;linkCode=as2&amp;camp=1789&amp;creative=9325&amp;creativeASIN=1928994458" target="_blank">Designing a Wireless Network</a></p><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-1606169808542999817?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-36816499200347908812007-02-14T12:00:00.000-08:002008-12-18T13:28:37.826-08:00<div align="justify">The increased popularity of Cisco routers has led to their ubiquitous presence within the network infrastructure of many enterprises. In such large corporations, it is also common for many applications to execute on the z/OS (formerly OS/390) platform. As a result, the interoperation of z/OS-based systems and Cisco network infrastructures is a crucial aspect of many enterprise internetworks. </div><blockquote></blockquote><div align="justify">This IBM Redbook provides a survey of the components necessary to achieve full interoperation between your z/OS-based servers and your Cisco IP routing environment. It may be used as a network design guide for understanding the considerations of the many aspects of interoperation. We divide this discussion into four major components:</div><ul><li><div align="justify">The options and configuration of channel-attached Cisco routers</div></li><li><div align="justify">The design considerations for combining OSPF-based z/OS systems with Cisco-based EIGRP networks</div></li><li><div align="justify">A methodology for deploying Quality of Service policies throughout the network </div></li><li><div align="justify">The implementation of load balancing and high availability using Sysplex Distributor and MNLB (including new z/OS V1R2 support)</div></li></ul><p align="justify">We highlight our discussion with a realistic implementation scenario and real configurations that will aid you in the deployment of these solutions. In addition, we provide in-depth discussions, traces, and traffic visualizations to show the technology at work.</p><p align="justify"><a href="http://www.redbooks.ibm.com/abstracts/sg246297.html" target="_blank">Click to Download</a></p><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-3681649920034790881?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-79858399668067415862007-02-14T11:55:00.000-08:002008-12-18T13:28:37.826-08:00<div align="justify"><blockquote></blockquote>Networks are an interconnection of computers. These computers can be linked together using a wide variety of different cabling types, and for a wide variety of different purposes. </div><blockquote></blockquote><div align="justify">The basis reasons why computers are networked are </div><blockquote></blockquote><ul><li><div align="justify">to share resources (files, printers, modems, fax machines) </div></li><li><div align="justify">to share application software (MS Office) </div></li><li><div align="justify">increase productivity (make it easier to share data amongst users) </div></li></ul><p align="justify">Take for example a typical office scenario where a number of users in a small business require access to common information. As long as all user computers are connected via a network, they can share their files, exchange mail, schedule meetings, send faxes and print documents all from any point of the network. </p><p align="justify">It would not be necessary for users to transfer files via electronic mail or floppy disk, rather, each user could access all the information they require, thus leading to less wasted time and hence greater productivity. </p><p align="justify">Imagine the benefits of a user being able to directly fax the Word document they are working on, rather than print it out, then feed it into the fax machine, dial the number etc. </p><p align="justify">Small networks are often called Local Area Networks [LAN]. A LAN is a network allowing easy access to other computers or peripherals. The typical characteristics of a LAN are, </p><blockquote></blockquote><ul><li><div align="justify">physically limited ( less than 2km)</div></li><li><div align="justify">high bandwidth (greater than 1mbps) </div></li><li><div align="justify">inexpensive cable media (coax or twisted pair) </div></li><li><div align="justify">data and hardware sharing between users </div></li><li><div align="justify">owned by the user </div></li></ul><p align="justify"><a href="http://www.scribd.com/doc/3774300/Networking" target="_blank">Click to Read More about networking</a></p><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-7985839966806741586?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-79138288215801909162007-02-14T11:48:00.000-08:002008-12-18T13:28:37.826-08:00<div align="center"><span style="font-size:100%;">By Tom Karygiannis and Les Owens</span></div><div align="justify"><blockquote><span style="font-size:100%;"></span></blockquote><span style="font-size:100%;">Wireless communications offer organizations and users many benefits such as portability and flexibility, increased productivity, and lower installation costs. Wireless technologies cover a broad range of differing capabilities oriented toward different uses and needs. Wireless local area network (WLAN) devices, for instance, allow users to move their laptops from place to place within their offices without the need for wires and without losing network connectivity. Less wiring means greater flexibility, increased efficiency, and reduced wiring costs. Ad hoc networks, such as those enabled by Bluetooth, allow data synchronization with network systems and application sharing between devices. Bluetooth functionality also eliminates cables for printer and other peripheral device connections. Handheld devices such as personal digital assistants (PDA) and cell phones allow remote users to synchronize personal databases and provide access to network services such as wireless e-mail, Web browsing, and Internet access. Moreover, these technologies can offer dramatic cost savings and new capabilities to diverse applications ranging from retail settings to manufacturing shop floors to first responders.</span></div><blockquote><span style="font-size:100%;"></span></blockquote><div align="justify"><span style="font-size:100%;">However, risks are inherent in any wireless technology. Some of these risks are similar to those of wired networks; some are exacerbated by wireless connectivity; some are new. Perhaps the most significant source of risks in wireless networks is that the technology’s underlying communications medium, the airwave, is open to intruders, making it the logical equivalent of an Ethernet port in the parking lot.</span></div><blockquote><span style="font-size:100%;"></span></blockquote><div align="justify"><span style="font-size:100%;">The loss of confidentiality and integrity and the threat of denial of service (DoS) attacks are risks typically associated with wireless communications. Unauthorized users may gain access to agency systems and information, corrupt the agency’s data, consume network bandwidth, degrade network performance, launch attacks that prevent authorized users from accessing the network, or use agency resources to launch attacks on other networks.</span></div><div align="justify"><blockquote><span style="font-size:100%;"></span></blockquote><a href="http://csrc.nist.gov/publications/nistpubs/800-48/NIST_SP_800-48.pdf" target="_blank"><span style="font-size:100%;">Click to Download</span></a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-7913828821580190916?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-28653686333962165692007-02-14T11:44:00.000-08:002008-12-18T13:28:37.827-08:00<div align="justify"><strong>An Introduction to the Key Security Issues for the E-Business Economy</strong><br />With the explosion of the public Internet and e-commerce, private computers, and computer networks, if not adequately secured, are increasingly vulnerable to damaging attacks. Hackers, viruses, vindictive employees and even human error all represent clear and present dangers to networks. And all computer users, from the most casual Internet surfers to large enterprises, could be affected by network security breaches. However, security breaches can often be easily prevented. How? This guide provides you with a general overview of the most common network security threats and the steps you and your organization can take to protect yourselves from threats and ensure that the data traveling across your networks is safe.</div><blockquote></blockquote><div align="justify"><strong>Importance of Security</strong><br />The Internet has undoubtedly become the largest public data network, enabling and facilitating both personal and business communications worldwide. The volume of traffic moving over the Internet, as well as corporate networks, is expanding exponentially every day. More and more communication is taking place via e-mail; mobile workers, telecommuters, and branch offices are using the Internet to remotely connect to their corporate networks; and commercial transactions completed over the Internet, via the World Wide Web, now account for large portions of corporate revenue.</div><div align="justify"><blockquote></blockquote><a href="http://www.cisco.com/warp/public/cc/so/neso/sqso/beggu_pl.pdf" target="_blank">Click to Download</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-2865368633396216569?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-9438581310560985672007-02-14T11:38:00.000-08:002008-12-18T13:28:37.827-08:00<div align="justify">Local Area Network Concepts and Products is a set of four reference books forthose looking for conceptual and product-specific information in the LAN environment. They provide a technical introduction to the various types of IBM local area network architectures and product capabilities.</div><blockquote></blockquote><div align="justify">The four volumes are as follows:</div><div align="justify">SG24-4753-00 - LAN Architecture</div><div align="justify">SG24-4754-00 - LAN Adapters, Hubs and ATM</div><div align="justify">SG24-4755-00 - Routers and Gateways</div><div align="justify">SG24-4756-00 - LAN Operating Systems and Management</div><blockquote></blockquote><div align="justify">These redbooks complement the reference material available for the products discussed. Much of the information detailed in these books is available through current redbooks and IBM sales and reference manuals. It is therefore assumed that the reader will refer to these sources for morein-depth information if required.</div><blockquote></blockquote><div align="justify">These documents are intended for customers, IBM technical professionals, services specialists, marketing specialists, and marketing representatives working in networking and in particular the local area network environments.</div><blockquote></blockquote><div align="justify">Details on installation and performance of particular products will not be included in these books, as this information is available from other sources.</div><div align="justify"><blockquote></blockquote>Some knowledge of local area networks, as well as an awareness of the rapidly changing intelligent workstation environment, is assumed.</div><div align="justify"><blockquote></blockquote><a href="http://www.redbooks.ibm.com/abstracts/sg244755.html" target="_blank">Click to Download</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-943858131056098567?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-40351741082578707172007-02-14T11:29:00.000-08:002008-12-18T13:28:37.827-08:00<div align="center">By Peter Bieringer </div><div align="justify"><blockquote></blockquote>IPv6 is a new layer 3 protocol (see linuxports/howto/intro_to_networking/ISO - OSI Model) which will supersede IPv4 (also known as IP). IPv4 was designed long time ago (<a href="http://www.faqs.org/rfcs/rfc760.html" target="_blank">RFC 760 / Internet Protocol</a> from January 1980) and since its inception, there have been many requests for more addresses and enhanced capabilities. Latest RFC is <a href="http://www.faqs.org/rfcs/rfc760.html" target="_blank">RFC 2460 / Internet Protocol Version 6 Specification</a>. Major changes in IPv6 are the redesign of the header, including the increase of address size from 32 bits to 128 bits. Because layer 3 is responsible for end-to-end packet transport using packet routing based on addresses, it must include the new IPv6 addresses (source and destination), like IPv4. </div><div align="justify"><blockquote></blockquote>Because of lack of manpower, the IPv6 implementation in the kernel was unable to follow the discussed drafts or newly released RFCs. In October 2000, a project was started in Japan, called USAGI, whose aim was to implement all missing, or outdated IPv6 support in Linux. It tracks the current IPv6 implementation in FreeBSD made by the KAME project. From time to time they create snapshots against current vanilla Linux kernel sources. </div><div align="justify"><blockquote></blockquote>USAGI is now making use of the new Linux kernel development series 2.5.x to insert all of their current extensions into this development release. Hopefully the 2.6.x kernel series will contain a true and up-to-date IPv6 implementation. </div><div align="justify"><blockquote></blockquote><a href="http://www.faqs.org/docs/Linux-HOWTO/Linux+IPv6-HOWTO.html" target="_blank">Click to Read More</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-4035174108257870717?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-14742180590196479832007-02-14T11:24:00.000-08:002008-12-18T13:28:37.827-08:00<div align="justify"><strong>What Is an Internetwork?</strong> <a name="wp1020554"></a><br />An internetwork is a collection of individual networks, connected by intermediate networking devices, that functions as a single large network. Internetworking refers to the industry, products, and procedures that meet the challenge of creating and administering internetworks.</div><div align="justify"><strong><blockquote><strong></strong></blockquote>History of Internetworking</strong> <a name="wp1020561"></a><br />The first networks were time-sharing networks that used mainframes and attached terminals. Such environments were implemented by both IBM's Systems Network Architecture (SNA) and Digital's network architecture. <a name="wp1020562"></a><br /><blockquote></blockquote>Local-area networks (LANs) evolved around the PC revolution. LANs enabled multiple users in a relatively small geographical area to exchange files and messages, as well as access shared resources such as file servers and printers. <a name="wp1020564"></a><br /><blockquote></blockquote>Wide-area networks (WANs) interconnect LANs with geographically dispersed users to create connectivity. Some of the technologies used for connecting LANs include T1, T3, ATM, ISDN, ADSL, Frame Relay, radio links, and others. New methods of connecting dispersed LANs are appearing everyday. <a name="wp1020565"></a><br /><blockquote></blockquote>Today, high-speed LANs and switched internetworks are becoming widely used, largely because they operate at very high speeds and support such high-bandwidth applications as multimedia and videoconferencing. <a name="wp1020566"></a><br /><blockquote></blockquote>Internetworking evolved as a solution to three key problems: isolated LANs, duplication of resources, and a lack of network management. Isolated LANs made electronic communication between different offices or departments impossible. Duplication of resources meant that the same hardware and software had to be supplied to each office or department, as did separate support staff. This lack of network management meant that no centralized method of managing and troubleshooting networks existed. </div><div align="justify"><blockquote></blockquote><a href="http://www.cisco.com/en/US/docs/internetworking/technology/handbook/ito_doc.html" target="_blank">Click to Read More</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-1474218059019647983?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-91466572975936594002007-02-14T10:45:00.000-08:002008-12-18T13:28:37.828-08:00<div align="justify">The potential for realizing a national information networking marketplace that can enrich people's economic, social, and political lives has recently been unlocked through the convergence of three developments: </div><blockquote></blockquote><ul><li><div align="justify">The federal government's promotion of the National Information Infrastructure through an administration initiative and supporting congressional actions; </div></li><li><div align="justify">The runaway growth of the Internet, an electronic network complex developed initially for and by the research community; and </div></li><li><div align="justify">The recognition by entertainment, telephone, and cable TV companies of the vast commercial potential in a national information infrastructure. </div></li></ul><p align="justify">A national information infrastructure (NII) can provide a seamless web of interconnected, interoperable information networks, computers, databases, and consumer electronics that will eventually link homes, workplaces, and public institutions together. It can embrace virtually all modes of information generation, transport, and use. The potential benefits can be glimpsed in the experiences to date of the research and education communities, where access through the Internet to high-speed networks has begu n to radically change the way researchers work, educators teach, and students learn. </p><p align="justify">To a large extent, the NII will be a transformation and extension of today's computing and communications infrastructure (including, for example, the Internet, telephone, cable, cellular, data, and broadcast networks). Trends in each of these component areas are already bringing about a next-generation information infrastructure. Yet the outcome of these trends is far from certain; the nature of the NII that will develop is malleable. Choices will be made in industry and government, beginning with inv estments in the underlying physical infrastructure. Those choices will affect and be affected by many institutions and segments of society. They will determine the extent and distribution of the commercial and societal rewards to this country for invest ments in infrastructure-related technology, in which the United States is still currently the world leader. </p><p align="justify">1994 is a critical juncture in our evolution to a national information infrastructure. Funding arrangements and management responsibilities are being defined (beginning with shifts in NSF funding for the Internet), commercial service providers are playi ng an increasingly significant role, and nonacademic use of the Internet is growing rapidly. Meeting the challenge of "wiring up" the nation will depend on our ability not only to define the purposes that the NII is intended to serve, but also to ensure that the critical technical issues are considered and that the appropriate enabling physical infrastructure is put in place.</p><p align="justify"><a href="http://books.nap.edu/html/rtif/" target="_blank">Click to Read More</a></p><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-9146657297593659400?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-40688872360327930472007-02-14T10:41:00.000-08:002008-12-18T13:28:37.828-08:00<div align="justify">The PVM project began in the summer of 1989 at Oak Ridge National Laboratory. The prototype system, PVM 1.0, was constructed by Vaidy Sunderam and Al Geist; this version of the system was used internally at the Lab and was not released to the outside. Version 2 of PVM was written at the University of Tennessee and released in March 1991. During the following year, PVM began to be used in many scientific applications. After user feedback and a number of changes (PVM 2.1 - 2.4), a complete rewrite was undertaken, and version 3 was completed in February 1993. It is PVM version 3.3 that we describe in this book (and refer to simply as PVM). The PVM software has been distributed freely and is being used in computational applications around the world. </div><div align="justify"><blockquote></blockquote>To successfully use this book, one should be experienced with common programming techniques and understand some basic parallel processing concepts. In particular, this guide assumes that the user knows how to write, execute, and debug Fortran or C programs and is familiar with Unix. </div><div align="justify"><blockquote></blockquote><a href="http://www.netlib.org/pvm3/book/pvm-book.html" target="_blank">Click to Read More</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-4068887236032793047?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-22093963921428238032007-02-14T10:34:00.000-08:002008-12-18T13:28:37.828-08:00<div align="center"><span style="color: rgb(51, 102, 255);"><strong>By Noel Estabrook </strong></span></div><div align="center"><blockquote></blockquote>Contributing Author: Bill Vernon </div><div align="justify"><blockquote></blockquote>Here is a quick preview of what you'll find in this book:<br /><blockquote></blockquote>Part I, "The Basics," takes you through some of the things you'll need to know before you start. You'll get a clear explanation of what the Internet is really like, learn how you can actually use the Internet in real life, find tips on Internet Service Providers, and receive an introduction to the World Wide Web.<br /><blockquote></blockquote>Part II, "E-Mail: The Great Communicator," teaches you all you'll need to know about e-mail. Learn basics like reading and sending e-mail, as well as more advanced functions such as attaching documents, creating aliases, and more. You'll also find out all about listservs and how to use them to your advantage.<br /><blockquote></blockquote>Part III, "News and Real-Time Communication," shows you many of the things that make the Internet an outstanding tool for communication. You'll learn about newsgroups and how to communicate with thousands of people by clicking your mouse. You'll also learn how to carry on live, real-time conversations over the Internet, as well as get information on some of the hottest new technology such as Net Phones.<br /><blockquote></blockquote>Part IV, "The World Wide Web," shows you what is now the most exciting part of the Internet. Learn which browser is best for you, get the basics of Web navigation, and find out how to help your browser with plug-ins. Finally, you'll discover the most powerful tool on the Web today--the search engine--and more importantly, how to use it.<br /><blockquote></blockquote>Part V, "Finding Information on the Net," explains some of the other useful functions of the Net. You'll learn how to transfer files and use Gopher. You'll also learn how to access libraries and other resources by using Telnet. Finally, this section will show you how to use the Internet to locate people, places, and things that might not be available directly through the Web.<br /><blockquote></blockquote>Part VI, "Getting the Most Out of the Internet," shows you practical ways to use the Internet. You can find resources and techniques on how to get information about entertainment, education, and business. Finally, learn how to use the Internet just to have fun. </div><div align="justify"><blockquote></blockquote><a href="http://www.ssuet.edu.pk/taimoor/books/1-57521-236-6/htm/fm.htm" target="_blank">Click to Read More</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-2209396392142823803?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-61179542154625274932007-02-14T10:29:00.000-08:002008-12-18T13:28:37.829-08:00<div align="center">By <a id="I7" name="I7">Patrick Smith </a></div><div align="justify"><blockquote></blockquote>In a competitive world it is necessary for organizations to take advantage of every opportunity to reduce cost, improve quality, and provide service. Most organizations today recognize the need to be market driven, to be competitive, and to demonstrate added value.<br /><blockquote></blockquote>A strategy being adopted by many organizations is to flatten the management hierarchy. With the elimination of layers of middle management, the remaining individuals must be empowered to make the strategy successful. Information to support rational decision making must be made available to these individuals. Information technology (IT) is an effective vehicle to support the implementation of this strategy; frequently it is not used effectively. The client/server model provides power to the desktop, with information available to support the decision-making process and enable decision-making authority.<br /><blockquote></blockquote>The Gartner Group, a team of computer industry analysts, noted a widening chasm between user expectations and the ability of information systems (IS) organizations to fulfill them. The gap has been fueled by dramatic increases in end-user comfort with technology (mainly because of prevalent PC literacy); continuous cost declines in pivotal hardware technologies; escalation in highly publicized vendor promises; increasing time delays between vendor promised releases and product delivery (that is, "vaporware"); and emergence of the graphical user in terface (GUI) as the perceived solution to all computing problems.<br /><blockquote></blockquote>In this book you will see that client/server computing is the technology capable of bridging this chasm. This technology, particularly when integrated into the normal business process, can take advantage of this new literacy, cost-effective technology, and GUI friendliness. In conjunction with a well-architected systems development environment (SDE), it is possible for client/server computing to use the technology of today and be positioned to take advantage of vendor promises as they become real.<br /><blockquote></blockquote>The amount of change in computer processing-related technology since the introduction of the IBM PC is equivalent to all the change that occurred during the previous history of computer technology. We expect the amount of change in the next few years to be even more geometrically inclined. The increasing rate of change is primarily attributable to the coincidence of four events: a dramatic reduction in the cost of processing hardware, a significant increase in installed and available processing power, the introduction of widely adopted software standards, and the use of object-oriented development techniques. The complexity inherent in the pervasiveness of these changes has prevented most business and government organizations from taking full advantage of the potential to be more competitive through improved quality, increased service, reduced costs, and higher profits. Corporate IS organizations, with an experience based on previous technologies, are often less successful than user groups in putting the new technologies to good use.<br /><blockquote></blockquote>Taking advantage of computer technology innovation is one of the most effective ways to achieve a competitive advantage and demonstrate value in the marketplace. Technology can be used to improve service by quickly obtaining the information necessary to make decisions and to act to resolve problems. Technology can also be used to reduce costs of repetitive processes and to improve quality through consistent application of those processes. The use of workstation technology implemented as part of the business process and integrated with an organization's existing assets provides a practical means to achieve competitive advantage and to demonstrate value.<br /><blockquote></blockquote>Computer hardware continues its historical trend toward smaller, faster, and lower-cost systems. Competitive pressures force organizations to reengineer their business processes for cost and service efficiencies. Computer technology trends prove to leading organizations that the application of technology is the key to successful reengineering of business processes.<br /><blockquote></blockquote>Unfortunately, we are not seeing corresponding improvements in systems development. Applications developed by inhouse computer professionals seem to get larger, run more slowly, and cost more to operate. Existing systems consume all available IS resources for maintenance and enhancements. As personal desktop environments lead users to greater familiarity with a GUI, corporate IS departments continue to ignore this technology. The ease of use and standard look and feel, provided by GUIs in personal productivity applications at the desktop, is creating an expectation in the user community. When this expectation is not met, IS departments are considered irrelevant by their users.<br /><blockquote></blockquote>Beyond GUI, multimedia technologies are using workstation power to re-present information through the use of image, video, sound, and graphics. These representations relate directly to the human brain's ability to extract information from images far more effectively than from lists of facts.<br /><blockquote></blockquote>Accessing information CAN be as easy as tapping an electrical power utility. What is required is the will among developers to build the skills to take advantage of the opportunity offered by client/server computing.<br /><blockquote></blockquote>This book shows how organizations can continue to gain value from their existing technology investments while using the special capabilities that new technologies offer. The book demonstrates how to architect SDEs and create solutions that are solidly based on evolving technologies. New systems can be built to work effectively with today's capabilities and at the same time can be based on a technical architecture that will allow them to evolve and to take advantage of future technologies.<br /><blockquote></blockquote>For the near future, client/server solutions will rely on existing minicomputer and mainframe technologies to support applications already in use, and also to provide shared access to enterprise data, connectivity, and security services. To use existing investments and new technologies effectively, we must understand how to integrate these into our new applications. Only the appropriate application of standards based technologies within a designed architecture will enable this to happen.<br /><blockquote></blockquote>It will not happen by accident.<br /><blockquote></blockquote><span style="color: rgb(51, 51, 255);">Patrick N. Smith with Steven L. Guengerich</span> </div><div align="justify"><blockquote></blockquote><a href="http://www.ssuet.edu.pk/taimoor/books/0-672-30473-2/index.htm" target="_blank">Click to Read More</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-6117954215462527493?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-59031970375194755632006-12-26T02:03:00.000-08:002008-12-18T13:28:37.829-08:00<div align="center">Microsoft TechNet</div><div align="justify"><blockquote></blockquote>This online book is a structured, introductory approach to the basic concepts and principles of the Transmission Control Protocol/Internet Protocol (TCP/IP) protocol suite, how the most important protocols function, and their basic configuration in the Microsoft® Windows Server® 2003 and Windows® XP operating systems. This book is primarily a discussion of concepts and principles to lay a conceptual foundation for the TCP/IP protocol suite. Unlike many other introductory TCP/IP texts, this book provides an integrated discussion of both Internet Protocol version 4 (IPv4) and Internet Protocol version 6 (IPv6). </div><blockquote></blockquote><div align="justify">This book is not a discussion of TCP/IP planning, configuration, deployment, management, or application development. For a discussion of TCP/IP planning, configuration, deployment, and management, see the online Help for Windows Server 2003 and the Windows Server 2003 Deployment Kit. For a discussion of how to develop TCP/IP applications using Windows Sockets, see the Microsoft Developer Network.</div><div align="justify"><blockquote></blockquote>This book provides an educational vehicle for the fundamentals of TCP/IP to either prepare you for a career in information technology or to augment your knowledge of TCP/IP-based networking in Microsoft Windows. This book is not intended to be a primer for computing or networking technology.</div><div align="justify"><blockquote></blockquote><a href="http://www.microsoft.com/technet/network/evaluate/technol/tcpipfund/tcpipfund.mspx" target="_blank">Click to Read More</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-5903197037519475563?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-21716629578561109352006-12-26T01:56:00.000-08:002008-12-18T13:28:37.829-08:00<div align="center">By Christopher R. Hertel</div><blockquote></blockquote><div align="justify">CIFS is a network filesystem plus a set of auxiliary services supported by a bunch of underlying protocols. Any and all of these various bits have been called CIFS, which leaves us with a somewhat muddy definition. To make things easier, we'll start by saying that CIFS is "Microsoft's way of doing network file sharing", and work out the details as we go on. </div><div align="justify"><blockquote></blockquote>The name "CIFS", of course, is an acronym. It stands for Common Internet File System, a title which deserves a bit of dissection: </div><strong></strong><blockquote><strong><strong></strong></strong></blockquote><div align="justify"><strong>Common</strong><br />The term has a variety of connotations, but we will assume that Microsoft was thinking of common in the sense of commonly available or commonly used. All MS operating systems have had some form of CIFS networking available or built in, and there are implementations of CIFS for most major non-MS operating systems as well. </div><div align="justify"><blockquote></blockquote>Unfortunately, there is not yet a specification for CIFS that is complete, correct, authoritative, and freely available. Microsoft defines CIFS by their implementations and, as we shall see, their attempts at documenting the complete suite have been somewhat random. This has an adverse impact on the commonality of the system.......</div><div align="justify"><blockquote><a href="http://ubiqx.org/cifs/" target="_blank"></a><a href="http://ubiqx.org/cifs/" target="_blank"></a></blockquote><a href="http://ubiqx.org/cifs/" target="_blank">Click to Read More/Download</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-2171662957856110935?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-71445099744704828932006-12-26T01:49:00.000-08:002008-12-18T13:28:37.829-08:00<div align="center">By John Larmouth</div><blockquote></blockquote><div align="justify">This text aims to provide an intelligent near-beginner (as far as OSI is concerned) with an understanding of Open Systems Interconnection (OSI). Some previous acquaintance with data communications as presented in the many text books on that broad subject would be useful. The book is aimed at the reader who is curious enough to ask: "Why is it that way? What advantages does that approach give? Might there be other or better ways?" </div><div align="justify"><blockquote></blockquote>This text is not an exposition of the technical detail of the OSI Standards. Rather it aims to explain why OSI is the shape it is, and to guide the reader in a critical examination of the OSI approach to specifying rules for computer communication (computer protocols). The text should be particularly valuable for those who are newly moving into positions where they are a part of a team developing applications using OSI, either in the International Standards' work or for their own firm. The text would also be useful for those sections of undergraduate and taught masters' courses that are dealing with OSI, either as the main text or as follow-on reading. </div><div align="justify"><blockquote></blockquote>Much of the material of necessity represents personal perceptions and reasoning, as the real reasons for approaches and choices are rarely presented in International Standards or CCITT/ITU-T Recommendations (the primary definitive documents on OSI). The main purpose of ISO Standards and CCITT/ITU-T Recommendations is to present clearly the protocol to be implemented, not to explain the reasons for the choices. Frequently such reasons are buried in old working documents, maybe even only in private or national papers rather than being recorded in official international documents. In some cases reasons are merely in the heads of early workers, and are perhaps not even well articulated. It can also happen that earlier non-OSI protocols provided the basis for the OSI work, and reasons and rationale at the OSI level are simply "because that is the way it was done in xyz", and the search for real reasons has to go back a level. Nonetheless, I have been active in both progressing the OSI work and in presenting it at conferences and seminars for close on two decades, and the presentation in this text is believed to be a fair one. </div><div align="justify"><blockquote><a href="http://www.isi.salford.ac.uk/books/osi/osi.html" target="_blank"></a><a href="http://www.isi.salford.ac.uk/books/osi/osi.html" target="_blank"></a></blockquote><a href="http://www.isi.salford.ac.uk/books/osi/osi.html" target="_blank">Click to Read More/Download</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-7144509974470482893?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-49497286874384501692006-12-26T01:40:00.000-08:002008-12-18T13:28:37.830-08:00<div align="center">By Gerard J. Holzmann</div><blockquote></blockquote><div align="justify">Protocols are sets of rules that govern the interaction of concurrent processes in distributed systems. Protocol design is therefore closely related to a number of established fields, such as operating systems, computer networks, data transmission, and data communications. It is rarely singled out and studied as a discipline in its own right. Designing a logically consistent protocol that can be proven correct, however, is a challenging and often frustrating task. It can already be hard to convince ourselves of the validity of a sequentially executed program. In distributed systems we must reason about concurrently executed, interacting programs.</div><div align="justify"><blockquote></blockquote>Books about distributed systems, computer networks, or data communications often do no better than describe a set of standard solutions that have been accepted as correct by, for instance, large international organizations. They do not tell us why the solutions work, what problems they solve, or what pitfalls they avoid.<br /><blockquote></blockquote>This text is intended as a guide to protocol design and analysis, rather than as a guide to standards and formats. It discusses design issues instead of applications. Two issues, therefore, are beyond the scope of this text: network control (including routing, addressing, and congestion control) and implementation. There is, however, no shortage of texts on both topics. The design problem is addressed here as a fundamental and challenging issue, rather than as an irritating practical obstacle to the development of reliable communication systems. The aim of the book is to make you familiar with all the issues of protocol validation and protocol design.</div><div align="justify"><blockquote></blockquote>The first part of the book covers the basics. Chapter 1 gives a flavor of the types of problems that are discussed. Chapter 2 deals with protocol structure and general design issues. Chapters 3 and 4 discuss the basics of error control and flow control. </div><div align="justify"><blockquote></blockquote>The next four chapters cover formal protocol modeling and specification techniques, beginning in Chapters 5 and 6 with the introduction of the concept of a protocol validation model, that serves as an abstraction of a design and a prototype of its implementation. In Chapter 5 a terse new language called PROMELA is introduced for the description of protocol validation models, and in Chapter 6 it is extended for the specification of protocol correctness requirements. In Chapter 7 we use PROMELA to discuss a number of standard design problems in the development of a sample file transfer protocol. Part II closes with a discussion, in Chapter 8, of the extended finite<br />state machine, a basic notion in many formal modeling techniques.<br /><blockquote></blockquote>The third part of the book focuses on protocol synthesis, testing, and validation techniques that can be used to battle a protocol’s complexity. Both the capabilities and the limitations of the formal design techniques are covered.<br /><blockquote></blockquote>The fourth and last part of the book gives a detailed description of the design of two protocol design tools based on PROMELA: an interpreter and an automated validator. Based on these tools, an implementation generator is simple to add. Source code for the tools is provided in Appendices D and E. The source is also available in electronic form. Ordering information can be found in Appendix E.</div><div align="justify"><blockquote></blockquote><a href="http://spinroot.com/spin/Doc/Book91.html" target="_blank">Click to Read More/Download</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-4949728687438450169?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-8468439248027486772006-12-26T01:35:00.000-08:002008-12-18T13:27:53.850-08:00<div align="center">By David Tse and Pramod Viswanath</div><div align="center"><blockquote></blockquote>Cambridge University Press, 2005</div><div align="justify"><blockquote></blockquote>The past decade has seen many advances in physical-layer wireless communication theory and their implementation in wireless systems. This textbook takes a unified view of the fundamentals of wireless communication and explains the web of concepts underpinning these advances at a level accessible to an audience with a basic background in probability and digital communication. Topics covered include MIMO (multiple input multiple output) communication, space-time coding, opportunistic communication, OFDM and CDMA. The concepts are illustrated using many examples from wireless systems such as GSM, IS-95 (CDMA), IS-856(1xEV-DO), Flash OFDM and ArrayComm SDMA systems. Particular emphasis is placed on the interplay between concepts and their implementation in systems. An abundant supply of exercises and figures reinforce the material in the text. This book is intended for use on graduate courses in electrical and computer engineering and will also be of great interest to practicing engineers.</div><div align="justify"><blockquote><a href="http://www.eecs.berkeley.edu/%7Edtse/book.html" target="_blank"></a><a href="http://www.eecs.berkeley.edu/%7Edtse/book.html" target="_blank"></a></blockquote><a href="http://www.eecs.berkeley.edu/%7Edtse/book.html" target="_blank">Click to Read More/Download</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-846843924802748677?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-27056126394235443022006-12-26T01:25:00.000-08:002008-12-18T13:27:53.851-08:00<p align="center">Limehouse Book Sprint Team</p><p align="justify"><strong>Purpose of The Book By Publishers</strong></p><p align="justify">The overall goal of this book is to help you build affordable communication technology in your local community by making best use of whatever resources are available. Using inexpensive off-the-shelf equipment, you can build high speed data networks that connect remote areas together, provide broadband network access in areas that even dialup does not exist, and ultimately connect you and your neighbors to the global Internet. By using local sources for materials and fabricating parts yourself, you can build reliable network links with very little budget. And by working with your local community, you can build a telecommunications infrastructure that benefits everyone who participates in it.</p><p align="justify">This book is not a guide to configuring a radio card in your laptop or choosing consumer grade gear for your home network. The emphasis is on building infrastructure links intended to be used as the backbone for wide area wireless networks. With that goal in mind, information is presented from many points of view, including technical, social, and financial factors. The extensive collection of case studies present various groups' attempts at building these networks, the resources that were committed to them, and the ultimate results of these attempts.</p><p align="justify">Since the first spark gap experiments at the turn of the last century, wireless has been a rapidly evolving area of communications technology. While we provide specific examples of how to build working high speed data links, the techniques described in this book are not intended to replace existing wired infrastructure (such as telephone systems or fiber optic backbone). Rather, these techniques are intended to augment existing systems, and provide connectivity in areas where running fiber or other physical cable would be impractical.......</p><p align="justify">We hope you find this book useful for solving your particular communication challenges.</p><p align="justify"><a href="http://wndw.net/download.html" target="_blank">Click to Read More/Download</a></p><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-2705612639423544302?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-57087920929830275262006-12-25T16:26:00.000-08:002008-12-18T13:27:53.851-08:00<div align="center">By Barry Wessler </div><div align="justify"></div><div align="justify"><blockquote></blockquote>In this talk a computer network is defined to be a set of autonomous, independent computer systems, interconnected so as to permit interactive resource sharing between any pair of systems. An overview of the need for a computer network, the requirements of a computer communication system, a description of the properties of the communication system chosen, and the potential uses of such a network will be described later. </div><div align="justify"><blockquote></blockquote><a href="http://portal.acm.org/ft_gateway.cfm?id=1147453&type=pdf&amp;amp;amp;coll=portal&dl=GUIDE&amp;CFID=7797713&amp;CFTOKEN=95640890" target="_blank">Click to Download</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-5708792092983027526?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-4291129276976247182006-12-25T15:56:00.000-08:002008-12-18T13:27:53.851-08:00<div align="center">Volume 14 , Issue SI ( June 2006 ) Special issue on networking and information theory</div><blockquote></blockquote><div align="justify"><strong>43 books relating networking</strong></div><div align="justify">PDF for each topics are available. They are</div><blockquote></blockquote><ul><li><div align="justify">Introduction to the special issue on networking and information theory </div></li><li><div align="justify">On the θ-coverage and connectivity of large random networks </div></li><li><div align="justify">Scaling properties of statistical end-to-end bounds in the network calculus </div></li><li><div align="justify">On the path-loss attenuation regime for positive cost and linear scaling of transport capacity in wireless networks </div></li><li><div align="justify">Relaying protocols for two colocated users </div></li><li><div align="justify">On the capacity of information networks </div></li><li><div align="justify">Unachievability of network coding capacity </div></li><li><div align="justify">An outer bound for multisource multisink network coding with minimum cost consideration </div></li><li><div align="justify">The encoding complexity of network coding </div></li><li><div align="justify">A unification of network coding and tree-packing (routing) theorems </div></li><li><div align="justify">On average throughput and alphabet size in network coding </div></li><li><div align="justify">The multicast capacity of deterministic relay networks with no interference </div></li><li><div align="justify">Matrix games in the multicast networks: maximum information flows with network switching </div></li><li><div align="justify">On achieving maximum multicast throughput in undirected networks </div></li><li><div align="justify">Algebraic gossip: a network coding approach to optimal multiple rumor mongering </div></li><li><div align="justify">Randomized gossip algorithms </div></li><li><div align="justify">Asymptotic analysis of multistage cooperative broadcast in wireless networks </div></li><li><div align="justify">Raptor codes </div></li><li><div align="justify">Optimal throughput-delay scaling in wireless networks: part I: the fluid model </div></li><li><div align="justify">On the throughput, capacity, and stability regions of random multiple access </div></li><li><div align="justify">Minimum-cost multicast over coded packet networks </div></li><li><div align="justify">Bandwidth- and power-efficient routing in linear wireless networks </div></li><li><div align="justify">A fast lightweight approach to origin-destination IP traffic estimation using partial measurements </div></li><li><div align="justify">Overcoming untuned radios in wireless networks with network coding </div></li><li><div align="justify">Coverage by randomly deployed wireless sensor networks </div></li><li><div align="justify">Statistical location detection with sensor networks </div></li><li><div align="justify">Optimal overload response in sensor networks </div></li><li><div align="justify">Capacity of queues via point-process channels </div></li><li><div align="justify">One-way delay estimation using network-wide measurements </div></li><li><div align="justify">On the scalability of cooperative time synchronization in pulse-connected networks </div></li><li><div align="justify">The feasibility of matchings in a wireless network </div></li><li><div align="justify">On the throughput scaling of wireless relay networks </div></li><li><div align="justify">Fundamental limits and scaling behavior of cooperative multicasting in wireless networks </div></li><li><div align="justify">On outer bounds to the capacity region of wireless networks </div></li><li><div align="justify">Degenerate delay-capacity tradeoffs in ad-hoc networks with Brownian mobility </div></li><li><div align="justify">Separating distributed source coding from network coding </div></li><li><div align="justify">Cycle-logical treatment for "Cyclopathic" networks </div></li><li><div align="justify">On the capacity of multiple unicast sessions in undirected graphs </div></li><li><div align="justify">Decentralized erasure codes for distributed networked storage </div></li><li><div align="justify">Lossy network correlated data gathering with high-resolution coding</div></li><li><div align="justify">Coding on demand by an informed source (ISCOD) for efficient broadcast of different supplemental data to caching clients </div></li><li><div align="justify">Critical node lifetimes in random networks via the Chen-Stein method </div></li><li><div align="justify">Constructions of optical FIFO queues </div></li></ul><p align="justify"><a href="http://portal.acm.org/toc.cfm?id=1148663&idx=J771&amp;type=issue&coll=portal&amp;dl=ACM&part=transaction&amp;WantType=Transactions&title=TON&amp;amp;CFID=7796975&amp;CFTOKEN=83753518" target="_blank">Click to Read More/Download</a></p><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-429112927697624718?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-47243622366745838382006-12-25T15:35:00.000-08:002008-12-18T13:27:53.851-08:00<div align="center">gd.tuwien.ac.at</div><div align="justify"><blockquote></blockquote>Following books were included in this networking CD Bookshelf</div><blockquote></blockquote><ul><li><div align="justify">DNS and BIND - By Cricket Liu & Paul Albitz</div></li><li><div align="justify">TCP/IP Network Administration -By Craig Hunt</div></li><li><div align="justify">Sendmail - By Bryan Costales &amp; Eric Allman</div></li><li><div align="justify">Sendmail Destop Reference - By Bryan Costales & Eric Allman</div></li><li><div align="justify">Building Internet Firewalls - By D. Brent Chapman &amp; Elizabeth D. Zwicky</div></li><li><div align="justify">Practical Unix and Internet Security - By Simson Garfinkel &amp; Gene Spafford</div></li></ul><p align="justify"><strong>Preface of DNS and BIND</strong></p><p align="justify">You may not know much about the<a class="indexterm" name="AUTOID-23"></a> Domain Name System - yet - but whenever you use the Internet, you use DNS. Every time you send electronic mail or surf the World Wide Web, you rely on the Domain Name System.</p><p align="justify">You see, while you, as a human being, prefer to remember the names of computers, computers like to address each other by number. On an internet, that number is 32 bits long, or between zero and four billion or so. That's easy for a computer to remember, because computers have lots of memory ideal for storing numbers, but it isn't nearly as easy for us humans. Pick ten phone numbers out of the phone book at random, and then try to remember them. Not easy? Now flip to the front of the book and attach random area codes to the phone numbers. That's about how difficult it would be to remember ten arbitrary internet addresses. And, with IP version 6, it's soon to be a whopping 128 bits long, or between zero and a decimal number with 39 digits.</p><p align="justify">This is part of the reason we need the Domain Name System. DNS handles mapping between host names, which we humans find convenient, and internet addresses, which computers deal with. In fact, DNS is the standard mechanism on the Internet for advertising and accessing all kinds of information about hosts, not just addresses. And DNS is used by virtually all internetworking software, including electronic mail, remote terminal programs such as telnet, file transfer programs such as ftp, and web browsers such as Netscape Navigator and Microsoft Internet Explorer.............</p><p align="justify"><a href="http://gd.tuwien.ac.at/books/misc/Networking.rar" target="_blank">Click to Read More/Download</a></p><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-4724362236674583838?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-37363398517568982672006-12-17T12:45:00.000-08:002008-12-18T13:27:53.851-08:00<div align="center">Network Working Group</div><div align="justify"><blockquote></blockquote>This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.</div><div align="justify"><blockquote></blockquote>This document specifies version 6 of the Internet Protocol (IPv6), also sometimes referred to as IP Next Generation or IPng.</div><div align="justify"><blockquote></blockquote><a href="http://www.ietf.org/rfc/rfc2460.txt" target="_blank">Click to Read More</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-3736339851756898267?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-54009673931051361782006-12-17T12:40:00.000-08:002008-12-18T13:27:53.852-08:00<div align="center">By Charles</div><blockquote></blockquote><div align="justify">Welcome to the free online version of The TCP/IP Guide! My name is Charles and I am the author and publisher. I hope you will find the material here useful to you in your studies of computing, networking, and programming.</div><blockquote></blockquote><div align="justify">Here are a few tips, links and reminders to help you out:</div><blockquote></blockquote><div align="justify">Introduction: Newcomers to The TCP/IP Guide may wish to read the Introduction and Guide to the Guide, which will explain what the Guide is about and provide you with useful information about how to use it. </div><blockquote></blockquote><div align="justify">Navigation: For assistance understanding The TCP/IP Guide’s page structure and buttons, please refer to the Navigation Tips page. </div><blockquote></blockquote><div align="justify">Getting Started on Content: Once you are ready to dive into the content, start at Networking Fundamentals if you are new to networking; if you know the basics of networks and the OSI Reference Model, feel free to jump straight to the TCP/IP Protocol Suite and Architecture section. Of course, remember you can use the Table Of Contents to start anywhere else you might wish! </div><blockquote></blockquote><div align="justify">News: News about the free version of The TCP/IP Guide will be posted on the main TCP/IP Guide home page...........</div><div align="justify"><blockquote></blockquote><a href="http://www.tcpipguide.com/free/" target="_blank">Click to Read More</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-5400967393105136178?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-79714457676915474852006-12-17T12:33:00.000-08:002008-12-18T13:27:53.852-08:00<div align="center"><blockquote></blockquote>comp.protocols.tcp-ip.domains </div><div align="justify"><blockquote></blockquote>comp.protocols.tcp-ip.domains is the usenet newsgroup for discussion onissues relating to the Domain Name System (DNS).This newsgroup is not for issues directly relating to IP routing andaddressing. Issues of that nature should be directed towards comp.protocols.tcp-ip.</div><blockquote></blockquote><div align="justify">Question 2.3. </div><div align="justify"><strong>What is BIND ?</strong></div><div align="justify">Date: Tue Sep 10 23:15:58 EDT 1996</div><div align="justify">From the BOG Introduction -</div><div align="justify"><blockquote></blockquote>The Berkeley Internet Name Domain (BIND) implements an Internet nameserver for the BSD operating system. The BIND consists of a server (or``daemon'') and a resolver library. A name server is a networkservice that enables clients to name resources or objects and share thisinformation with other objects in the network. This in effect is adistributed data base system for objects in a computer network. BINDis fully integrated into BSD (4.3 and later releases) network programsfor use in storing and retrieving host names and address. The systemadministrator can configure the system to use BIND as a replacement tothe older host table lookup of information in the network hosts file/etc/hosts. The default configuration for BSD uses BIND.</div><div align="justify"><blockquote></blockquote><a href="http://www.faqs.org/faqs/internet/tcp-ip/domains-faq/part1/" target="_blank">Click to Read More</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-7971445767691547485?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-91158025100289338482006-12-17T12:27:00.000-08:002008-12-18T13:27:53.852-08:00<div align="center">By Julian Moss</div><div align="justify"><br />Everyone knows that TCP/IP is a network protocol used on LANs, WANs and the Internet, but not everyone who uses it understands howitworks. It’s possible to use TCP/IP with little more than a knowledge of how to configure the protocol stack, but a better understanding will give you a clearer picture of what is going on in your network and why the protocol needs to be set up in a particular way.</div><div align="justify"><blockquote></blockquote>The aim of this multi-part article is to explain the key concepts behind TCP/IP. TCP/IP stands for Transmission Control Protocol/Internet Protocol. If this leads you to think that it is not just one protocol, you’re right. In fact, it is not just two protocols, either. TCP/IP is a suite of protocols. We’ll cover the most important ones in the course of this article.</div><div align="justify"><blockquote><a href="http://www.pcsupportadvisor.com/search/c04100.htm" target="_blank"></a><a href="http://www.pcsupportadvisor.com/search/c04100.htm" target="_blank"></a></blockquote><a href="http://www.pcsupportadvisor.com/search/c04100.htm" target="_blank">Click to Read More</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-9115802510028933848?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-81792381715987061672006-12-17T12:19:00.000-08:002008-12-18T13:27:53.852-08:00<div align="justify"><blockquote></blockquote><strong>OSI Seven Layer Model &amp; Seminar Outline</strong></div><blockquote></blockquote><div align="justify">This seminar will present TCP/IP communications starting from Layer 2 up to Layer 4 (TCP/IP applications cover Layers 5-7) </div><blockquote></blockquote><ul><li><div align="justify">IP Addresses </div></li><li><div align="justify">Data Link Layer - Network Frames , Address Resolution Protocol </div></li><li><div align="justify">Network Layer - Internet Protocol , IP Routing , ICMP Error Reporting </div></li><li><div align="justify">Transport Layer - User Datagram Protocol , Transmission Control Protocol, </div></li><li><div align="justify">Session through Application Layers - Domain Name System </div></li><li><div align="justify">Final example tracing DNS transaction through a router </div></li></ul><p align="justify"><a href="http://www.eits.uga.edu/lans/tcpipsem/" target="_blank">Click to Read More</a></p><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-8179238171598706167?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-10748900868247237232006-12-17T12:14:00.000-08:002008-12-18T13:27:53.852-08:00<blockquote></blockquote><p align="center">Sangoma Technologies Corp.</p><div align="justify"><blockquote></blockquote>This tutorial is intended to supply enough information to set up a relatively simple WAN or Internet-connected LAN using WANPIPE® router cards or other routers. Explanations of IP addresses, classes, Netmask asks, subnetting, and routing are provided, and several example networks are considered. Example address and routing configurations are provided for running WANPIPE® router cards under the following protocol stacks and platforms: Unix and Linux., Microsoft TCP/IP on Windows NT Workstation/Server and Windows 95, and others. A basic explanation of IPX routing is also included. </div><div align="justify"><blockquote></blockquote>All brand names and product names are trademarks of their respective companies. </div><div align="justify"><blockquote><a href="http://www.sangoma.com/main/support/tutorials/tcpip" target="_blank"></a><a href="http://www.sangoma.com/main/support/tutorials/tcpip" target="_blank"></a></blockquote><a href="http://www.sangoma.com/support/tutorials/tcp_ip.html" target="_blank">Click to Read More</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-1074890086824723723?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-37906292816118619302006-12-17T12:08:00.000-08:002008-12-18T13:27:53.853-08:00<div align="center">By Theodore John Socolofsky and Claudia Jeanne Kale</div><div align="justify"><blockquote></blockquote>This RFC is a tutorial on the TCP/IP protocol suite, focusing particularly on the steps in forwarding an IP datagram from source host to destination host through a router. It does not specify an Internet standard. Distribution of this memo is unlimited.</div><blockquote></blockquote><div align="justify">This tutorial contains only one view of the salient points of TCP/IP, and therefore it is the "bare bones" of TCP/IP technology. It omits the history of development and funding, the business case for its use, and its future as compared to ISO OSI. Indeed, a great deal of technical information is also omitted. What remains is a minimum of information that must be understood by the professional working in a TCP/IP environment. These professionals include the systems administrator, the systems programmer, and the network manager. This tutorial uses examples from the UNIX TCP/IP environment, however the main points apply across all implementations of TCP/IP. Note that the purpose of this memo is explanation, not definition. If any question arises about the correct specification of a protocol, please refer to the actual standards defining RFC. The next section is an overview of TCP/IP, followed by detailed descriptions of individual components.</div><blockquote></blockquote><div align="justify"><a href="http://www.faqs.org/rfcs/rfc1180.html" target="_blank">Click to Read More</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-3790629281611861930?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-28264985105066114582006-12-17T12:04:00.000-08:002008-12-18T13:27:53.853-08:00<div align="center">By Charles C. Botsford </div><blockquote></blockquote><div align="justify">This " Free, Lecture-Based Presentation on IP Addressing and Subnetting" was created to teach computer professionals how to address IP networks and perform subnetting. Subnetting is one of the most difficult activities network technicians are required to perform. Many people have found viewing these presentations multiple times increases understanding. Use these methods for success: </div><blockquote></blockquote><ul><li><div align="justify">View and listen to the sections in consecutive order. Each section relies on information from the previous sections. (The entire course takes about two and half hours.) </div></li><li><div align="justify">Print Out Practice Problems and Section Helpers before you view the presentation (where available). </div></li><li><div align="justify">Take notes, and refer to the Section Helpers while you listen to and view the presentation.<br />Perform the Practice Problems to sharpen your skills. </div></li><li><div align="justify">Be prepared to re-view key modules where needed (usually three times is standard). </div></li><li><div align="justify">View summary sections to reinforce key concepts. </div></li></ul><p align="justify">For test takers: </p><ul><li><div align="justify">Learn Subnet ID/Host Charts that are a part of the "Subnetting Section Helper" </div></li><li><div align="justify">Practice twice a day for a week </div></li><li><div align="justify">Before you click start on the test, write down Subnet ID/Host Charts from memory on paper provided at testing center. (Do NOT smuggle in charts or violate testing rules!) </div></li><li><div align="justify">Use Charts to lookup answers to subnetting questions! </div></li></ul><p align="justify"><a href="http://www.learntosubnet.com/" target="_blank">Click to Read More</a></p><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-2826498510506611458?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-49329800164536925402006-12-17T10:18:00.000-08:002008-12-18T13:27:53.853-08:00<div align="center">IBM.com</div><blockquote></blockquote><div align="justify">The TCP/IP protocol suite has become the de facto standard for computer communications in today's networked world. The ubiquitous implementation of a specific networking standard has led to an incredible dependence on the applications enabled by it. Today, we use the TCP/IP protocols and the Internet not only for entertainment and information, but to conduct our business by performing transactions, buying and selling products, and delivering services to customers. We are continually extending the set of applications that leverage TCP/IP, thereby driving the need for further infrastructural support.In TCP/IP Tutorial and Technical Overview, we take an in-depth look into the TCP/IP protocol suite. In Part I, we introduce TCP/IP, providing a basic understanding of the underlying concepts essential to the protocols. We continue our discussion in Part II with a survey of today's most popular TCP/IP application protocols, including emerging wireless and multimedia applications. Finally, in Part III, we cover advanced concepts and the latest infrastructural trends in networking, including IPv6, security, Quality of Service, IP mobility, and MPLS. We address the challenges that TCP/IP is currently facing and the technology being developed to overcome them.</div><blockquote></blockquote><div align="justify"><strong>Table of Contents</strong><br /><em>Part I. Core TCP/IP protocols</em></div><div align="justify">Chapter 1. Architecture, history, standards, and trends</div><div align="justify">Chapter 2. Network interfaces</div><div align="justify">Chapter 3. Internetworking protocols</div><div align="justify">Chapter 4. Routing protocols</div><div align="justify">Chapter 5. Transport layer protocols</div><div align="justify">Chapter 6. IP multicast</div><div align="justify"><blockquote></blockquote><em>Part 2. TCP/IP application protocols</em></div><div align="justify">Chapter 7. Application structure and programming interfaces</div><div align="justify">Chapter 8. Directory and naming protocols</div><div align="justify">Chapter 9. Remote execution and distributed computing</div><div align="justify">Chapter 10. File related protocols</div><div align="justify">Chapter 11. Mail applications</div><div align="justify">Chapter 12. The World Wide Web</div><div align="justify">Chapter 13. Multimedia protocols</div><div align="justify">Chapter 14. Wireless Application Protocol (WAP)</div><div align="justify">Chapter 15. Network management</div><div align="justify">Chapter 16. Utilities</div><div align="justify"><blockquote></blockquote><em>Part 3. Advanced concepts and new technologies</em></div><div align="justify">Chapter 17. IP Version 6</div><div align="justify">Chapter 18. Multiprotocol Label Switching (MPLS)</div><div align="justify">Chapter 19. Mobile IP</div><div align="justify">Chapter 20. Integrating other protocols with TCP/IP</div><div align="justify">Chapter 21. TCP/IP security</div><div align="justify">Chapter 22. Quality of Service</div><div align="justify">Chapter 23. Availability, scalability, and load balancing</div><div align="justify"><blockquote></blockquote><a href="http://publib-b.boulder.ibm.com/redbooks.nsf/RedbookAbstracts/gg243376.html?Open" target="_blank">Click to Read More</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-4932980016453692540?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-82927581615780593082006-12-17T10:13:00.000-08:002008-12-18T13:27:53.853-08:00<div align="center">By Daryl Banttari</div><blockquote></blockquote><div align="justify">This document is designed to give the reader a reasonable working knowledge of TCP/IP subnetting, addressing, and routing. It is not intended to be complete, or to cover all issues. This is targeted toward LAN administrators just moving to TCP/IP, however it should help anyone who wants to know a little (more) about how TCP/IP works. This document does not, generally, apply to dial-up SLIP/PPP connections. </div><div align="justify"><blockquote></blockquote>The difference between this (a primer) and an FAQ, is that most FAQ's, in practice, tend to be question-and-answer oriented, and generally seem to try to cover ALL issues, not just the ones frequently asked about. This primer is intended as a starting point for someone who has an interest in the subject, but doesn't know where to start or what questions to ask. This should also help to broaden the understanding of people who have worked with TCP/IP for a while, but either haven't had the time to study all the less-than-useful theory behind the subject, or have been somewhat overwhelmed by the many theoretical details and have missed the big picture. </div><div align="justify"><blockquote></blockquote><a href="http://www.ipprimer.com/overview.cfm" target="_blank">Click to Read More</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-8292758161578059308?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-22129424823022649052006-12-17T10:09:00.000-08:002008-12-18T13:27:53.853-08:00<div align="center">By Gary C. Kessler</div><blockquote><a name="intro"></a><a name="intro"></a></blockquote><div align="justify"><a name="intro"><strong>Introduction</strong></a><br />An increasing number of people are using the Internet and, many for the first time, are using the tools and utilities that at one time were only available on a limited number of computer systems (and only for really intense users!). One sign of this growth in use has been the significant number of TCP/IP and Internet books, articles, courses, and even TV shows that have become available in the last several years; there are so many such books that publishers are reluctant to authorize more because bookstores have reached their limit of shelf space! This memo provides a broad overview of the Internet and TCP/IP, with an emphasis on history, terms, and concepts. It is meant as a brief guide and starting point, referring to many other sources for more detailed information.</div><div align="justify"><strong></strong><blockquote><strong><a name="what"><strong></strong></a><a name="what"></a></strong></blockquote><strong><a name="what">What are TCP/IP and the Internet?</a></strong><br />While the TCP/IP protocols and the Internet are different, their histories are most definitely intertwingled! This section will discuss some of the history. For additional information and insight, readers are urged to read two excellent histories of the Internet: Casting The Net: From ARPANET to INTERNET and beyond... by Peter Salus (Addison-Wesley, 1995) and Where Wizards Stay Up Late: The Origins of the Internet by Katie Hafner and Mark Lyon (Simon &amp; Schuster, 1997).......</div><div align="justify"><blockquote></blockquote><a href="http://www.garykessler.net/library/tcpip.html" target="_blank">Click to Read More</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-2212942482302264905?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-52176915016798235202006-12-17T10:05:00.000-08:002008-12-18T13:27:53.854-08:00<div align="center">By Bradley Mitchell</div><div align="justify"><blockquote></blockquote>Internet Protocol (IP) technology was developed in the 1970s to support some of the first research computer networks. Today, IP has become a worldwide standard for home and business networking as well. Our network routers, Web browsers, email programs, instant messaging software - all rely on IP or other network protocols layered on top of IP. </div><div align="justify"><blockquote></blockquote>Two versions of IP technology exist today. Essentially all home computer networks use IP version 4 (IPv4), but an increasing number of educational and research institutions have adopted the next generation IP version 6 (IPv6). </div><div align="justify"><blockquote></blockquote><a href="http://compnetworking.about.com/od/tcpiptutorials/a/ipaddrnotation.htm" target="_blank">Click to Read More</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-5217691501679823520?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-20588655177271900542006-12-17T03:25:00.000-08:002008-12-18T13:27:53.854-08:00<div align="center">By Vincenzo Mendillo</div><blockquote></blockquote><div align="justify">TCP/IP is a set of protocols that allow cooperating computers to share resources across a network. It was developed by a community of researchers centered around the ARPAnet. Certainly the ARPAnet was the best known TCP/IP network, but now has been replaced by the Internet. The most accurate name for the set of protocols we will describing is the "Internet protocol suite" or "Internet protocol stack". TCP and IP are two of the protocols in this suite and because they are the best known of the protocols, it has become common to use the term TCP/IP to refer to the whole family. So the generic term TCP/IP usually means anything and everything related to the specific protocols of TCP and IP. It can include other protocols, applications, and even the network medium. A sample of these protocols are: UDP, ARP, and ICMP. A sample of these applications are TELNET, FTP, TFTP, SMTP and SNMP. The Internet is a collection of international and national networks, regional networks, local networks at a number of universities and research institutions, and also a number of military networks. The term "Internet" applies to this entire set of networks. All of these networks are connected to each other. Users can send messages from any of them to any other, except where there are security or other policy restrictions on access. </div><div align="justify"><blockquote></blockquote>Officially speaking, the Internet protocol documents are simply standards adopted by the Internet community for its own use. Internet standards are called RFC. RFC stands for Request for Comment. A proposed standard is initially issued as a proposal, and given an RFC number. When it is finally accepted, it is added to Official Internet Protocols, but it is still referred to by the RFC number. Whenever an RFC is revised, the revised version gets a new number. These documents are being revised all the time, so the RFC number keeps changing.</div><div align="justify"><blockquote></blockquote><a href="http://www.ictp.trieste.it/%7Eradionet/nuc1996/ref/tcpip/" target="_blank">Click to Read More</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-2058865517727190054?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-62538652721719011822006-12-17T03:21:00.000-08:002008-12-18T13:27:53.854-08:00<div align="center"><blockquote></blockquote>By Rich Casselberry, et al.</div><blockquote></blockquote><div align="justify">The Internet has been growing in popularity at a phenomenal rate. Many television ads now contain URLs (Uniform Resource Locators) such as CNN's <a href="http://www.cnn.com/">http://www.cnn.com/</a> and surveys commonly ask for an e-mail address. An even faster growing phenomenon, though, is the use of the Intranet. </div><blockquote></blockquote><div align="justify">An Intranet is an IP network designed for internal use. The growth of Intranets has been silent but rapid, and is actually where most sales of Web servers are used. </div><blockquote></blockquote><div align="justify">Intranets are used in many types of companies from high-tech computer firms to real estate companies to oil refineries. Everyone can benefit from the technology available. </div><blockquote></blockquote><div align="justify">Intranet technology is used in many different ways. It can be used to set up a central document repository or workgroup server. It can be used to integrate with existing databases, either by writing custom software or using commercial applications. Most database vendors currently have or are working on WWW interfaces to their products. </div><blockquote></blockquote><div align="justify">Intranets can also be used as a client/server combination, allowing quick building of distributed applications. Use of the Web can also allow develop-ers to quickly build cross-platform tools. Because HTML is an open standard, almost any computer will have a browser that can be used as a graphical user interface, or GUI. </div><div align="justify"><blockquote></blockquote>Intranet-based tools also allow groupware applications to be integrated. Groupware applications can be built using free software, or commercial applications such as Lotus can be purchased and integrated. </div><div align="justify"><blockquote><a href="http://docs.rinet.ru/PerfectIntranet/" target="_blank"></a><a href="http://docs.rinet.ru/PerfectIntranet/" target="_blank"></blockquote>Click to Read More</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-6253865272171901182?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-18949140630990484272006-12-17T03:13:00.000-08:002008-12-18T13:27:53.854-08:00<blockquote></blockquote><p align="center"><a id="I10" name="I10"><strong>Introduction </strong></a><br /><a id="I11" name="I11">--by Billy Barron </a></p><div align="justify">The Internet guru is a hard person to define. No test exists to qualify a person as an Internet guru. It is not always obvious who is and is not a guru. Often, I am talking to some novices and they mention that someone is an "Internet guru." When I meet this person, it is frequently the case that the supposed guru is giving out wrong and misleading information. Therefore, the first criteria of being an Internet guru is that other Internet gurus must be able to respect the accuracy your Internet knowledge. </div><blockquote></blockquote><div align="justify">If you watch Internet gurus in action, they usually show extremely strong feelings about the Internet. Almost all, if not all, find the Internet to be an exciting and fun place. This interest is critical to any Internet guru; the Internet is so large and changing so fast that without a strong passion, a guru will become a nonguru within a couple of years. </div><blockquote></blockquote><div align="justify">An Internet guru knows that the Internet only works due to information sharing that is mostly for free. The guru, therefore, must give something back to the Internet to improve the network. It might be a piece of software, documentation, frequently answering posts on Usenet constructively, or even just having a useful Gopher or Web server. </div><blockquote></blockquote><div align="justify">The guru knows that he or she does not and cannot know everything about the Internet. Therefore, this books offers a great deal, even to the guru. For example, while I was reading this book, I learned quite a bit about a subject that I knew nothing about, like programming muds. The guru, though, has many tools and an ability to learn that compensates for gaps in knowledge. Related to this, the Internet guru has contacts and/or friendships with other gurus that provide invaluable information. </div><blockquote></blockquote><div align="justify">Every guru is different in knowledge, background, career, and personality. This is important to remember. Some are not even computer professionals and instead are librarians, scientists, artists, musicians, or students. Basically, they can be from any place and any walk of life. For a brief sampling of Internet gurus, consider a few of the authors who wrote parts of this book. In many ways, I may be one of the most typical of Internet gurus. I am very strong in end-user Internet services (WWW, Gopher, OPACs, FTP sites, and so on) and can even manage routers, but I know very little about network management or muds. Another author, Kevin Mullet, is one of the people who holds Internet connectivity together within Texas—he knows network management inside and out (among other aspects of the Internet). Kenny Greenberg is also an Internet guru, even though he is first and foremost an artist. The other authors all come from different backgrounds. </div><blockquote></blockquote><div align="justify">Now that you may have a vague idea of what an Internet guru is, you may want to become one yourself. Fortunately, it is much easier to define the steps in becoming a guru than defining what a guru is. The steps I recommend: </div><blockquote></blockquote><ol><li><div align="justify">Become a proficient Internet user. Many books and training sessions are available to help you get to this state. </div></li><li><div align="justify">Learn about the society and politics of the Internet. Books, such as The Internet Unleashed (Indianapolis: Sams Publishing, 1994), will help with this. However, nothing substitutes for some time spent on mailing lists and Usenet news. </div></li><li><div align="justify">Decide which parts of the Internet excite you. Concentrate on learning these. As I said earlier, nobody knows everything about the Internet. </div></li><li><div align="justify">Do some background reading. This book will definitely help you here, but reading some network documents such as RFCs is also important. </div></li><li><div align="justify">Try out what you have learned—as long as it is legal and ethical. No Internet guru evolves without spending a lot of hands-on time on the network itself. </div></li><li><div align="justify">When your experiments fail (and they sometimes will), either go back to Step 4 or ask on mailing lists or newsgroups, and then try again. The urge to give up may be strong at times, but don't give in! </div></li></ol><p align="justify">Good luck on becoming an Internet guru. Also, make sure you have fun while reading Tricks of the Internet Gurus, or you have been missing the point. </p><p align="justify"><a href="http://docs.rinet.ru/ITricks/" target="_blank">Click to Read More</a></p><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-1894914063099048427?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-87417296360394029542006-12-17T03:10:00.001-08:002008-12-18T13:27:53.855-08:00<div align="center">By John Enck and Dan W. Blacharski </div><p align="center">Macmillan Computer Publishing</p><p align="justify">Lot has happened in the computer world since John Enck wrote the first edition of this book in 1990. The Internet has become wildly popular, which has led to the suprem-acy of TCP/IP; the mainframe is being slowly replaced (or at least augmented) by a distributed, client/server architecture; and high-speed technologies, such as ATM and FDDI, have significantly enhanced the very nature of networking.</p><p align="justify">John had three goals in writing this book: </p><ol><li><div align="justify">To introduce and define the fundamental network architectures of four key computer manufacturers. This information gives executive management a sufficient understanding of the basics for making informed, intelligent decisions about networks and networking strategies.</div></li><li><div align="justify">To help technical management and systems personnel begin the cross-training process. By covering each vendor's systems and networking architectures using the same orientation and organization, this book gives you a common level of understanding and facilitates this horizontal training.</div></li><li><div align="justify">To explore standards and technologies that greatly affect the world of multivendor networking and data communications. Many of these developments result from third-party efforts and serve to define a middle ground on which to build multivendor solutions. </div></li></ol><p align="justify">In this edition, I have endeavored to supplant Mr. Enck's comprehensive work with information on some of the latest technologies and to cover some of the changes that have taken place in the networking industry during the past six years.........</p><p align="justify"><a href="http://docs.rinet.ru/MuNet/" target="_Blank">Click to Read More</a></p><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-8741729636039402954?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-46513550807451098912006-12-17T02:57:00.000-08:002008-12-18T13:27:53.855-08:00<div align="center"><blockquote></blockquote>by Rob Kolstad, Berkeley Software Design, Inc. </div><div align="justify"><blockquote></blockquote>Becoming an Internet Service Provider is not a mysterious or difficult process. This document outlines the steps necessary. </div><strong></strong><blockquote><strong><strong></strong></strong></blockquote><div align="justify"><strong>Introduction<br /></strong>For a topic that has seen so much hype of late, it is amazing how little is explained about what the Internet is and how one leverages it. This white paper gives a brief explanation of the Internet, services it provides, and how new `Internet Service Providers' start up their operation. </div><blockquote></blockquote><div align="justify">This article is written as an overview. It is not intended to be 100% complete (that would take an entire book!). Finally, it is written from the biased point of view of someone who does not wish to spend tens of thousands of dollars to start such a service. This bias extends to the occasional emphasis on BSDI's products. </div><blockquote></blockquote><div align="justify"><strong>The Internet: A Brief Overview</strong><br />The formal definition of the Internet says ``The Internet is a network that connects thousands of other computer networks''. This does not seem to be particularly helpful in understanding what's really going on. </div><div align="justify"><blockquote></blockquote>Computer networks became practical when Ethernet and the Berkeley 4.1 follow-on releases of the Berkeley BSD UNIX system started becoming widely available back in the 1982 timeframe. These `Local Area Networks' (LANs) typically spanned an area smaller than a couple square miles. Some hardware existed to connect these LANs to extend the area slightly, but not on a nation-wide scale........</div><div align="justify"><blockquote></blockquote><a href="http://docs.rinet.ru/becomeISP/" target="_blank">Click to Read More</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-4651355080745109891?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-80630238020746265862006-12-17T02:47:00.000-08:002008-12-18T13:27:53.855-08:00<div align="center">Second Edition</div><div align="center"><blockquote></blockquote>Sams Publishing</div><blockquote></blockquote><div align="justify">So you've just been told you are on a TCP/IP network, you are the new TCP/IP system administrator, or you have to install a TCP/IP system. But you don't know very much about TCP/IP. That's where this book comes in. You don't need any programming skills, and familiarity with operating systems is assumed. Even if you've never touched a computer before, you should be able to follow the material. </div><blockquote></blockquote><div align="justify">This book is intended for beginning through intermediate users and covers all the protocols involved in TCP/IP. Each protocol is examined in a fair level of detail to show how it works and how it interacts with the other protocols in the TCP/IP family. Along the way, this book shows you the basic tools required to install, configure, and maintain a TCP/IP network. It also shows you most of the user utilities that are available. </div><blockquote></blockquote><div align="justify">Because of the complex nature of TCP/IP and the lack of a friendly user interface, there is a lot of information to look at. Throughout the book, the role of each protocol is shown separately, as is the way it works on networks of all sizes. The relationship with large internetworks (like the Internet) is also covered. </div><blockquote></blockquote><div align="justify">Each chapter in the book adds to the complexity of the system, building on the material in the earlier chapters. Although some chapters seem to be unrelated to TCP/IP at first glance, all the material is involved in an integral manner with the TCP/IP protocol family. The last few chapters cover the installation and troubleshooting of a network. </div><div align="justify"><blockquote></blockquote>By the time you finish this book, you will understand the different components of a TCP/IP system, as well as the complex acronym-heavy jargon used. Following the examples presented, you should be able to install and configure a complete TCP/IP network for any operating system and hardware platform. </div><div align="justify"><blockquote></blockquote><a href="http://docs.rinet.ru/TCP-IP/" target="_blank">Click to Read More</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-8063023802074626586?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.comtag:blogger.com,1999:blog-7529903632713810200.post-9712342613075136722006-12-17T02:39:00.000-08:002008-12-18T13:27:53.856-08:00<div align="center">Macmillan Computer Publishing</div><blockquote></blockquote><div align="justify">The past decade has been witness to the radical evolution of data networks from their humble origins to their current forms. The original Local Area Networks (LANs), were nothing more than coaxial cabling, strung from terminal servers to desktop terminals whose users were treated to monochromatic text displayed on low-resolution cathode ray tubes (CRTs).</div><blockquote></blockquote><div align="justify">In the mid-1980s, wide area networks (WANs), too, were slow and crude. Terminal servers multiplexed access for dozens of users to 9.6Kbps circuits. These circuits connected users to mainframe-based applications that lay hidden in a remote data center.</div><blockquote></blockquote><div align="justify">Today, LANs have metamorphosed into high-bandwidth, high-performance, local area networks that support bandwidth- and CPU-intensive client applications such as live, interactive voice and videoconferencing, as well as e-mail and some of the more traditional forms of data processing.<br />WANs, too, have experienced radical, evolutionary change. Today, 9.6Kbps is deemed inadequate for most of the needs of even a single user. Just try to give a user a 9.6Kbps modem for use as anything but a paperweight!</div><blockquote></blockquote><div align="justify">It is important to recognize that the impetus for all these changes has been, and remains, the user's business requirements. The competitive environment of most business entities ensures that any technological innovations that offer competitive advantages--that is, better, cheaper, and/or faster--get accepted. For example, the introduction of the mouse facilitated access to computing by obviating the need for typing skills. Suddenly, almost everyone could use a computer! Personal computers, too, offered countless advantages by distributing intelligence down to the desktop.</div><blockquote></blockquote><div align="justify">Software developers also drove changes by constantly upgrading a dizzying array of increasingly complex products that enabled users to actually use the newly distributed processing power at their fingertips. Together, these innovations quickly made hard-wired connections to terminal servers obsolete.</div><blockquote></blockquote><div align="justify">Into this void came the first generation of LANs. These networks offered almost obscene amounts of bandwidth, such as 1 or 4Mb per second (Mbps), depending on whose network you purchased. Initially, these LANs were used as a more flexible means of connecting users with terminal servers. After all, the users' basic requirements hadn't changed all that much, and the increased bandwidth was more than adequate to support terminal emulation.</div><blockquote></blockquote><div align="justify">Towards the end of the 1980s, this first generation of LANs began to show its age. Once the user community understood that the distributed microprocessors on their desktops could do more than just terminal emulation, their quest for even more bandwidth and for higher performance networking began.</div><div align="justify"><blockquote></blockquote>The second generation of LANs were little more than faster versions of their predecessors. 1Mbps Ethernets grew into 10Mbps Ethernets. Similarly, 4Mbps Token Rings were accelerated to 16Mbps. This increase in the clock rates would keep users somewhat satisfied up to the middle of the 1990s.......</div><div align="justify"><blockquote></blockquote><a href="http://docs.rinet.ru/NeHi/" target="_blank">Click to Read More</a></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7529903632713810200-971234261307513672?l=more-networking.blogspot.com' alt='' /></div>Administratornoreply@blogger.com