nslookup is a command-line tool that helps in finding the DNS records of a website. It sends a name server query to the DNS and obtains the corresponding IP address. Aside from that, it can also perform some complex functionality such as finding details about FTP server, Mail server and many more but most of them are used by administrators. The best thing about nslookup is that it queries the DNS server directly and it does not rely on the cache.
On the other hand, there is another tool called PING that is used to verify connectivity. PING sends a packet of information to the IP address or Domain and gets back a response in the form of packets. So if everything goes well, all packets are received but if not, it will help you find out where the delay in the network exactly is. However, the ping command does not always attempt a DNS lookup which means that it might be using the DNS cache and use the IP address available in that table.
Although both nslookup and PING help you in identifying the host or IP address, however, they don’t always work and sometimes fail. So if your nslookup works but ping fails on your Windows 10 PC when querying the IP address of a website then it could be caused by many reasons. It could be that the nslookup queries work for you but when you try to use PING, it fails. For instance, if you open the abc.com website, here’s how it will look like:
C:> ping xyz.com
Ping request could not find host xyz.com. Please check the name and try again.
The domain is converted into an IP address and then data is sent to that IP address when you use PING. So when a reply comes back it means that the data is going back and forth to that domain without any problem. However, if the DNS fails to resolve the IP address of the website or if your PC does not attempt a DNS lookup, you will receive a similar error message that says, “Could not find host” and so on. To resolve this issue, here are some options that might help.
Resetting Winsock, TCP/IP, and flushing DNS might help you resolve the issue with nslookup and PING. To do so, follow these steps:
If your computer has more than one NIC connected and there are multiple default gateways, then it will most likely create confusion which is why you need to remove the default gateway from the configuration of all NICs and make sure that there is only one default gateway.
You might want to change your DNS to Google Public DNS as it could also help you in fixing the nslookup and PING issues. To do so, follow the steps below.
You can also try to cross-check the Windows Hosts file to find out if the website you are trying to open has been blocked, because if it is, then it’s no wonder why PING fails even when nslookup works. There are instances when some third-party application modifies the file and adds some websites to the blocklists. So if the website is indeed blocked, you need to remove it from the list.
Deleting the WLAN Profiles might be a good idea if you are not able to connect to the internet on your computer and if you’re using Wi-Fi. It could be that the networks that were connected previously have gone rogue which is why it is not connecting properly. And so deleting the WLAN profiles might help you in fixing the issue with nslookup and PING.
This error code occurs when users fail to activate their Windows operating system. It is one of the more popular Windows error codes since it affects many versions of Windows including Windows 7, Windows 8.1, and Windows 10. Error code 0x8007007b has common symptoms which include the following:
Windows error codes such as Error code 0x8007007b can be a complicated issue, requiring the use of technical knowledge and skills. For this reason, we have listed instructions in the simplest of forms to enable even average users to successfully complete manual repair methods that will resolve error code 0x8007007b.
This method involves the use of a Multiple Activation Key (MAK) instead of the Key Management Service (KMS) to activate the Windows operating system you intend to use on your PC. This manual repair method requires the use of Command Prompt so ensure you follow the instructions provided carefully so as to avoid the risks of causing harm to your system.
Attempt to activate your Windows installation once you’ve completed the exact instructions above. If you are unable to complete this process, consider getting help from a Windows repair technician or simply move to the next manual repair method listed below.
System File Checker (SFC) enables Windows users to scan and repair errors or corruption on system files. Since such errors within your system files can cause error code 0x8007007b to occur, follow the steps below to fix this error code.
The System File Checker tool will begin scanning your machine for corrupted or missing files in need of repair. If these files are found on your system, the tool will repair and replace them. Once this is done, restart your computer then check to see if you can now activate your Windows operating system.
If you wish to always have at your disposal a utility tool to fix these Windows 8 and other related issues when they do arise, download and install a powerful automated tool.
Error Code 0x8007000b has appeared on Windows operating systems from Windows 10 all the way back to Windows XP. In most cases, it occurs when there is a problem within the transaction log for the filing system within Windows.
Common symptoms include:
There are several different ways that you can attempt to resolve the problems that cause Error Code 0x800700b to appear on your operating system. Several of these methods are pretty easy for basic users, but others require some comfort and knowledge in working with advanced tools on your operating system.
If the methods below do not completely resolve the appearance of Error Code 0x800700b on your Windows operating system or if you are not confident in your ability to undertake these steps on your own, you may need to get in touch with a qualified computer repair professional to assist you with the error resolution process. If this error message is not resolved, you could expose your computer to other error codes such as error code 80070103.
The primary cause for Error Code 0x800700b is that there is an issue or corrupt entry in the transaction log for the file system within Windows. This makes it impossible for Windows to complete the Windows Update process. Although the error message states that an unknown error has been encountered, it is usually fairly simple to resolve the appearance of faulty or corrupt entries in the transaction log if you follow the steps below to complete.
There are several ways that you can attempt to resolve Error Code 0x800700b manually on your Windows operating system. At least one of these methods requires some advanced knowledge or skill in using the command prompt, so if you aren’t confident in your ability to follow these steps through to completion, be sure to get in touch with a qualified computer repair technician who can help you to resolve the error.
Here are the top three methods that can be used to resolve Error Code 0x800700b on your machine:
To clear and reset the entries in your transaction log, there are a few simple steps that you should follow:
An alternative method to resolving Error Code 0x800700b is to open and run the System Update Readiness Tool on your machine. This program runs a scan on your Windows operating system to determine whether it is ready for updates, attempting to resolve any errors it encounters along the way.
After you have scanned and run this tool, you should always take the time to restart your computer before attempting to perform the update process, so that any changes made can be successfully applied to your computer.
The System File Checker is a tool for Windows that runs a basic scan for problem files and attempts to resolve them. To run this tool, follow these steps:
This tool should tell you what the specific issues are so that you can resolve them. It may give you a message that the action couldn’t be performed, that corrupt files were fixed, or that corrupt files were encountered, but could not be fixed automatically.
Some users wanting to upgrade to Windows 10 from Windows 7 or Windows 8.1 experienced errors with installation. One of these errors is CPU Not Compatible. When you click and run the “Get Windows 10” from your system tray bar, you’ll receive the “CPU is not compatible with Windows 10” error. When this happens, it might be good to check if there’s a bug or if your NX feature (a requirement for the Windows 10 installation) is enabled.
The “CPU is not compatible with Windows 10” error normally occurs when:
To successfully upgrade to Windows 10, your CPU must support Physical Address Extension (PAE), SSE2, and NX features. If any of these features are not activated on your system, it’ll cause the CPU not compatible error. However, some users still reported experiencing this error even though their CPU has these features activated. Normally, this is due to the bug that Windows acknowledged.
If any of these two scenarios apply to your computer, the following methods will help you fix the problem:
The bug applies to some Windows 7 and Windows 8.1 systems. The bug occurs when the “Get Windows 10” app fails to recognize CPUs as being compatible. This produces a false negative result with a message, “Here’s why Windows 10 cannot be installed on this PC: The CPU isn’t supported”. To fix this bug, Microsoft released an update.
Unfortunately, the patch update (KB2976978 for Windows 8/8.1 and KB2952664 for Windows 7 SP1) to fix the bug may not be automatically downloaded to your computer. If this is the case, you need to verify first if the patch was installed correctly. To do this, follow the steps below:
A major requirement for Windows 10 upgrade is for the CPU to have Physical Address Extension (PAE), SSE2, and NX features enabled on your system. If you receive the CPU not compatible error, one possible cause is that any of the mentioned features are not available OR not enabled on your system. Here’s how you can fix this:
If changing the settings in your BIOS doesn’t do the trick, your final option is to force enable the NX bit in your Windows system. However, this is only applicable IF and ONLY IF your CPU does support it. To force enable NX bit, do the following: