What You Need:

Required:

• CAT 5 Cable – bulk Category 5, 5e or 6 cable
• RJ45 Ends
• Crimper for RJ45
• Wire Cutters – to cut and strip the cable if necessary

Recommend:

• Wire Stripper
• Cable Tester

About the Cable:

You can find bulk supplies of the cable at many computer stores or most electrical or home centers. You want UTP (Unshielded Twisted Pair) Category 5 cable for basic 10/100 functionality. You need CAT 5e for gigabit (1000BaseT) operation and CAT 6 gives you a measure of future proofing. Bulk cable comes in many types, there are 2 basic categories, solid and braided cable. Braided cable tends to work better in “patch” applications for desktop use. It is more flexible and resiliant than solid cable and easier to work with, but really meant for shorter lengths. Solid cable is meant for longer runs in a fixed position. Plenum rated cable should/must be used whenever the cable travels through an air circulation space. For example, above a false celing or below a raised floor.You’re likely going to want braided type cable but it may be difficult or impossible to tell from the box. Here is what the internals of the cable look like: <!–[if !vml]–><!–[endif]–>
Internal Cable Structure and Color Coding Inside the cable, there are 8 color coded wires. These wires are twisted into 4 pairs of wires, each pair has a common color theme. One wire in the pair being a solid or primarily solid colored wire and the other being a primarily white wire with a colored stripe (Sometimes cable doesn’t have any color on the striped cable, the only way to tell is to check which other wire it is twisted around). Examples of the naming schemes used are: Orange (alternatively Orange/White) for the solid colored wire and White/Orange for the striped cable. The twists are extremely important. They are there to counteract noise and interference. It is important to wire according to a standard to get proper performance from the cable. The TIA/EIA-568-A specifies two wiring standards for a 8-position modular connector such as RJ45. The two wiring standards, T568A and T568B vary only in the arrangement of the colored pairs. Tom writes to say “…sources suggest using T568A cabling since T568B is the AT&T standard, but the US Government specifies T568A since it matches USOC cabling for pairs 1 & 2, which allows it to work for 1/2 line phones…”. Your choice might be determined by the need to match existing wiring, jacks or personal preference, but you should maintain consistancy. I’ve shown both below for straight through cabling and just T568B for cross over cabling.

About the RJ45 Ends:

The RJ45 end is a 8-position modular connector that looks like a large phone plug. There are a couple variations available. The primary variation you need to pay attention to is whether the connector is intended for braided or solid wire. For braided/stranded wires, the connector has contacts that actually pierce the wire. For solid wires, the connector has fingers which pierce the insulation and make contact with the wire by grasping it from both sides. The connector is the weak point in an ethernet cable, choosing the wrong one will often cause grief later. If you just walk into a computer store, it’s nearly impossible to tell what type of connector it is. Here is a diagram and pinout:
RJ45 Jack and Plug Pinout

Ethernet Cable Pinouts:

There are two basic cables. A straight through cable, which is used to connect to a hub or switch, and a cross over cable used to operate in a peer-to-peer fashion without a hub/switch. Some interfaces can cross and un-cross a cable automatically as needed, really quite nice.

Standard, Straight-Through Wiring (both ends are the same):

RJ45 Pin #	Wire Color (T568A)	Wire Diagram (T568A)	10Base-T Signal 100Base-TX Signal	1000Base-T Signal
1	White/Green	<!–[if !vml]–><!–[endif]–>	Transmit+	BI_DA+
2	Green	<!–[if !vml]–><!–[endif]–>	Transmit-	BI_DA-
3	White/Orange	<!–[if !vml]–><!–[endif]–>	Receive+	BI_DB+
4	Blue	<!–[if !vml]–><!–[endif]–>	Unused	BI_DC+
5	White/Blue	<!–[if !vml]–><!–[endif]–>	Unused	BI_DC-
6	Orange	<!–[if !vml]–><!–[endif]–>	Receive-	BI_DB-
7	White/Brown	<!–[if !vml]–><!–[endif]–>	Unused	BI_DD+
8	Brown	<!–[if !vml]–><!–[endif]–>	Unused	BI_DD-

Straight-Through Cable Pinout for T568A

