MODEM:- No bytes received!

I'm a novice user of linux. I have installed RedHat 9.01, and everything works fine except my modem.

I have Prolink 33.6 External Modem. It worked fine with 7.2 (when i tried Linux for the first time ever) and had no trouble configuring it. How that i have the latest one, I need to select the the COM port for myself and the query seems to work fine with the modem. I can even connect to the net, but I cant load even a single page from the Internet. Its just like connected to the internet but completely isolated when it comes to receiving bytes. Please help me, I dont know much of commands so please can anyone help me?

- deeps
deepeshpAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
jlevieConnect With a Mentor Commented:
Can you now execute 'host www.redhat.com" and get an IP back?

Note that the contents of /etc/ppp/resolv.conf will be re-created each time you dial up. So if you've dropped the connection and brought it back up you have to redo the edit.
0
 
jlevieCommented:
Is DNS being properly set up when you connect as evidenced by 'host www.redhat.com' returns an IP?

Can you 'ping' an Internet site?

It might help for you to show us what:

ifconfig -a
netstat -nr
cat /etc/resolv.conf

shows when you go on-line.
0
 
deepeshpAuthor Commented:
Thanks jlevie,

While issuing the ping, no result is obtained... not even the error message, so I aborted it using Ctrl+C and as per other things, I've done exactly as you've asked me to... and here are the respective results:

[root@localhost root]# ifconfig -a
lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:2809 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2809 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:191209 (186.7 Kb)  TX bytes:191209 (186.7 Kb)
 
ppp0      Link encap:Point-to-Point Protocol
          inet addr:203.78.165.51  P-t-P:203.78.160.2  Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:4 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:3
          RX bytes:256 (256.0 b)  TX bytes:150 (150.0 b)


[root@localhost root]# netstat -nr
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
203.78.160.2    0.0.0.0         255.255.255.255 UH        0 0          0 ppp0
169.254.0.0     0.0.0.0         255.255.0.0     U         0 0          0 lo
127.0.0.0       0.0.0.0         255.0.0.0       U         0 0          0 lo
0.0.0.0         203.78.160.2    0.0.0.0         UG        0 0          0 ppp0



[root@localhost root]# cat /etc/resolv.conf
domain info.com.np              #kppp temp entry
nameserver 203.78.160.36        #kppp temp entry
nameserver 203.78.160.3 #kppp temp entry

Now what shall I do?
- Deepesh

0
Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
jlevieCommented:
Let's try:

ping -n 203.78.160.2
ping -n 203.78.160.36
ping -n 203.78.160.3

What I'm trying to find out there is whether you can reach anything on the PPP link. The first ping will go to the next hop in the PPP link and the other two check for the name servers being reachable.

According to the ifconfig output the link is up & running, with no errors. A default route & nameservers were negotiated, which suggests that basic IP connectivity exists. Now we need to figure out what the failure is.

0
 
deepeshpAuthor Commented:
This is what it looked like when I did exactly as you direct...

[root@dialup-pool3-174 root]# ping -n 203.78.160.2
PING 203.78.160.2 (203.78.160.2) 56(84) bytes of data.
64 bytes from 203.78.160.2: icmp_seq=1 ttl=255 time=224 ms
64 bytes from 203.78.160.2: icmp_seq=2 ttl=255 time=199 ms
64 bytes from 203.78.160.2: icmp_seq=3 ttl=255 time=198 ms
........
<I pressed Ctrl+C>

--- 203.78.160.2 ping statistics ---
7 packets transmitted, 6 received, 14% packet loss, time 6094ms
rtt min/avg/max/mdev = 179.987/196.546/224.499/14.193 ms


[root@dialup-pool3-174 root]# ping -n 203.78.160.36
PING 203.78.160.36 (203.78.160.36) 56(84) bytes of data.
........
<No activity, so I pressed Ctrl+C>
 
--- 203.78.160.36 ping statistics ---
14 packets transmitted, 0 received, 100% packet loss, time 12999ms
 
[root@dialup-pool3-174 root]# ping -n 203.78.160.3
PING 203.78.160.3 (203.78.160.3) 56(84) bytes of data.
64 bytes from 203.78.160.3: icmp_seq=1 ttl=253 time=188 ms
64 bytes from 203.78.160.3: icmp_seq=2 ttl=253 time=199 ms
64 bytes from 203.78.160.3: icmp_seq=3 ttl=254 time=179 ms
........
<I pressed Ctrl+C>
 
--- 203.78.160.3 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3038ms
rtt min/avg/max/mdev = 179.987/189.430/199.679/7.001 ms
[root@dialup-pool3-174 root]#


So what do you think could be the problem...?

With thanks
- Deepesh
0
 
jlevieCommented:
Your resolv.conf contains, in part:

nameserver 203.78.160.36        #kppp temp entry
nameserver 203.78.160.3 #kppp temp entry

and the ping tests indicate that the first nameserver listed (203.78.160.36) isn't reachable. Everything else worked and if you manually edit resolv.conf so that it looks like:

domain info.com.np              #kppp temp entry
nameserver 203.78.160.3 #kppp temp entry

I think you'll find that Internet access will work. This is really a problem at your ISP in that they should not be handing out (via PPP) the IP of a nameserver that isn't usable.
0
 
deepeshpAuthor Commented:
The /etc/resolv.conf is empty... however The /etc/ppp/resolv.conf had something like u told..

i did as u said... but nothing has changed....
All i can see is "Sending request to..... my url" and nothing happens even if wait for minutes...

what could be the reason?

Thanks again
- Deepesh
0
 
deepeshpAuthor Commented:
Dear jlevie

Thanks for your support.

- Deepesh
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.