Sunday, May 17, 2009

Cisco Certifications...CCVP

CCVP - Cisco Certified Voice Professional

The CCVP certification recognizes the increased importance placed on IT professionals of today who are responsible for integrating voice technology into underlying network architectures. Individuals who earn a CCVP certification can help create a telephony solution that is transparent, scalable, and manageable.

Earning a CCVP certification validates a robust set of skills in implementing, operating, configuring, and troubleshooting a converged IP network.

The certification content focuses on Cisco Unified Communications Manager (formerly Unified CallManager), quality of service (QoS), gateways, gatekeepers, IP phones, voice applications, and utilities on Cisco routers and Cisco Catalyst switches.

There are now two paths that can be taken to achieve CCVP certification

CCVP Recertification:
CCVP certifications are valid for three years. To recertify, pass any 642 exam that is part of the professional level curriculum after 01/01/06, or pass a current CCIE written exam.

Requirement Training and Exam:

CCVP - CallManager 4.x and 5.x
CCVP - Cisco Unified Communications Manager (formerly CallManager) 6.0

Cisco Certifications...CCNP

CCNP - Cisco Certified Network Professional

According to Cisco, "CCNP certification validates a network professional's ability to install, configure and troubleshoot converged local and wide area networks with 100 to 500 or more nodes. Network Professionals who achieve the CCNP have demonstrated the knowledge and skills required to manage the routers and switches that form the network core, as well as edge applications that integrate voice, wireless, and security into the network."
Global Knowledge is proud to have been an integral partner in the development of the updated BSCI and BCMSN courses, and is committed to delivering the most up-to-date curriculum available.

Overview of the courses:

BSCI - Building Scalable Cisco Internetworks v3.0

Develop an advanced set of skills to help you optimize the configuration and deployment of a Cisco router-based internetwork. Learn the complex concepts and commands necessary to configure Cisco routers for scalable operation in large and/or growing internetworks. Whether your goal is to take your Cisco routing skills to the next level or to achieve CCNP or CCIP certification, this is the right course for you.

BCMSN - Building Cisco Multilayer Switched Networks v3.0

Implement campus networks using multilayer switching technologies over high-speed Ethernet and wireless topologies. This course addresses the integration of routing and switching technologies to create an efficient campus network. Design, build, and configure a reliable campus network so that if any physical link, switch, or router fails, an end user won't know, while maintaining the performance to meet today's demanding application requirements, such as voice, video, and secure wireless technologies.

ISCW - Implementing Secure Converged Wide Area Networks

Learn to secure the network environment using existing Cisco IOS security features and configure the three primary components of the Cisco IOS Firewall Feature set (Firewall, Intrusion Prevention System [IPS], and Authentication, Authorization, and Accounting [AAA]). In this task-oriented course, you'll get the knowledge and skills needed to secure Cisco IOS router networks. Expand the reach of your enterprise network to teleworkers and remote sites, and explore implementing a highly available network with connectivity options such as VPN and wireless.

ONT (Optimizing Converged Cisco Networks)

Learn the characteristics of real-time multimedia traffic, such as voice, and you'll investigate the importance of Quality of Service management on the network and learn about the application of wireless technologies to the enterprise. Get an introduction to Cisco's Lightweight Wireless Access Point architecture, and cover such areas as Wireless LAN (WLAN) configuration, QoS for wireless, and wireless security techniques for authentication and data encryption. You will also explore the management of Wireless LAN Controllers across the enterprise using Cisco's Wireless Control System.

CCNP Certification Prep Kit

To better prepare you to achieve your certification, we have bundled all four courses, four Self Test Software vouchers, and four exam vouchers into one high-value package. This bundle is perfect for an individual planning to attend all four courses or four individuals planning to attend one course. Click the link above for complete details.

Exams

Our courses prepare you for the following Cisco exams:

Required Training and Exams:

BSCI - Building Scalable Cisco Internetworks v3.0for 642-901
BCMSN - Building Cisco Multilayer Switched Networks v3.0 for 642-812
ISCW - Implementing Secure Converged Wide Area Networks for 642-825
ONT - Optimizing Converged Cisco Networks for 642-845

Cisco Certifications...CCNA

