Showing posts with label Certification. Show all posts
Showing posts with label Certification. Show all posts

Saturday, November 13, 2010

10 practice questions for Microsoft MCSA Certification Exam - 70-291

Implement, manage and maintain a Server 2003 Network Infrastructure

After studying the text books is important to test your new knowledge and how well they absorbed the material shown. Practice Exams ....

* Reinforces what you've learned - the gaps of what you missed
* Gets you used to answer questions to build confidence and familiarity

Here are 10 multiple choice questions for practice examsto:

______________________________

Question # 1 - You have to return implemented a remote access server for receiving requests from incoming connections. Lately there has been receiving complaints that some compounds have been fired without just cause and connections are very slow. The implementation of a different remote server, but this does not help the situation, even if the number of complaints reduced by 25%.

What should I do?

A. Completed 2S remote server instead of just one

B. Since the reduction of symptoms by 25% with the addition of a remote access server, you need a total of 4 servers on a complaint reduced by 100%

C. Implementing a RADIUS server that takes responsibility for authenticating access to the remote server

D. Implementing IIS server

_____________________

Question # 2 - You are on the SOA (Start of Authority) tab of the DNS server on which you want to configure DNS1The zone transfer to another DNS server DNS2 once every 8 hours. Which of the following will help you transfer you to configure the DNS zone between the two servers?

A. Update Interval
B. Attempts Again
C. Retry Interval
D. Decay

_____________________

Question # 3 - When you press software updates for all clients on the network from a designated server, which of the following Group Policy settings shouldconfigured?

A. Audit Object Access setting
B. Specify the location of the service intranet Microsoft update
C. Give the location of Internet services from Microsoft Update
D. Auto Update Settings

_____________________

Question # 4 - You've just created a number of DNS zones in the network. To the extent that you have a DNS primary and secondary DNS. The response was very smooth and without problems. You want the zone transfer and updates on the network isas smooth after the areas have been created.

What should I do?

A. Make sure all areas are integrated into Active Directory

B. Make sure that all DNS servers running on domain controllers

C. Make sure that all DNS servers running on member servers

D. Avoid the use of areas

_____________________

Question # 5 - You are required to an institution by the previous management, to change the IPSec policy. Which of theHe would later use to manage this?

A. IP Security Monitor Console
B. Microsoft Management Console
C. Network Monitor Tool
D. IPSec Tools

_____________________

Question # 6 - You are required to change certain security based on existing network to be applied. Which of the following would you use to analyze what exists and what needs to be applied?

A. Microsoft Baseline Security Analyzer
B. IP Security MonitorConsole
C. Network Monitor
D. basic setting up Group Policy

_____________________

Question # 7 - You want to keep track of your DNS server database by date and free of unnecessary documents. Which of the following will help to maintain the DNS database as required?

A. Tombstone
B. Aging and Disposal
C. DDNS
D. Secure Updates

_____________________

Question # 8 - The network consists of a single domain with aWindows Server 2003 DNS. The DNS server hosts a standard primary zone. Users report that the response time for the network seems slow. Using Network Monitor to examine network traffic, you will find that there is an abnormal amount of traffic between the DNS client and DNS server.

What better tool could help you learn the cause of the excess traffic?

A. System Monitor
B. Registers
C. Tracert
D. SecurityMonitor

_____________________

Question # 9 - You are about to expand its network of remote access if your company is fast gaining small businesses around the world.

The policy of the Company's written that all remote access server are the same security settings. If changes are made to this policy in writing or otherwise to be given to all servers at once to ensure that the administrative time for the above activitiesminimized. What should I do?

A. The use of RADIUS
B. Use RRAS
C. Using IIS
D. Use a server certificate

_____________________

Question # 10 - You must configure the updates for your network. The network consists of 100 Windows Server 2003 domain controllers and 48 Windows 2003 server. There are about 2500 clients. Which of the following would be an ideal and efficient method for implementing an automated process for software updates?

Each instruction selectionpresents a part of the solution. Choose two explanations come to a complete solution

A. Configuring Software Update Services (SUS), together with Group Policy Objects (GPO).

B. Configuring Automatic Updates on all domain controllers and clients

C. Configure Automatic Updates on the Root DC and the rest do not connect to the Internet at all

D. Do only the critical DC connect to the Microsoft site for updates and a designated server pushes the update torest of the computer network

_____________________

ANSWERS

