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

Clean-up Tool (FindFile)

       Management of information stored on our network drives is important for many reasons but a major reason is cost control. By nature, our storage continues to grow and many users acknowledge that some stored information is old or has little value. These unneeded files can be either deleted or archived, resulting in significant reductions in business unit expense. A complete storage review can be time consuming but even a cursory review could easily result in significant annual savings. Below are three search methods that can use to reduce your network storage.

• Size - largest files first. You can significantly reduce your storage by identifying and eliminating only a few files.
• Date - oldest files. These files may no longer be needed.
• Type - Certain file types are known to be large in size such as BMP, JPG and MP3 files.

       FileFind is a tool that can help you with all three of these search methods. FileFind is an Excel spreadsheet with macros that assists in managing your disk storage. Below are instructions for using this tool. Should you have problems, please contact your local IT group.
Note: Secure and efficient storage of data is critical to our business. The data belongs to Company and, as a steward of portions of that data, the storage space on the servers is there for your use. However, it is expected that each user be accountable for their own data storage or that of their group.

       Company highly recommends that you not store business data on your C: drive. Data stored in this manner is not secure, is not backed up, is difficult to share, and in many cases conflicts with company information protection guidelines.


Welcome!  If you are not yet a network member, please register.

Read More