CCNA - Cisco Certified Network Associate

CCNA certification is a first-level Cisco Career certification and indicates a foundation in and apprentice knowledge of networking. CCNA certification validates the ability to install, configure, operate, and troubleshoot medium-size routed and switched networks, including implementation and verification of connections to remote sites in a WAN.

Cisco has retired their INTRO and ICND courses, replacing them with more robust offerings ICND1 and ICND2, respectively. This new CCNA training curriculum includes basic mitigation of security threats, introduction to wireless networking concepts and terminology, and performance-based skills. The CCNA training curriculum also includes, but is not limited to, the use of IP, Enhanced Interior Gateway Routing Protocol (EIGRP), Serial Line Interface Protocol Frame Relay, Routing Information Protocol Version 2 (RIPv2),VLANs, Ethernet, and access control lists (ACLs).

Our CCNA training courses include enhanced content that exceeds standard authorized Cisco content, expanded lab equipment, and an unrivaled guarantee for CCNA certification success. Our three-step blended learning approach to the CCNA Boot Camp includes a readiness assessment, self-paced e-learning materials, and post-class lab access to maximize your CCNA training experience and ensure that you get comprehensive coverage of the CCNA training materials.

Certification Requirements
Required Exam:
640-822 ICND1 AND
640-816 ICND2 OR
640-802 CCNA

Recommended Training:
ICND1 - Interconnecting Cisco Network Devices 1 For 640-822 ICND1
ICND2 - Interconnecting Cisco Network Devices 2 For 640-816 ICND2
CCNA Boot Camp v2.0 For 640-802 CCNA

Cisco Certifications...CCENT

CCENT - Cisco Certified Entry Network Technician

CCENT - Cisco Certified Entry Network Technician CCENT certification was created to address the need for networking professionals with a solid practical understanding of modern TCP/IP networks built with Cisco hardware, and it verifies practical skills required for entry-level network support positions.
CCENT certification serves as the base of Cisco's certification pyramid, is similar in nature to CompTIA's Network+ Certification, and represents a tangible first step in earning your CCNA certification.

CCENT Training
Achieving CCENT certification is as easy as attending a single course. Attend either ICND1 or the CCENT e-Camp, pass the related exam, and you'll be awarded CCENT certification. With our flexible CCENT training options, validating your skills has never been easier

Certification Requirement
Required Exam: 640-822 ICND1
Recommended Training: ICND1(Interconnecting Cisco Network Devices 1) or CCENT e-Camp

Install and Configure Virtual Private Netwok (VPN)

How to install and Turn on a VPN Server:
To install and turn on a VPN server, follow these steps:
1. Click Start, point to Administrative Tools,
and then click Routing and Remote Access.

2. Click the server icon that matches the local server name in the left pane of
the console. If the icon has a red circle in the lower-left corner, the Routing
and Remote Access service has not been turned on. If the icon has a green arrow
pointing up in the lower-left corner, the Routing and Remote Access service has
been turned on. If the Routing and Remote Access service was previously turn on,
you may want to reconfigure the server. To reconfigure the server:

a) Right-click the server object, and then click
Disable Routing and Remote Access
. Click Yes to
continue when you are prompted with an informational message.


b) Right-click the server icon, and then click
Configure and Enable Routing and Remote Access
to start the Routing and
Remote Access Server Setup Wizard. Click Next to continue.


c) Click Remote access (dial-up or VPN) to
turn on remote computers to dial in or connect to this network through the
Internet. Click Next to continue.


3. Click to select VPN or Dial-up depending on
the role that you intend to assign to this server.

4. In the VPN Connection window, click the network interface which is connected
to the Internet, and then click Next.

5. In the IP Address Assignment window, click
Automatically
if a DHCP server will be used to assign addresses to
remote clients, or click From a specified range of
addresses
if remote clients must only be given an address from a
pre-defined pool. In most cases, the DHCP option is simpler to administer.
However, if DHCP is not available, you must specify a range of static addresses.
Click Next to continue.

6. If you clicked From a specified range of addresses, the Address Range Assignment dialog box opens. Click New. Type the first IP address in the range of addresses that you want to use in the Start IP address box. Type the last IP address in the range in the End IP address box. Windows calculates the number of addresses automatically. Click OK to return to the Address Range Assignment window. Click Next to continue.

