connected but could neither surf nor ftp

[abtimoteo]

1. i have a new installation of zipslack v10.0, which i transferred to a linux partition from drive c: using the installation method prescribed in faqs accompanying the installation files.

2. to download and install xfree86 and many other software packages, i set up an internet connection using pppsetup.

3. when i ran ppp-go, i got the following:

root@zipslack:/# Serial connection established
Using interface ppp0
Connect ppp0 <--> /dev/ttyS1
PAP authentication succeeded
local IP address xxx.xxx.xxx.xxx
remote IP address nnn.nn.nn.nnn
Local: xxx.xxx.xxx.xxx -> Remote: nnn.nn.nn.nnn ppp0

i assume the above means i got connected.

4. but when i did this: root@zipslack:/# links http://www.mozilla.org.
i got this: Error Host not found Cancel

5. and when i did this: lftp www.mozilla.org.
i got this: open 'www.mozilla.org' [Resolving host address... ]. that was how far i could go. after waiting for a long time, i just pressed ctrl+c, assuming that there was a problem.

6. can somebody please tell me where the problem lies? with the above, it looks like that i really got connected but i could neither surf nor ftp. thanks in advance!

[sarumont]

Check your /etc/resolv.conf and make sure that you have some nameservers in it. Also, see if you can ping IPs. Google's is 216.239.39.99. If you can ping that, then you have invalid nameservers (or none). If not, then you are not properly connected.

[abtimoteo]

1. resolv.conf looks ok with the following lines:

search my_isp.com
nameserver xxx.xx.xx.xx

2. pinged google.com with the following results:

PING 216.239.39.99 (216.239.39.99) 56(84) bytes of data.
From 202.78.97.142 ICMP_seq=1 Unreachable, Bad Code: 9

x packets trasmitted, 0 recieved, +x errors, 100% packet loss, time ....

something is wrong, i believe.

3. anyway, i ran pppsetup again using login details to another isp. this enabled me to surf using links and to ftp with lftp.

i guest the problem lies with my first isp because i ran pppsetup several times and tested the results with it. no luck! it is only when i tried another isp that i got things right.

4. thanks for the reply, sarumont.

[sarumont]

Glad you got it working (and that you had another ISP to use). If you get a chance to talk to intelligent tech support from your first ISP and figure out what was going wrong, I'd be interested to know.