Having Internet Problem with some web pages

Hi, just bought a Belkin ADSL Router which is spot on as i can use my laptop & main desktop at the sametime if more than one person wants to access the net. After a gruling 2 days of getting the network to work i was made up , as i have AOL broadband which is one of the worst to setup. Now i can see the laptop and vice versa and acces the net, But some pages don't load, just timeout & go to the famous refresh screen. So what can cause that problem?? I have a ZA as a firwall & i know the router has it own Firewall, & i'am using Nortons Anti-virus as well.


Can anyone shed some light why somepages laod & are ok, and some don't???


Cheers

just an idea although probably not it: go to your itnernet explorer properties>connection tab>advanced proxy settings>make sure that the "automatically detect proxy settings" is disabled

I don't think it's that as i'am using a LAN. I don't it is anything to do with me Firewall, or Perrguardian as i've turned both of them off. It has to be a setup somewhere as both IE & Firefox don't load these web pages. Could it be the setup on my router as it is auto detect??? Plus some pages work and some don't.

ok this is what it says exactly:--




Connection Failure Error

Net Timeout Error

Redirect Loop Error

Unknown Socket Error

Net Reset Error

Offline Error
The connection was refused when attempting to contact ad.uk.doubleclick.net.

The address (URL) is not a valid format and cannot be read. A typical address will start with "http://", followed by an address, (e.g. www.netscape.com), followed by a path to the content (or just "/"). A common cause for the problem is using backslashes(\) instead of forward slashes (/).

The file specified by the address (URL) cannot be found. Check that the file exists and that you have sufficient permissions to view it.

The address (URL) does not correspond to a known site and could not be loaded. This could be due to a misspelling in the address or because the site does not exist. If the address is known to be valid, or if the problem occurs for many sites, it may be an issue with your proxy service (if you use one) or the directory name service lookup. In such cases you should consult your system documentation, administrator or Internet Service Provider (ISP) as appropriate for further assistance.

The address (URL) starts with a protocol that is not recognised by the browser. A protocol is the part at the front of the address, such as http: or ftp: which tells the browser how to connect to the site. In this instance, the protocol is unknown so loading cannot continue. Check that the address is correct before retrying.

The browser was unable to connect to the specified site, even though it exists. This may be because the site does not accept connections from your computer, the service may be down, or the site does not support the service or port that you tried to connect to.

The browser timed out while trying to connect to the specified site. The site may be experiencing high loads that are slowing it down, or network problems are preventing data from being received from it in a timely manner. If the site is likely to be busy, consider waiting a few moments before retrying the request.

The browser has stopped a connection because the site is redirecting requests to itself in a manner which prevents it from ever completing.

The site responded to the network request in an unexpected manner. This may be due to address (URL) using the wrong protocol for the specified port, or a non-standard configuration on the site which is running different services than expected.

The link to the site was dropped unexpectedly while negotiating a connection or transferring data. This may be due to a network fault somewhere between the site and your computer. If the problem persists, consult your system documentation, administrator or Internet Service Provider (ISP) as appropriate for further assistance.

The browser is currently offline and cannot connect to the requested site. Place your browser in online mode before trying again.

Try again

sorted something to do with the settings of the router.