7. Accept the default setting of No, use Routing and
Remote Access to authenticate connection requests
, and then click
Next to continue. Click Finish to turn on the
Routing and Remote Access service and to configure the server as a Remote Access
server.

How to Configure the VPN Server:

To continue to configure the VPN server as required, follow these steps.

How to Configure the Remote Access Server as a Router:

For the remote access server to forward traffic properly inside your network,
you must configure it as a router with either static routes or routing
protocols, so that all of the locations in the intranet are reachable from the
remote access server.

To configure the server as a router:

1. Click Start, point to Administrative Tools,
and then click Routing and Remote Access.

2. Right-click the server name, and then click Properties.

3. Click the General tab, and then click to select
Router
under Enable this computer as a.

4. Click LAN and demand-dial routing, and then
click OK to close the Properties dialog box.

How to Modify the Number of Simultaneous Connections:

The number of dial-up modem connections is dependent on the number of modems
that are installed on the server. For example, if you have only one modem
installed on the server, you can have only one modem connection at a time.

The number of dial-up VPN connections is dependent on the number of simultaneous
users whom you want to permit. By default, when you run the procedure described
in this article, you permit 128 connections. To change the number of simultaneous connections, follow these steps:

1. Click Start, point to Administrative Tools,
and then click Routing and Remote Access.

2. Double-click the server object, right-click Ports, and then
click Properties.

3. In the Ports Properties dialog box, click WAN
Miniport (PPTP)
, and then click Configure.

4. In the Maximum ports box, type the number of VPN connections
that you want to permit.

5. Click OK, click OK again, and then close
Routing and Remote Access.

How to Manage Addresses and Name Servers:

The VPN server must have IP addresses available to assign them to the VPN
server's virtual interface and to VPN clients during the IP Control Protocol (IPCP)
negotiation phase of the connection process. The IP address assigned to the VPN
client is assigned to the virtual interface of the VPN client.

For Windows Server 2003-based VPN servers, the IP addresses assigned to VPN
clients are obtained through DHCP by default. You can also configure a static IP
address pool. The VPN server must also be configured with name resolution
servers, typically DNS and WINS server addresses, to assign to the VPN client
during IPCP negotiation.

How to Manage Access

Configure the dial-in properties on user accounts and remote access policies to
manage access for dial-up networking and VPN connections.
NOTE: By default, users are denied access to dial-up
networking.

Access by User Account:

To grant dial-in access to a user account if you are managing remote access on a
user basis, follow these steps:

1. Click Start, point to Administrative Tools,
and then click Active Directory Users and computers.

2. Right-click the user account, and then click Properties.

3. Click the Dial-in tab.

4. Click Allow access to grant the user permission to dial in. Click OK.

Access by Group Membership:

If you manage remote access on a group basis, follow these steps:

1. Create a group with members who are permitted to create VPN connections.

2. Click Start, point to Administrative Tools,
and then click Routing and Remote Access.

3. In the console tree, expand Routing and Remote Access, expand the server name, and then click Remote Access Policies.

4. Right-click anywhere in the right pane, point to New, and
then click Remote Access Policy.

5. Click Next, type the policy name, and then click
Next
.

6. Click VPN for Virtual Private Access access method, or click
Dial-up for dial-up access, and then click Next.

7. Click Add, type the name of the group that you created in
step 1, and then click Next.

8. Follow the on-screen instructions to complete the wizard.

If the VPN server already permits dial-up networking remote access services, do
not delete the default policy. Instead, move it so that it is the last policy to
be evaluated.

How to Configure a VPN Connection from a Client Computer:

To set up a connection to a VPN, follow these steps. To set up a client for
virtual private network access, follow these steps on the client workstation:
NOTE: You must be logged on as a member of the Administrators
group to follow these steps.

NOTE: Because there are several versions of Microsoft Windows,
the following steps may be different on your computer. If they are, see your
product documentation to complete these steps.

1. On the client computer, confirm that the connection to the Internet is
correctly configured.

2. Click Start, click Control Panel, and then
click Network Connections. Click Create
a new connection
under Network Tasks, and then click
Next.