Question # 1 - correct answers: C
Question # 2 - correct answers: A
Question # 3 - correct answers: B
Question 4 # - correct answers: A
Question # 5 - correct answers: A
Question # 6 - correct answers: A
Question # 7 - correct answers: B
Question # 8 - correct answers: A
Question # 9 - correct answers: A
Question # 10 - correct answers: A, D

My Links : Cool Phones Review Switch Hub Store. LOWER Prices in The Same Item, Rosetta Stone Store LOWER Prices in The Same Item

Friday, November 5, 2010

CompTIA Network + Certification Exam Tutorial: DHCP and DHCP relay agents

CompTIA Network + exam as a candidate, you're probably familiar with DHCP - but just in case, here we will review bases DHCP, and then a discussion of DHCP relay agents to go.

When it comes to assign an IP address of all PCs in our network, along with their network masks, DNS server location, and more, we have two choices on how to do it:

Or go to each workstation and statically configure the workstation

Or go to each workstation andall set to use DHCP

What we have here is the classic argument "static vs. dynamic". I do not want you think I'm lazy, but it will be a dynamic way of doing things almost every break.

One might ask why it matters, because both methods include a visit to every workstation. You're right about this, and although it's much faster to configure a workstation to mask gets its IP address from a DHCP server and then configure the IP address and the entirestatic form, the real benefits come when the network changes.

And from me - the network will change. The hosts clear, add the host, and if the previous operation did not plan for future growth, the day may come when you have the numbering system for IP network for change. The choice was originally between the static and DHCP configuration will determine how easy the change will come.

o If the network is statically configured, younow every workplace and their IP address to the new regime to change.

o If the network with DHCP, you only need to change the pattern of the network on the DHCP server and allow the workstations to get their new addresses dynamically.

Believe me, I run IP address changes, both in fashion and I assume DHCP every time! Avoid static IP address assignments also cuts the likelihood that the two machines on your network are assigned the same IPaddress.

As host gets an IP address via DHCP is not a permanent part of the host. The address is actually leased from a DHCP server. We walk through the DHCP process from the point of view the array of view.

The primary DHCP client boots and sends a DHCP Discover packet on the network. The landlord does to "discover" a DHCP server or servers. Explore this packet is a transmission of a Layer 3 IP destination address is255.255.255.255.

