Printable View
i have installed knoppix to hdd, installed nforce2 drivers, configured adsl connection...
one problem... i can't browse web pages through mozilla or konqueror.
then i pinged my internet provider everything was ok.
please help me to connect to internet normally!
to me this looks like a nameserver related problem.
what doessay?Code:cat /etc/resolv.conf
that is, open a console (that screen icon on thew bottom of the screen) and type the line above.
I didn't get that impression by what linukas had said, but it all depends on what he meant by pinging his internet provider.Quote:
Originally Posted by OErjan
linukas, what did you do when you got a good ping? Did you ping an IP address (as in ping 123.100.200.245) or did you ping a URL (as in ping myIPS.com)/ And if you did ping the IP address, how did you determine what IP address to use?
command "cat /etc/resolv.conf" shows: nameserver 212.59.0.2
nameserver 212.59.0.1
Situation is, that i can't ping any normal web site, such as www.yahoo.com etc.,
but i can ping providers ip 213.190.60.19, wich gives me a ip address.
but thiers another problem i can't ping these two address 212.59.0.2, 212.59.0.1.
this is some information
root@kompas:~# ifconfig ppp0
ppp0 Link encap:Point-to-Point Protocol
inet addr:82.135.133.111 P-t-P:213.190.60.19 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1
RX packets:38 errors:0 dropped:0 overruns:0 frame:0
TX packets:23 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:2374 (2.3 KiB) TX bytes:1609 (1.5 KiB)
root@kompas:~# /sbin/route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
213.190.60.19 * 255.255.255.255 UH 0 0 0 ppp0
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
default 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
and here is some lines from file "/var/log/PPP_CONNECT_ERRORS"
pppoe: read (asyncReadFromPPP): Session 3319: Input/output error
pppoe: Timeout waiting for PADS packets
***
pppoe: read (asyncReadFromPPP): Session 3537: Input/output error
pppoe: read (asyncReadFromPPP): Session 4069: Input/output error
pppoe: Timeout waiting for PADS packets
pppoe: read (asyncReadFromPPP): Session 4480: Input/output error
pppoe: Timeout waiting for PADS packets
***
pppoe: read (asyncReadFromPPP): Session 4657: Input/output error
pppoe: read (asyncReadFromPPP): Session 4995: Input/output error
pppoe: read (asyncReadFromPPP): Session 6381: Input/output error
pppoe: read (asyncReadFromPPP): Session 7946: Input/output error
pppoe: read (asyncReadFromPPP): Session 1765: Input/output error
pppoe: read (asyncReadFromPPP): Session 1961: Input/output error
pppoe: read (asyncReadFromPPP): Session 2569: Input/output error
pppoe: Timeout waiting for PADS packets
***
pppoe: read (asyncReadFromPPP): Session 2985: Input/output error
pppoe: read (asyncReadFromPPP): Session 3075: Input/output error
*** this sign means that i deleted same lines like above
Maby something is wrong with my ethernet card (nforce2)
Help me please...
This does look like it might be a DNS issue. Can you ping 68.142.226.44 ? That is the IP address that www.yahoo.com translates into.Quote:
Originally Posted by linukas
OK, that is strange, maybe it's not a DNS issue. I can ping those two addresses. What are they, why did you select them as addresses to ping that you thought were worth mentioning when they didn't reply for you? Can you run a trace route to any of the IP addresses we've been discussing?Quote:
Originally Posted by linukas
can't ping 68.142.226.44, and other address...
in another forum said that these two adress belongs for LithuaninaTelecom (my internet provider) 212.59.0.2, 212.59.0.1.
i'm a newbie in linux and i don't understend what to do, please explain me...Quote:
Originally Posted by Harry Kuhman
This is confusing because in your first post you said:Quote:
Originally Posted by linukas
If you could ping then I would say it's not a hardware issue; ping needs to be able to send and receive packets and if the hardware can do that for a ping it should be able to do it for other packets too. But if you can't ping any IP addresses then there could be a hardware or driver problem (or software stack problem). I don't understand exactly what does and what does not work for your system, as there seems to be a conflict in the above two quotes.Quote:
Originally Posted by linukas
Trace route is a networking technique that determines what other IP addresses are in the route between you and the address that you pinged. If some pings work and not others, looking at the trace route might help to determine where the ping is getting lost. But if you can't ping anything then it's not going to help. By the way, this is not a Linux concept; there are many tools that will do it for Windows, including a command line tool that, unless removed, is on all Windows systems.Quote:
Originally Posted by linukas