3. Click Connect to the network at my workplace
to create the dial-up connection. Click Next to continue.

4. Click Virtual Private Network connection, and
then click Next.

5. Type a descriptive name for this connection in the Company name
dialog box, and then click Next.

6. Click Do not dial the initial connection if the computer is
permanently connected to the Internet. If the computer connects to the Internet
through an Internet Service Provider (ISP), click
Automatically dial this initial connection
, and then click the name of
the connection to the ISP. Click Next.

7. Type the IP address or the host name of the VPN server computer (for example,
VPNServer.SampleDomain.com).

8. Click Anyone's use if you want to permit any
user who logs on to the workstation to have access to this dial-up connection.
Click My use only if you want this connection to
be available only to the currently logged-on user. Click Next.

9. Click Finish to save the connection.

10.Click Start, click Control Panel, and then
click Network Connections.

11. Double-click the new connection.

12. Click Properties to continue to configure options for the
connection. To continue to configure options for the connection, follow these
steps:
a) If you are connecting to a domain, click the Options
tab, and then click to select the Include Windows logon
domain
check box to specify whether to request Windows Server 2003
logon domain information before trying to connect.


b) If you want the connection to be redialed if the line is dropped, click
the Options tab, and then click to select the
Redial if line is dropped check box.


To use the connection, follow these steps:

1. Click Start, point to Connect to, and then click the new connection.

2. If you do not currently have a connection to the Internet, Windows offers to
connect to the Internet.

3. When the connection to the Internet is made, the VPN server prompts you for
your user name and password. Type your user name and password, and then click
Connect.

Your network resources must be available to you in the same way they are when
you connect directly to the network.NOTE: To disconnect from
the VPN, right-click the connection icon, and then click Disconnect

Sunday, May 3, 2009

Install and configure Logging Agent

Install and configure Logging Agent

To install and configure Logging Agent


1. Click Start, point to
Administrative Tools
, and then click Server Manager.

2. In the console tree, expand Roles, right-click
Streaming Media Services
, and then click Add Role services.

The Add Role Services Wizard starts.

3. In the Add Role Services Wizard, on the Select Role Services
page, select the Logging Agent role service, and then complete
the wizard.
During installation, a message informs you that this role service requires additional role services. Click Add Required Role Services to
close the message and continue with the installation.
The Multicast and Advertisement Logging Agent ISAPI logging extension Wmsiislog.dll)
is copied into the following directory:
%systemdrive%\WMPub\WMIISlog
The ISAPI logging extension properties are set in the registry. For more
information about how to configure these settings,

4. Add a virtual directory that references %systemdrive%\WMPub\WMIISlog
and grant the ISAPI logging extension (Wmsiislog.dll) executable permissions on
the virtual root. For more information, see Internet Information Services (IIS)
Manager Help.

5. In the Windows Media Services snap-in, click the broadcast publishing point
for which you want to log multicast information. If it is started, stop the
publishing point.

6. On the Properties tab for the publishing point, in
Category
, click Multicast streaming.

7. In Plug-in, click WMS Multicast Data Writer,
and then click Properties.

8. On the Advanced tab, in Logging URL, type
the URL of ISAPI logging extension (Wmsiislog.dll) on the Web server, for
example:

http://
web_server_name/virtual_directory_name/wmsiislog.dll


9. Click OK to apply the new setting to
the plug-in.

10. In the details pane, click the Enable button.

11. Run the Multicast Announcement Wizard to update the multicast information
file (a file that has an .nsc file name extension) for the broadcast publishing
point.

Terminal Services

Terminal Services Role

Terminal services is Microsoft's thin client solution. The Windows 2003 server does all the processing, and the clients connect from a machine which essentially becomes a dumb terminal. Terminal Services is built into Windows Server 2003, it is not a separate product as it was in NT 4.0. However it lies dormant and you need to install it thought the Add or Remove Programs / Windows Components. You will also need to install Terminal Service Licensing on one of your servers. Check out special group for Terminal Server Licencing in Built-in folder of Active Directory Users and Computers.
The main question is which mode will you run terminal? Remote Desktop for Administration or Application mode.
When you install the programs for Terminal Services check out - special 'Transforms' method. 32 Bit programs should be o.k. Also search websites for scripts to make any non Microsoft applications operate in multi session mode.
Group Policy. There are Group Policies just for Terminal services, e.g. Do not let users accidentally Shut Down the terminal server when they think they are shutting down their own machine!
Permissions. By default every user can access a terminal server, perhaps you wish to change this.

