This is a cool batch script that I found to ping a range of IP addresses and report whether they respond to the ping.

Simply copy and paste this code into a notepad file and save with the bat extension (remember to enclose the save as file name in quotes so that it doesnt add a txt extension.

A useful management tool available in IOS is the one that gives you the ability to assign levels of
privilege. Privilege levels are assigned to both users and commands. The privilege levels range
from 0 to 15. By default, commands are assigned either level 1 or level 15. Those commands that
need to be executed in privileged EXEC mode are level 15 commands. With a few exceptions,
those commands that can be executed in user EXEC mode are level 1 command. A small number
of commands are level 0 commands. These commands include enable, disable, exit, logout, and
help. Level 0 commands can be executed at any level.

A user operating in privileged EXEC mode is a level 15 user. A user operating in user EXEC
mode is a level 1 user. Commands and users can be assigned a privilege level different from their
default. The way the privileges work is a higher level has the same rights as the lower levels
beneath it. For instance, a level 10 user (if you set one up) can do everything users at levels 9
through 0 can do. Level 15 users can execute all commands.

Commands can be reassigned a different level of privilege as well. You can raise or lower the
level of privilege on any command. Privilege levels on commands are assigned using the
Privilege command; the command syntax is as follows. Use global configuration mode for this
command.

    privilege level <0 – 15>

This feature is quite useful as it allows us to create various levels of users with custom rights to
IOS commands. Imagine if you had a number of administrators with limited knowledge of the
workings of IOS. But you need their help with certain specific tasks such as shutting down and
re-enabling an interface or adding users to an access server. You can configure the router or
access server so that depending upon the password provided, the user will be assigned a specific
level of privilege and will only be allowed to use commands assigned to that level and below.

Privilege levels for users can be set in a number of ways via the IOS. They can be set
permanently on a line using the privilege level command; at the command prompt using the
enable command; or when logging in using the username command.

To set the default privilege level for a line, use the privilege level command in line configuration
mode. The syntax is as follows: privilege level <0 – 15>.

To interactively reset the level of privilege from the command line, use the enable command.
The command syntax is enable <0 – 15>. The command can be executed in any EXEC mode. If
you leave off the level number, the router assumes you mean 15. It is advisable to set up an
“enable secret” password for each level of privilege. Be sure each level’s password is different
and that the passwords are only known to users within the appropriate level. The syntax for this
command is enable secret level <1-15> .

The most common way to assign levels of privilege is to do so based on the user’s username.
The IOS allows you to create and use username/password pairs in your router configuration for
authentication purposes. Along with the authentication process, the user can be assigned as level
of privilege.

Examples:

In the example below, we have created three custom user levels using level numbers 2, 3, and 4.
Level 2 users can do show commands as well as all commands in levels below. By default, level
1 users can do most show commands. But after issuing the command privilege exec level 2
show in our configuration, it will no longer be possible. Level 3 users are permitted to issue the
command show ip route, but level 2 users cannot. Level 4 and above users can issue the show
access-list command as well as any command in levels below.

    Router(config)# privilege exec level 2 show
    Router(config)# privilege exec level 3 show ip route
    Router(config)# privilege exec level 4 show access-list

The example below shows us assigning level 2 to any user that enters the router via telnet. It
assigns level 3 to any user that enters via the auxiliary port. And it assigns level 4 to anyone that
enters via the console port.

    Router(config)# line vty 0 4
    Router(config-line)# privilege level 2
    Router(config-line)# line aux 0
    Router(config-line)# privilege level 3
    Router(config-line)# line console 0
    Router(config-line)# privilege level 4

The example below creates a separate password for each custom level of privilege. If a user
issues the command enable 2, that user will be prompted for the password “twopass”. A level
three request will require the level three password and so on.

    Router(config)# enable secret level 2 twopass
    Router(config)# enable secret level 3 threepass
    Router(config)# enable secret level 4 fourpass

The example below creates three users: bob, fred, and sam. Bos is a level 2 user. Fred is a level 3
user. Sam is a level 4 user. To have the router prompt for username and password when logging
in, use the command login local in your line configuration mode.

    Router(config)# username bob privilege 2 password bobpass
    Router(config)# username fred privilege 3 password fredpass
    Router(config)# username sam privilege 4 password sampass
    Router(config)# line vty 0 4
    Router(config-line)# login local

Today I'd like to share with you some light ideas about network troubleshooting in Windows XP.
Most of your network connection issues can be fixed with an very enigmatic command called “Repair”. You can find this by clicking right mouse button on network icon at System Tray area. Please take a look on a picture below.

PsExec

psexec \\RemoteComputer cmd.exe

SSH on Windows

The PSTools suite is one of those things that you’ll find new uses for every time you play with it. The PSTools suite was developed by Mark Russinovich who worked on the original NTFS file system, and hence has a rather unique insight into the inner workings of Windows systems.
The PSTools suite is comprised of the following utilities:

• PsExec – execute processes remotely
• PsFile – shows files opened remotely
• PsGetSid – display the SID of a computer or a user
• PsInfo – list information about a system
• PsKill – kill processes by name or process ID
• PsList – list detailed information about processes
• PsLoggedOn – see who’s logged on locally and via resource sharing (full source is included)
• PsLogList – dump event log records
• PsPasswd – changes account passwords
• PsService – view and control services
• PsShutdown – shuts down and optionally reboots a computer
• PsSuspend – suspends processes
• PsUptime – shows you how long a system has been running since its last reboot (PsUptime’s functionality has been incorporated into PsInfo)

A common tool that network and system admins make use of is the “Ping” command which is a very simple and effective way to verify a machine is available on the network (firewall rules depending of course). So if you find yourself having to ping multiple machines at once, a very useful tool is the batch files, which will not only ping all the ip addresses but also give you ping results in text file format with just single click.

A batch file is a text file containing a series of commands intended to be executed by the command interpreter. When a batch file is run, the shell program (usually COMMAND.COM  or cmd.exe) reads the file and executes its commands, normally line-by-line. Batch files are useful for running a sequence of executables automatically and are often used by system administrators to automate tedious processes.

Steps to create batch file::

1. Open up Notepad, type in the following commands (Example)

Will organize and monitor software, hardware, and patches on your network.

Spiceworks Desktop delivers nearly everything you need to simplify your IT job. Designed for small- and medium-sized businesses, Spiceworks single, easy-to-use interface combines Network Inventory, Help Desk, Reporting, Monitoring and Troubleshooting. In addition, Spiceworks IT Desktop will connect you with other IT professionals to share ideas, solve issues and choose what other features you need in Spiceworks.

 

Here are some key features of "Spiceworks Desktop":
Inventory Everything on Your Network:
· Discover the Windows, Mac, and Linux PCs and servers, routers, printers and any other IP-based devices on your network.
· Gather all of their relevant technical data plus the software, patches and services on each machine.
· Add important data such as the number of licenses you have, the purchase price and physical location.
· Keep track of other assets such as mobile phones and even office furniture. All without agents.
· Store all inventory information locally and securely on your network - so there's no concern about sensitive data flying across the Internet.


Run an IT Helpdesk:
· Create a ticket in one click if you discover an asset that requires your attention while browsing your network in Spiceworks.
· Let your clients submit tickets with attachments to you via email or the Web and then allow them to view the status of those tickets online.
· Assign tickets across your IT team, attach them to hardware on your network, and manage your projects.
· Easily run reports on your tickets so you can see things like due dates and which assets (or even departments!) cause you the most issues.


Monitor Your Network for Trouble:
· See and set up alerts for Windows events that occur across your environment - so you can easily detect, diagnose and troubleshoot issues that disrupt your network.
· Automatically identify PCs and servers with low disk space, the presence of unwanted software on your network, the status of your anti-virus updates, printers with low toner and ink levels, and offline servers.
· Receive email alerts about potential issues.
· View all the monitors you care most about in one centralized spot.


Report on Your Network:
· With one-click, see software installed on your machines, disk usage across the network, trouble tickets you've created in the past month, and much more.
· Create the custom reports you need with a simple interface.
· Publish reports so others in your company can stay in the loop.
· Export any report to PDF and Excel.
· Exchange useful report templates with other Spiceworks users.


Troubleshoot Issues on Your Network:
· See what software is on a machine that is causing it to run slowly.
· Launch your remote control tool from within Spiceworks.
· Compare two machines to see what settings are different.
· Ping machines to see if they are online.
· See traceroutes to identify the flow of data.
· Identify when a server is running out of capacity.

::::Get it from here::::

http://download.spiceworks.com/Spiceworks.exe

Theres no real intro needed to this tutorial. This is literally going to be a step by step, just
as the title suggests. However, before I go on, I think it important to know WHY and HOW
this works as well as it can be applied somewhat to other devices/situations.

Cisco routers work like this:
ROM > NVRAM > FLASH > DRAM
lets break it down:

ROM:
This is your Basic IOS. (thats Internetworking Operating System for those who dont know)
Think of it kind of like CMOS with the exception that you cannot flash or alter it. The ROM
contains the /BOOTP as well.

The Bootp has a value which defines how the device will boot.
They are as follows:
0x2102 <-- normal boot sequence
0x2142 <-- skips NVRAM
0x2101 <-- skips FLASH
0x2000 <-- diagnostic mode

NVRAM:
Non Volatile RAM. This is like a hard drive being that the memory is non-volatile meaning
that the info in it stays after a reboot. This contains the startup-config which contains the
PWs to the device.

FLASH:
This is your IOS.

DRAM:
Think of this as RAM, because thats what it is. Its volatile memory that contains the
running-config. Any changes you make to the system are saved to the running config but
being its volatile, once the system is rebooted for whatever reason, those changes are gone.
This is why you "copy run start" to save the changes in the running config to the startup
config so that they are applied if/when the device is rebooted.

(pardon the abbreviation of the commands, but as anyone thats used Ciscos IOS knows,
you can abbreviate any command or subcommand pretty well, so no need to write it all out.
"cop ru st" will so the same thing as "copy run start". Blah blah blah, you get the idea, no
need to get into this now.)

Moving on.
Now that Ive explained all that and you hopefully have an understanding of how the
devices boot sequence works, on to the password recovery.

1. Reboot the device.

2. press control + break within 60 seconds of the reboot.
this brings you to the basic IOS.
Now you can change the value in the BOOTP from 0x2102 to 0x2142, which skips
NVRAM, which contans the startup-config, which contains the password.

3. Reset.
Ok, so now that this point the device will boot up and due to the change in the bootp will
bypass the NVRAM and bring you into the IOS.

4. At the prompt:
Router> enable
Router# copy start run
ROUTERNAME#config t
here is where you either view or change the password. You may be able to view it if the
administrator hasnt encrypted it. If thay have, you can crack it or easier still just assign a
new one.
ROUTERNAME(config)#config 0x2102
this changes the boot sequence back to normal.
ROUTERNAME#copy run start
This copies the DRAM to the NVRAM... thus saving the changes you made.

5. Reboot.
Done. The device will then reboot and prompt you for the password that you just set. Enter
it and its all good.
Hope you enjoyed this tutorial.

Background Information

The OSI architecture was set up by the ISO (International Standards
Organization) as the first formally defined way of connecting computers. The
OSI architecture divides network functionality up into seven layers, where
various protocols implement the functionality assigned to a given layer. 



The Layers

The Physical Layer 
This is the first layer of standards. It’s a set of rules regarding the hardware
used to transmit data. Among items covered at this layer are the voltages
used, the timings of transmission, and the rules used for the initial
handshaking connection. 

The Data Link Layer
The physical layer provides the data link layer with bits. Now this layer
provides the bits with some meaning. We no longer deal with bits but
instead with data frames - packets, containing data as well as control
information. The data link layer adds flags to indicate the start and end of
messages.

This layer’s standards perform two important tasks. It ensures that data is
not mistaken for flags, and that it checks for errors within the frame.

 The Network Layer
The network layer, is concerned with packet switching. It establishes virtual
circuits (Paths between terminals) for data communications. As the sending
end, the network layer repackages messages from the transport layer above
it into data packets, so the lower layers can transmit them.

The Transport Layer
The transport layer of the OSI model has many functions, including several
order f error recognitions and recoveries. As the highest order, the Transport
layer can detect errors, identify packets that have been sent in the incorrect
order, and then rearrange them. The transport layer also regulates the
information flow by controlling the messages movements.

The Session Layer
The session layer is concerned with the management of the network. The
user communicates directly with this layer. It can verify passwords entered
by the user. It can determine who uses the network, for how long, and for
what purpose. It controls data transfers and even handles recovery from
system crashes.

The Presentation Layer
This layer is concerned with the network security, file transfers and
formatting functions. At the bit level it is capable of encoding data in a
variety of different forms including ASCII and EBCDIC.

For true Communication, both communicating computers must contain the
same protocols. This level handles protocol conversions between different
computers using different formats.

The Application layer
The application layer handles messages, remote logons and the
responsibility of network management statistics. At this level are the
database management programs, electronic mail, file server and printer
server programs. The operating systems command and response language.


OSI Vs TCP/IP

Unfortunately (for the many people and companies that spent so much time
and money on the effort), the TCP/IP suite of protocols has eclipsed OSI,
and you don't hear much about OSI anymore (except for a few applications,
such as the X.500 directory service).

