Ping Multiple Destination With Batch File

       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)
   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   @Echo off
   ping 192.168.1.1 > "%userprofile%\desktop\pingresult.txt"
   ping www.google.com >> "%userprofile%\desktop\pingresult.txt"
   ping 146.23.4.45 >> "%userprofile%\desktop\pingresult.txt"
   tracert 192.168.1.1 >> "%userprofile%\desktop\pingresult.txt"
   tracert www.google.com >> "%userprofile%\desktop\pingresult.txt"
   tracert 146.23.4.45 >> "%userprofile%\desktop\pingresult.txt"
   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   Remember::  > will run the command and create a file with ping results and >> will append or add next ip address ping results to the created file . So whenever you create batch file first command should always have single > and subsequent  commands should have  >>.
2. Now save this file with Filename Ping_result.cmd or whatever you want and Change  Save as type to All files.
3. Run the Ping_result.cmd and you will get pingresult.txt on your desktop.

       Play around with netstat , ipconfig and other commands by creating batch files in the similar manner.., just change the ping command to the command of your choice in the above example.

Read More

How to Use the Traceroute Command

     Traceroute is a command which can show you the path a packet of information takes from your computer to one you specify. It will list all the routers it passes through until it reaches its destination, or fails to and is discarded. In addition to this, it will tell you how long each 'hop' from router to router takes.
    In Windows, select Start > Run > Type cmd or Start > Programs > Accessories > Command Prompt.  This will give you a window like the one below.

    Enter the word tracert, followed by a space, then the domain name.

    The following is a successful traceroute from a my machine in Thailand to liverpoolfc.tv:

     Firstly it tells you that it's tracing the route to liverpoolfc.tv, tells you the IP address of that domain, and what the maximum number of hops will be before it times out.
Next it gives information about each router it passes through on the way to its destination.
1 is the internet gateway on the network this traceroute was done from (an ADSL modem in this case)
2 - 5 are the ISP the origin computer is connected to (totbb.net)
6 - 8 are also in the xtra network
9 - 10 are all routers on the sg.bb.gin.ntt.net network (the domain that is the internet gateway Sigapore side)
11 - 13 are all uk.bb.gin.ntt.net in the UK (a telecom supplier in the UK)
14 - 15 are on the UK network 
and finally, line 16 is the computer liverpoolfc.tv is hosted on (liverpoolfc.tv)

      This is extremely useful when trying to find out why a website is unreachable, as you will be able to see where the connection fails. If you have a website hosted somewhere, it would be a good idea to do a traceroute to it when it is working, so that when it fails, you can do another traceroute to it (which will probably time out if the website is unreachable) and compare them. Be aware though, that it will probably take a different route each time, but the networks it passes through will generally be very similar. 
If the example above had continued to time out after line 9, you could suspect that sg.bb.gin.ntt.net was the problem, and not liverpoolfc.tv.

     If it timed out after line 1, you would know there was a problem connecting to your ISP (in this case you would not be able to access anything on the internet).

    It is generally recommended that if you have a website that is unreachable, you should use both the traceroute and ping commands before you contact your ISP to complain. More often that not, there will be nothing to your ISP or hosting company can do about it.

Read More

How to Use the Ping Command

       Pinging is a command which tells you if the connection between your computer and a particular domain is working correctly.


       In Windows, select Start > Run > Type cmd or Start > Programs > Accessories > Command Prompt. This will give you a window like the one below.
      Enter the word ping, followed by a space, then the domain name.
      If the results show a series of replies, the connection is working. The time shows you how fast the connection is. If you see a "timed out" error instead of a reply, there is a breakdown somewhere between your computer and the domain. In this case the next step is to perform a traceroute.

      Online ping. If you can't use the Ping command from your own computer because of a firewall or other restriction, or want to do an Internet ping from another location than your own, you can use one of the following websites that offer online ping services:

his.com Ping http://www.his.com/cgi-bin/ping?
Network-Tools http://network-tools.com/
Spfld.com Ping   http://www.spfld.com/ping.html
Theworldsend.net ping http://www.theworldsend.net/php-ping.php

Read More