RJ45 Pin #	Wire Color (T568B)	Wire Diagram (T568B)	10Base-T Signal 100Base-TX Signal	1000Base-T Signal
1	White/Orange	<!–[if !vml]–><!–[endif]–>	Transmit+	BI_DA+
2	Orange	<!–[if !vml]–><!–[endif]–>	Transmit-	BI_DA-
3	White/Green	<!–[if !vml]–><!–[endif]–>	Receive+	BI_DB+
4	Blue	<!–[if !vml]–><!–[endif]–>	Unused	BI_DC+
5	White/Blue	<!–[if !vml]–><!–[endif]–>	Unused	BI_DC-
6	Green	<!–[if !vml]–><!–[endif]–>	Receive-	BI_DB-
7	White/Brown	<!–[if !vml]–><!–[endif]–>	Unused	BI_DD+
8	Brown	<!–[if !vml]–><!–[endif]–>	Unused	BI_DD-

Straight-Through Cable Pinout for T568B

Cross Over Cable (T568B):

RJ45 Pin # (END 1)	Wire Color	Diagram End #1	RJ45 Pin # (END 2)	Wire Color	Diagram End #2
1	White/Orange	<!–[if !vml]–><!–[endif]–>	1	White/Green	<!–[if !vml]–><!–[endif]–>
2	Orange	<!–[if !vml]–><!–[endif]–>	2	Green	<!–[if !vml]–><!–[endif]–>
3	White/Green	<!–[if !vml]–><!–[endif]–>	3	White/Orange	<!–[if !vml]–><!–[endif]–>
4	Blue	<!–[if !vml]–><!–[endif]–>	4	White/Brown	<!–[if !vml]–><!–[endif]–>
5	White/Blue	<!–[if !vml]–><!–[endif]–>	5	Brown	<!–[if !vml]–><!–[endif]–>
6	Green	<!–[if !vml]–><!–[endif]–>	6	Orange	<!–[if !vml]–><!–[endif]–>
7	White/Brown	<!–[if !vml]–><!–[endif]–>	7	Blue	<!–[if !vml]–><!–[endif]–>
8	Brown	<!–[if !vml]–><!–[endif]–>	8	White/Blue	<!–[if !vml]–><!–[endif]–>

Cross Over Cable Pinouts +Note: The cross over cable layout is suitable for 1000Base-T operation, all 4 pairs are crossed.

How to wire Ethernet Cables:

1. Strip off about 2 inches of the cable sheath.
2. Untwist the pairs – don’t untwist them beyond what you have exposed, the more untwisted cable you have the worse the problems you can run into.
3. Align the colored wires according to the diagrams above.
4. Trim all the wires to the same length, about 1/2″ to 3/4″ left exposed from the sheath.
5. Insert the wires into the RJ45 end – make sure each wire is fully inserted to the front of the RJ45 end and in the correct order. The sheath of the cable should extend into the RJ45 end by about 1/2″ and will be held in place by the crimp.
6. Crimp the RJ45 end with the crimper tool
7. Verify the wires ended up the right order and that the wires extend to the front of the RJ45 end and make good contact with the metal contacts in the RJ45 end.
8. Cut the cable to length – make sure it is more than long enough for your needs. Remember, an end to end connection should not extend more than 100m (~328ft). Try to keep cables short, the longer the cable becomes the more it may affect performance, usually noticable as a gradual decrease in speed and increase in latency.
9. Repeat the above steps for the second RJ45 end.
10. If a cable tester is available, use it to verify the proper connectivity of the cable.

That should be it, if your cable doesn’t turn out, look closely at each end and see if you can find the problem. Usually a wire ended up in the wrong place or more commonly, one of the wires didn’t extend to the front of the RJ45 connector and is making no, or poor contact. If you see a mistake or problem, cut the end off and start again.

Notes:

Power over Ethernet (PoE):

Power over Ethernet has been implemented in many variations before IEEE standardized 802.3af. 802.3af specifies the ability to supply an endpoint with 48V DC at up 350mA or 16.8W. The endpoint must be capable of receiving power on either the data pairs [Mode A] (often called phantom power) or the unused pairs [Mode B] in 100Base-TX. PoE can be used with any ethernet configuration, including 10Base-T, 100Base-TX and 1000Base-T. Power is only supplied when a valid PoE endpoint is detected by using a low voltage probe to look for the PoE signature on the endpoint. PoE power is typically supplied in one of two ways, either the host ethernet switch provides the power, or a “midspan” device is plugged in between the switch and endpoints which supplies the power. No special cabling is required.