When work began (in the late 1970s) on providing a standard method for
communications between different hardware platforms, TCP/IP was not
considered an option for serious commercial applications, since TCP/IP:


Required you to run UNIX (which, at the time, was not used for commercial
applications and had only a command-line user interface)

Had poor security and management features

Had too small an address size

Therefore the ISO promoted development of OSI.

Although all major (and many minor) computer vendors now have OSI
products, the OSI protocols were never widely implemented, and TCP/IP has
become the first choice for multi-vendor networking, because of its:

Lower-cost and more-efficient implementation (less CPU time required,
smaller programs)

Availability for most operating systems

Fast standardization and development cycle (usually using the Internet to
facilitate communications) when a new requirement is identified

Familiarity among college graduates (universities use TCP/IP, so once out of
school, a graduate's first choice when designing a system is to use TCP/IP)

Easier-to-access (and zero-cost) documentation and standards (they are all
available on the Internet)

Subnet Mask Quick Reference

1. Configuration Manual Resolution:

Note: This article is geared towards “power users” of Windows, and if you are confused on something mentioned here, look it up on Google or find more information about it other wise. Anyway, this is a guide to some REAL network troubleshooting issues that truly occur on a day-to-day basis. Whenever I had these problems, I was never able to find them in any network “troubleshooting” guides on the Internet. Instead, I had to figure these out by long searching or trial and error. Here are some fixes to common problems:

Problem: I cannot see people on my network using “My Network Places” or “Network Neighborhood” and they cannot see me, yet I can use the Internet!

Solution: You are probably on a different subnet than the others. Open up your TCP/IP configuration in Windows and change your subnet mask to whatever the other people are.

Problem: I have rejoined another workgroup; yet, both the new one and the old one show up in “My Network Places” or “Network Neighborhood.”

Solution: Give it about 30 minutes. The Windows browser service is screwed up.

Problem: I cannot access the Internet but my friends can!

Solution: Make sure that you have the same TCP/IP settings as the rest of the people (except for IP address – make sure it is unique). If the other people obtain their IP’s automatically, do the same for your computer. Then, open a command prompt [Start->Run->Cmd] and type in ping www.google.com. If it says “Request Timed Out.” then you still cannot connect to the Internet. So, we will continue. See if you have the Internet Connection Firewall enabled. If so, disable it and try again. If it still doesn’t work, check to see if your cables are snug in both ends and to see if both the hub/switch/router and your network adapter are both blinking. Next, go back to command prompt and type in ipconfig /release. Wait a bit, then type ipconfig /renew. If you do all this and your Internet still does not work, then restart your computer and pray.

Problem: I cannot host a game over the Internet.

Solution: Usually has something to do with routers. Find out which port(s) that your game uses. Then, in your router configuration (usually located at 192.168.0.1 or 192.168.1.1 or 192.168.254.254), go to the “Port Forwarding” section. Forward requests from the port(s) needed by your game to your computer’s ip address (you can find it by typing in ipconfig /all or winipcfg). Then, you are set!

Problem: I cannot join a domain from a computer that is otherwise perfectly configured for networking.

Solution: The most likely reason for this occurring is that your domain requires an Administrator’s login and password to confirm a computer joining a domain. When the box comes up that requests a username/password for your domain have your domain admin type in his or her password. The computer will then require a restart, and when it has restarted, you will be able to login to your domain with your own username and password. Don’t forget to update your user settings on your own computer!

Problem: I cannot ping localhost or 127.0.0.1

Solution: TCP/IP is not installed. Install it using the Network Connections properties configuration screen.

Problem: When I plug in a network cable into my NIC, the “Link” light does not light up like it should be doing.

Solution: This could be due to three problems. I will list them in the “most likely” order they would occur:

1. The “other end” of the cable leads to nowhere, or is not connected to any powered network device.
2. Your NIC is not properly inserted in your motherboard.
3. The cable is bad.

1. Your Ethernet hub does not support 100 MB/S. Buy a hub that does.
2. Your adapter is improperly configured. Go to your Adapter settings and change it to “Auto-Negotiation.”
3. There is a bottleneck in your network. If you are trying to connect over a WAN (such as the Internet) realize that you will never achieve full 100 MB/S or even 10 MB/S for that matter. Run tracert to find bottlenecks, and then consider an alternate route or a different routing protocol (if the option is available).
4. The end that you are communicating with does not have a 10/100 NIC. Buy the other computer a 10/100 MB/S. card.

PingInfoView is a small utility that allows you to easily ping multiple host names and IP addresses, and watch the result in one table. It automatically ping to all hosts every number of seconds that you specify, and displays the number of succeed and failed pings, as well as the average ping time. You can also save the ping result into text/html/xml file, or copy it to the clipboard.

Using PingInfoView

Use IP-Host Description format

192.168.1.10 Main Server
192.168.1.11 Host 01
192.168.1.12 Host 02

Command-Line Options

System Requirements

Description of IPv6 Packet Header

Hexadecimal "Hex"

Addressing Description

Broadcasting Methods

•Unicast

•Multicast

•Anycast

Unicast

Multicast

Anycast

Summary

Review Questions

Checkout new CCNA Video Zone under Pages , will be adding some more videos soon ...

Happy learning :)