Color Batch File To Check Network~Server

       I wrote this today to provide an easy way for anyone to see if a computer is on the network/internet and even do some basic troubleshooting. If someone wanted to take this. Just cut and past into a text file and save with a .bat extension and you should be good to go. Could easily be put on a floppy or e-mailed to someone to test with..

Here is the basic color command:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

@echo off

::

:: cecho by thomas

::

cecho {00}**********{\n}

cecho {0C}{\n}

echo This is a private system operated for HXXX Company business.

echo Authorization from XXX management is required to use this system.

echo Use by unauthorized person is prohibited.

cecho {00}**********{\n}

cecho {0C}{\n}

echo WARNING: This computer system is accessed by authorized users outside

echo of HP. All security and control procedures must be strictly followed.

pause

cecho {00}**********{\n}

echo Unpacking cecho utility

call :unpack_cecho

cecho {00}**********{\n}

cecho {0E}***************************************{\n}

cecho {0E}** BKKGCAP01.asiapacific..net **{\n}

cecho {0E}***************************************{\n}

cecho {0B}{\n}

cecho {9F} ------- {9F}Location: Row {9F}2 {9F}Rack {9F}8 {9F}------ {\n}

cecho {0B}{\n}

ping bkkgcap01 -n 5

cecho {00}**********{\n}

cecho {00}**********{\n}

cecho {0A}**************************************{\n}

cecho {0A}** TLAEXC01.asiapacific.xxxx.net **{\n}

cecho {0A}**************************************{\n}

cecho {0B}{\n}

cecho {9F} ------ {9F}Location: Row {9F}2 {9F}Rack {9F}2 {9F}------ {\n}

cecho {0B}{\n}

ping tlaexc01 -n 5

cecho {00}**********{\n}

cecho {00}**********{\n}

cecho {0E}***************************************{\n}

cecho {0E}** BKKFILE01.asiapacific.xxxx.net **{\n}

cecho {0E}***************************************{\n}

cecho {0B}{\n}

cecho {9F} ------- {9F}Location: Row {9F}2 {9F}Rack {9F}1 {9F}------ {\n}

cecho {0B}{\n}

ping bkkfile01 -n 5

cecho {00}**********{\n}

cecho {00}**********{\n}

cecho {0A}**************************************{\n}

cecho {0A}** BKKCOE01.asiapacific.xxxx.net **{\n}

cecho {0A}**************************************{\n}

cecho {0B}{\n}

cecho {9F} ------ {9F}Location: Row {9F}2 {9F}Rack {9F}1 {9F}------ {\n}

cecho {0B}{\n}

ping bkkcoe01 -n 5

cecho {00}**********{\n}

cecho {00}**********{\n}

cecho {0E}**************************************{\n}

cecho {0E}** THACOE01.asiapacific.xxxx.net **{\n}

cecho {0E}**************************************{\n}

cecho {0B}{\n}

cecho {9F} ------ {9F}Location: Row {9F}2 {9F}Rack {9F}* {9F}------ {\n}

cecho {0B}{\n}

ping thacoe01 -n 5

cecho {00}**********{\n}

cecho {00}**********{\n}

cecho {0A}***************************************{\n}

cecho {0A}** THNCIU01.asiapacific.xxxx.net  **{\n}

cecho {0A}***************************************{\n}

cecho {0B}{\n}

cecho {9F} ------- {9F}Location: Row {9F}1 {9F}Rack {9F}8 {9F}------ {\n}

cecho {0B}{\n}

ping thnciu01 -n 5

cecho {00}**********{\n}

cecho {00}**********{\n}

cecho {0A}**************************************{\n}

cecho {0A}** BKKSQL01.asiapacific.xxxx.net **{\n}

cecho {0A}**************************************{\n}

cecho {0B}{\n}

cecho {9F} ------ {9F}Location: Row {9F}2 {9F}Rack {9F}8 {9F}------ {\n}

cecho {0B}{\n}

ping bkksql01 -n 5

cecho {00}**********{\n}

cecho {00}**********{\n}

cecho {0E}*************************************{\n}

cecho {0E}** BKKDP01.asiapacific.cpqcorp.net **{\n}

cecho {0E}*************************************{\n}

cecho {0B}{\n}

cecho {9F} ----- {9F}Location: Row {9F}1 {9F}Rack {9F}8 {9F}------ {\n}

