How to Open Event Viewer in Windows 7

Since many of our Windows 7 troubleshooting steps require to open Event Viewer, it is necessary to write a complete guide to open Event Viewer in Windows 7. So I do not need to repeat the same steps to open Event Viewer in every Windows 7 guides. This supporting article can reduce the size of actual troubleshooting guides by just proving a link to this article without mentioning the steps to open Event Viewer. For those who are not familiar with Event Viewer, "Using Event Viewer we can see system event logs about hardware and software issues". To know how to Open Event Viewer in Windows XP click on the link below.

Open Event Viewer in Windows XP

How to Open Event Viewer in Windows 7



In Windows 7, we can open Event Viewer in two ways.


Method 1

In this method we just need to type "Event Viewer" in Windows 7 search.

1. Click on Start

2. Type "Event Viewer" on Search

Search and open Event Viewer in Windows 7 Computer

Just click on Event Viewer to open it.

Method 2

To open Event Viewer follow the steps below.

1. Click on Start

2. click on Control Panel

How to open Event Viewer in Windows 7

3. Click on Administrative Tools

Start Event Viewer in Windows 7

4. Click on Event Viewer


What is Event Viewer

Technology Blog

PING: Transmit failed. General Failure - Reasons and Solution

Yesterday while checking network connectivity I received one error message while trying to ping loopback address from my Windows computer. The error message I received is "PING: Transmit failed. General Failure" and all the packets send from command prompt were lost. I tried to ping a different loopback address but the result was same. I fixed the issue by following a set of steps and would like to share those troubleshooting steps with you hoping it may help in case if you experience the same error message PING: Transmit failed. General Failure.



This is the output I received when I ping loopback address.

C:\Users\sijugk>ping 172.0.0.21 

Pinging 172.0.0.21 with 32 bytes of data: 
PING: transmit failed. General failure. 
PING: transmit failed. General failure. 
PING: transmit failed. General failure. 
PING: transmit failed. General failure. 

Ping statistics for 172.0.0.21: 
   Packets: Sent = 4, Received = 0, Lost = 4 (100% loss) 

What is PING: Transmit failed. General Failure


Reasons and fix for PING: Transmit failed. General Failure


Major possible reasons for the error message  PING: Transmit failed. General Failure are:

  1. Misconfigured Firewall
  2. Outdated Network drivers or firmware
  3. DNS and other socket issues
  4. Other software or hardware errors

Solution for Ping: Transmit failed. General Failure

To solve "Ping: Transmit failed. General Failure" follow the steps below.
  1. Power Cycle the entire network :
    To know more about this step go to the link below.
    How to perform power cycle
  2. Command Prompt troubleshooting :

    Use the following command prompt commands to solve the issue.

    ipconfig/release

    ipconfig/renew

    ipconfig /flushdns

    netsh int ip reset c:\tcp.txt

    netsh winsock reset

    Type each commands on command prompt and press enter. After completing every commands reboot your computer.
  3. Disable Firewall (other security programs ) and check for the issue: Sometimes you may get this error message "PING: Transmit failed. General Failure" when firewall stops packets.
  4. Perform System Restore to last known good configuration
  5. Update the adapter driver: To perform this step follow the instructions provided in the link below.
    How to Update Adapter Driver from Device Manager
  6. Update the modem and router (if any) firmware

Just like this guide for "Ping: Transmit failed. General Failure" error message, we have a troubleshooting guide for some other important Internet connectivity error messages. They are:
Error 718: Connection was terminated

Above error message says about a state where the entire connection is terminated. However, if the modem fails to get a connection with remove host you will receive following error message.
Error 777 : Connection Attempt failed

Technology Blog

Error 718: The Connection was Terminated because the Remote Computer did not Respond in a timely manner

Yesterday night while trying to access Internet, I received one error message and failed to access Internet. The error message is " Error 718: The Connection was Terminated because the Remote Computer did not Respond in a timely manner". I am using Tata Photon Plus to access Internet from my laptop. Network Connection Prompt gives two options either redial or cancel the connection. I tried redial but right after the authentication process, I received the same Error 718. The error message seems like the modem is trying to authenticate the connection but the remove server/computer seems stopped responding to the modem request. This is how the error 718 message looks like.

How to solve Error 718: The Connection was Terminated because the Remote Computer did not Respond in a timely manner

Reasons for Error 718



The major reason for "Error 718:The Connection was Terminated because the Remote Computer did not Respond in a timely manner" is the modem driver issues. Either the modem driver we are using is outdated or misconfigured. We get this error message when our computer is expecting a reply/response from network and if it is failed to receive any in a timely manner, error 718 will be displayed. Another important cause for error 718 is the malfunctioning of remote server. If the remote server is not in a situation to accept new connections, clients will get error 718 message.

How to Solve Error 718



Some workarounds for error 718 is provided below.

1. Disconnect the modem and reconnect

2. Check the modem settings including ISP user name and password

3. Restart your computer and check for the issue

4. Update modem driver

5. Connect modem to a different computer and check whether the problem is with ISP

6. If the problem is with ISP, contact them to fix it.


Other Error Codes

1. Error 651: The Modem has Reported an Error

2. Error 777: Connection Attempt Failed

Technology Blog