In Feburary 2016 14,
Find out whether you can view any web pages. Open Internet Explorer and type in the address of a site with which you are unfamiliar. If you need an idea, look around the room and type in a brand name you see, such as 'Sony.com' or 'Saltines.com.' The reason for this is that if you have recently visited a site, the 'cached' files might appear on your screen and not provide an accurate determination. If you are able to see a new site, the issue is likely with the website you are trying to visit.
Check the connection to the modem or router. If you are unable to view any web pages, your connection might have been lost. Check physical connections to see if anything is unplugged. If you are using a wireless connection, verify that it is still working.
Unplug the modem. Pull both the power cord and the phone line or Ethernet plug out of the back of the modem and leave it alone for a few minutes. Plug the cords back in and allow it to power up completely. Try the connection again.
Contact your Internet service provider. A cable, DSL or phone line outage is a common cause for connectivity issues.
Delete Internet Explorer's history. Close any open applications and open a new Internet Explorer window. Click 'Tools' and then click 'Delete Browsing History.' Click each 'Delete' button, except passwords if you allow IE to retain them for you.
In Feburary 2016 14,
Showing posts with label issue. Show all posts
Showing posts with label issue. Show all posts
Sunday, 14 February 2016
Friday, 12 February 2016
How Does a 404 Error Occur?In Feburary 2016 12,
In Feburary 2016 12,
A '404 Error' appears when a person trying to get to a website or URL but the site is unavailable or unreachable. This error may also manifest in different appearances on the web page, depending on the way the website administrator programs the error to appear to the users. Aside from 'Page cannot be displayed,' it can also appear as 'Page cannot be displayed,' '404-Page not Found,' 'Error 404: Not Found,' 'The page cannot be found' or 'HTTP 404- Not Found.' Aside from the error messages, the error page may have additional information indicating the possible cause and resolution.
Causes
There are different reasons why a website becomes unreachable or unavailable, possibly due to a problem on the web server hosting the website or a possible problem with the link or URL. Another possibility would be a network connection issue between the web server and the user's computer. It is also possible that certain components within the web server that is hosting the site is having issues, such as services and web instances not running that the website is depending on to run normally.
Troubleshooting
The common resolution suggested by technical support or programmers would be to do the simplest thing, often suggested on the error page itself, which is to refresh the screen by hitting the refresh button on the web browser menu bar. This will allow the web browser to try to reconnect to the website that is having issues. Oftentimes, companies that host websites have redundant servers in place to provide minimal disruptions, after hitting refresh the other server or servers in the pool will process the request in order to display the website. Another way to solve the 404 Error code is to make sure that the website spelling is correct. The cause may be a typing error by misspelling or missing letters or symbols. By typing the correct URL or link to the website, the error code will disappear and will lead to the correct web page. Sometimes, if the error does not go away, it is best to wait patiently until the problem disappears. This is often the case when a web site may be experiencing technical difficulties and a user has no control over the situation. Most reputable webhosting companies already know the problem before the users do; therefore, they may already be hard at work to resolve the problem. If the wait is taking much longer as anticipated, it is best to call the webmaster or webhosting services to report the problem or find out the status of the problem. Technicians supporting the websites may need to restart services, recycle web instances or reboot the web server to resolve the problem. If the website is corrupt or it needs the programmer to rebuild it again may take several hours to resolve. If the web server is broken, support technicians may need to repair or replace the broken parts or replace the entire server with another one. It is best practice for webhosting companies operate with redundant pairs in order to minimize disruption of service or to provide uninterrupted service. If the problem is due to network connectivity, support technicians will have to fix the network connections first before the website can come back up.
In Feburary 2016 12,
A '404 Error' appears when a person trying to get to a website or URL but the site is unavailable or unreachable. This error may also manifest in different appearances on the web page, depending on the way the website administrator programs the error to appear to the users. Aside from 'Page cannot be displayed,' it can also appear as 'Page cannot be displayed,' '404-Page not Found,' 'Error 404: Not Found,' 'The page cannot be found' or 'HTTP 404- Not Found.' Aside from the error messages, the error page may have additional information indicating the possible cause and resolution.
Causes
There are different reasons why a website becomes unreachable or unavailable, possibly due to a problem on the web server hosting the website or a possible problem with the link or URL. Another possibility would be a network connection issue between the web server and the user's computer. It is also possible that certain components within the web server that is hosting the site is having issues, such as services and web instances not running that the website is depending on to run normally.
Troubleshooting
The common resolution suggested by technical support or programmers would be to do the simplest thing, often suggested on the error page itself, which is to refresh the screen by hitting the refresh button on the web browser menu bar. This will allow the web browser to try to reconnect to the website that is having issues. Oftentimes, companies that host websites have redundant servers in place to provide minimal disruptions, after hitting refresh the other server or servers in the pool will process the request in order to display the website. Another way to solve the 404 Error code is to make sure that the website spelling is correct. The cause may be a typing error by misspelling or missing letters or symbols. By typing the correct URL or link to the website, the error code will disappear and will lead to the correct web page. Sometimes, if the error does not go away, it is best to wait patiently until the problem disappears. This is often the case when a web site may be experiencing technical difficulties and a user has no control over the situation. Most reputable webhosting companies already know the problem before the users do; therefore, they may already be hard at work to resolve the problem. If the wait is taking much longer as anticipated, it is best to call the webmaster or webhosting services to report the problem or find out the status of the problem. Technicians supporting the websites may need to restart services, recycle web instances or reboot the web server to resolve the problem. If the website is corrupt or it needs the programmer to rebuild it again may take several hours to resolve. If the web server is broken, support technicians may need to repair or replace the broken parts or replace the entire server with another one. It is best practice for webhosting companies operate with redundant pairs in order to minimize disruption of service or to provide uninterrupted service. If the problem is due to network connectivity, support technicians will have to fix the network connections first before the website can come back up.
In Feburary 2016 12,
Thursday, 11 February 2016
DNS Problems with VistaIn Feburary 2016 11,
In Feburary 2016 11,
DNS problems frequently originate in the cache. Over time, the DNS cache can become corrupted causing issues with the DNS in Vista. In order to clear the cache and thus resolve the problems, a command prompt must be launched as an Administrator. Once the command prompt loads, simply type 'ipconfig /flushdns' to clear the DNS cache.
No Connection Without Router Reboot
Many Windows Vista users report DNS problems initially establishing a DHCP (Dynamic Host Configuration Protocol) connection with their router. A workaround to this issue is to simply manually reboot the router to which the Windows Vista machine is attempting to connect. This clears the DNS addresses and submits a new address to the computer. If it is a desktop computer, another solution is to manually input the DNS addresses that the computer will use.
Conflicts with Wireless Card or Ethernet Controller Checksum Offload
Windows Vista is not compatible with some features that are bundled with popular wireless cards and Ethernet controllers. In particular, checksum offload features can cause problems when Vista attempts to renew a DNS address once connected to the Internet. To resolve these issues, simply disable the checksum offload feature.
Firmware Problems
Many Vista DNS problems can be solved by simply updating the firmware of the router. The firmware is the software that operates on the router. If an old version of the firmware is currently installed, this will cause problems with Windows Vista. Windows Vista utilizes an improved TCP/IP (Transmission Control Protocol/Internet Protocol) stack procedure that calls DNS addresses in a different manner than Windows XP. These updates to the TCP/IP stack procedure necessitate having the latest router firmware installed.
Conflicts with LAN Connection
If Windows Vista is used to connect to the Internet via both a wired LAN connection and a Wi-Fi wireless connection, it is possible that the wired LAN connection could create problems when attempting to attain a DNS address through a Wi-Fi wireless connection. This problem arises because the wired LAN connection, even when disconnected, is assigned an IP address if it has been used in the past. This presents difficulties when Vista attempts to connect to the Internet on a wireless connection since it prefers the faster, wired connection. To solve this, simply disable the LAN connection when using the computer in a wireless setting.
In Feburary 2016 11,
DNS problems frequently originate in the cache. Over time, the DNS cache can become corrupted causing issues with the DNS in Vista. In order to clear the cache and thus resolve the problems, a command prompt must be launched as an Administrator. Once the command prompt loads, simply type 'ipconfig /flushdns' to clear the DNS cache.
No Connection Without Router Reboot
Many Windows Vista users report DNS problems initially establishing a DHCP (Dynamic Host Configuration Protocol) connection with their router. A workaround to this issue is to simply manually reboot the router to which the Windows Vista machine is attempting to connect. This clears the DNS addresses and submits a new address to the computer. If it is a desktop computer, another solution is to manually input the DNS addresses that the computer will use.
Conflicts with Wireless Card or Ethernet Controller Checksum Offload
Windows Vista is not compatible with some features that are bundled with popular wireless cards and Ethernet controllers. In particular, checksum offload features can cause problems when Vista attempts to renew a DNS address once connected to the Internet. To resolve these issues, simply disable the checksum offload feature.
Firmware Problems
Many Vista DNS problems can be solved by simply updating the firmware of the router. The firmware is the software that operates on the router. If an old version of the firmware is currently installed, this will cause problems with Windows Vista. Windows Vista utilizes an improved TCP/IP (Transmission Control Protocol/Internet Protocol) stack procedure that calls DNS addresses in a different manner than Windows XP. These updates to the TCP/IP stack procedure necessitate having the latest router firmware installed.
Conflicts with LAN Connection
If Windows Vista is used to connect to the Internet via both a wired LAN connection and a Wi-Fi wireless connection, it is possible that the wired LAN connection could create problems when attempting to attain a DNS address through a Wi-Fi wireless connection. This problem arises because the wired LAN connection, even when disconnected, is assigned an IP address if it has been used in the past. This presents difficulties when Vista attempts to connect to the Internet on a wireless connection since it prefers the faster, wired connection. To solve this, simply disable the LAN connection when using the computer in a wireless setting.
In Feburary 2016 11,
Tuesday, 9 February 2016
How to Disable Sites in Apache 2In Feburary 2016 09,
In Feburary 2016 09,
Verify that the site is still enabled. From the Ubuntu Linux command line, issue the following commands:cd \etc\apache2\sites-enabledlsThe first command switches the working directory to the 'sites-enabled' sub-directory. The second command lists the files in the directory. If there is a file for the site you want to disable, continue with Step 2. If not, the site already is disabled.
Issue the following commands at the Ubuntu command prompt:cd (changes to your home directory)sudo a2dissite sitename (where 'sitename' is the name of the site you want to disable) This command removes 'sitename' from the /etc/apache2/sites-available sub-directory.
Verify that the site has been removed from the list of enabled sites with the following command:ls /etc/apache2/sites-enabledYour site should not appear in the sub-directory listing.
Restart the Apache 2 Web server with the following command:sudo /etc/init.d/apache2 restartThis causes Apache 2 to stop listening for requests for the disabled site.
Start a browser session and attempt to navigate to the site. If your site is disabled, you should get a 'Not Found' message on a default error page.
In Feburary 2016 09,
Verify that the site is still enabled. From the Ubuntu Linux command line, issue the following commands:cd \etc\apache2\sites-enabledlsThe first command switches the working directory to the 'sites-enabled' sub-directory. The second command lists the files in the directory. If there is a file for the site you want to disable, continue with Step 2. If not, the site already is disabled.
Issue the following commands at the Ubuntu command prompt:cd (changes to your home directory)sudo a2dissite sitename (where 'sitename' is the name of the site you want to disable) This command removes 'sitename' from the /etc/apache2/sites-available sub-directory.
Verify that the site has been removed from the list of enabled sites with the following command:ls /etc/apache2/sites-enabledYour site should not appear in the sub-directory listing.
Restart the Apache 2 Web server with the following command:sudo /etc/init.d/apache2 restartThis causes Apache 2 to stop listening for requests for the disabled site.
Start a browser session and attempt to navigate to the site. If your site is disabled, you should get a 'Not Found' message on a default error page.
In Feburary 2016 09,
Subscribe to:
Comments (Atom)