recycledreading2 from IL, United States offers this stuff for:

Price : $14.95 Usually ships in 1-2 business days

Dartagnan's Books offers this stuff with condition New, new for:

Price : $14.95 Usually ships in 1-2 business days

kualawu offers this stuff with condition New, new for:

Price : $18.55 Usually ships in 1-2 business days

jwong_ca offers this stuff with condition New, new for:

Price : $19.50 Usually ships in 1-2 business days

multigates offers this stuff with condition New, new for:

Price : $68.00 Usually ships in 1-2 business days

bennettbooksltd from IL, United States offers this stuff for:

Price : $70.47 Usually ships in 1-2 business days

What our customer's say!

"Administer for performance, not convenience", Anyone who has been concerned or is currently concerned with the performance of networks, no matter how large, has had to deal with the TCP/IP protocol. It has its origins in the late 1960's, being invented essentially by government researchers and finally finding its first specification in 1979. This book is written for Unix systems administrators who must deal with the intricacies of TCP/IP but unfortunately does not suggest to them methods for improving TCP/IP performance. It is one thing to administer for convenience and ease in troubleshooting. It is quite another thing to administer for performance. For this reason, this reviewer only read the last chapter in the book, which deals with the troubleshooting of the TCP/IP implementation. A future edition would be greatly improved by detailed discussion of performance issues and how to administer for optimum performance.

The author does however give a fairly detailed discussion of troubleshooting in TCP/IP and give a few hints to assist the beginning sys/ad person. Many of these are readily apparent to those who are acquainted with the dynamics of TCP/IP, while others are based more on a commonsense understanding of how networks are configured. For example, the author advises checking to see if the trouble is unique to only one application or if it only occurs on one remote host versus all remote hosts. Problems that are application specific are to be distinguished from those that may require investigation into the actual network, the latter occurring when hosts are experiencing problems on only certain subnets.

