>Only guesses based on what you wrote, but perhaps I'll get lucky.
>
>1. Can you successfully connect to sites using their IP addresses rather
>than their hostnames? If you can, you have a DNS problem. Possibly the
>nameserver entries you have are wrong - either the wrong addresses (check
>with the ISP) or entered incorrectly into resolv.conf (each line should be
>in the form "nameserver 192.168.23.42", with your ISP's nameserver address
>replacing the dummy one here).
Nope, neither url nor IP adress worked. But as all the other probs i
solved it by installing my Linux distrib totally new and installing a fresh
download of KDE1.1.1
Btw - it was asking always for a libstdc++.so.2.9, in /usr/lib were the
libstdc++.so.2.8 and libstdc++.2.9, last one from installing a
libstdc++.2.9.i386.rpm i fished from a Mandrake ftp. Still the
libstdc++.so.2.9 was missing making rpm create error messages. Finally i
told rpm just to ignore that and to install the packages i had. KDE1.1.1 is
working fine.
What are these libsdtc++ libs and what difference is between an so-version
and a non so-version ????
>
>2. Is the ppp0 interface set up as the default route? Check this with
>"route" or "route -n". If not, add this to the command-line call for pppd or
>its options file (or whatever kppp does).
I think that was the source for my former probs, i remember that i "played
around" with the ppp0 settings, good chance i messed it up.
>
>3. the ping test you report isn't definitive; I know that some ISPs have
>their routers set to block pings - this happened a year or more ago when
>pings were being used in denial-of-service attacks. Try traceroute instead.
Neither ping nor traceroute worked farther then to my ISP, but i know i
can ping / traceroute if i connect to the internet with W95, so i guess my
ISP supports it.
>4. Do your logs tell you anything helpful? (logs are usually
>/var/log/messages and /var/log/debug, but the actual names are installation
>specific, set up in syslog.conf .)
They told sth, but didn't help me with my prob, i checked them.
>
>5. Could there be a problem at the ISP? If you can telnet to a shell account
>at your ISP, see if you can ping, traceroute, telnet, etc. from it to the
>same hosts that you cannot reach from your Linux host. If you can't, the ISP
>is having a connectivity problem, not you. (This is a VERY remote
>possibility, one I usually don't bother to mention. But it does happen -- it
>has happened to me -- so you want to keep it at least at the back of your
>mind when you do this sort of troubleshooting.)
No, it was that i had tried out a SuSE evaluation 6.0 before and
everything worked fine, but i didn't like all the libs and compiler stuff
that were missing. So i switched back to RedHat (still SuSE is far easier
to install and to configure !) and "out of a sudden" it didn't work. It
worked fine before and during the probs occured it worked fine with my W95.
So i guess sth was cranky on my side.
>6. When you try to access the net, are you running as root? It's not good
>practice to do this routinely, but for troubleshooting, trying as root it a
>quick way to spot a permissions problem.
I was logged in as root. But this leads to another question, what is so
bad about being logged in as root and have access to the net ?
Anyways the problem is solved now, but thanks a lot Ray for giving advice.
:)))) Sorry that you spent time on it, but i'm horribly impatient in those
things, hehehe.
Greez
Dave