cecho {0B}{\n}

ping bkkdp01 -n 5

pause

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Download sample file
cecho.c      cecho.exe      cecho.vcproj      cecho BoYLaSeR.cmd    

Read More

NIC Teaming Preparation Items

Preparation Items
NOTE: This is a critical preparation work in order for the NIC Teaming to be successful. DO NOT proceed to any NIC Teaming if any of the below 3 pre-requisites are satisfied.

1. Ensure that Local Admin Account password is obtained and verified on each server. It is a contingency plan against failure to logon to domain due to NIC configuration error.	_____
2. Capture all server current IP configurations before the change.	_____
3. Ensure that the Secondary NIC to be teamed is switch-enabled and functional. Things to check: network cable need to be plugged in, switch port need to be activated and NIC interface need to be enabled.	_____

Adding and configuring NICs in a team
      Before a NIC is teamed, verify the following: The NICs must be DHCP enabled and the DNS server address must be left blank.
NOTE: The teaming utility becomes unstable if static IP addresses, subnets, and DNS addresses are set before teaming.

1.Duplex and speed settings must be set to use the default values (Auto)	_____
2.Open the HP Network Teaming utility. Highlight the NICs to team. Click Team.	_____
3.The Team Properties dialog box appears. Select one of the following methods: · If you will be using Fault Tolerant NIC teaming, select Fault Tolerant. Under Redundancy Control, select Smart Switch.	_____
4.Click OK to accept the team properties.	_____
5.Click OK in the HP Network Teaming and Configuration Properties dialog box to apply the changes.	_____
6.Click Yes when prompted to apply all configuration changes. Wait while the adapters are configured. This process could take several seconds.	_____
7.Click OK. An HP Load Balancing Team icon is now displayed in the HP Network Teaming and Configuration dialog box	_____
8.Click Yes to reboot now.	_____

Renaming the teamed connection
       The assigned name for the new NIC team connection is “Local Area Connection X,” where X represents the next available connection number generated by the system. HP recommends changing this name to a more meaningful name, such as “NIC Team.” To change the name of the connection:

1.From the desktop, right-click the My Network Places icon, and then click Properties.	_____
2.Move the cursor over each connection icon to view the pop up box of the icon’s name. Locate HP Network Teaming Virtual Miniport.	_____
3.Right-click the connection icon for HP Network Teaming Virtual Miniport, and then click Rename. Enter a name that is more descriptive than “Local Area Connection X,” such as “NIC Team.” For SQL server – to be maintained as PUBLIC For WFE – to be named as PUBLIC	_____

Configuring the TCP/IP protocol on the new team
      After teaming the NICs, a new virtual network adapter for the team is automatically created. However, by default, the new adapter is set to DHCP. To manually configure the IP address, perform the following steps. To enter the TCP/IP address information for the team:

1.From the desktop, go to the Network and Dial up Connections window, and then click Properties. Right-click the NIC Team icon, and then select Properties.	_____
2. Use the arrows and the scroll bar on the right of the screen to scroll through the Components list.	_____
3. Click Internet Protocol (TCP/IP), and then click Properties. NOTE: If a NIC is teamed, do not modify the TCP/IP settings for the individual NIC ports.	_____
4.Repopulate the following IP address information on the General tab for: IP address Subnet mask Default gateway Preferred DNS server Alternate DNS server	_____
5.Click Advanced.	_____
6.Click the DNS tab and uncheck the Register this connection’s addresses in DNS checkbox.	_____
7.Click the WINS tab and type the primary and secondary WINS server addresses in order of use.	_____
8.Close the windows and Exit.	_____
9.If you receive this warning message, Multiple default gateways are intended to provide redundancy to a single network …Do you want to save this configuration?, then click Yes.	_____
10.Click OK. The Ethernet Team should be working.	_____

Checking the status of the NIC team
      This is the post NIC Teaming implementation check items.

1.To check the status of the Ethernet Team, open the HP Network Teaming utility. The Configuration Properties window is displayed, showing the teamed NICs.	_____
2.To verify that the NIC Teaming is functioning as expected, plug out one of the cable physically. The network connectivity should be un-interrupted.	_____

Read More