There has been a great deal of discussion about this problem but never with any resourceful results.

The common problem shared by myself and a few others with SuSe 9.0 + is that we use Qwest/Actiontec DSL Gateway boxes and for some reason we have a reoccurring problem with either constant timeouts on sites such as google, or odd instances such as I had with this site pertaining to a 'phantom' display that when loaded only shows a blank white page with missing images. It usually hangs at the point when it is 'connecting' to the google ad service.

Another common denominator, is that it seems that if a site has redirect links, ad links, or anything that may cause a slight delay, the browser (no matter if you use Mozilla, Konq, Firefox..etc..) times out.

There were a couple of solutions to this in earlier versions of SuSe, however for the most part, after trying both methods, they yielded no positive results.

I have been quite depressed that I have for the good part of the day had to use XP to visit web sites in general because of this problem with SuSe.

If there is anybody with a solution, you would not only be helping myself, but probably many others that are in the same situation.

A thanks in advance is in order, and hopefully I can get SuSe back to its full potential.

The only reason that I was even able to post this message, is that I switched to windowmanager, and was lucky enough to have a stored link cached.

Did you try, in the first place, to check if this problem occurs in another distros? Maybe trying a livecd would let you see where the problem may be.
It's simpler to find what kind of dns/network the other distor uses, to try to install in in suse 9.0.

Concerning dsl setups, its quite mainstream. There should be no problem on suse connecting it.

There are alot of factors that are mostly SuSe related toward the DSL problem. I am very quite familiar with the whole DNS and connection scheme with SuSe, and yes it is mainstream and pretty much self explanatory.

The situation pretty much presents a scenario that points to the actual DSL box, rather than SuSe. With Suse, a configuration of using PPOE or PPOA is an option, however since the box already contains that information than the only needed thing to configure in Suse is the eth0 for my network card which has been done.

Basically what is happening is that I have two systems on a collision course with one another. The box contains firewall settings, DNS, actual connection, username and password..etc..It can be configured to be a DNS server, a DHCP server, Wireless server..etc...
When Suse goes to connect to the net, a timeout can occur because the box is already sending out the information, than Suse right behind it.
There are several "fixes" that have not worked because for the most part they were earlier versions of SuSe and a simple config line was all that was needed to be changed in most cases.

This has become a pretty wide spread problem with SuSe 9.0 and 9.1 so it is nothing remote by any means. I have been in contact with quite a few people with this same problem and switching distros actually worked for them, so in essence, there is something that SuSe needs to clear up for the next release or update if it can actually be reached. (another problem many SuSe9.1 users are having currently in which YOU times out)