It is interesting that the troubleshooting techniques and tools that are described in this chapter still require a great deal of human intervention, and therefore are dependent on the time restrictions of the network engineer or administrator. These tools include "built-in" investigative ones like `ipconfig', `ping', `traceroute', and `snoop'. Some of these tools unfortunately can also be used to disrupt a network, such as for example when `ping attacks' are used to flood a host with a barrage of ping packets. In addition, many of them can be used to hack into a particular host, or gain information for a successful intrusion into that host's networked computers. Many of them also can be used to gain information on the layers that are below the TCP layer, such as the `arp' command that allows one to analyze problems with translation between IP and Ethernet addresses.

It is not surprising to find discussions on network design in this chapter, and in these discussions one must go deeper into the lower OSI levels. And in these discussions, particularly in the one on how to subdivide an Ethernet in order to manage the network traffic on a particular segment, the author does indirectly discuss performance issues, although they are strictly speaking outside of the TCP/IP protocol, and its sometimes striking and unpredictable behavior on real networks. This complicated behavior of TCP/IP, and the severe financial impact that its maladies can cause for business and industry dictate that a much more sophisticated approach to troubleshooting TCP/IP be used. This approach would deploy a system that responds immediately to TCP problems, analyzes them, and takes correction (on its own if the risks are understood). In addition it would learn from experience, or "keep a historical record' in the words of the author, so as to be able to confront similar problems in the future more efficiently. Having such an autonomous real-time TCP/IP troubleshooter that is not bound by the long time scales characteristic of human intervention would be complex but definitely useful and a huge return on investment.

"TCP/IP Fundamentals", This book covers the in's and out's of TCP/IP with a Unix focus. Non-Unix users will find this book equally useful as the Unix user, in that it presents the information in a format that is easy to follow as well as comprehensive.

This book doesn't cater to the casual reader, instead it gives the facts required for administration of a TCP/IP based network. If you want to understand this topic, this is the book to use.

"Cannot Live Without", Though this book is oriented to UNIX, I find it tremendously useful as a Windows administrator. Core concepts gleamed from this book has catapulted me greatly into my career, and allowed me to solve complex networking problems and avert major disasters.

I was introduced to this book for a UNIX Network Administration course, and from this I was able to really flesh out core TCP/IP concepts as well as play with services like DHCP and DNS, which are essential pieces for a Windows Active Directory environment. Using this book I was able to dabble with other services like NFS and SAMBA from a variety of systems ranging from Mac OS X to Solaris x86 to Linux to Windows XP...

I don't have any complaints, but rather some requests for future editions. I wish there was some coverage of IPSec and Kerberos in Chapter 12 "Network Security". I think Chapter 9 "Local Netowrk Services" could be expanded, as some topics are sparsely covered and there is no mention of printing technologies like IPP or CUPS. I do wish there was more coverage of the raw SMTP protocol and related technologies of POP, IMAP, and LDAP and maybe even mail servers like Exim and Postfix. However, don't touch that sendmail chapter (Chapter 10), as this coverage is so very excellent; other books go off on the deep end are far way too complex to get started.

"Best TCP/IP Book Hands Down!", As with all of O'Reilly's books, this one is technically accurate and fundamentally sound.

It does not teach TCP/IP from a simplistic approach--telling you only what you need to know and leaving you begging for more. It lays a ground work based upon the actual theory of these protocols and how they were developed and the thinking that was involved in their creation.

From there, it takes you step by step through the layers of the protocols and presents everything that most people would need to know--even more than they would need to know.

Especially enlightening were the chapters on IPv6--the next generation of the IP protocol, and the chapter covering subnetting.

Overall, if you need the one book to explain TCP/IP and the "ins-and-outs" of these networking protocols, look no further.

This book has all you'll need.

"A decent book to learn from and reference.", This coveres some aspects, and can be used to learn from--but doesn't cover all the aspects that you'll want to know. For a reference, it's pretty good too. It's a pretty decent book, though has a good mix of information that makes it a little better than average.

Read this reviews before You buy...

"Wonderful reference", Maintaining any type of computer network is a challenge (to say the least) and books like this one are a welcome addition to any sys admin's library. Above the book's title on the cover are the words "Help for UNIX System Administrators" and that's precisely what this book is. Starting off with a "primer" on TCP/IP and how data moves around on a TCP/IP network gives anyone new to TCP/IP a general idea of how it all works. There are also chapters on configuring your interface (along with general info on installing PPP & SLIP), routing, network servers, and sendmail, all important parts of a TCP/IP system. Near the book's end, the topics of troubleshooting and network security are also addressed.

All the O'Reilly books I have read always have thorough descriptions of the their topics and prove to be excellent sources of information. This book is no exception. If you maintain (or will be maintaining) this type of network, you need this book

"A wonderful intro to TCP/IP", I read this book because I needed to know as much as I could about what TCP/IP is, and things like email, networking, and how it all works. This book taught me everything I could want to know about TCP/IP, and was for the most part pretty easy to read. On chapter in particular gave a brief intro to Sendmail, so i went home and tried it out and it worked great! The other chapters are just as good. Of the many O'Reilly books I have read and bought, this ranks in the top 2 (the other is Running LInux). Thanks Mr. Hunt and thanks O'Reilly!!!

"The Best TCP/IP How-To Book!", This is anything but another how to book. This is the original TCP/IP how to book and it is still the best! It provides clear, accurate descriptions of the protocols in exactly the level of detail required by a network administrator. Then it provides clear step-by-step instructions on how to properly configure a TCP/IP server. What could be better? The book description clearly states that this is a "tutorial on how to configure" network services. It is so rare when it happens, I can't understand why anyone would complain when a book actually delivers what it promises. O'Reilly books always do!

"A book that [is awful]", Yeah, this one really [is awful]. I did not find it useful at all. It is just another step-by-step how-to book (seems like a cooking book), with poor and halfway explanations. Not recommended for serious network administration.

"Another excellent contribution to the O'Reilly Empire", I am responsible for a 50+ person intrusion detection mission, and I read this book in February 2000 to supplement my knowledge of TCP/IP. Like other great technical books, this volume manages to educate the reader on subjects related to TCP/IP, while still covering the main material thoroughly. (I place Rod Smith's "Multi-Boot Configuration Handbook in this category as well.) This is the type of book that tempts you to highlight chunks of text on every page. Keep in mind the audience is a system administrator, so theory is supplemented by suggested best practices and configuration options. I'm looking forward to an updated version of the Windows version of TCP/IP Network Administration -- any publication dates available, Craig?