Click on Image to Download Pdf file

 Protocols

BGP

version 2.0 (2 pages)

EIGRP

version 2.0 (1 page)

First Hop Redundancy

version 2.0 (1 page)

IEEE 802.11 WLAN

version 2.1 (2 pages)

IEEE 802.1X

version 2.0 (1 page)

IPsec

version 2.0 (1 page)

IPv4 Multicast

version 2.0 (1 page)

IPv6

version 2.0 (1 page)

IS-IS

version 2.0 (2 pages)

OSPF

version 2.1 (2 pages)

PPP

version 1.01 (1 page)

Spanning Tree

version 2.0 (2 pages)

Applications

tcpdump

version 2.0 (1 page)

Wireshark Display Filters

version 2.0 (2 pages)

Reference

Common Ports

version 1.1 (1 page)

IOS IPv4 Access Lists

version 2.0 (1 page)

IPv4 Subnetting

version 2.0 (1 page)

Syntax

Markdown

version 2.0 (1 page)

MediaWiki

version 2.1 (1 page)

Technologies

Frame Mode MPLS

version 2.0 (1 page)

NAT

version 1.0 (1 page)

QoS

version 2.0 (2 pages)

VLANs

version 2.0 (1 page)

Voice

VOIP Basics

version 1.0 (1 page)

Miscellaneous

Cisco IOS Versions

version 2.0 (1 page)

Physical Terminations

I have uploaded Packet Tracer 5 lab activites for CCNA 640-802 as well as Cisco Networking Academy Student Lab Manuals of Routing Protocol and Concepts and Lan Switching and Wireless.

http://rapidshare.com/files/396002499/PacketTracer5.3_Team-ND.rar 
or 
http://hotfile.com/dl/46822557/61763ae/PacketTracer5.3_Team-ND.rar.html 
or 
http://www.fileserve.com/file/RJmbsmH/PacketTracer5.3_Team-ND.rar