RJ45 Pin #	Wire Color (T568A)	Wire Diagram (T568A)	10Base-T Signal 100Base-TX Signal	PoE
1	White/Green	<!–[if !vml]–><!–[endif]–>	Transmit+	Mode A +
2	Green	<!–[if !vml]–><!–[endif]–>	Transmit-	Mode A +
3	White/Orange	<!–[if !vml]–><!–[endif]–>	Receive+	Mode A -
4	Blue	<!–[if !vml]–><!–[endif]–>	Unused	Mode B +
5	White/Blue	<!–[if !vml]–><!–[endif]–>	Unused	Mode B +
6	Orange	<!–[if !vml]–><!–[endif]–>	Receive-	Mode A -
7	White/Brown	<!–[if !vml]–><!–[endif]–>	Unused	Mode B -
8	Brown	<!–[if !vml]–><!–[endif]–>	Unused	Mode B -

Power over Ethernet Power Delivery

Protocol Details:

*Designed to work on MOST category 5 cable, category 5e specifications ensure 1000Base-T operation

Cable Category Details:

Increasing category levels are backward compatible.
Manufacturers will often test and certify their cable well beyond the standards.
*10GBase-T should work on Cat6, but to get the full 100m range, Cat 6a is required.

Related Reading Material

• Get IEEE 802 – Ethernet Standards
• Charles Spurgeon’s Ethernet Website
• Network Connection Speeds Reference
• Fiber Optic Connector Reference
• Ethernet: The Definitive Guide <!–[if !vml]–><!–[endif]–>
• Interconnections: Bridges, Routers, Switches, and Internetworking Protocols <!–[if !vml]–><!–[endif]–>
• The Switch Book: The Complete Guide to LAN Switching Technology <!–[if !vml]–><!–[endif]–>
• TCP/IP Illustrated 3 Volume Set:
  
  • The Protocols (TCP/IP Illustrated, Volume 1)
  • The Implementation (TCP/IP Illustrated, Volume 2)
  • TCP for Transactions, HTTP, NNTP, and the UNIX(R) Domain Protocols (TCP/IP Illustrated, Volume 3)
• UNIX Network Programming
  
  • Unix Network Programming, Vol. 1: The Sockets Networking API, Third Edition
  • UNIX Network Programming, Volume 2: Interprocess Communications (2nd Edition)

MORE INFORMATION

loadTOCNode(1, \’moreinformation\’); This message generally appears after you lose a network signal. You may lose a network signal for several reasons. Use the following options to determine the cause of this issue:

REFERENCES

loadTOCNode(1, \’references\’); For more information about other related network issues, click the following article numbers to view the articles in the Microsoft Knowledge Base:

