[Pickax4515]

I am currently running Yellowdog 3.1 (an adaption of RH9 for macintosh) on a beige G3. My isp is Access4less. When I fill out all of the information required for connection to the ISP in KPPP and connect it calls the ISP connects but then times out. I get a "Timed out while waiting for PPP" message ever time. Does anyone have any ideas as to why this is happening or how i can fix it? Oh yeah Access4less gives a guide on how to connect via linux but they don't apply to KPPP. The instructions are at access4less.net/Linux.htm

[lynch]

Try this:
Look for a file called resolv.conf in /etc. If it's not there, then create it:

1. Open a console an login as root
2. type touch /etc/resolv.conf

Go back into kppp setup and on the DNS tab choose automatic configuration.
Try to connect.
HTH
lynch

[Pickax4515]

resolv.conf was already there. i touched it, set dns to automatic, connected, and got the same error "Timeout expired while waiting for the PPP interface to come up!". any other advice?

[Pickax4515]

I was reading some other threds and ran accross someone saying that /etc/resolv.conf should have:
search localhoast
nameserver 172.0.0.1
nameserver xxx.xxx.xxx.xxx
nameserver xxx.xxx.xxx.xxx
where the xxx's are my ISP's DNS addies.
Well i was wondering if that was ALL that should be in resolv.conf because mine was completely empty and after i put all of that in the file and tried connecting to no avail. I then tried many variations of connecting and touching resolv.conf and got the same errors.

[lynch]

Originally Posted by Pickax4515

I was reading some other threds and ran accross someone saying that /etc/resolv.conf should have:
search localhoast
nameserver 172.0.0.1
nameserver xxx.xxx.xxx.xxx
nameserver xxx.xxx.xxx.xxx
where the xxx's are my ISP's DNS addies.
Well i was wondering if that was ALL that should be in resolv.conf because mine was completely empty and after i put all of that in the file and tried connecting to no avail. I then tried many variations of connecting and touching resolv.conf and got the same errors.

If you selected automatic configuration in the DNS tab of kppp setup, the resolv.conf file can be empty.kppp will take care of refreshing the listings in resolv.conf.
The localhost line is 127.0.0.1, not 172.0.0.1. And, unless you run a DNS server on your comp you dont need the "nameserver 127.0.0.1" entry.
If you go back into kppp setup>DNS tab and select manual configuration and then enter your isp's DNS addresses in the dialog box, it should find them.
Give that a try.
HTH
lynch

[Pickax4515]

Well i've tried every possible combanation of ip addy config that's been given to me and still i get the same error message. if there are any other random and/or obscure ideas/possabilities that could possibly fix the timeout waiting for ppp to start up error would be welcome.

[codejockey]

OK, just a thought ...

You are using PAP authentication, right? You might also try connecting to access4less directly, and seeing if they require a command to initiate PPP. You may also be able to get some more information from reviewing the logfile.

Hope this helps.

[Pickax4515]

I'd love to try that but I don't know how i would go about connecting to access4less directly. BTW yes it is PAP authentication.

[codejockey]

OK, here's a couple of things to try ...

Since you are using kppp, you can make sure the "show log window" box is checked when you connect to access4less; this will open a separate window that shows the progress of the connection, and may give you a clue.

You can also connect directly from kppp by using kppp->setup->modem->terminal which should open a terminal window where you are connected directly to the modem. Give the command: ATDT <phone number> followed by a carriage return, where <phone number> is the number you normally use to connect to access4less. You should begin dialing access4less.

Once you connect, you will probably be prompted for your username and password, which you should supply interactively, and follow each with a carriage return.

When I tried this, I received the following:

May 29 13:26:47 chumley pppd[885]: By default the remote system is required to authenticate itself
May 29 13:26:47 chumley pppd[885]: (because this system has a default route to the internet)
May 29 13:26:47 chumley pppd[885]: but I couldn't find any suitable secret (password) for it to use to do so.

which suggests my PAP authentication was not set up correctly.

Hope this helps, and feel free to post with additional results/info ...

[Pickax4515]

I tried connecting through terminal. After connecting it waited a second and then returned NO CARRIER. Could this be a server error?

[codejockey]

If your NO CARRIER message is consistent, you've likely found the problem. However, are you certain that you connected? Usually, a NO CARRIER message is given when the calling modem cannot establish a connection with the answering modem. You should have seen at least a CONNECT message if you indeed connected to the remote modem. If you received a CONNECT message and then later received a NO CARRIER message, this indicates that the connection was dropped (but doesn't tell you the reason). For example, when I dial access4less, I receive the following in my log window:

ATZ
OK
ATM1L1
OK
ATS0=0DTXXX-YYYY
CARRIER 45333

PROTOCOL: LAP-M

CONNECT 45333

after which I get the login and password prompts. Do you get this far?

Hope this helps. Additional info appreciated.

[Pickax4515]

The no carrier was after connect

JATZ
OK
ATDT972-354-1008
CONNECT 26400/ARQ/V34/LAPM/V42BIS

NO CARRIER

is what I get. btw the NO CARRIER message comes after a considerable delay.

[codejockey]

OK, here are a couple additional ideas:

Start kppp from the command line (i.e., in a terminal window -- NOT using F2 in KDE and not from the icon). Just type kppp at the command line, and it should open the initial window. Make sure you have the "show logfile" box checked, which should open an additional window that will show you the progress of the login sequence. Try to connect.

Pay particular attention to the messages in the terminal -- i.e., where you stared kppp from the command line. The logfile window probably won't show you much that's new, but the terminal will contain all of the output from kppp that's normally discarded, and you might find a clue there. For reference, the following is the terminal output I received when I connected to access4less to post this:

chumley: 30 /home/codejockey-> kppp
Xlib:  extension "GLX" missing on display ":0.0".
Opener: received SetSecret
Opener: received OpenLock

Opener: received OpenDevice
Opener: received ExecPPPDaemon
In parent: pppd pid 829
Couldn't find interface ppp0: No such device
Kernel supports ppp alright.
Opener: received OpenResolv
Opener: received RemoveSecret
Opener: received RemoveSecret

Hope this helps.

[Pickax4515]

OK after running Kppp from terminal this is what i recieved:

Opener: received SetSecret
Opener: received OpenDevice
Opener: received ExecPPPDaemon
In parent: pppd pid 939
Opener: received OpenResolv
Opener: received OpenResolv
Opener: received OpenResolv
Couldn't find interface ppp0: No such device
Kernel supports ppp alright.
//12 pages // Couldn't find interface ppp0: No such device
Opener: received RemoveSecret
Opener: received RemoveSecret
Opener: received OpenResolv
Opener: received OpenResolv

Something is aparently wrong with the ppp0 interface now what do I do to fix it?

[codejockey]

You might check the permissions on /etc/ppp, /etc/ppp/options and /etc/ppp/resolv.conf. It appears you may not able to open resolv.conf, (just a guess from the output you provided). I don't have access to my Linux system at the moment, but will try to research further when I do.

Hope this helps.