Mail Server

Mail Server Role:

Mail servers benefit from being on their own server, separate from domain controllers and separate from database servers like SQL. Your checklist should include: Authentication DNS (MX) record Site Connectors, SMTP connectors SMTP service, SMTP virtual server object POP3 and IMAP server objects Fire Wall Configuring Mailboxes OWA (Outlook web access) (Client's Outlook).

Application Server:

Application Server Role:

The sort of applications that I mean are database, e.g. SQL or web e.g. IIS.

There is rarely any advantage in installing Active Directory on Application servers, and often this combination creates problems as Active Directory and application services fight for resources or control of components. So install Application servers on their own member server.

Authentication is important for all server roles, but fail to tie down permissions on an application server and you could get sensitive company information being made available to everyone. Failure to control security could also invite hackers to attacking your data. So, delve into all aspects of security on your database servers. There are extra hardware considerations for your application server. Pamper your database 'crown jewels' with hardware RAID. Get a trial of clustering. Clustering is technically interesting, is the way of the future and it will take reliability to another level. Convince who ever holds the purse strings that the greater availability and less downtime will pay for clustering.

Install and Configure File and Print Server


Install File and Printer Sharing:
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:

1. Click Start, point to Administrative Tools,
and then click Configure Your Server Wizard.

2. Click Next.

3. Click Next.

4. Click File server in the
Server role box, and then click Next.

5. On the "File Server Disk Quotas" page, configure any quotas you need to
control disk-space usage on the server, and then click Next.

6. On the "File Server Indexing Service" page, click the indexing configuration that is appropriate for your server, and then click Next.

7. Click Next.

8. Click Finish.

9. The Share a Folder Wizard starts. Click Next.

10. Click Browse, locate the folder that you want to share, and then click OK.

11. Click Next.

12. Type a share name for the folder, and then click Next.

13. Click one of the basic permissions for the folder, or click
Customize
to set custom permissions on the folder. Click Finish.

14. Click Close.

How to Manually Install a File Server on Windows Server 2003:

1. Click Start, and then click Windows Explorer.

2. Locate the folder that you want to share.

3. Right-click the folder, and then click Sharing and Security.

4. Click Share this folder, and then accept the
default name or type a different name for the share.

5. Optionally, configure the number of users who can connect, configure permissions for this folder, and then configure the caching options.

6. Click OK.

7. A little hand is displayed in the Windows Explorer window to indicate that the folder is being shared.

8. Quit Windows Explorer.

Install a Windows Server 2003 Print Server:

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

1. Click Start, point to Administrative Tools,
and then click Configure Your Server Wizard.

2. Click Next.

3. Click Next.

4. Click Print server in the Server role box, and then click Next.

5. On the "Printers and Printer Drivers" page, click the types of Windows
clients that your print server will support, and then click Next.

6. Click Next.

7. On the "Add Printer Wizard Welcome" page, click Next.

8. Click Local printer attached to this computer,
click to clear the Automatically detect and install my
Plug and Play printer
check box, and then click Next.

9. Click the port for your printer, and then click Next.

10. Click the printer make and model or provide the drivers from the printer manufacturer media, and then click Next.

NOTE: If you are prompted to keep or not keep your existing printer driver, either keep the existing driver or replace the existing driver. If you replace the driver, you must provide the manufacturer driver for this printer. Click Next to continue.

11. Accept the default name of the printer or provide a different name, and then
click Next.

12. Click the Share as option, type the share
name, and then click Next.

NOTE: This step is optional because you can share the printer later.

13. You may provide the location of the printer and a comment to make it easier to locate. Click Next to continue.

14. Click the Print a test page option, click
Next, and then click Finish to quit the Add Printer Wizard. Your printer appears in the Printers and Faxes folder.

How to Share a Printer:

1. Click Start, and then click Printers and Faxes.

2. Right-click the printer that you just installed, and then click
Sharing
.

3. Click Share this printer, and then type a
share name for the printer.

4. Optionally, click Additional Drivers, click the operating
systems of the client computers that may attach to this printer, and then click
OK. By adding drivers for these operating systems, users on
client computers can connect to the print server and automatically download the
appropriate drivers for this model of printer without having to configure
anything.

5. When you are prompted to do so, insert the Windows Server 2003 CD-ROM.

6. Click OK to close the printer properties.

7. Close the Printers and Faxes folder.

How to Manually Install a Print Server on Windows Server 2003:

1. Click Start, point to Settings, and then
click Printers.

2. Double-click Add Printer to start the Add Printer Wizard.

3. To complete the Add Printer Wizard, repeat steps 7 through 14 in the "Install a Windows Server 2003 Print Server" section of this article.
NOTE: The only difference between the manual installation of
the print server and the use of the Configure Your Server Wizard to create the
print server is how you start the Add Printer Wizard.

Configuring the DHCP Service

Configuring the DHCP Service:

After you install and start the DHCP service, you must create a scope (a range
of valid IP addresses that are available for lease to the DHCP clients). Each
DHCP server in your environment should have at least one scope that does not
overlap with any other DHCP server scope in your environment. In Windows 2003,
DHCP servers within an Active Directory domain environment must be authorized to
prevent rogue DHCP servers from coming online and authorizing a DHCP Server.

When you install and configure the DHCP service on a domain controller, the
server is typically authorized the first time that you add the server to the
DHCP console. However, when you install and configure the DHCP service on a
member server, you need to authorize the DHCP server.

Note A stand-alone DHCP server cannot be authorized against an
existing Windows Active Directory.

To authorize a DHCP server:

1. click Start, click Programs, click
Administrative Tools
, and then click DHCP.

Note You must be logged on to the server with an account that
is a member of the Enterprise Administrators group.

2. In the console tree of the DHCP snap-in, select the new DHCP server. If there
is a red arrow in the bottom-right corner of the server object, the server has
not yet been authorized.

3. Right-click the server, and then click Authorize.

4. After a few moments, right-click the server again and then click
Refresh
. The server should display a green arrow in the bottom-right
corner to indicate that the server has been authorized.

To create a new scope:

1. Click Start, click Programs, point to
Administrative Tools, and then click DHCP.
Note In the console tree, select the DHCP server on which you
want to create the new DHCP scope.

2. Right-click the server, and then click New Scope. In the New
Scope Wizard, click Next, and then type a name and description
for the scope. This can be any name that you choose, but it should be
descriptive enough to identify the purpose of the scope on your network. For
example, you might use Administration Building Client Addresses.

3. Type the range of addresses that can be leased as part of this scope, for
example, 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 should 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.

4. Type any IP addresses that you want to exclude from the range you entered.
This includes any addresses that may have already been statically assigned to
various computers in your organization. Click Next.

5. Type the number of days, hours, and minutes before an IP address lease from
this scope expires. This determines the length of time that a client can hold a
leased address without renewing it. Click Next to select
Yes, I want to configure these options now, and then extend the
wizard to include settings for the most common DHCP options. Click Next.

6. 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 place
the default gateway address into the list, and then click Next.

Note When DNS servers already exist on your network, type your
organization's domain name in Parent domain. Type the name of
your DNS server, and then click Resolve to ensure that your
DHCP server can contact the DNS server and determine its address. Then click
Add to include that server in the list of DNS servers that are
assigned to the DHCP clients. Click Next.

7. 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
. Click Finish.

Troubleshooting:

Clients are unable to obtain an IP address
If a DHCP client does not have a configured IP address, it generally means that
the client has not been able to contact a DHCP server. This is either because of
a network problem or because the DHCP server is unavailable. If the DHCP server
has started and other clients have been able to obtain a valid address, verify
that the client has a valid network connection and that all related client
hardware devices (including cables and network adapters) are working properly.

The DHCP server is unavailable
When a DHCP server does not provide leased addresses to clients, it is often
because the DHCP service has failed to start. If this is the case, the server
may not have been 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 the cause.

Note To restart the DHCP service, click Start,
click Run, type cmd, and then press ENTER.
Type net start dhcpserver, and then press ENTER.