814152 (http://support.microsoft.com/kb/814152/) “A network cable is unplugged” message when you try to use a network cable to connect to your MN-100 or MN-500

240395 (http://support.microsoft.com/kb/240395/) Description of the possible “Local Area Connection” icon states

822585 (http://support.microsoft.com/kb/822585/) Internet Mail Wizard displays the IP address 0.0.0.0 when a network adapter is disabled

APPLIES TO

Install Internet Information Services and the FTP Service

 Because FTP depends on Microsoft Internet Information Services (IIS), IIS and the FTP Service must be installed on the computer. To install IIS and the FTP Service, follow these steps.

NOTE: In Windows Server 2003, the FTP Service is not installed by default when you install IIS. If you already installed IIS on the computer, you must use the Add or Remove Programs tool in Control Panel to install the FTP Service.

IIS and the FTP service are now installed. You must configure the FTP Service before you can use it.

Configure The FTP Service

loadTOCNode(2, \’summary\’); To configure the FTP Service to allow only anonymous connections, follow these steps:

The FTP server is now configured to accept incoming FTP requests. Copy or move the files that you want to make available to the FTP publishing folder for access. The default folder is drive:\Inetpub\Ftproot, where drive is the drive on which IIS is installed.

Install Internet Information Services and the FTP Service

Because FTP depends on Microsoft Internet Information Services (IIS), IIS and the FTP Service must be installed on the computer. To install IIS and the FTP Service, follow these steps.

NOTE: In Windows Server 2003, the FTP Service is not installed by default when you install IIS. If you already installed IIS on the computer, you must use the Add or Remove Programs tool in Control Panel to install the FTP Service.

IIS and the FTP service are now installed. You must configure the FTP Service before you can use it.

Configure The FTP Service

To configure the FTP Service to allow only anonymous connections, follow these steps:

The FTP server is now configured to accept incoming FTP requests. Copy or move the files that you want to make available to the FTP publishing folder for access. The default folder is drive:\Inetpub\Ftproot, where drive is the drive on which IIS is installed.

APPLIES TO

1. Start the Network Control Applet by clicking on Network from Control Panel (Start – Settings – Control Panel) or right click on Network Neighborhood and select Properties
2. Click on the Services tab and click Add
3. Select “Microsoft DHCP <!–[if !vml]–><!–[endif]–> Server” and click OK
4. You will be prompted to insert the NT Server installation CD or say where the i386 directory is
5. A warning that all local adapters must use a static IP address and click OK
6. Click Close and select Yes to reboot

Under Windows 2000 to install perform the following:

1. Start the Add/Remove Programs Control Panel applet (Start – Settings – Control Panel – Add/Remove Programs)
2. In the left hand pane click ‘Add/Remove Windows Components”
3. Click the ‘Components’ button to start the Components wizard
4. Click Next
5. Select ‘Networking Services’ and click Details
6. Check the ‘Dynamic Host Configuration Protocol (DHCP)’ option and click OK
7. Click Next and the relevant files and services will be configured.
8. Click Finish when all operations have completed
9. Click Close to the Add/Remove Programs dialog

SUMMARY

This step-by-step article describes how to use Group Policy to automatically distribute programs to client computers or users. You can use Group Policy to distribute computer programs by using the following methods:

Note Windows Server 2003 Group Policy automated-program installation requires client computers that are running Microsoft Windows 2000 or later.

<!–[if !supportLineBreakNewLine]–>
<!–[endif]–>

Create a Distribution Point

To publish or assign a computer program, you must create a distribution point on the publishing server:

Create a Group Policy Object

To create a Group Policy object (GPO) to use to distribute the software package:

Assign a Package

To assign a program to computers that are running Windows Server 2003, Windows 2000, or Microsoft Windows XP Professional, or to users who are logging on to one of these workstations:

Publish a Package

To publish a package to computer users and make it available for installation from the Add or Remove Programs tool in Control Panel:

Redeploy a Package

In some cases you may want to redeploy a software package. For example, if you upgrade or modify the package. To redeploy a package:

Remove a Package

To remove a published or assigned package:

Troubleshoot

loadTOCNode(2, \’summary\’); Published Packages Are Displayed on a Client Computer After You Use a Group Policy to Remove Them

loadTOCNode(3, \’summary\’); This situation can occur when a user has installed the program but has not used it. When the user first starts the published program, the installation is finalized. Group Policy then removes the program.

REFERENCESFor more information about how to use a Group Policy to deploy software, click the following article numbers to view the articles in the Microsoft Knowledge Base: 304953 (http://support.microsoft.com/kb/304953/) How to deploy Office XP over a network 302430 (http://support.microsoft.com/kb/302430/) How to assign software to a specific group by using Group Policy <!–[if !vml]–><!–[endif]–>Back to the top

APPLIES TO

Back to the top

Introduction

Step-by-Step Guides

The Microsoft Windows Server 2003 Deployment step-by-step guides provide hands-on experience for many common operating system configurations. The guides begin by establishing a common network infrastructure through the installation of Windows Server 2003, the configuration of Active Directory, the installation of a Windows XP Professional workstation, and finally the addition of this workstation to a domain. Subsequent step-by-step guides assume that you have this common network infrastructure in place. If you do not wish to follow this common network infrastructure, you will need to make appropriate modifications while using these guides.

The common network infrastructure requires the completion of the following guides.

Once the common network infrastructure is configured, any of the additional step-by-step guides may be employed. Note that some step-by-step guides may have additional prerequisites above and beyond the common network infrastructure requirements. Any additional requirements will be noted in the specific step-by-step guide.

Microsoft Virtual PC

The Windows Server 2003 Deployment step-by-step guides may be implemented within a physical lab environment or through virtualization technologies like Microsoft Virtual PC 2004 or Virtual Server 2005. Virtual machine technology enables customers to run multiple operating systems concurrently on a single physical server. Virtual PC 2004 and Virtual Server 2005 are designed to increase operational efficiency in software test and development, legacy application migration, and server consolidation scenarios.

The Windows Server 2003 Deployment step-by-step guides assume that all configurations will occur within a physical lab environment although most configurations can be applied to a virtual environment without modification.

Applying the concepts provided in these step-by-step guides to a virtual environment based is beyond the scope of this document.

Important Notes

The example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious. No association with any real company, organization, product, domain name, email address, logo, person, places, or events is intended or should be inferred.

This common infrastructure is designed for use on a private network. The fictitious company name and Domain Name System (DNS) name used in the common infrastructure are not registered for use on the Internet. You should not use this name on a public network or Internet.

The Active Directory service structure for this common infrastructure is designed to show how Windows Server 2003 Change and Configuration Management works and functions with Active Directory. It was not designed as a model for configuring Active Directory for any organization.

This guide explains how to build a common network infrastructure beginning with the installation and configuration of the Microsoft Windows Server 2003 operating system as a domain controller. This common infrastructure allows you to learn about and evaluate Windows Server 2003. As you implement this guide, think about how you will use them in your organization.

This guide, which is the first in a two-part series, shows how to install a server as a domain controller and populate a sample Active Directory service structure. Part two describes steps to install a Windows XP Professional client and connect that client to the domain controller. First, complete the procedures in this guide, then use “Part II: Installing a Windows XP Professional Workstation and Connecting It to a Domain” to complete your common network infrastructure.

Prerequisites

Guide Requirements

These are the hardware requirements for the common infrastructure.

Notes:

Additional Server Parameters

If you add additional servers to the common infrastructure, use the following server naming convention.

Server Configuration

Overview

Figure 1 shows the basic server configuration.

Figure 1.  The Server Configuration

Server Disk Configuration

To use a single server for the infrastructure in this guide, you will need a server with either two disk drives or a single disk drive with two partitions.

Note:  Subsequent step-by-step guides in this series may require additional servers or other equipment; those additions are addressed in the specific guide.

The first disk or partition holds Windows Server 2003 and other files for the common infrastructure, such as the Windows Installer packages and application source files. The second disk or partition is reserved for Active Directory log files and procedures required by other step-by-step guides.

Each disk or partition must hold several gigabytes of information, and each disk or partition must be formatted for the NT file system (NTFS). The steps for creating and formatting partitions are contained in this guide.

Server Installation

To begin the installation procedure, boot directly from the Windows Server 2003 CD. Your CD-ROM must support bootable CDs.

Note:  When you configure partitions and format drives, all data on the server hard drive is destroyed.

Beginning the Installation

Setup creates the disk partitions on the computer running Windows Server 2003, formats the drive, and then copies installation files from the CD to the server.

Note:  These instructions assume that you are installing Windows Server 2003 on a computer that is not already running Windows. If you are upgrading from an older version of Windows, some of the installation steps may differ.

To begin the installation

Windows Server 2003 Setup formats the partition and then copies the files from the Windows Server 2003 Server CD to the hard drive. The computer restarts and the Windows Server 2003 Installation Program continues.

Completing the Installation

To continue the installation with the Windows Server 2003 Setup Wizard

Preparing a Secondary Partition or Secondary Disk Drive

The unpartitioned space from the installation of Windows Server 2003 requires formatting before it can be accessed by the operating system. Management of disks and partitions occurs through the Computer Management snap-in for Microsoft Management Console. The following steps assume a second disk drive is in use; modify procedures accordingly for a second partition.

To prepare a secondary partition or disk drive

Warning:  Formatting a partition destroys all data on that partition. Make sure that you select the correct partition.

Configuring Your Server as a DHCP Server

Dynamic Host Configuration Protocol (DHCP) can be installed manually or by using the Windows Server 2003 Manage Your Server wizard. This section uses the wizard to complete the installation.

To install DHCP using the Windows Server 2003 Manage Your Server wizard

Warning: The following section will configure your server as a DHCP server. If this server resides on a production network, the server may distribute IP address information that might not be valid on the network. Microsoft recommends that these exercises be completed on an isolated network.

Configuring Your Server as a Domain Controller

Domain Name Service (DNS) and DCPromo (the command-line tool that creates DNS and Active Directory) can be installed manually or by using the Windows Server 2003 Manager Your Server Wizard. This section uses the manual tools to complete the installation.

To install DNS and Active Directory using the manual tools

To authorize the DHCP server

Active Directory Sample Infrastructure

The common infrastructure is based on the fictitious organization Contoso. Contoso owns the DNS name contoso.com, which was configured with the Active Directory Installation Wizard in the preceding section. Figure 4 illustrates the sample Active Directory structure.

<!–[if !vml]–><!–[endif]–>

Figure 4.  Sample Active Directory Structure

The most interesting aspects of this structure are the Domain (contoso.com); the Accounts, Headquarters, Production, Marketing, Groups, Resources, Desktops, Laptops, and Servers organizational units (OUs). These are represented by folders (book) in Figure 4. OUs exist for the delegation of administration and for the application of Group Policy—not simply to mirror a business organization. For an in-depth discussion on designing an OU structure, see “Designing and Deploying Directory and Security Services”.

Populating Active Directory

This section describes how to manually create the OUs, Users, and Security Groups outlined in Appendix A.

Creating Organizational Units and Groups

To create OUs and Security Groups

Creating User Accounts

To create a user account

Adding Users to Security Groups

To add a user to a security group

<!–[if !vml]–><!–[endif]–>Top of page

Appendix A:  Active Directory Populace

Users

How To Install and Configure a File and Print Server in Windows Server 2003

Install File and Printer Sharing

loadTOCNode(2, \’summary\’); By default, a Windows Server 2003-based computer is installed with Client for Microsoft Networks, File and Printer Sharing for Microsoft Networks, and TCP/IP.

NOTE: You can view these services in the properties for the local area connection.

You can create a Windows Server 2003 file server and print server manually, or you can use the wizards that are provided in the Configure Your Server Wizard administrative tool.

How to Install a File Server on Windows Server 2003 by Using the Configure Your Server Wizard

How to Manually Install a File Server on Windows Server 2003

Install a Windows Server 2003 Print Server

loadTOCNode(2, \’summary\’); How to Install a Print Server on Windows Server 2003 by Using the Configure Your Server Wizard

How to Share a Printer

How to Manually Install a Print Server on Windows Server 2003

Command-line options

As you’re starting the program from a DOS prompt:
ftp [-v] [-d] [-i] [-n] [-g] [-s:filename] [-a] [-w:windowsize] [computer]

• -v – Suppresses verbose display of remote server responses.
• -n – Suppresses auto-login upon initial connection.
• -i – Turns off interactive prompting during multiple file transfers.
• -d – Enables debugging, displaying all ftp commands passed between the client and server.
• -g – Disables filename globbing, which permits the use of wildcard chracters in local file and path names.
• -s:filename – Specifies a text file containing ftp commands; the commands will automatically run after ftp starts. No spaces are allowed in this parameter. Use this switch instead of redirection (>).
• -a – Use any local interface when binding data connection.
• -w:windowsize – Overrides the default transfer buffer size of 4096.
• computer – Specifies the computer name or IP address of the remote computer to connect to. The computer, if specified, must be the last parameter on the line.

Client commands

• ! – Runs the specified command on the local computer
• ? – Displays descriptions for ftp commands
• append – Appends a local file to a file on the remote computer
• ascii – Sets the file transfer type to ASCII, the default
• bell – Toggles a bell to ring after each file transfer command is completed (default = OFF)
• binary – Sets the file transfer type to binary
• bye – Ends the FTP session and exits ftp
• cd – Changes the working directory on the remote computer
• close – Ends the FTP session and returns to the command interpreter
• debug – Toggles debugging (default = OFF)
• delete – Deletes a single file on a remote computer
• dir – Displays a list of a remote directory’s files and subdirectories
• disconnect – Disconnects from the remote computer, retaining the ftp prompt
• get – Copies a single remote file to the local computer
• glob – Toggles filename globbing (wildcard characters) (default = ON)
• hash – Toggles hash-sign (#) printing for each data block transferred (default = OFF)
• help – Displays descriptions for ftp commands
• lcd – Changes the working directory on the local computer
• literal – Sends arguments, verbatim, to the remote FTP server
• ls – Displays an abbreviated list of a remote directory’s files and subdirectories
• mdelete – Deletes one or more files on a remote computer
• mdir – Displays a list of a remote directory’s files and subdirectories
• mget – Copies one or more remote files to the local computer
• mkdir – Creates a remote directory
• mls – Displays an abbreviated list of a remote directory’s files and subdirectories
• mput – Copies one or more local files to the remote computer
• open – Connects to the specified FTP server
• prompt – Toggles prompting (default = ON)
• put – Copies a single local file to the remote computer
• pwd – Displays the current directory on the remote computer (literally, “print working directory”)
• quit – Ends the FTP session with the remote computer and exits ftp (same as “bye”)
• quote – Sends arguments, verbatim, to the remote FTP server (same as “literal”)
• recv – Copies a remote file to the local computer
• remotehelp – Displays help for remote commands
• rename – Renames remote files
• rmdir – Deletes a remote directory
• send – Copies a local file to the remote computer (same as “put”)
• status – Displays the current status of FTP connections
• trace – Toggles packet tracing (default = OFF)
• type – Sets or displays the file transfer type (default = ASCII)
• user – Specifes a user to the remote computer
• verbose – Toggles verbose mode (default = ON)

!

Runs the specified command on the local computer.Syntax: ! [command]

Parameter(s):
command – Specifies the command to run on the local computer. If command is omitted, the local command prompt is displayed; type “exit” to return to ftp.

?

Displays descriptions for ftp commands. ? is identical to help.Syntax: ? [command]

Parameter(s):
command – Specifies the name of the command about which you want a description. If command is not specified, ftp displays a list of all commands.

append

Appends a local file to a file on the remote computer using the current file type setting.Syntax: append local-file [remote-file]

Parameter(s):
local-file – Specifies the local file to add.
remote-file – Specifies the file on the remote computer to which local-file will be added. If remote-file is omitted, the local filename is used for the remote filename.

ascii

Sets the file transfer type to ASCII, the default.Syntax: ascii

Note
FTP supports two file transfer types, ASCII and binary image. ASCII should be used when transferring text files. See also binary.

In ASCII mode, character conversions to and from the network standard character set are performed. For example, end-of-line characters are converted as necessary, based on the target operating system.

bell

Toggles a bell to ring after each file transfer command is completed. By default, the bell is off.Syntax: bell

binary

Sets the file transfer type to binary.Syntax: binary

Note
FTP supports two file transfer types, ASCII and binary image. Binary should be used when transferring executable files. In binary mode, the file is moved byte-by-byte. See also ascii.

bye

Ends the FTP session with the remote computer and exits ftp.Syntax: bye

cd

Changes the working directory on the remote computer.Syntax: cd remote-directory

Parameter(s):
remote-directory – Specifies the directory on the remote computer to change to.

close

Ends the FTP session with the remote server and returns to the command interpreter.Syntax: close

debug

Toggles debugging. When debugging is on, each command sent to the remote computer is printed, preceded by the string —>. By default, debugging is off.Syntax: debug

delete

Deletes a single file on a remote computer. See also mdelete, which can delete multiple files.Syntax: delete remote-file

Parameter(s):
remote-file – Specifies the file to delete.

dir

Displays a list of a remote directory’s files and subdirectories. See also mdir, which can list multiple directories.Syntax: dir [remote-directory] [local-file]

Parameter(s):
remote-directory – Specifies the directory for which you want to see a listing. If no directory is specified, the current working directory on the remote computer is used.
local-file – Specifies a local file to store the listing. If not specified, output is displayed on the screen.

disconnect

Disconnects from the remote computer, retaining the ftp prompt.Syntax: disconnect

get

Copies a remote file to the local computer using the current file transfer type. See also mget, which can copy multiple files.Syntax: get remote-file [local-file]

Parameter(s):
remote-file
Specifies the remote file to copy.

local-file
Specifies the name to use on the local computer. If not specified, the file is given the remote-file name.

glob

Toggles filename globbing. Globbing permits use of wildcard characters in local file or path names. By default, globbing is on.Syntax: glob

hash

Toggles hash-sign (#) printing for each data block transferred. The size of a data block is 2048 bytes. By default, hash mark printing is off.Syntax: hash

help

Displays descriptions for ftp commands.Syntax: help [command]

Parameter(s):
command – Specifies the name of the command about which you want a description. If command is not specified, ftp displays a list of all commands.

lcd

Changes the working directory on the local computer. By default, the working directory is the directory in which ftp was started.Syntax: lcd [directory]

Parameter(s):
directory – Specifies the directory on the local computer to change to. If directory is not specified, the current working directory on the local computer is displayed.

literal

Sends arguments, verbatim, to the remote FTP server. A single FTP reply code is expected in return.Syntax: literal argument [ ...]

Parameter(s):
argument – Specifies the argument to send to the FTP server.

ls

Displays an abbreviated list of a remote directory’s files and subdirectories.Syntax: ls [remote-directory] [local-file]

Parameter(s):
remote-directory – Specifies the directory for which you want to see a listing. If no directory is specified, the current working directory on the remote computer is used.
local-file – Specifies a local file to store the listing. If not specified, output is displayed on the screen.

mdelete

Deletes one or more files on a remote computer.Syntax: mdelete remote-files [ ...]

Parameter(s):
remote-files – Specifies the remote files to delete.

mdir

Displays a list of a remote directory’s files and subdirectories. Mdir allows you to specify multiple files.Syntax: mdir remote-files [ ...] local-file

Parameter(s):
remote-files – Specifies the directory for which you want to see a listing. Remote-files must be specified; type “-” to use the current working directory on the remote computer.
local-file – Specifies a local file to store the listing. Type “-” to display the listing on the screen.

mget

Copies one or more remote files to the local computer using the current file transfer type.Syntax: mget remote-files [ ...]

Parameter(s):
remote-files – Specifies the remote file(s) to copy to the local computer.

mkdir

Creates a remote directory.Syntax: mkdir directory

Parameter(s):
directory – Specifies the name of the new remote directory.

mls

Displays an abbreviated list of a remote directory’s files and subdirectories.Syntax: mls remote-files [ ...] local-file

Parameter(s):
remote-files – Specifies the files for which you want to see a listing. Remote-files must be specified; type “-” to use the current working directory on the remote computer.
local-file – Specifies a local file to store the listing. Type “-” to display the listing on the screen.

mput

Copies one or more local files to the remote computer using the current file transfer type.Syntax: mput local-files [ ...]

Parameter(s):
local-files – Specifies the local files to copy to the remote computer.

open

Connects to the specified FTP server.Syntax: open computer [port]

Parameter(s):
computer – Specifies the remote computer to connect to. Computer can be specified by IP address or computer name (a DNS or HOSTS file must be available). If auto-login is on (default), FTP also attempts to automatically log the user in to the FTP server (see Ftp command-line options to disable auto-login).
port – Specifies a port number to use to contact an FTP server.

prompt

Toggles prompting. Ftp prompts during multiple file transfers to allow you to selectively retrieve or store files; mget and mput transfer all files if prompting is turned off. By default, prompting is on.Syntax: prompt

put

Copies a local file to the remote computer using the current file transfer type. See also mput, which can copy multiple files.Syntax: put local-file [remote-file]

Parameter(s):
local-file – Specifies the local file to copy.
remote-file – Specifies the name to use on the remote computer. If not specified, the file is given the local-file name.

pwd

Displays the current directory on the remote computer.Syntax: pwd

quit

Ends the FTP session with the remote computer and exits ftp.Syntax: quit

quote

Sends arguments, verbatim, to the remote FTP server. A single FTP reply code is expected in return. Quote is identical to literal.Syntax: quote argument [ ...]

Parameter(s):
argument – Specifies the argument to send to the FTP server.

recv

Copies a remote file to the local computer using the current file transfer type. Recv is identical to get.Syntax: recv remote-file [local-file]

Parameter(s):
remote-file – Specifies the remote file to copy.
local-file – Specifies the name to use on the local computer. If not specified, the file is given the remote-file name.

remotehelp

Displays help for remote commands.Syntax: remotehelp [command]

Parameter(s):
command – Specifies the name of the command about which you want help. If command is not specified, ftp displays a list of all remote commands.

rename

Renames remote files.Syntax: rename filename newfilename

Parameter(s):
filename – Specifies the file you want to rename.
newfilename – Specifies the new filename.

rmdir

Deletes a remote directory.Syntax: rmdir directory

Parameter(s):
directory – Specifies the name of the remote directory to delete.

send

Copies a local file to the remote computer using the current file transfer type. Send is identical to put.Syntax: send local-file [remote-file]

Parameter(s):
local-file – Specifies the local file to copy.
remote-file – Specifies the name to use on the remote computer. If not specified, the file is given the local-file name.

status

Displays the current status of FTP connections and toggles.Syntax: status

trace

Toggles packet tracing; trace displays the route of each packet when running an ftp command.Syntax: trace

type

Sets or displays the file transfer type.Syntax: type [type-name]

Parameter(s):
type-name – Specifies the file transfer type; the default is ASCII. If type-name is not specified, the current type is displayed.

Note
FTP supports two file transfer types, ASCII and binary image.

ASCII should be used when transferring text files. In ASCII mode, character conversions to and from the network standard character set are performed. For example, end-of-line characters are converted as necessary, based on the destination’s operating system.

Binary should be used when transferring executable files. In binary mode, the file is moved byte-by-byte.

user

Specifes a user to the remote computer.Syntax: user user-name [password] [account]

Parameter(s):
user-name – Specifies a user name with which to log in to the remote computer.
password – Specifies the password for user-name. If not specified, but required, ftp prompts for the password.
account – Specifies an account with which to log on to the remote computer. If account is not specified, but required, ftp prompts for the account.

verbose

Toggles verbose mode. If on, all ftp responses are displayed; when a file transfer completes, statistics regarding the efficiency of the transfer are also displayed. By default, verbose is on.