To do this, follow these steps:
|
a. |
Click Start, point to Control Panel, and then click Add/Remove Programs. |
|
b. |
Click Add/Remove Windows Components. |
|
c. |
In the Windows Components list, double-click Networking Services. |
|
d. |
Click to select the Domain Name System (DNS) check box, and then click OK. |
|
e. |
Click Next, and then click Finish. |
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
|
1. |
Click the Start button, click Run, type DCPROMO, and then click OK. |
|
2. |
When the Active Directory Installation Wizard appears, click Next to begin the installation. |
|
3. |
After reviewing the Operating System Compatibility information, click Next. |
|
4. |
Select Domain controller for a new domain (default), and then click Next. |
|
5. |
Select Domain in a new forest (default), and then click Next. |
|
6. |
For Full DNS name, type contoso.com, and then click Next. (This represents a Fully Qualified name.) |
|
7. |
Click Next to accept the default Domain NetBIOS name of CONTOSO. (NetBIOS names provides for down-level compatibility.) |
|
8. |
On the Database and Log Folders screen, point the Active Directory Log Folder to L:\Windows\NTDS, and then click Next to continue. |
|
9. |
Leave the default folder location for Shared System Volume, and then click Next. |
|
10. |
On the DNS Registration Diagnostics screen, click Install and configure the DNS server on this computer. Click Next to continue. |
|
11. |
Select Permissions compatible only with Windows 2000 or Windows Server 2003 (default), and then click Next. |
|
12. |
Type password for Restore Mode Password and Confirm password, and then click Next to continue. Note: Production environments should employ complex passwords for Directory Services Restore passwords.
<!–[if gte vml 1]> <![endif]–><!–[if !vml]–> |
|
13. |
Figure 3 represents a summary of the Active Directory installation options. Click Next to start the installation of Active Directory. If prompted, insert the Windows Server 2003 installation CD. |
|
14. |
Click OK to acknowledge the warning of having a dynamically assigned IP address for a DNS server. |
|
15. |
If you have more than one network interface, select the 10.0.0.0 network interface from the Choose Connection drop-down list, and then click Properties. |
|
16. |
Under the This connection uses the following items section, click Internet Protocol (TCP/IP), and then click Properties. |
|
17. |
Select Use the following IP address, and then type 10.0.0.2 for the IP address. Press the Tab key twice, and then type 10.0.0.1 for the Default gateway. Type 127.0.0.1 for the Preferred DNS server, and then click OK. Click Close to continue. |
|
18. |
Click Finish once the Active Directory Installation Wizard is finished. |
|
19. |
Click Restart Now to reboot the computer |
To create OUs and Security Groups
|
1. |
Click the Start button, point to All Programs, point to Administrative Tools, and then click Active Directory Users and Computers. |
|
2. |
Click the + next to contoso.com to expand it. Click contoso.com itself to show its contents in the right pane. |
|
3. |
In the left pane, right-click contoso.com, point to New, and then click Organizational Unit. |
|
4. |
Type Accounts in the name box, and then click OK. |
|
5. |
Repeat steps 3 and 4 to create the Groups and Resources OUs. |
|
6. |
Click Accounts in the left pane. Its contents now display in the right pane. (It is empty at the beginning of this procedure.) |
|
7. |
Right-click Accounts, point to New, and then click Organizational Unit. |
|
8. |
Type Headquarters, and then click OK. |
|
9. |
Repeat steps 7 and 8 to create the Production and Marketing OUs in Accounts. When you have finished, the OU structure should look like Figure 5.
<!–[if gte vml 1]> <![endif]–><!–[if !vml]–> Figure 5. Creating Organizational Units |
|
10. |
In the same way, create Desktops, Laptops, and Servers in the Resources OU. |
|
11. |
Create the two security groups by right-clicking Groups, pointing to New, and then clicking Group. The two groups to add are Management and Non-management. The settings for each group should be Global and Security. Click OK to create each group. When all steps are completed, the final OU structure should look like Figure 6.
Figure 6. Final OU Structure |
Creating User Accounts
To create a user account
|
1. |
In the left-hand pane, click Headquarters (in Accounts).. Its contents now display in the right pane. (It is empty at the beginning of this procedure.) |
|
2. |
Right-click Headquarters, point to New, and then click User. |
|
3. |
Type Christine for the first name and Koch for the last name. (Note that the full name automatically appears in the Full name box.) |
|
4. |
Type Christine for the User logon name. The window should look like Figure 7. <!–[if gte vml 1]> <![endif]–><!–[if !vml]–>
Figure 7. Adding a User |
Wi-Fi, which stands wireless fidelity, in a play on the older term Hi-Fi, is a wireless networking technology used across the globe. Wi-Fi refers to any system that uses the 802.11 standard, which was developed by the Institute of Electrical and Electronics Engineers (IEEE) and released in 1997. The term Wi-Fi, which is alternatively spelled
In a Wi-Fi network, computers with wifi network cards connect wirelessly to a wireless router. The router is connected to the Internet by means of a modem, typically a cable or DSL modem. Any user within 200 feet or so (about 61 meters) of the access point can then connect to the Internet, though for good transfer rates, distances of 100 feet (30.5 meters) or less are more common. Retailers also sell wireless signal boosters that extend the range of a wireless network.
Wifi networks can either be “open”, such that anyone can use them, or “closed”, in which case a password is needed. An area blanketed in wireless access is often called a wireless hotspot. There are efforts underway to turn entire cities, such as
Wifi technology uses radio for communication, typically operating at a frequency of 2.4GHz. Electronics that are “WiFi Certified” are guaranteed to interoperate with each other regardless of brand. Wifi is technology designed to cater to the lightweight computing systems of the future, which are mobile and designed to consume minimal power. PDAs, laptops, and various accessories are designed to be wifi-compatible. There are even phones under development that would switch seamlessly from cellular networks to wifi networks without dropping a call.
New wifi technologies will extend range from 300 feet (91.5 meters) to 600 feet (183 meters) and beyond, while boosting data transfer rates. Most new laptops nowadays come equipped with internal wireless networking cards.
This step-by-step article describes how to install and configure a File Transfer Protocol (FTP) server for anonymous access.
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.
|
1. |
Click Start, point to Control Panel, and then click Add or Remove Programs. |
|
2. |
Click Add/Remove Windows Components. |
|
3. |
In the Components list, click Application Server, click Internet Information Services (IIS) (but do not select or clear the check box), and then click Details. |
|
4. |
Click to select the following check boxes (if they are not already selected): Common Files |
|
5. |
Click to select the check boxes next to any other IIS-related service or subcomponent that you want to install, and then click OK. |
|
6. |
Click Next. |
|
7. |
When you are prompted, insert the Windows Server 2003 CD-ROM into the computer’s CD-ROM or DVD-ROM drive or provide a path to the location of the files, and then click OK. |
|
8. |
Click Finish. |
IIS and the FTP service are now installed. You must configure the FTP Service before you can use it.
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.
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.
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.
Toggles a bell to ring after each file transfer command is completed. By default, the bell is off.
Syntax: bell
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.
Ends the FTP session with the remote computer and exits ftp.
Syntax: bye
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.
Ends the FTP session with the remote server and returns to the command interpreter.
Syntax: close
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
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.
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.
Disconnects from the remote computer, retaining the ftp prompt.
Syntax: disconnect
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.
Toggles filename globbing. Globbing permits use of wildcard characters in local file or path names. By default, globbing is on.
Syntax: glob
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
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.
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.
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.
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.
Deletes one or more files on a remote computer.
Syntax: mdelete remote-files [ …]
Parameter(s):
remote-files – Specifies the remote files to delete.
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.
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.
Creates a remote directory.
Syntax: mkdir directory
Parameter(s):
directory – Specifies the name of the new remote directory.
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.
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.
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.
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
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.
Displays the current directory on the remote computer.
Syntax: pwd
Ends the FTP session with the remote computer and exits ftp.
Syntax: quit
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.
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.
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.
Renames remote files.
Syntax: rename filename newfilename
Parameter(s):
filename – Specifies the file you want to rename.
newfilename – Specifies the new filename.
Deletes a remote directory.
Syntax: rmdir directory
Parameter(s):
directory – Specifies the name of the remote directory to delete.
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.
Displays the current status of FTP connections and toggles.
Syntax: status
Toggles packet tracing; trace displays the route of each packet when running an ftp command.
Syntax: trace
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.
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.
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.
Syntax: verbose
Client commands
<!–[if !supportLists]–>· <!–[endif]–>! – Runs the specified command on the local computer
<!–[if !supportLists]–>· <!–[endif]–>? – Displays descriptions for ftp commands
<!–[if !supportLists]–>· <!–[endif]–>append – Appends a local file to a file on the remote computer
<!–[if !supportLists]–>· <!–[endif]–>ascii – Sets the file transfer type to ASCII, the default
<!–[if !supportLists]–>· <!–[endif]–>bell – Toggles a bell to ring after each file transfer command is completed (default = OFF)
<!–[if !supportLists]–>· <!–[endif]–>binary – Sets the file transfer type to binary
<!–[if !supportLists]–>· <!–[endif]–>bye – Ends the FTP session and exits ftp
<!–[if !supportLists]–>· <!–[endif]–>cd – Changes the working directory on the remote computer
<!–[if !supportLists]–>· <!–[endif]–>close – Ends the FTP session and returns to the command interpreter
<!–[if !supportLists]–>· <!–[endif]–>debug – Toggles debugging (default = OFF)
<!–[if !supportLists]–>· <!–[endif]–>delete – Deletes a single file on a remote computer
<!–[if !supportLists]–>· <!–[endif]–>dir – Displays a list of a remote directory’s files and subdirectories
<!–[if !supportLists]–>· <!–[endif]–>disconnect – Disconnects from the remote computer, retaining the ftp prompt
<!–[if !supportLists]–>· <!–[endif]–>get – Copies a single remote file to the local computer
<!–[if !supportLists]–>· <!–[endif]–>glob – Toggles filename globbing (wildcard characters) (default = ON)
<!–[if !supportLists]–>· <!–[endif]–>hash – Toggles hash-sign (#) printing for each data block transferred (default = OFF)
<!–[if !supportLists]–>· <!–[endif]–>help – Displays descriptions for ftp commands
<!–[if !supportLists]–>· <!–[endif]–>lcd – Changes the working directory on the local computer
<!–[if !supportLists]–>· <!–[endif]–>literal – Sends arguments, verbatim, to the remote FTP server
<!–[if !supportLists]–>· <!–[endif]–>ls – Displays an abbreviated list of a remote directory’s files and subdirectories
<!–[if !supportLists]–>· <!–[endif]–>mdelete – Deletes one or more files on a remote computer
<!–[if !supportLists]–>· <!–[endif]–>mdir – Displays a list of a remote directory’s files and subdirectories
<!–[if !supportLists]–>· <!–[endif]–>mget – Copies one or more remote files to the local computer
<!–[if !supportLists]–>· <!–[endif]–>mkdir – Creates a remote directory
<!–[if !supportLists]–>· <!–[endif]–>mls – Displays an abbreviated list of a remote directory’s files and subdirectories
<!–[if !supportLists]–>· <!–[endif]–>mput – Copies one or more local files to the remote computer
<!–[if !supportLists]–>· <!–[endif]–>open – Connects to the specified FTP server
<!–[if !supportLists]–>· <!–[endif]–>prompt – Toggles prompting (default = ON)
<!–[if !supportLists]–>· <!–[endif]–>put – Copies a single local file to the remote computer
<!–[if !supportLists]–>· <!–[endif]–>pwd – Displays the current directory on the remote computer (literally, “print working directory”)
<!–[if !supportLists]–>· <!–[endif]–>quit – Ends the FTP session with the remote computer and exits ftp (same as “bye”)
<!–[if !supportLists]–>· <!–[endif]–>quote – Sends arguments, verbatim, to the remote FTP server (same as “literal”)
<!–[if !supportLists]–>· <!–[endif]–>recv – Copies a remote file to the local computer
<!–[if !supportLists]–>· <!–[endif]–>remotehelp – Displays help for remote commands
<!–[if !supportLists]–>· <!–[endif]–>rename – Renames remote files
<!–[if !supportLists]–>· <!–[endif]–>rmdir – Deletes a remote directory
<!–[if !supportLists]–>· <!–[endif]–>send – Copies a local file to the remote computer (same as “put”)
<!–[if !supportLists]–>· <!–[endif]–>status – Displays the current status of FTP connections
<!–[if !supportLists]–>· <!–[endif]–>trace – Toggles packet tracing (default = OFF)
<!–[if !supportLists]–>· <!–[endif]–>type – Sets or displays the file transfer type (default = ASCII)
<!–[if !supportLists]–>· <!–[endif]–>user – Specifes a user to the remote computer
<!–[if !supportLists]–>· <!–[endif]–>verbose – Toggles verbose mode (default = ON)
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]
Before you can configure the DHCP service, you must install it on the server. DHCP is not installed by default during a typical installation of Windows Standard Server 2003 or Windows Enterprise Server 2003. You can install DHCP either during the initial installation of Windows Server 2003 or after the initial installation is completed.
How to Install the DHCP Service on an Existing Server
|
1. |
Click Start, point to Control Panel, and then click Add or Remove Programs. |
|
2. |
In the Add or Remove Programs dialog box, click Add/Remove Windows Components. |
|
3. |
In the Windows Components Wizard, click Networking Services in the Components list, and then click Details. |
|
4. |
In the Networking Services dialog box, click to select the Dynamic Host Configuration Protocol (DHCP) check box, and then click OK. |
|
5. |
In the Windows Components Wizard, click Next to start Setup. Insert the Windows Server 2003 CD-ROM into the computer’s CD-ROM or DVD-ROM drive if you are prompted to do so. Setup copies the DHCP server and tool files to your computer. |
|
6. |
When Setup is completed, click Finish. |
How to Configure the DHCP Service
After you have installed the DHCP service and started it, you must create a scope, which is a range of valid IP addresses that are available for lease to the DHCP client computers on the network. Microsoft recommends that each DHCP server in your environment have at least one scope that does not overlap with any other DHCP server scope in your environment. In Windows Server 2003, DHCP servers in an Active Directory-based domain must be authorized to prevent rogue DHCP servers from coming online. Any Windows Server 2003 DHCP Server that determines itself to be unauthorized will not manage clients.
How to Create a New Scope
|
1. |
Click Start, point to Programs, point to Administrative Tools, and then click DHCP. |
|
2. |
In the console tree, right-click the DHCP server on which you want to create the new DHCP scope, and then click New Scope. |
|
3. |
In the New Scope Wizard, click Next, and then type a name and description for the scope. This can be any name that you want, but it should be descriptive enough so that you can identify the purpose of the scope on your network (for example, you can use a name such as “Administration Building Client Addresses”). Click Next. |
|
4. |
Type the range of addresses that can be leased as part of this scope (for example, use a range of IP addresses from a starting IP address of 192.168.100.1 to an ending address of 192.168.100.100). Because these addresses are given to clients, they must all be valid addresses for your network and not currently in use. If you want to use a different subnet mask, type the new subnet mask. Click Next. |
|
5. |
Type any IP addresses that you want to exclude from the range that you entered. This includes any addresses in the range described in step 4 that may have already been statically assigned to various computers in your organization. Typically, domain controllers, Web servers, DHCP servers, Domain Name System (DNS) servers, and other servers, have statically assigned IP addresses. Click Next. |
|
6. |
Type the number of days, hours, and minutes before an IP address lease from this scope expires. This determines how long a client can hold a leased address without renewing it. Click Next, and then click Yes, I want to configure these options now to extend the wizard to include settings for the most common DHCP options. Click Next. |
|
7. |
Type the IP address for the default gateway that should be used by clients that obtain an IP address from this scope. Click Add to add the default gateway address in the list, and then click Next. |
|
8. |
If you are using DNS servers on your network, type your organization’s domain name in the Parent domain box. Type the name of your DNS server, and then click Resolve to make sure that your DHCP server can contact the DNS server and determine its address. Click Add to include that server in the list of DNS servers that are assigned to the DHCP clients. Click Next, and then follow the same steps if you are using a Windows Internet Naming Service (WINS) server, by adding its name and IP address. Click Next. |
|
9. |
Click Yes, I want to activate this scope now to activate the scope and allow clients to obtain leases from it, and then click Next. |
|
10. |
Click Finish. |
|
11. |
In the console tree, click the server name, and then click Authorize on the Action menu. |
Troubleshooting
The following sections explain how to troubleshoot some of the issues that you may experience when you try to install and configure a Windows Server 2003-based DHCP server in a workgroup.
Clients Cannot Obtain an IP Address
If a DHCP client does not have a configured IP address, this typically indicates that the client was not able to contact a DHCP server. This can be caused by a network problem, or because the DHCP server is unavailable. If the DHCP server started and other clients can obtain valid addresses, verify that the client has a valid network connection and that all the related client hardware devices (including cables and network adapters) are working properly.
The DHCP Server Is Unavailable
If a DHCP server does not provide leased addresses to clients, it is frequently because the DHCP service did not start. If this is the case, the server may not be authorized to operate on the network. If you were previously able to start the DHCP service, but it has since stopped, use Event Viewer to check the System log for any entries that may explain why you cannot start the DHCP service.
To restart the DHCP service:
|
1. |
Click Start, and then click Run. |
|
2. |
Type cmd, and then press ENTER. |
|
3. |
Type net start dhcpserver, and then press ENTER. |
-or-
|
1. |
Click Start, point to Control Panel, point to Administrative Tools, and then click Computer Management. |
|
2. |
Expand Services and Applications, and then click Services. |
|
3. |
Locate and then double-click DHCP Server. |
|
4. |
Verify that Startup is set to Automatic and that Service Status is set to Started. If not, click Start. |
|
5. |
Click OK, and then close the Computer Management window. |
|
<!–[endif]–>
