UNIX and Windows 2000 Interoperability Guide

Description

• Copyright 2001
• Edition: 1st

• Book
• ISBN-10: 0-13-026332-X
• ISBN-13: 978-0-13-026332-2

The task-focused quick-reference for every UNIX/Windows sysadmin.

• Fast answers for experienced sysadmins in any UNIX/Windows environment
• Detailed commands, step-by-step techniques, and practical interoperability solutions
• Hands-on coverage of integrating UNIX and Windows 2000 file/print services
• TCP/IP, DNS, common logins, and much more

If you're a system administrator in a mixed UNIX and Windows 2000/NT environment, you need fast answers for both platforms: step-by-step techniques for performing key tasks and real-world solutions for integration. UNIX and Windows 2000 Interoperability Guide delivers all that, in a proven quick-reference format that'll save you time, effort, and money.

Long-time UNIX sysadmin and MCSE Alan R. Roberts focuses on practical techniques for experienced system administrators -- not basic theory for beginners. Each chapter addresses one essential system administration task, offering precise UNIX "how-to" instructions and practical interoperability tips for heterogeneous environments. Coverage includes:

• Effective file and print sharing in UNIX/Windows environments
• Multiplatform TCP/IP and DNS solutions
• Common login environments
• File systems, file and directory locations, and command behavior
• Detailed coverage of HP-UX, with supplementary techniques for Linux, Solaris, and AIX environments

When you need interoperability solutions, you don't have time to search through piles of UNIX and Windows manuals. With UNIX and Windows 2000 Interoperability Guide, you won't have to!



Sample Content

Downloadable Sample Chapter

Click here for a sample chapter for this book: 013026332X.pdf

Table of Contents

(NOTE: Each chapter concludes with a Conclusion and References.)

Preface.


Acknowledgments.


1. What Is UNIX?

In the Beginning. The New Face of UNIX. UNIX and Open Source Software. The Elements of UNIX. Is There More?

2. What Is Windows 2000?

A New Operating System. Windows 2000 Architecture. Elements of Windows 2000.

3. The Network Interface Layer.

Network Interface Cards and Drivers.

4. The Internet Layer.

ARP. IP.

5. The Transport Layer.

TCP. UDP. Network Application Interfaces.

6. Name Resolution.

Windows 2000. HP-UX. Nslookup Differences. Name Resolution Issues in a Mixed Environment.

7. DHCP and DNS.

DHCP Clients. Windows 2000 DHCP Server.

8. User Authentication.

Windows 2000. HP-UX. PAM Kerberos.

9. Basic TCP/IP Utilities.

General Observations. Finger. FTP. Tftp. Rsh and Rcp. Rexec. Telnet. Authentication Issues.

10. Windows Services for UNIX.

Telnet Client. Telnet Server. Server For NIS.

11. NFS File Sharing.

Basic Concepts. NFS and Windows 2000 Issues. Windows 2000 NFS Client/HP-UX NFS Server. Windows 2000 NFS Server/HP-UX NFS Client.

12. CIFS File Sharing.

CIFS Versus NFS. The Case for CIFS. CIFS Implementations. CIFS/9000 Server in a Windows 2000 Domain. CIFS/9000 Client in a Windows 2000 Domain.

13. Miscellaneous Interoperability Topics.

Network-Attached Storage. The X Window System. Printing.

Index.

Preface

Preface

There is a debate raging among many computer professionals over the merits (or demerits) of the UNIX operating system versus those of Microsoft's Windows 2000 (formerly NT). I address the fact that there is more than one version of UNIX in the first chapter, but for ease of communication I will simply say "the UNIX operating system" for now. This type of debate, often bordering on a religious war, is not a new phenomenon. There was once one concerning MVS and VMS, then VMS and UNIX, then UNIX and DOS, then UNIX and Windows NT. All the while, we have seen similar battles pitched over Windows, OS/2, and Mac OS.

