Jump to content
Posted 15 August 2005 - 02:18 AM
Posted 15 August 2005 - 05:10 AM
Posted 15 August 2005 - 10:54 AM
Posted 20 August 2005 - 06:38 AM
Posted 20 August 2005 - 06:56 AM
Posted 20 August 2005 - 09:25 AM
Posted 15 October 2005 - 10:33 PM
Ok Dorothy...No problem...What we need to do is find out what your DNS setting should be. did your ISP provide you with details of your network setting?...
If So...you ned to check them against what you have setup at the minute..
If you get to a command prompt...this can be din by clicking on start then run which should give you an optiuon to type a programe name to run...
Into this you type CMD (if you are running XP....command if you are running 98)
This will give you a load of numbers relating to your ip address/gateway etc. It will also provide the address for your DNS servers. Ensure this is what has been advised by your ISP. Theymay not have given you the details if you use DHCP. If not dont worry. Simply make a note of the address of your DNS servers.
It May be at some point changes have been made to your network setup...so you need to ensure you have your IP setting on your network card set to pick up DNS from DHCP.
Go to control panel/network connections and select the card you are using. Right click and go to properties and highlight the tcp/ip value. slect properties for this and you should see a page which describes the config of your ip...whether automatic(DHCP) or manual settings. These should both be set to Automatic.
Can you try these and tell me if everything is as described ?....or if the entries are different from what Ive described?
Try rebooting all your equipment from the cable modem on up to the computer.
Shut everything off, then after about a minute start turning things back on starting with the cable modem, then the router, then the computer.
Posted 15 October 2005 - 11:02 PM
Posted 15 October 2005 - 11:14 PM
Posted 15 October 2005 - 11:36 PM
# Try later (after the cache entry has expired)
# Reboot your computer (which clears the DNS cache)
# Clear (flush) the DNS cache manually (run "ipconfig /flushdns")
# Turn off the "DNS Client" service entirely (hurts performance by requiring unnecessary lookups)
# Disable caching of unsuccessful ("negative") DNS lookups (the best method -- see below)
How to turn off unsuccessful ("negative") DNS caching
(Applies only to Windows XP and Windows 2000.)
Unsuccessful ("negative") DNS caching can be disabled by adding three Registry Values (NegativeCacheTime, NetFailureCacheTime, and NegativeSOACacheTime, all not normally present), setting them to zero. Since manual editing of the Registry is a tricky and risky business, I've provided a simple Registry script to do the job.
(Click the link to start the download; save the script to your desktop; and then double-click on it to run it. When you get "Are you sure you want to add the information..." dialog box, click Yes. The script can be tossed into the Recycle Bin after it has been run.)
There is no real downside to making these changes -- just delay if you make repeated tries to an invalid Internet name. (Nevertheless, please note that you use this script at your own risk, and that it's always a good idea to back up your Registry before making any change.)
* Works for dial-up too
Although it may not be as noticeable as on broadband, this problem can occur on dial-up as well, so turning off unsuccessful ("negative") DNS caching (as described above) is also recommended for dial-up.
* If you change your mind
To go back to Windows default behavior, simply remove the three Registry Values described above. Since manual editing of the Registry is a tricky and risky business, I've provided a simple INF script to do the job. (Click the link to start the download; save the INF file to your desktop; right-click on it, and then choose Install to run it. The INF file can be tossed into the Recycle Bin after it has been run.) (See note above before proceeding.)
0 members, 0 guests, 0 anonymous users