Tuesday, September 18, 2007
Network Security Tools 2005
Ettercap is a network analyzer that is free and open source. Advanced features such as ARP poisoning, packet filtering, and OS fingerprinting, along with support for password dissectors and plug-ins make Ettercap a powerful tool and a favorite among many network administrators. Ettercap has been known to compile on various Unix and Linux flavors, and has been successfully ported to run on Microsoft Windows operating systems.
This chapter introduces the concept of writing dissectors and plug-ins for Ettercap. Dissectors allow you to grab important information, such as usernames and passwords, that are transmitted over a network. For the purposes of understanding how to write a dissector, we will step through a dissector that captures and displays FTP usernames and passwords. Then, to demonstrate how to write an Ettercap plug-in, we will step through a plug-in that alerts the user when one host on the network attempts to establish a new TCP connection with another host.
Network Security Hacks 2004
These options are specified from the command line by running mount with the -o flag. For example, if you have a separate partition for /tmp that is on the third partition of your first IDE hard disk, you can mount with the nodev, noexec, and nosuid flags, which are enabled by running the following command:
# mount -o nodev,noexec,nosuid /dev/hda3 /tmp
An equivalent entry in your /etc/fstab would look something like this:
/dev/hda3 /tmp ext3 defaults,nodev,noexec,nosuid 1 2
By carefully considering your requirements and dividing up your storage into multiple filesystems, you can utilize these mount options to increase the work that an attacker will have to do in order to further compromise your system. A quick way to do this is to first categorize your directory tree into areas that need write access for the system to function and those that don't. You should consider using the read-only flag on any part of the filesystem where the contents do not change regularly. A good candidate for this might be /usr, depending on how often updates are made to system software.
Network Security Assessment 2004
-
Directly compromising key network components using private exploit tools, such as scripts that the attacker or his hacking group have developed for their own personal use
-
Compromising traffic and circumventing security mechanisms using ARP redirection and network sniffing
-
Compromising user account passwords and using those passwords to compromise other hosts where the user may have an active account
-
Abusing blatant system or network configuration issues, reading sensitive information from publicly accessible web folders, or bypassing poor firewall rules that open up the network to attack
Monday, September 10, 2007
Network Programming for Microsoft Windows 1999
Remote Access Service Client
All Microsoft Windows platforms feature a Remote Access Service (RAS) client, which allows you to connect your computer from a remote location to another computer featuring a remote access server component. Typically, a RAS client will do this by using a modem that connects to a telephone line and calls the remote computer by dialing a telephone number. Because of this, the RAS client is sometimes referred to as a dial-up networking (DUN) client.
On the server side, you must have a service awaiting your DUN connection. A RAS client is capable of establishing a communication link with several types of remote access servers.
Network Certification Training Kit 2001
The user-level security model is based on individual accounts created for specific users. When you want to grant users permission to access resources on a specific computer, you select them from a list of user accounts and specify the permissions you want to grant them, as shown in Figure 13.7. Windows 2000 and Windows NT always use user-level security, whether they are operating in client/server or peer-to-peer mode. In peer-to-peer mode, each computer has its own user accounts. When users log on to their computers, they are authenticated against an account on that system. If several people use the same computer, they must each have their own user account (or share a single account). When users elsewhere on the network attempt to access server resources on that computer, they are also authenticated using the accounts on the computer that hosts the resources.
Home Networking Bible, 2nd ed 2004
Using Windows 2000 Server
Windows 2000 Server is a 32-bit operating system that supports multitasking, which is the simultaneous execution of two or more programs, just as other Windows operating systems do. 2000 Server works well with Windows 98 and XP clients, as well as with Macintosh and Linux. You also can use computers running Windows 2000 Professional (although, as mentioned earlier
the chapter, Microsoft is phasing this operating system out) as clients for 2000 Server.
2000 Server provides security features that enable you to limit access to the server, printer, files, folders, and other resources on the network. You also can incorporate a logging and tracking feature that enables you to follow any application or system errors, so you can easily troubleshoot network problems.
Additionally, 2000 Server provides tracking and logging for security breaches. If someone tries to gain access to the network but doesn’t have the appropriate permissions, for example, 2000 Server records the event in a log so that you can see the time, username, and other information. You might not need this feature in your home network; however, if your teenager brings his friends home to work on the computer, you may be glad you have 2000 Server security.
the chapter, Microsoft is phasing this operating system out) as clients for 2000 Server.
2000 Server provides security features that enable you to limit access to the server, printer, files, folders, and other resources on the network. You also can incorporate a logging and tracking feature that enables you to follow any application or system errors, so you can easily troubleshoot network problems.
Additionally, 2000 Server provides tracking and logging for security breaches. If someone tries to gain access to the network but doesn’t have the appropriate permissions, for example, 2000 Server records the event in a log so that you can see the time, username, and other information. You might not need this feature in your home network; however, if your teenager brings his friends home to work on the computer, you may be glad you have 2000 Server security.
Kerberos The Definitive Guide 2003
The previous two chapters introduced the major concepts that underlie the Kerberos authentication system, and presented a short, high-level discussion of how Kerberos performs its magic. This chapter continues that discussion by drilling down into the nitty-gritty of the Kerberos protocol and presenting it on a fundamental level.
Creating a protocol that verifies the identity of two endpoints on a network given an underlying network that provides no security is a daunting task. Kerberos was designed under the assumption that attackers can read, copy, and create network traffic at will.
Ethernet Networks Design Implementation Organization and Management 4th Ed 2003
Originally, access to the computational capability of first-generation computers was through the use of punched cards. After an employee of the organization used a keypunch to create a deck of cards, that card deck was submitted to a window in the data center, typically labeled input/output (I/O) control. An employee behind the window would accept the card deck and complete a form that contained instructions for running the submitted job. The card deck and instructions would then be sent to a person in production control, who would schedule the job and turn it over to operations for execution at a predefined time. Once the job was completed, the card deck and any resulting output would be sent back to I/O control, enabling the joboriginator to return to the window in the data center to retrieve his or her card deck and the resulting output. With a little bit of luck, programmers might see the results of their efforts on the same day that they submitted their jobs.
Ethernet Definitive Guide 2000
The first part of this book provides a tour of basic Ethernet theory and operation. These chapters cover those portions of Ethernet operation that are common to all Ethernet media systems. Common portions include the Ethernet frame, the operation of the media access control system, full-duplex mode, and the AutoNegotiation protocol.
Part I contains these chapters:• Chapter 1, The Evolution of Ethernet
• Chapter 2, The Ethernet System
• Chapter 3, The Media Access Control Protocol
• Chapter 4, Full-Duplex Ethernet
• Chapter 5, Auto-Negotiation
Essential SNMP 2001
The Windows System Policy Editor comes with the Windows 95/98 Resource Kit, and must be installed before you can configure the SNMP agent. The first time you run the System Policy Editor it will ask you for an .adm file. Select C:\WINDOWS\INF \ADMIN.ADM as this file. Select "File Open Registry," then double-click the Local Computer icon. In the Policies tab, click down the plus signs until you reach Network and then SNMP. This should leave you with four SNMP agent configuration items. shows what your window should look like. To enable an option, place a check next to it. When you are finished, click "OK," then "File Save" at the main screen. If you don't follow these steps, your configuration won't be saved to the registry.
Designing Large-Scale LANs
The American architect Louis Henry Sullivan described his design philosophy with the simple statement "form follows function." By this credo he meant that a structure's physical layout and design should reflect as precisely as possible how this structure will be used. Every door and window is where it is for a reason.
He was talking about building skyscrapers, but this philosophy is perhaps even more useful for network design. Where building designs often include purely esthetic features to make them more beautiful to look at, every element of a good network design should serve some well-defined purpose. There are no gargoyles or frescos in a well-designed network.
The location and configuration of every piece of equipment and every protocol must be carefully
optimized to create a network that fulfills the ultimate purposes for which it was designed. Any sense of esthetics in network design comes from its simplicity and reliability. The network is most beautiful when it is invisible to the end user.
He was talking about building skyscrapers, but this philosophy is perhaps even more useful for network design. Where building designs often include purely esthetic features to make them more beautiful to look at, every element of a good network design should serve some well-defined purpose. There are no gargoyles or frescos in a well-designed network.
The location and configuration of every piece of equipment and every protocol must be carefully
optimized to create a network that fulfills the ultimate purposes for which it was designed. Any sense of esthetics in network design comes from its simplicity and reliability. The network is most beautiful when it is invisible to the end user.
DNS On Windows Server 2003
With the release of Windows 2000, Microsoft replaced the Windows NT Security Account Manager (SAM) with Active Directory (AD), which serves as the repository for information about users, groups, computers, and other network resources. In contrast to the SAM, Active Directory is built on several well-known standards including the Lightweight Directory Access Protocol (LDAP) for accessing and manipulating data, Kerberos for authentication, and—you guessed it—DNS for name resolution.
DNS on Windows 2000 2nd ed
This book is organized, more or less, to follow the evolution of a zone and its administrator. Chapter 1 and Chapter 2 discuss Domain Name System theory. Chapter 3 through Chapter 6 help you to decide whether to set up your own zones, then describe how to go about it, should you choose to. The middle chapters, Chapter 7 through Chapter 11, describe how to maintain your zones, configure hosts to use your name servers, plan for the growth of your zones, create subdomains, secure your name servers, and integrate DNS with Active Directory. The last chapters, Chapter 12 through Chapter 14, deal with common problems and troubleshooting tools.
DNS and BIND 4th ed 2001
Now that you have your name servers running, you might want to support more zones. What needs to be done? Nothing special, really. All you need to do is add more primary or secondary statements (BIND 4) or zone statements (BIND 8 and 9) to your configuration file. You can even add secondary lines to your primary master server and primary lines to your slave server. (You may have already noticed that your slave server is primary master for 0.0.127.in-addr.arpa.)
At this point, it's useful to repeat something we said earlier in this book. Calling a given name server a primary master name server or a slave name server is a little silly. Name servers can be—and usually are—authoritative for more than one zone. A name server can be a primary master for one zone and a slave for another. Most name servers, however, are either primary master for most of the zones they load or slave for most of the zones they load. So if we call a particular name server a primary master or a slave, we mean that it's the primary master or a slave for most of the zones it loads.
Sunday, September 9, 2007
DNS & BIND Cookbook 2003
All first moves in a Scrabble game have a few things in common: you play across the star, the opening square. You try to score high without opening up a premium square, particularly a Triple Word Score, for your opponent.
Most DNS setups start in very similar ways, too: you register a new domain and maybe a reverse-mapping domain; choose a version of BIND; download the BIND source code, if you need to, and build it; configure a primary master and slave name server; and make sure both name servers start at boot time.
This chapter will guide you through those opening moves and help you get your DNS infrastructure established.
Friday, September 7, 2007
Thursday, September 6, 2007
O'Reilly - Java RMI
Coding Conventions
For the most part, the examples are written in a fairly generic coding style. I follow standard Java
conventions with respect to capitalization. Instance variables are preceded by an underscore (_),
while locally scoped variables simply begin with a lowercase letter.
Variable and method names are longer, and more descriptive, than is customary.[2] References to
methods within the body of a paragraph almost always omit arguments™ instead of
readFromStream(InputStream inputStream), we usually write readFromStream( ).
conventions with respect to capitalization. Instance variables are preceded by an underscore (_),
while locally scoped variables simply begin with a lowercase letter.
Variable and method names are longer, and more descriptive, than is customary.[2] References to
methods within the body of a paragraph almost always omit arguments™ instead of
readFromStream(InputStream inputStream), we usually write readFromStream( ).
O'Reilly - Java Programming with Oracle JDBC
I am a firm believer that good foundational knowledge is a must if you, as an application developer, are going to write a robust application. Your knowledge of the fundamentals of the technologies you're using makes or break not only any application you write, but your programming career as well. I was extremely pleased to write a book about Oracle JDBC, because it is the foundation for using Java with Oracle.
This is a book written by a programmer for programmers. I try to include enough detail to get the novice up and running without boring the experienced programmer to death. My hope is that this book will guide you through the process of making a connection and executing SQL statements while maintaining database integrity and enabling you to use all the database technologies offered by Oracle.
O'Reilly - Java Network Programming (2nd Ed)
• Java 1.0 refers to all versions of Java that more or less implement the Java API as defined in Sun's Java Development Kit 1.0.2.
• Java 1.1 refers to all versions of Java that more or less implement the Java API as defined in any version of Sun's Java Development Kit 1.1.x. This includes third-party efforts such as Macintosh Runtime for Java (MRJ) 2.0, 2.1,and 2.2.
• Java 1.2 refers to all versions of Java that more or less implement the Java API as defined in the Standard Edition of Sun's Java Development Kit 1.2.x. This does not include the Enterprise Edition additions, which will be treated as extensions to the standard. These normally come in the javax package rather than the java packages.
• Java 1.3 refers to all versions of Java that more or less implement the Java API as defined in the Standard Edition of Sun's Java Development Kit 1.3.
• Java 1.1 refers to all versions of Java that more or less implement the Java API as defined in any version of Sun's Java Development Kit 1.1.x. This includes third-party efforts such as Macintosh Runtime for Java (MRJ) 2.0, 2.1,and 2.2.
• Java 1.2 refers to all versions of Java that more or less implement the Java API as defined in the Standard Edition of Sun's Java Development Kit 1.2.x. This does not include the Enterprise Edition additions, which will be treated as extensions to the standard. These normally come in the javax package rather than the java packages.
• Java 1.3 refers to all versions of Java that more or less implement the Java API as defined in the Standard Edition of Sun's Java Development Kit 1.3.
O'Reilly - Java Extreme Programming Cookbook [Ed 2003]
Ant is a portable, Java-based build tool designed to support software builds—and many other tasks— on any platform supporting Java. An XML file known as a buildfile specifies which tasks Ant follows when building your project. Ant ships with well over 100 tasks that perform operations ranging from compiling code to playing sound files when a build finishes. Java classes implement Ant tasks that can do anything Java can do. The Ant API is open and designed for extensibility; you can write your own custom tasks if the need arises.
O'Reilly - Java Extreme Programming Cookbook (Ed. 2004)
Creating great software is an art. If you ask a dozen programmers to solve a particular problem, you are likely to get a dozen radically different solutions. If you observe how these programmers reach their solutions, you will note that each programmer has her own favorite set of tools. One programmer may start by designing the application architecture using a UML CASE tool. Another may use wizards included with a fancy IDE, while another is perfectly content to use Emacs or vi.
O'Reilly - Java Distributed Computing (Ed. 2001)
Any given implementation of the event channel interface can support a particular quality of service. Some implementations may guarantee delivery of every event to every consumer attached to the channel, while others may just guarantee to make a best effort to deliver the events generated by its suppliers. The Event Service specification leaves the implementation open to these different levels of service to allow for different application requirements. The trade−offs here are similar to those found at a lower level, in choosing between TCP and UDP packet delivery over IP network connections. Guaranteed event delivery typically means reduced net throughput. Best−effort event delivery can potentially provide higher event throughput, but at the cost of potentially undelivered events, or events delivered to only some of the consumers attached to the channel.
O'Reilly - Java Cookbook
Using the command-line Java Development Kit (JDK) may be the best way to keep up with the very latest improvements from Sun/JavaSoft. This is not the fastest compiler available by any means; the compiler is written in Java and interpreted at compile time, making it a sensible bootstrapping solution, but not necessarily optimal for speed of development. Nonetheless, using Sun's JDK (or Java SDK), the commands are javac to compile and java to run your program. For example:
C:\javasrc>javac HelloWorld.java
C:\javasrc>java HelloWorld
Hello, World
C:\javasrc>
O'Reilly - Java And XML
XML. These three letters have brought shivers to almost every developer in the world today at some point in the last two years. While those shivers were often fear at another acronym to memorize, excitement at the promise of a new technology, or annoyance at another source of confusion for today's developer, they were shivers all the same. Surprisingly, almost every type of response was well merited with regard to XML. It is another acronym to memorize, and in fact brings with it a dizzying array of companions: XSL, XSLT, PI, DTD, XHTML, and more. It also brings with it a huge promise: what Java did for portability of code, XML claims to do for portability of data. Sun has even been touting the rather ambitious slogan "Java + XML = Portable Code + Portable Data" in recent months. And yes, XML does bring with it a significant amount of confusion. We will seek to unravel and demystify XML, without being so abstract and general as to be useless, and without diving in so deeply that this becomes just another droll specification to wade through. This is a book for you, the Java developer, who wants to understand the hype and use the tools that XML brings to the table.
O'Reilly - Java And XML ,2nd Ed v2
With the introductions behind us, let's get to it. Before heading straight into Java, though, some basic structures must be laid down. These address a fundamental understanding of the concepts in XML and how the extensible markup language works. In other words, you need an XML primer. If you are already an XML expert, skim through this chapter to make sure you're comfortable with the topics addressed. If you're completely new to XML, on the other hand, this chapter can get you ready for the rest of the book without hours, days, or weeks of study.
O'Reilly - Java - Enterprise In A Nutshell
Anyone can write distributed applications: you don't have to work for a major corporation, university, government agency, or any other kind of large−scale "enterprise" to program with the Java Enterprise APIs. Small businesses may not have the same enterprise−scale distributed computing needs large organizations have, but most still engage in plenty of distributed computing. With the explosive growth of the Internet and of network services, just about anyone can find a reason to write distributed applications. One such reason is that it is fun. When distributed computing is used to leverage the power of the network, the results can be amazingly cool!
O'Reilly - J2ME in a Nutshell
This book is an introduction to and a quick reference for the Java 2 Micro Edition (J2ME) APIs. J2ME is a family of specifications that defines various downsized versions of the standard Java 2 platform; these downsized versions can be used to program consumer electronic devices ranging from cell phones to highly capable Personal Data Assistants (PDAs), smart phones, and set-top boxes. Diverse as they are in both form and function, these devices have in common the fact that they either do not have the memory and/or processing power or do not need to support J2SE, the standard Java platform used on desktop and server systems. This chapter introduces J2ME and compares it to other platforms that target the same range of hardware.
O'Reilly - J2EE - Building Java Enterprise Applications Vol.1-Architecture (Ed. 2002)
All of this has led the folks at O'Reilly to be interested in a book specifically focused on building enterprise applications with these APIs. Instead of small, piecemeal examples, we've found that readers want large applications built from the ground up, and explanations of design decisions. Additionally, readers have been adamant about seeing more than just theJava part of the picture; they want to know how to set up a database, and get an LDAP store running, and integrate these. How does a UDDI registry fit into the equation? I'm going to address all of these issues in this series (yes, I said series!) of books, Building Java Enterprise Applications. You hold Volume I in your hands.
O'Reilly - Developing Java Beans
The Java Event Model
The JavaBeans architecture takes advantage of the event model that was introduced in version 1.1 of the Java language. Beans are treated the same as every other object within the event model. In fact, there is nothing at all about the event model that is specific to Beans. This is a common theme in JavaBeans. The Beans component model is designed to take advantage of features that are already available in Java. This is not to say that some of those features were not designed with Beans in mind, because apparently they were. But in many cases the features that are needed by Beans are generic enough to be provided by a core Java class library, making them available to any Java class whether or not it happens to be a Bean.
O'Reilly - Ant - The Definitive Guide (Ed. 2002)
This chapter describes where to get Ant, explains the differences between the various distributions, and covers the most common installation scenarios. As a portable Java application, Ant works very consistently on many different platforms. This should not be a surprise, given that Ant was written as an alternative to platform-specific make utilities. Most differences manifest themselves in the Ant startup scripts, which are understandably different on Windows and Unix systems. Once Ant is installed and configured, it does a remarkable job of insulating you from differences between platforms.
Hungry Minds - Java 2 Bible - Enterprise Edition
We won't cover parsing an XML document until Chapter 12, but it helps to see what you're constructing if you understand how it can later be parsed. Consider the following XML document, designed to convey information about a candidate to a possible employer:
One way to read through it is in an event−driven way. Just imagine yourself saying, "...and then thishappened." In the case of this resume, you can read it as follows:
Addison-Wesley - Java Look and Feel Design Guidelines Advanced Topics
An application's usability depends on its appearance and behavior--its look and feel. A consistent look and feel helps users learn an application faster and use it more efficiently. In addition, a consistent look and feel helps users learn other applications that share that look and feel. This book provides guidelines for designing applications with the Java look and feel. All the guidelines are intended to help you create a well-designed application.
Addison Wesley - Effective Java - Programming Language Guide
This book is designed to help you make the most effective use of the Java™ programming language and its fundamental libraries, java.lang, java.util, and, to a lesser extent, java.io. The book discusses other libraries from time to time, but it does not cover graphical user interface programming or enterprise APIs.
This book consists of fifty-seven items, each of which conveys one rule. The rules capture practices generally held to be beneficial by the best and most experienced programmers. The items are loosely grouped into nine chapters, each concerning one broad aspect of software design. The book is not intended to be read from cover to cover: Each item stands on its own, more or less. The items are heavily cross-referenced so you can easily plot your own course through the book.
Addison Wesley - Design Patterns Java
The Java Foundation Classes
The Java Foundation Classes (JFC) which were introduced after Java 1.1 and incorporated into Java 1.2 are a critical part of writing good Java programs. These were also known during development as the “Swing” classes and still are informally referred to that way. They provide easy ways to write very professional-looking user interfaces and allow you to vary the look and feel of your interface to match the platform your program is running on. Further, these classes themselves utilize a number of the basic design patterns and thus make extremely good examples for study. Nearly all of the example programs in this book use the JFC to produce the interfaces you see in the example code. Since not everyone may be familiar with these classes, and since we are going to build some basic classes from the JFC to use throughout our examples, we take a short break after introducing the creational patterns and spend a chapter introducing the JFC. While the chapter is not a complete tutorial in every aspect of the JFC, it does introduce the most useful interface controls and shows how to use them.
Windows Server Hacks (2004)
If you manage deployment of Active Directory in a medium-sized or large organization, you probably are spending a significant amount of time trying to maintain consistency in the Active Directory hierarchy. Even within a single domain, it typically makes sense to keep your organizational units (OUs) structured according to some agreed-upon rules. Regardless of whether your top-tier OU design is based on functional, business, geographic, or some other criteria, you will likely benefit from keeping the lower tiers arranged in the same fashion. This way, for example, you can formulate standard operating procedures that will apply across the entire organization. You can also attempt to automate some of the common administrative tasks, such as user, group, or computer account creation; script delegations and permission assignments; and group policy object management on the OU level.
Windows Server Cookbook (2005)
The Windows Server operating system (OS) has come a long way in the past ten years. In the early days of Windows NT, system crashes were common annoyances that administrators had to learn to deal with. There were few tools to manage the OS, and the ones that were available, which mainly consisted of the graphical variety, were limited in functionality and didn't scale well. Also at that time, Microsoft was not yet serious about providing intuitive scripting interfaces, which would enable administrators to automate repetitive tasks. The result was that administrators were forced to do a lot with a little.
Windows Server 2003 Weekend Crash Course
Windows Server 2003 is the latest version of Microsoft’s enterprise server operating system. The Windows Server 2003 family is the successor to the Windows 2000 Server family, which in turn built upon Windows NT Server. Windows Server 2003 introduces many new features and offers significant improvements to many features found in earlier Windows Server operating systems. Before you can begin using Windows Server 2003, though, you need to understand the family of products that carry the Server name and how they differ from one another. You also have to understand their common memory and processor architecture, and some of the basic technologies that Windows Server 2003 is built upon.
Windows Server 2003 In A Nutshell (2003)
If you are familiar with the Windows NT administrative tools and desktop, you may initially be thrown by WS2003 and its new Microsoft Management Console tools and enhanced desktop. Tables 1-1 through 1-3 help you bridge the gap between the two platforms, with the base Windows NT platform being Service Pack 4 or later.
To begin with, Table 1-1 lists the various Windows NT administrative tools and their counterparts in WS2003. Note that there is frequently no one-to-one correspondence between the old tools and the new. The steps for accessing administrative tools from the Start menu also differ slightly between the two platforms, namely:
Windows Server 2003 For Dummies
Welcome to Windows Server 2003 For Dummies, the book that helps anyone who's unfamiliar with Windows Server 2003 (or networks in general) find his or her way around a Windows Server 2003-based network. In a wired world, networks provide the links that tie all users together. Even if you're not using a network already, you probably will use one someday! This book tells you what's going on, in basic, straightforward terms. Although a few fortunate individuals may be acquainted with Windows Server 2003 and networks already, a lot more of us are not only unfamiliar with networking but also downright scared of it. To those who may be worried about the prospect of facing new and difficult technologies, we say, "Don't worry. Be happy." Using a network is not beyond anyone's wits or abilities — it's mostly a matter of using a language that ordinary people can understand. Ordinary folks are why this book talks about using Windows Server 2003 and networks in simple — and deliberately irreverent — terms. Nothing is too highfalutin to be mocked, nor too arcane to state in plain English. And when we do have to get technical, we'll warn you and make sure to define our terms to boot. This books aims to help you meet your needs. You'll find everything you need to know about Windows Server 2003 and networking in here, so you'll be able to find your way around — without having to learn lots of jargon or obtain an advanced degree in computer science along the way. We want you to enjoy yourself. If networking really is a big deal, it's important that you be able to get the most out of it. We really want to help!
Windows Server 2003 - The Complete Reference (2003)
Introduction
Windows Server 2003 is the new and improved version of Windows 2000, offering new features and functions that make administration of your network efficient and easier. If you’re moving to Windows Server 2003 from Windows NT, learning about Active Directory, Group Policies, and the other management features may seem overwhelming at first, and in fact, the learning curve can be quite consuming. This book helps you put the concepts and tasks you need to understand into an orderly pattern, which will shorten your learning curve.
Wednesday, September 5, 2007
The Ultimate Windows Server 2003 System Administrator's Guide
Windows Server 2003 offers extensive control over system configuration and user environments through a feature called Group Policy. Group Policy settings may be applied to domain, site, and organizational unit (OU) Active Directory containers, giving the administrator more granular control over system configurations and user settings. The OS adds refinements to the group policies functions but does not substantially change the administrative interface or their basic nature in Windows 2000. More than 160 new policy settings are now available in Windows Server 2003. Among the affected functionality are settings for Control Panel, error reporting, Terminal Server, Remote Assistance, networking and dial-up connections, Domain Name System (DNS), network logon, Group Policy, and roaming profiles.
Securing Windows Server 2003
Security is one of the primary functions of any server-based operating system. Without security, any user or program could do anything to your servers—and wreak havoc on your ability to effectively manage the environment. As a security administrator, you want to provide functionality and security to your users without burdening them or restricting them in a way that hinders their work. This is the mark of a great security administrator: the ability to successfully balance the security of proprietary and personal data and the usability of your systems in a way that maximizes the productivity of your organization. This book will show you how to do exactly that.
Microsoft Windows Small Business Server 2003 Administrator's Companion
The first time you noticed Microsoft Windows Small Business Server 2003, it might have been because it’s such a remarkable bargain. For no more than the price of a mid-level desktop copier, you get Microsoft Windows Server 2003, Windows SharePoint Services, Exchange Server 2003, Routing and Remote Access firewall technology, and five client access licenses. And that’s just the Standard Edition.
In the Premium Edition, you get all that plus Microsoft SQL Server 2000, Internet Security an Acceleration Server 2000, and Microsoft Office FrontPage 2003. In both editions, the technologies are optimized to work as a package for the small business user.
In the Premium Edition, you get all that plus Microsoft SQL Server 2000, Internet Security an Acceleration Server 2000, and Microsoft Office FrontPage 2003. In both editions, the technologies are optimized to work as a package for the small business user.
Microsoft Windows Server 2003 Security Guide (2003)
●Windows Server 2003 Security Guide — contains the Portable Document Format (PDF) file document that you are currently reading, as well as the Test Guide, Delivery Guide, and Support Guide associated with this material.●Windows Server 2003 Security Guide\Tools and Templates — contains subdirectories for an items that may accompany this guide.
●Windows Server 2003 Security Guide\Tools and Templates\Security Guide\Security Templates — contains all security templates that are discussed in the guide.
●Windows Server 2003 Security Guide\Tools and Templates\Security Guide\Sample Scripts — contains all sample IPSec filter scripts and an Excel workbook containing all traffic maps discussed in the guide.
Microsoft Windows Server 2003 Insider Solutions (2003)
Microsoft Windows Server 2003 Inside Out
To distinguish between the use of the terms upgrading and migrating as used in this chapter:
● Upgrading involves installing Windows Server 2003 over the top of an existing Microsoft Windows server installation, maintaining all configuration settings. When you upgrade a server to Windows Server 2003, you maintain all of the existing infor- mation in place. Most applications and services operate just as they did before the upgrade, although a few, Microsoft Internet Information Services (IIS) among them, are somewhat different.
● Migrating involves creating a new installation of Windows Server 2003 and transfer- ring the domain and user settings from another Windows server operating system
(Microsoft Windows NT 4, Microsoft Windows 2000, or Windows Server 2003). Dur-
ing a migration, a new installation of Windows Server 2003 is done, most often on a new machine. Once the operating system is installed, information is moved from the existing server to the new one using migration tools. You can use tools from Microsoft
or a number of third-party vendors such as Aelita and NetPro.
Microsoft Windows Server 2003 Administrator's Pocket Consultant (2003)
Microsoft Windows Server 2003 Administrator's Pocket Consultant is designed to be a concise and compulsively usable resource for Microsoft Windows Server 2003 administrators. This is the readable resource guide that you'll want on your desk at all times. The book covers everything you need to perform the core administrative tasks for servers running Windows Server 2003. Because the focus is on giving you maximum value in a pocket-sized guide, you don't have to wade through hundreds of pages of extraneous information to find what you're looking for. Instead, you'll find exactly what you need to get the job done.
Microsoft Windows Server 2003 Administrator's Companion, 2nd Edition
The Windows Server Post-Setup Security Updates window (shown in Figure 7-1) is the first thing that you see when you log on to a server as an administrator after performing
Mastering Windows Server 2003
If you lived through the change from NT 4 Server to Windows 2000 Server, then you might be a bit gun-shy about Windows Server 2003; how much more will you have to learn, and how hard will it be? If so, then I have good news: while Server 2003 offers a lot of new stuff, there’s not nearly as much new stuff—if 2000 was a tsunami, 2003 is just a heavy storm. (If, however, you’re an NT 4 guy getting ready to move to 2003, then yes, there’s a whole lot of new stuff to learn. But don’t worry, this is the right book, and I’ll make it as easy as is possible!) Clearly explaining what Server 2003 does is the job of the entire book, but in this chapter I’ll give you a quick overview of what’s new. I’m mainly writing this chapter for those who already know Windows 2000 Server and are looking for a quick overview of what’s new in 2003, so if you’re just joining the Microsoft networking family then don’t worry if some of this doesn’t make sense. I promise, in the rest of the book I’ll make it all clear.
Learning Windows Server 2003, 2nd Edition (2006)
It all started with Windows NT, Microsoft's first serious entry into the network server market. Versions 3.1 and 3.5 of Windows NT didn't garner very much attention in a NetWare-dominated world because they were sluggish and refused to play well with others. Along came Windows NT 4.0, which used the new Windows 95 interface (revolutionary only to those who didn't recognize Apple's Macintosh OS user interface) to put a friendlier face on some simple yet fundamental architectural improvements. With Version 4.0, larger organizations saw that Microsoft was serious about entering the enterprise computing market, even if the product currently being offered was still limited in scalability and availability. For one, Microsoft made concessions to NetWare users, giving them an easy way to integrate with a new NT network. The company also included a revised security feature set, including finely grained permissions and domains, which signified Microsoft considered enterprise computing an important part of Windows.
Inside Windows Server 2003
It's about time to install DNS, but first let's configure a few DNS clients so that they will be ready to use the server after it is in operation. Windows Server 2003 clients need two pieces of information about DNS:
-
The IP address of the DNS server or servers to which they will send queries.
-
The default domain name to use when sending queries. (This is also called the DNS Suffix.)
The IP address information is configured in TCP/IP Properties. The DNS Suffix information is configured in two places: the TCP/IP Properties for the network interface and System Properties for the computer. These entries are stored in separate places in the Registry.
DNS On Windows Server 2003
Microsoft ships a name server on the Windows Server 2003 CD-ROM, but you have to install it separately from the OS. This server, which we call the Microsoft DNS Server, is the server we cover in this book. It's notable because it sports a nice graphical front-end for configuring the server. This isn't the only name server available for Windows Server 2003, however. There are several others. Many are ports of BIND, which has traditionally been a Unix-based name server. If you're more comfortable configuring BIND than learning to configure a new name server (even with a GUI), you might consider running the latest version of BIND (9.2.2 as of this writing) on Windows Server 2003.
Active Directory Cookbook For Windows Server 2003 & Windows 2000 (2003)
Active Directory domains are named using the Domain Name Service (DNS) namespace. The domains that are part of a common DNS namespace are considered to be in the same domain tree. For example, the amer.rallencorp.com, emea.rallencorp.com, and rallencorp.com domains are part of the rallencorp.com domain tree. A single domain tree is sufficient for most implementations, but one example when multiple domain trees are necessary is with large conglomerate corporations. Conglomerates are made up of multiple individual companies. Each company typically wants to maintain its own identity and, therefore, its own namespace. Describing the conglomerate scenario is a good way to show the relationships between forests, domains, domain trees, and trusts.
Monday, September 3, 2007
Sunday, September 2, 2007
Saturday, September 1, 2007
phrasalverb
The inspiration for The Ultimate Phrasal Verb Book came about when a student asked me for a textbook to help her learn the meanings of common phrasal verbs. I had nothing to offer. The only textbook focusing on common verbs that I could give her contains not one phrasal verb — it teaches arise but not get up, awake but not wake up, seek but not look for.
Phrasal verbs are verbs, not idiomatic curiosities. There is no logic to classifying take over with take the bull by the horns. Phrasal verbs are an essential part of spoken and written English at all levels, and no student who hopes to master the language can afford to overlook them.
Although this textbook is intended primarily for high-intermediate to advanced students, ambitious students at lower levels will benefit from it as well. Only some FOCUS sections may prove to be a little beyond them; otherwise, there is nothing to prevent any student from studying the definitions and examples and attempting the exercises.
Subscribe to:
Posts (Atom)