A problem with dial-up connection

colorpurple21859 · 09-09-2009, 10:24 AM

do you have call waiting. the error message suggest a phone is off the hook, call waiting service, or telephone line problems

siaswar · 09-11-2009, 08:24 PM

Quote:

Originally Posted by j_jerry

good, I really appreciate you for not giving up.

Can you post your wvdial.conf

Also please describe a bit about your isp

As you're using dial-up, make sure your telephone cables are ok. You can test this if you have a windows or other os box, make sure it's fine

Well, I discover The ISP is problem! I Changed my ISP so after 5 or 6 time of redialing it's going to connect (sending user/password, getting an IP address, the DNS's IP address, BUT NO MORE). I thinked it's may connected but not and Mozilla can't connect and display any page online. Except my IP address there is no any omen of connecting Internet!!! in disconnecting It shows connecting time. It may connection not completed.
after determining DNS's IP address (in connecting state) the last line in terminal is:
pppd: TYPE
I don't know whether it is connected or not. also gui kppp is useless.
Technically, what is difference between Windows XP and Linux (as my fedora) dialing rolls that windows is able to connect but Linux is not

colorpurple21859 · 09-11-2009, 09:06 PM

what's in your /etc/resolv.conf file, if it's not correct you will connect but can't view webpages

SharpyWarpy · 09-12-2009, 12:54 AM

Yes you should post your wvdial.conf file, minus your REAL password or other sensitive info. I quit using wvdial way back and just use ppp directly, editing appropriate config files like /etc/ppp/options and /etc/ppp/chat-username, but this all hinges on what your ISP does to make your connection work.
What it sounds like to me is the ISP is not getting your user name and password and waits for it until it times out. The busy signal is probably because it retries without adequate time intervals.

lutusp · 09-12-2009, 01:25 AM

Quote:

Originally Posted by siaswar

Here is the output for wvdial:

[ snip ]

These three expressions (Timed out, No Carrier, Line is busy) happen one after another!

Try dialing the ISP's number by hand -- see if a modem tone comes on the line. This is the only way you can be sure the problem isn't with the number, your local telephone service, or your ISP.

If the line is really busy, your ISP has signed up too many customers, this isn't at all uncommon. Make sure you have all available dialup numbers -- contact your ISP to get a complete set. The idea is to set things up to test the numbers in sequence, to avoid the busy-signal problem.

Next, set up to hear the modems negotiating (how to do this differs from modem to modem). Once you've heard a successful modem negotiation you won't forget it -- your ear is a reliable debugging tool for dial-up.

siaswar · 09-12-2009, 03:42 PM

This is my wvdial.conf file which generated by: wvdialconf /etc/wvdial.conf

Code:

[Dialer Defaults]
Modem = /dev/modem
Baud = 460800
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ISDN = 0
Modem Type = Analog Modem
Phone = 9712228
Username = UsErNaMe HeRe
Password = PaSs HeRe

SharpyWarpy · 09-12-2009, 05:41 PM

As colorpurple21859 said, you should also post your /etc/resolv.conf. I've a feeling it's either not there or messed up by dhcp or some other gremlin.

siaswar · 09-14-2009, 08:28 AM

Quote:

Originally Posted by SharpyWarpy

As colorpurple21859 said, you should also post your /etc/resolv.conf. I've a feeling it's either not there or messed up by dhcp or some other gremlin.

Well the /etc/resolv.conf is empty!
There is another file /etc/resolv.conf.back and it is empty too!

GrapefruiTgirl · 09-14-2009, 08:39 AM

Ok, the resolv.conf file should contain the nameserver IP addresses of the usually two nameservers that your ISP uses. If you're using DHCP (which is most likely with a dial-up ISP) then DHCP usually configures resolv.conf automatically.

Since this is not the case, have a look in /etc/ppp or /root/.ppp after being connected. There should be a file in there called *something like* ppp0.info -- I'm not sure what the filename will be, it's been a little while since I used ppp.

If you're not sure which file, then open the /etc/ppp folder in your file browser, and WATCH CLOSELY the files in the folder, while dialing your ISP with the modem. After the connection is established, one of the files in there should either update itself, or a brand new file should appear. The filename should contain the word "info" in it.

Open that file. You should see in there, two lines (or maybe one line with comma-separated values) with the "nameserver" or "dns-server" or something like this. There should be 2 IP addresses.

Copy those addresses into your resolv.conf file, like so:

Code:

#Example resolv.conf file:
nameserver 111.222.333.444
nameserver 123.233.222.222

and save the file resolv.conf.

Now, try using your browser.

If this works, we'll look more closely at WHY your resolv.conf file is not being updated.

Sasha

SharpyWarpy · 09-16-2009, 04:44 PM

Or you can use OpenDNS. Here are two sample lines you can put in your /etc/resolv.conf:
nameserver 208.67.222.222
nameserver 208.67.220.220
Just open /etc/resolv.conf with the "gedit" command (or similar text editor) and put in the above lines. Then try again. You'll have to restart the ppp daemon.