Quite frankly, I don't care which of these operating systems and their variants is "better." Nor do a lot of businesses. The reality is that most businesses run either some form of UNIX or some form of Windows in their environments. Typically, they run both. Presumably, then, each type of operating system offers something the other does not. Granted, much of what was once considered the domain of UNIX-the Internet, for example-Windows 2000 is relatively new at. Also, Windows 2000's legacy is that of the PC world, one which most people associate with DOS, Windows, and Intel processor-based computers. So, a dichotomy has naturally developed in the last several years, and many IT departments reflect this dichotomy: They maintain independent workgroups and staffs based upon operating systems. Administrators in these camps often know little of how the "other side" works.

The times, however, they are a-changin'. Increasingly it is the network that really matters, and for that, the world has standardized on TCP/IP and the applications that run on top it: FTP, Telnet, HTTP, DNS, NFS, CIFS, and SMNP. Web servers offer applications that clients can access with a browser, regardless of what platform that browser runs on. NFS products are available for Windows systems; you can install CIFS servers on UNIX systems. IT departments typically deploy any number of platforms to support these and other network services. So the key is finding ways to minimize the impact of operating system differences so that administrators can concentrate on higher-level technical issues.

The goal of this book is to do just that. It is aimed at experienced system administrators who already know concepts such as DNS, directory services, and file systems. It also assumes that they are already familiar with one or the other respective operating systems-UNIX or Windows 2000-and that all they need is a jump start to do key tasks with the operating system that is new to them. Finally, it does indeed provide interoperability tips. It is important to note that "interoperability" is not just how the two operating systems can work together, but how they can coexist. So this book simply helps an administrator understand just how things are done, where the files and directories (or folders) are, how similarly named commands behave, what commands and utilities are equivalent. Ultimately, I hope the book will help the administrator make peaceful coexistence and interoperability a reality.

Organization of This Book

With the exception of the first two chapters, each chapter of this book contains material pertaining to Windows 2000, UNIX (usually with HP-UX examples), and interoperability. We use the four-layer TCP/IP model as the model of this book, starting with the network interface layer, the Internet layer, the transport layer, and then the application layer. Application layer issues comprise the majority of chapters.

• Chapter 1, "What Is UNIX?," is a good Chapter for administrators with mostly Windows backgrounds to read. While not a comprehensive introduction to UNIX, it will help these administrators to make sense of the examples in the book.
• Chapter 2, "What Is Windows 2000?," is for UNIX-oriented administrators. Again, it is designed to help UNIX administrators understand the Windows 2000 examples in this book rather than to be a definitive overview.
• Chapter 3, "The Network Interface Layer," examines network interface cards and drivers, and looks briefly at Ethernet and Fibre Channel technologies.
• Chapter 4, "The Internet Layer," examines a few key topics found at this layer, including ARP, ICMP, IP, routing, and Ping.
• Chapter 5, "The Transport Layer," concentrates on comparing tunable TCP parameters between Windows 2000 and HP-UX. We also look at UDP and network application programming interfaces.
• Chapter 6, "Name Resolution," begins the application layer discussion. Name resolution is a key component to network application interoperability. We look at things such as computer names, resolver, DNS, BIND, and NetBIOS.
• Chapter 7, "DHCP and DNS," looks more closely at these two technologies. Of particular importance is whether HP-UX DHCP clients can have their IP addresses registered with Microsoft's dynamic DNS.
• Chapter 8, "User Authentication," looks at topics such as NTLM, Kerberos, NIS, and pluggable application modules.
• Chapter 9, "Basic TCP/IP Utilities," compares the Windows 2000 and HP-UX versions of Finger, Ftp, Tftp, Rsh, Rcp, Rexec, and Telnet, and describes to what degree these utilities interoperate.
• Chapter 10, "Windows Services for UNIX," describes this optional product for Windows 2000, concentrating on the Telnet client and server and Server for NIS.
• Chapter 11, "NFS File Sharing," looks at employing NFS as a file sharing mechanism between Windows 2000 and HP-UX. The Windows 2000 NFS component is part of Windows Services for UNIX.
• Chapter 12, "CIFS File Sharing," compares CIFS and NFS and looks at Hewlett-Packard's CIFS/9000 product, available in both client and server versions.
• Chapter 13, "Miscellaneous Interoperability Topics," briefly describes network-attached storage, X Window, and Lpr as interoperability tools.



Updates

Submit Errata