Each package includes a DHCP server responds with this broadcast a DHCP server, and is an IP address and a mask that is offered. The proposal also includes a subnet mask DHCP, the IP address from the DHCP server sending the response and how long the host can) keep this address (the DHCP lease time.

If multiple DHCP servers happen to hear this broadcast, each have an IP address.

The DHCP client to accept the first offer isreceives. It does this by sending another broadcast a DHCP request packet.

The server that the DHCP server offer is accepted, it will send an acknowledgment DHCP, DNS, which contains the rest of the information that the host to the demands of work, including the location of one. The DHCP server pool made the offer was not accepted, it returns the IP address offered to its range of assignable addresses, the address.

I made several referencesIn this chapter on DHCP packets are broadcast. Remember that the device forwards broadcast network connectivity? That's right, it's our old friend, the router!

If a PC is on one side of the DHCP server and router is on the other hand, we have a problem. The first is a broadcast DHCP Discover packet, and sends the router does not broadcast to the DHCP server. Fortunately, this does not mean that we all need a DHCP serversubnet in the network, because we can configure the router as a DHCP relay agent.

A DHCP Relay Agent DHCP server DHCP requests to send. You can also configure a Windows server as a DHCP relay agent. Of course, the relay agent on the same physical segment as the hosts can not reach the DHCP server - not on the same segment as the DHCP server itself.

Configuring a router as a DHCP relay agent is very differentconfiguration of a Windows server and the network + exam does not require the user to configure it. Need to know why the need for a relay agent there, and you need to configure your network, always check the vendor documentation.

Related : Corrugated Plastic Compare Price Store Spark Energy

Thursday, October 7, 2010

Cisco CCNP BCMSN 642-812 Certification Exam Tutorial - DHCP snooping

An important part of passing the Cisco CCNP BCMSN exam and protect the network from intrusions is that the protocols and services daily to work against us to recognize that once intruded into our network.

It can be hard to believe, but something as innocent as DHCP can actually cause problems for the network. If a host sends a packet to the DHCP discover, listen DHCPOFFER packets - and accepts the first proposal that is!

Part of this is the address DHCPOFFERthat the host must set its default gateway. What happens if a DHCP server that is not part of our network - a rogue DHCP server - is placed on that subnet?
If the host uses the DHCPOFFER from the rogue server would host the final with the rogue server as the default gateway or DNS server!

We can prevent this DHCP snooping. DHCP snooping interface is classified as trusted or untrusted.

Message received the DHCPtrust interfaces will be allowed through the switch, but the DHCP messages received on untrusted interface result in the interface itself will be put into err-disabled state.

By default, the switch considers all ports of trust - this means you better remember to configure the switch for some ports, when you enable DHCP snooping trust!

First, we need to enable DHCP snooping on the entire switch:

SW1 (config) # ip dhcp snooping

To enable DHCP snooping on a specificVLAN, use the ip dhcp snooping.

SW1 (config) # ip dhcp snooping vlan 4

Ports can be configured as familiar with the ip dhcp snooping trust command.

SW1 (config-if) # ip dhcp snooping trust

There are other options available DHCP snooping, and we'll see some of these in a future tutorial. DHCP Snooping is an important topic for the CCNP BCMSN exam, and it is equally important in real-world networks - where to get familiar with both the examination room andnetwork room!

Tags : AutoCAD LT 2010 Store. LOWER Prices in Same Item Gaming Desktop Guide Baldor Motors

Friday, September 3, 2010

Microsoft Server 2008 Certification - Routing's Not Just For Cisco Exams Anymore!

Knowing routing theory and routing protocols has always been a big part of earning your Cisco CCNA and CCNP certifications. According to Microsoft's exam blueprints for the Server 2008 certification exams, that knowledge will also serve you well on your Microsoft exams.

The topic outline for the Configuring Windows Server 2008 Network Infrastructure exam (70-642) specifically mentions routing and routing protocols as exam topics. Specifically mentioned are RIP, OSPF, and static routing - three topics every CCNA and CCNP candidate will be well prepared to handle!

IPSec isn't part of the CCNA exam, but you'll see it on at least one CCNP exam, and it's also listed as a 70-642 exam topic. IPv6 and IPv4 addressing are both covered on the 70-642 as well.

Microsoft's website lists the following major skills you should expect to see on this exam:

Configuring IP addresses and Services (routing with RIP and OSPF, static routing, persistent routing, addressing, DHCP and DHCP options including relay agents, IPSec policies, Authentication Header and Encapsulating Security Payload, subnetting, supernetting)

Configuring Name Resolution (DNS configuration, zones, records, replication, and integration with Active Directory, and client computer name resolution techniques)

Configuring Network Access (includes NAT, VPNs, RADIUS, 802.1x authentication, MS-CHAP, firewalls, and remote authentication methods)

Configuring File And Print Services (self-explanatory)

Monitoring And Managing A Network Infrastructure (includes SNMP and Windows Server Update Services)

Your CCNA and CCNP preparation will not quite be enough to get you past this exam, but as you can see, it'll give you a great head start!

Friends Link : Blank DVDs Store. LOWER Prices in The Same Item

Wednesday, September 1, 2010

CompTIA Network+ Certification Exam Tutorial: DHCP and DHCP Relay Agents

As a CompTIA Network+ exam candidate, you're probably familiar with DHCP - but just in case, we're going to review DHCP basics here and then go into a discussion of DHCP Relay Agents.

When it comes to assigning an IP address to all the PCs on our network, along with their network mask, DNS server location, and more, we've got two choices on how to do it:

o Go to every workstation and configure the workstation statically

o Go to every workstation and configure them all to use DHCP

What we have here is the classic "static vs. dynamic" argument. I don't want you to think I'm lazy, but I'll take the dynamic way of doing things almost every single time.

You may wonder why it matters, since both methods involve visiting each workstation. You're right about that, and even though it's a lot quicker to configure a workstation to get its IP address and mask from a DHCP server than it is to configure the entire IP address and mask statically, the real benefits come in when the network changes.

And take it from me - your network will change. You'll remove hosts, you'll add hosts, and if the previous network manager didn't plan for future growth, the day may come when you've got to change the IP numbering scheme for your network. The choice that was made originally between static configuration and DHCP will then determine how easy the change will be.

o If the network was statically configured, you will now have to go to every single workstation and change their IP addressing to the new scheme.

o If the network is using DHCP, you simply change the networking scheme on the DHCP server and allow the workstations to get their new addresses dynamically.

Believe me, I've performed IP address changes in both fashions, and I'll take DHCP every time! Avoiding static IP address assignments also cuts down on the chances of two hosts in your network being assigned the same IP address.

When hosts receive an IP address from DHCP, it does not belong to that host permanently. The address is actually leased from a DHCP server. Let's walk through the DHCP process from the host's point of view.

First, the DHCP Client boots up, and sends a DHCP Discover packet onto the network. The host does this in order to "Discover" a DHCP server or servers. This Discover packet is a Level 3 broadcast, which has a destination IP address of 255.255.255.255.

Every DHCP Server that hears this broadcast will respond with a DHCP Offer, and it's an IP address and mask that is being offered. The DHCP Offer also includes a subnet mask, the IP address of the DHCP Server sending the response, and how long the host can keep this address (the DHCP lease duration).

If multiple DHCP Servers happen to hear this broadcast, they will each offer an IP address.

The DHCP Client will accept the first offer it receives. It does so by sending another broadcast, a DHCP Request packet.

The DHCP Server that made the offer that's being accepted will now send a DHCP Acknowledgement, which contains the rest of the information the host needs to function, including the location of a DNS server. The DHCP Server that made the offer that was not accepted will return the offered IP address to its range of assignable addresses, its address pool.

I made several mentions in this section about these DHCP packets being broadcasts. Do you remember which network connectivity device does not forward broadcasts? That's right, it's our old friend, the router!

If a PC is on one side of the router and the DHCP Server is on another side, we've got a problem. The initial DHCP Discover packet is a broadcast, and the router will not forward that broadcast to the DHCP Server. Luckily, this doesn't mean that we need a DHCP server on every single subnet on the network, because we can configure the router as a DHCP Relay Agent.

A DHCP Relay Agent will forward DHCP Requests to the DHCP Server. You can also configure a Windows server as a DHCP Relay Agent. Naturally, the Relay Agent must be on the same physical segment as the hosts that cannot reach the DHCP Server - never put it on the same segment as the DHCP Server itself.

Configuring a router as a DHCP Relay Agent is a lot different than configuring a Windows server, and your Network+ exam will not require you to configure either. You should know why the need for a Relay Agent exists, though, and should you need to configure one on your network, always check the vendor's documentation.

Related : PDA Mobiles Spark Energy

Friday, August 20, 2010

CCNA - CCNP Certification - Hands-On Lab Configuring Two Cisco Routers

Objective: In this lab you will configure a simple network to allow two routers to route packets between to remote networks. The text that is in bold is the text you need to type during the lab. Requirements:


Two Cisco routers with one Ethernet port and one serial port.
Cisco IOS 10.0 or higher
One PC for consoling into routers with terminal emulation software
One serial cable
One Cisco rollover cable

Setup: Step 1: Physical Connections Connect the following interfaces:


Console: Connect your PC/terminal to the console port using a rollover cable and HyperTerminal (9600-8-N-1-no flow)
Ethernet: Connect Ethernet ports to a hub or a switch using a straight-through cable. Use a cross-over cable if going directly from the PC's NIC to the Ethernet (AUI) port on the router using a transceiver.
Serial: If going directly between two routers, don't forget to connect one port via the DTE cable and the other via the DCE cable.

Step 2: Boot up the routers Just say "no" to use the setup mode (setup dialogue). The setup mode will only allow you to configure the router with the basic features and not with any advanced features. If asked if you would like to terminate the auto configuration; say "yes". Let the routers finish booting.

Step 3: Host Name and Passwords Begin your configuration with the host name and passwords. This is to remind you of what router you are configuring and now's the time to start thinking about router security.

RouterA

router>en

router#config t Enter configuration commands, one per line. End with CNTL/Z.

router(config)#hostname RouterA (sets the router's name)

RouterA(config)#enable secret cisco (Sets the secret password for the router)

RouterA(config)#line vty 0 4 (there are five concurrent connections for the telnet ports coming into a Cisco 2500 router. We are setting the login password on all five of them)

RouterA(config-line)#login (This enables the router to require a login password for a telnet session to the router)

RouterA(config-line)#password cisco (this sets the login password for all 5 telnet sessions coming into the router as cisco)

RouterA(config-line)#exit

RouterA(config)#^Z (This is the key combination of control+z which takes you back to the privileged executive mode)

RouterA#

RouterB

router>en

router#config t Enter configuration commands, one per line. End with CNTL/Z.

router(config)#hostname RouterB (sets the router's name)

RouterB(config)#enable secret cisco (Sets the secret password for the router) RouterB(config)#line vty 0 4 (there are five concurrent connections for the telnet ports coming into a Cisco 2500 router. We are setting the login password on all five of them)

RouterB(config-line)#login (This enables the router to require a login password for a telnet session to the router)

RouterB(config-line)#password cisco (this sets the login password for all 5 telnet sessions coming into the router as cisco)

RouterB(config-line)#exit

RouterB(config)#^Z (This is the key combination of control+z which takes you back to the privileged executive mode)

FYI: Anytime you make a configuration change to a router and you come back to the privileged exec mode you need to save your changes to NVRAM. This ensures that if the router reboots, you won't loose your changes which are in the running-config which is volatile RAM. The following command(s) saves your changes to the startup-config.

RouterA#copy running-config startup-config

or

RouterA# copy run start

or

RouterA#wr me (short for write memory)

Step 4: Adding IP Addresses Adding IP addresses, is a basic function of configuring routers. Below is an example of configuring both an Ethernet and serial interface. For serial interface with the DCE cable you will need to also add the clocking with the clockrate command. Get the IP addresses from the network diagram.

RouterA RouterA#config t Enter configuration commands, one per line. End with CNTL/Z.

RouterA(config)#int e0

RouterA(config-if)#ip address 172.16.12.1 255.255.255.0

RouterA(config-if)# description LAN Network for

RouterA RouterA(config-if)# no shutdown

RouterA(config-if)#int s0

RouterA(config-if)#ip address 172.16.10.1 255.255.255.0 (RouterA will have the serial 0 with the DCE end of the serial cable. The other partner will have serial1 with the DTE end of the serial cable. Check the network diagram to confirm to see who has what interface)

RouterA(config-if)#clockrate 250000 (DCE interface only which is the s0 on RouterA)

RouterA(config-if)#no shutdown

RouterA(config-if)#description Network connection to RouterB

RouterB

RouterB#config t Enter configuration commands, one per line. End with CNTL/Z.

RouterB(config)#int e0

RouterB(config-if)#ip address 172.16.11.1 255.255.255.0

RouterB(config-if)# description LAN Network for RouterB

RouterB(config-if)# no shutdown

RouterB(config-if)#int s1

RouterB(config-if)#ip address 172.16.10.2 255.255.255.0

RouterB(config-if)#no shutdown

RouterB(config-if)#description Network connection to RouterA

Once both routers are configured properly, you should be able to use the ping command and ping the interface e0 on each of the routers from the neighboring router. If you do a show ip route on both routers and do not see the directly connected interfaces in the routing table, they are either not configured or they never came up. Confirm that the IP addressing took and the interfaces came up by using the show ip int and looking at the interfaces' status and ip address configuration. RouterA# show ip route RouterA# show ip int Do this on both routers.

Step 5a: Adding Dynamic Routing: RIP For this router to participate in a dynamic routing using a dynamic routing protocol like RIP or IGRP, you'll need to enable a routing protocol and advertise the directly connected networks that want advertised.. We only advertise the classful network address, not the subnet mask of the network.

RouterA

RouterA>en RouterA#config t Enter configuration commands, one per line. End with CNTL/Z. RouterA(config)#router RIP RouterA(config-router)#network 172.16.12.0

RouterB

RouterB>en RouterB#config t Enter configuration commands, one per line. End with CNTL/Z.

RouterB(config)#router RIP

RouterB(config-router)#network 172.16.11.0

FYI: We need to advertise the network, not any particular host. An example of that would be enabling RIP on RouterB. We want the other router (RouterA) to know that any packet destined for the network 172.16.11.0 can be sent to RouterB which has a directly connected 5 entry in it's routing table showing what interface to send the packet to; in this case its e0. If you route to 172.16.11.1, all your every going to route to, is the e0 on RouterB and nothing else. Test your configuration to ensure that it is configured properly by pinging from router to router. Check your routing table for entries that are preceded by a capital letter "R" to ensure that you are receiving routing updates using RIP. Ensure that your partner has finished configuring his router so that you can receive his updates. No updates, no ping. Do a show ip protocol to see what routing protocol is configured on the routers.

Step 5b: Adding Dynamic Routing: IGRP IGRP uses an autonomous system (AS) number or process id. This number must be the same on all routers wanting to share IGRP routing updates or they don't share. Turn RIP off before you turn on IGRP. For this lab we'll be using an AS number of 100.

RouterA

RouterA>en RouterA#config t

RouterA(config)#no router rip RouterA(config)#router igrp 100

RouterA(config-router)#network 172.16.12.0 (again, just the network portion of the IP for your Ethernet network, NO subnet mask)

RouterB

RouterB>en RouterB#config t Enter configuration commands, one per line. End with CNTL/Z.

RouterB(config)#no router rip

RouterB(config)#router igrp 100

RouterB(config-router)#network 172.16.11.0 (again, your Ethernet network IP NO Subnet Address)

Step 6: Adding Default Routes Good candidates for default routes are routers which are known as the boundary router. This is a router which is normally part of a stub network. Inside the stub network, the routers may be participating in a dynamic routing using a protocol like RIP, but only a static default route is needed to connect the stub network to the Internet.

RouterA

RouterA>en RouterA#config t RouterA(config)#ip route 0.0.0.0 0.0.0.0 172.16.10.2

RouterB

RouterB>en RouterB#config t

RouterB(config)#ip route 0.0.0.0 0.0.0.0 172.16.10.1

Step 7: Adding Static Routes A static route can be used for different reasons. One reason may be for a router to connect to another router in a lab. You'll need to turn off all routing protocols before you configure the router for static routing.

RouterA

RouterA>en

RouterA#config t

RouterA(config)#no router igrp 100

RouterA(config)#ip route 172.16.11.0 255.255.255.0 172.16.10.2 What we are saying here is: For RouterA to route to the network 172.16.11.0, go to the next hop interface which is the serial1 (172.16.10.2) attached to RouterB. Since RouterB knows about the directed connected Ethernet network of 172.16.11.0, it will have route for it in its routing table proceeded by the letter "C". (See next example)

RouterB#sh ip route (Output omitted) 172.16.0.0/24 is subnetted, 1 subnets C 172.16.0.0 is directly connected, Ethernet0 RouterB# RouterB

RouterB>en

RouterB#

RouterB#config t

RouterB(config)#no router igrp 100

RouterB(config)#ip route 172.16.12.0 255.255.255.0 172.16.10.1

Step 8: Testing and Monitoring At this point it is a good idea to start testing your network using various commands. Perform the following on both routers.

RouterA# show ip route

RouterA# show ip interface brief (This command shows the IP and status of all interface)

RouterA# show controller s0 (Shows whether or not the serial cable is DCE or DTE.)

RouterA# ping ip-address

RouterA# trace ip-address

RouterA# debug ip rip (Remember to turn debug off when done, use undebug all, no debug all or un all)

RouterA# terminal monitor (for using debug from a telnet session, otherwise debug output will go to the console. Caution: This will cause the debug output to go to all telnet sessions on the router.)

Show commands

RouterA# terminal no monitor(To turn off monitoring during a telnet session.)

RouterA# show cdp neighbors

RouterA# show ip protocols

RouterA# #show version

RouterA# #show flash

RouterA# show ip route (shows the routing table)

RouterA# show memory

RouterA# show stacks

RouterA# show buffers

RouterA# show arp

RouterA# show processes

RouterA# show processes cpu

RouterA# show tech-support

Step 9: Finishing up Once you have your routers up and working you may wish to run some commands to make working on Cisco routers easier and to stop some of the default annoying behavior of Cisco routers.

RouterA(config)# ip host RouterB 172.16.10.2 (This configures a host table entry for the name RouterB. So instead of having to remember the IP of RouterB to ping it, you can now ping it using its name, RouterB. It's the same as using a hosts file on a computer. If you just type in RouterB and hit enter, the router will assume you're wanting to telnet into RouterB using port 23)

RouterA(config)# no ip domain-lookup (When there is no DNS server and you miss spell a single word command, it will try to do a DNS lookup using a broadcast address of 255.255.255.255. To stop this lookup of a non-existent DNS server, we can turn off the DNS lookup capability using this command.)

RouterA(config)# banner motd #!!!!Warning! Authorized Access Only!!!!# (This message will be seen by anyone trying to logon to your router. The # sign is known as a delimiting character and is used to identify the text portion of the MOTD. Notice that the actual message starts and ends with the delimiting character)

RouterA(config)# no service-config (When you reboot a Cisco router, the default behavior is to try and find a configuration file on the network using a number of methods over a broadcast address of 255.255.255.255. To stop this annoying behavior, Use this command.)

RouterA(config)#no logging console (Each time you leave one level of the router and return to the previous level or bring an interface up, you get a read out on the console screen. If you get busy typing and configuring the router this can be distracting and annoying. Use this command to stop the logging of messages to the console screen.) And don't forget to...

RouterA# show running-config

RouterA# copy running-config startup-config

Friends Link : Temperature Data Logger